The Anthropic team looks to be eating all the usecases and application layer. I personally know of many figma + AI startups that are going to feel shaken up with this launch.
Anthropic has distribution on their side, their engineers are excellent (I have ran with them across the ggb in the past and they work 12 hours plus a day regularly.)
I think what actually might be slowing them down is the public releases and pr lol, not ideas or execution
"Hot" companies with stupid managers often have such workdays.
In the case of engineers and programmers, the amount of useful completed "work" has only a very weak correlation with the length of the workdays.
Good engineers or programmers will think anyway most of the time about the problems that they must currently solve, regardless whether they are in the office or at home or in any other place, and regardless whether to an external observer they appear to be "working" or they appear to do nothing.
Programmers who spend all day typing lines of code into a computer, are more likely to not be competent programmers, because otherwise they would have found ways to automate such activities that require continuous physical involvement, making impossible the allocation of enough time for thinking about the right solution.
If whatever they do does not require true thinking, then that is the kind of job that can be done by AI agents.
> their engineers are excellent... they work 12 hours plus a day regularly
What? In my experience people who are good at their job can get it done in a reasonable amount of time. Working 12 hours a day is obsession, no competence. There can be overlap, but there is no causation.
Looks amazing. I've been trying different stacking PR tools and Graphite and this looks to be the most human-centric so far. I'll have a shot at using this within our team soon. Congrats on the launch!
Nice vision, "alternative frontends" is something really useful for horizontal SaaS. We do this for over 2000 customers, from field workers to CEOs of public companies, and it's so satisfying to hear the great feedback when they tell me that they finally have software perfectly adapted to their workflows.
If attention-span was shot with social-media, it has no chance in the age of AI. All these deep tech-tools potentially have tons of value, but if it doesn't make sense in 5 seconds, very hard to compete.
Nice post and I agree that making software with really simple UX for last mile cases is the solution to the SaaS-pocalypse and is something new that was not possible before AI.
I'm solving this from the other side of the equation: we work directly with the SaaS vendors to make vibe coding embedded into their platform. Working with some Series B companies right now, 2000 business users are now able to build any feature they want, within the guardrails of the SaaS vendor. (More info in profile if anyone wants to chat)
I don't have a horse in this race, but this seems the right way to me. As a developer, I do already inject custom scripts to provide extra functionality / automation on SaaS I use where APIs are not available or limited.
However, the thought of the non-technical users I work with doing that is scary, they have no idea if the code the LLM writes is correct, is it going to have a bug that causes a massive issue down the line?
I've seen fat finger errors cause financial loss, but at least in those cases the user always had a chance to realise their error and fix it, with something like this how would you even know?
ty! any CEOs or product people at SaaS companies that come to mind to reach out to? I've been trying to get this in front of more people, so far they're always mind blown when they see how the product works
Regarding etymology, for many centuries the substances that are now called "sulfides" were called "pyrites", after the "iron pyrite" i.e. the iron (II) disulfide, which is the most abundant sulfide mineral.
At the end of the 18th century, Lavoisier together with a few other French chemists have created the modern systematic chemical nomenclature, so the old term "pyrite" was replaced by "sulfide" (like also "vitriol" was replaced with "sulfate").
For who does not know, "pyrite" comes from "fire", i.e. from the pronunciation in Ancient Greek of the corresponding word that was cognate with English "fire" (Ancient Greek or Latin "p" corresponds with English "f").
Striking pyrite produces sparks, which can be used to start a fire.
> Ancient Greek or Latin "p" corresponds with English "f"
Similarly, ancient Greek "p" corresponds with modern Greek "f", and ancient Greek "b" corresponds with modern Greek "v".
We may have done it first, but the sound change is pretty common. "B" -> "v" is arguably in process in Spanish. Something similar had already happened in Latin; compare Latin "frater" to English "brother" or Latin "fero" to Greek "phero".
I love when this comes up and also I see it play out in my life, where my GF prefers fast fashion whereas I buy something from brands I like and I wear it for long (some of the clothes in my wardrobe have been there for 12+ years.. I feel old.)
Also Sir Terry Pratchett is a gem of an author and you should read all of his books. I have read through maybe 25% of Discworld and it's the funniest fantasy series ever.
“Yes, yes,” said Bethan, sitting down glumly. “I know you don’t. Rincewind, all the shops have been smashed open, there was a whole bunch of people across the street helping themselves to musical instruments, can you believe that?”
“Yeah,” said Rincewind, picking up a knife and testing its blade thoughtfully. “Luters, I expect.”
I do the same (wear clothing for a long time) but I only buy the cheap stuff. I bought 1 replacement shirt in the last 5 years and 1 bag of replacement socks in the same time frame.
He definitely grew significantly as a writer over time, and I would agree that some of his early work isn't particularly strong (The Light Fantastic, for example, is relatively bog-standard comic fantasy without any of the depth his later work showed).
If you start reading at the very beginning of the Discworld, you're slogging through the weaker stuff, and it's easy to get discouraged. A smoother path is to pick one of the defined sub-series (the guards are very popular, but my vote goes to the witches) and start along just that track; you'll get to the strong stuff much faster.
My advice has always been to start with Small Gods. It is a standalone book that references but does not rely on any others, and is far enough into his career that it’s fair to say that if you don’t like it, you won’t like his work in general.
Nice article Ben! I think the HN crowd would be more familiar by calling those "Entities" but I like the new perspective of all companies only handling two or three of them really well.
I think there is more nuance about it for the SaaS-pocalypse though. I have been talking to hundreds of B2B companies and customers are now vibe coding solutions when they need something that the platform doesn't support: a dashboard, a workflow, or an integration.
And once a B2B customer gets a taste of vibe coding... then it's just a matter of time before they start to think about replacing the entire SaaS completely. I have seen this play over and over again so many times in the last few months, it's honestly shocking.
I am working to find solutions to the SaaSpocalypse but don't want to derail from the main topic, there's more info in my profile if this has been something you're thinking about!
Something I'm really good at is ending my articles with half-baked ideas :) so thank you for challenging it
Regarding "entities", totally understand. I like to write in ways that my mom would understand- not the HN community. In fact, I have a post called "Everything is a Spreadsheet", where I explicitly defined that Entity<->Noun relationship. Should have linked it!
Back to the Saaspocalypse... my startup is reckoning with this like all others. My next blog post will be titled "What's Preventing Me from Building Your App in a Weekend?". The ultimate "what's your moat" question. I think every SaaS should be forced to answer this on their marketing site. Thinking aloud, I'm considering good answers companies can say to this question... I think a perfectly legitimate answer is still "our prompts are better than your prompts". There are some companies where I simply believe the founders/engineers when they say they understand the problem better than I, because they've explored it more deeply. This is kinda what I was hinting at at the end... softwares that go mega-vertical in one or two nouns accrue more subject matter expertise than I ever will. Thus, that gives me more reason to trust their infrastructure, their configurations, and their prompts. This is not new but rather an extension of what created the SaaS economy in the first place.
I will definitely check out your profile- thank you for the thoughtful reply!
Domain specific knowledge has been the moat for a long time, hasn't it? Outsourcing isn't new. Maybe you can do in a weekend for $500 what would have taken a month and $20k before, but code itself isn't a barrier to competition - even really good code.
On the other hand, much of the code I write is in an industry where training and operations manuals are closely guarded corporate secrets that make up the recipe or soul of a company. The job of the SWE is to deeply understand the processes and procedures that employees follow, and to write code that helps facilitate those and then gets out of the way. A lot of it comes from walking around and seeing how people are actually using the software and what works, and what's a pain point. I've always maintained that the value is in the operations manuals, and the code is just a logical extension of that. But that's where SaaS usually is insufficient because regardless how versatile and broad it is, it doesn't usually encapsulate enough domain knowledge, let alone the proprietary stuff.
Anthropic has distribution on their side, their engineers are excellent (I have ran with them across the ggb in the past and they work 12 hours plus a day regularly.)
I think what actually might be slowing them down is the public releases and pr lol, not ideas or execution
reply