My point was more that it seems this wave of AI is more profitable if you're in B2B vs. B2C.
6,844 karma · joined March 18, 2013
My point was more that it seems this wave of AI is more profitable if you're in B2B vs. B2C.
1. OpenAI bet largely on consumer. Consumers have mostly rejected AI. And in a lot of cases even hate it (can't go on TikTok or Reddit without people calling something slop, or hating on AI generated content). Anthropic on the other hand went all in on B2B and coding. That seems to be the much better market to be in.
2. Sam Altman is profoundly unlikable.
I pay Slack $50k/year. They have no reason to shut me off.
> or there is some new Slack policy that prevents it
Prevents what exactly? The new API pricing they introduced doesn't apply to internal apps. I suppose they could apply it to internal apps. We'd have to figure out a path around it
> or they increase their pricing by 1000%
1000% increase in pricing seems incredibly unlikely. That would not only disrupt thousands of companies but would likely kill Slack entirely
---
> Haven’t you basically built your entire business on this singular proprietary platform they you have almost no control over?
Not really. We service clients through Slack. Could we switch? Sure. Would it be a pain? Yeah. Would it be costly? Yeah.
But there's also no reason to switch. And if a new platform comes out (like the one this thread is about), I would expect them to have the features to compete with Slack if they are posiitioning themselves as a Slack competitor
I wouldn't wish Teams on my worst enemy, so in that regard, I love Slack
The thing I struggle with the most is how I'd move all of our core functionality from Slack. A lot of the people/teams that build these "Slack killers" I don't think have ever run Slack at scale
How are you going to replace the 30+ in-house apps I've built that automate 50+ workflows?
How are you going to replace the 100+ workflows I use with 1,000+ clients when they have to submit a ticket, or questionnaire, or a security event?
How are you going to replace the 100+ partner channels I have where we send out automated messages about specials and discounts we're running?
What about the 500+ other apps I run that integrate with our systems? Are they going to support your new platform?
Do you have retention settings? DLP? How granular can I go on permissions? What about picking up events via the API so I can train people in real time on what not to do in public channels?
I have no affinity or personal ties to Slack. But if you're going to position yourself as a Slack competitor you have to actually do what Slack does
As someone who has hired hundreds of SWEs over the last 12 years from 20+ states, I have to disagree.
$150k is on the lower end for base for a Sr. SWE, and well below the total comp someone would expect. You can make the argument that $150k base is reasonable, but even Sr. SWE in the middle of the country are looking for closer to $180k -$200k OTE.
The symptom of wanting to give up is because you aren't growing fast enough
The symptom of founder turmoil is because whatever strategy you're currently using isn't growing the company fast enough
The symptom of running out of money is because you're not hitting your sales targets
- It's autonomous
- It learns (not retraining, but true learning)
- By definition some semblance of consciousness must arise
This is why I think we're very far from anything close to this. Easily multiple decades if not far longer.
- scan cloud configurations for policy violations - detect and remediate infrastructure misconfigurations - real-time visibility into cloud resource inventories - early detection of issues - container vuln. scanning - runtime anomalous behavior - alerts and correlate security events - compliance mappings - id risky permissions in IAM policies - track changes and configuration drift over time - implement zero-trust policies across microservices - eforce network seg in containerized environments - run security checks during build and deploy stages - vulnerability assessments on running VMs and containers - policy-as-code for consistent security standards
To answer your question. Google doesn't acquire Wis because Google can’t build a comparable product themselves. The real driver is that Wiz has already achieved market penetration and trust. Replicating that from scratch would be a massive undertaking, requiring not just a sophisticated product but also the brand credibility, customer relationships, and reputation for reliability. establishing that level of traction and trust is difficult, time-consuming, and expensive. I highly doubt Google would try to build a direct competitor from the ground up when acquiring Wiz allows them to leverage its existing success right away.
Mighty always sounded like a bad idea. But when I saw PG really making a big deal about it I followed Suhail on twitter because I just had to see what PG was going on about. From what was posted online it sounded like the company was super successful and growing, and I still didn't get it. And then it went under, without any fanfare. Just poof.
- $90k bill - you pay your annual $10k deductible - the remaining $80k is only covered 80% because emergency visits only have 80% co insurance - you now owe $16k, after you've already paid $10k out of pocket for the deductible
This is a real thing that happened to me recently. Not to mention I pay $1500/month for a family of 4.
Nothing, absolutely nothing about the U.S. healthcare pricing structure is good for patients.
It seems to have worked out for you because you appear to have very good insurance. Most people are like me, and have the type of insurance that should be illegal.