Ohalo tried vibe coding its own CRM. Here’s why it chose Salesforce instead.
The SaaSpocalypse thesis sounds right until you actually try it. David Friedberg, CEO of Ohalo Genetics, tried it. He spent a weekend vibe coding a CRM. Then he signed up for Salesforce.
His admission is the kind of thing most founders won’t say out loud, but probably recognize from experience:
“I always said I think SaaS was this temporary phenomenon between the founding of the Internet and the start of AI. But I think that it’s a little more nuanced than that.”
What came out of the experiment is a practical build vs. buy framework that any lean operator can apply today.
Who Ohalo Is
Ohalo Genetics accelerates crop improvement using proprietary proteins and gene-editing techniques that alter plant reproductive biology. Critically, the company does not introduce foreign DNA. Instead, it restructures how existing genomes are inherited.
Its hybrid breeding system eliminates vegetative propagation by producing uniform seed, which reduces time, cost, and pesticide use. The company is named after an archaeological site on the Sea of Galilee where a 20,000-year-old pot of seeds was discovered, rewriting assumptions about early agriculture and plant breeding.
️ The Vibe Coding Experiment
Friedberg tested the popular idea that AI frontier models could replace enterprise systems of record. He built a CRM prototype over a weekend.
It did not hold up:
“You quickly realize just how much it takes to do maintenance, to do accounts, to do security. There’s just much more to it.”
The failure wasn’t about the AI. It was about scope. Maintenance cycles, security models, access controls, and account structures are years of compounded engineering that a weekend build doesn’t touch.
The Framework: Platform vs. Vertical
Ohalo’s conclusion is a two-bucket model for every software decision.
Bucket 1: Buy the platform
Horizontal tools that every company uses the same way are not where Ohalo creates value. CRM, ERP, communications, messaging. These get bought, not built. The reasoning is direct:
“If everyone else is using Microsoft Excel, I’m not going to go build Microsoft Excel. If everyone else is using an ERP tool, well, we integrate with NetSuite. We’re not going to go build an ERP tool, and we’re not going to go build Slack.”
Ohalo chose Salesforce for CRM and Slack for internal communications. NetSuite handles ERP via a Salesforce integration. These are standard platform selections, made once and then built around.
Bucket 2: Build the vertical
Vertical SaaS is where the calculus flips. Friedberg argues that standardized vertical tools actively destroy competitive advantage because every player in that market ends up doing the same thing the same way. Ohalo dumped all its vertical software and rebuilds those workflows in-house.
The vertical builds Ohalo is doing:
- Custom plant breeding interfaces
- Custom prospecting tools that scan public county databases for farmer planting data, names, and contact information
- Custom product selection interfaces that use satellite and radar imagery to estimate what a farmer’s field will look like next season, then recommend the right product
These interfaces then feed into Salesforce. The transaction record, account settings, access controls, and data storage all stay on the platform.
The Claude and Slack Example
Ohalo built an Ask HR channel inside Slack using Claude. Any employee can ask HR questions that would normally require a call or email to the HR team.
The channel has access to internal HR documents, knows the identity of the person asking, respects access controls for personal information, and covers standard benefits policies. It answers questions without pulling HR staff into the loop.
“I don’t need to go build a communications tool to do that. I can leverage Slack and I can leverage Claude to deliver that internally.”
This is the pattern in practice: custom logic and proprietary data on top of a bought platform, not instead of it.
The Updated SaaSpocalypse Take
Friedberg hasn’t abandoned the thesis entirely. His revised position is more precise:
“I think there’s still a SaaSpocalypse but with a lower case ‘s’ rather than the upper case ‘S’, for verticalized tools where I think AI really allows you to re-build something that’s unique, which creates value for your business in a vertical.”
The horizontal stack survives and arguably gets more valuable as AI capabilities layer on top of it. The vertical stack is fair game for rebuilding from scratch when you can create a genuine competitive edge.
The Replication Playbook
For any operator running a lean software stack, the Ohalo framework collapses to three questions:
- Does every company in my industry use this the same way? If yes, buy it. You won’t out-engineer Salesforce, Slack, or NetSuite on their core function.
- Does this workflow reflect something unique about how my business creates value? If yes, build it. Standardizing your differentiator on off-the-shelf vertical SaaS means your competitors can replicate it by buying the same license.
- Does this custom build connect back to a platform? It should. The custom interface creates the edge. The platform handles the transaction, the record, and the compliance surface.
One procurement implication Friedberg flags: when buying platforms, prioritize integration depth. Whatever you choose has to work with everything else and support the custom workflows you plan to build on top of it.
I’m founder of BizStack at Cagri Sarigoz LLC and a passionate advocate for entrepreneurs.
With over 14 years in tech, marketing, and AI, including my role as Head of SEO at CitizenShipper and co-founder of TaleBot at Intale AI, I’m dedicated to sharing genuine, useful product insights and tips.
At BizStack, I aim to cut through the digital noise to provide clear, actionable advice.
And more than all else, I’m a father to a (always) little girl and a husband.
Contact me at [email protected] for assistance.
