Summary of Selling an AI SaaS Platform After 200 Buyers Called It Crazy

Overview of Selling an AI SaaS Platform After 200 Buyers Called It Crazy

This episode features David, founder of Revo, discussing how he built an AI-native, vertically integrated go-to-market platform that aims to replace much of a company’s sales stack. He explains why the company stayed in stealth for two years, how he approached product-building before revenue, and why he initially lost early sales conversations by trying to sell the full platform too aggressively. The conversation centers on contrarian startup strategy, founder-led sales, trust-based branding, and the tradeoffs of building a broad platform versus a point solution.

What Revo Does

Revo (“Revenue Evolution”) is designed to improve and eventually unify the tools used across the go-to-market motion:

• CRM and data layer
• Prospecting and enrichment
• Deal progression and closing workflows
• Forecasting and reporting
• Manager coaching and enablement

David frames Revo as an AI-native, vertically integrated go-to-market platform that can replace multiple point tools or be adopted in smaller slices, depending on the customer.

Core product thesis

Revo is built on a shared:

• data architecture
• semantic layer
• memory layer
• workflow layer
• agentic layer

The long-term vision is for the platform to self-improve based on customer needs, reducing reliance on custom services and manual product requests.

Founder Story and Why He Built It

David is an engineer, introvert, and serial founder. Revo is his fifth startup. His path into the problem came from firsthand pain running go-to-market at OpenStore, where he realized how difficult it was to stitch together Salesforce, HubSpot, prospecting tools, and reporting systems.

Key origin insight

He saw that:

• GTM teams were forced to use too many disconnected tools
• data lived in silos
• the “source of truth” often wasn’t trustworthy
• onboarding and implementation were painfully slow

That experience pushed him to build the platform he wished existed.

Stealth, Build Strategy, and Early Traction

Revo stayed in stealth for roughly two years while the team built the core architecture. David says this was necessary because the company was not a simple point solution—it was closer to building “20 companies in one.”

Why stealth made sense

• The product required breadth across many GTM workflows
• The team wanted strong architecture before exposing the market to the product
• They used internal domain expertise and operator input to shape the build
• They wanted paying customers before treating feedback as “real”

Traction highlights

• First paying customer: mid-January
• Revenue: millions in ARR
• Growth: hundreds of customers
• Team: expanded from 14 founding team members to about 105–110 employees
• Marketing spend: zero dollars on paid marketing
• Funding: about $80M publicly announced

The Early Sales Mistake

One of the biggest lessons in the episode is that David initially made the mistake of trying to sell the platform exactly as it was architected: as a full-stack replacement.

What went wrong

He and the team approached the market saying, in effect:

• replace your entire Salesforce stack
• switch your whole revenue motion to Revo
• adopt the full platform up front

That message created major resistance:

• early prospects thought the idea was too ambitious
• many mid-market buyers were unwilling to rip out existing systems
• early validation from smaller startups was misleading because they had less infrastructure and fewer switching costs

The result

For about a year, he describes the experience as “darkness” because the company kept getting pushback and had very low win rates.

The Aha Moment: Dogmatic on Product, Flexible on Sales

The breakthrough came when David realized he could stay committed to the architecture but become much more flexible commercially.

New commercial strategy

Instead of insisting on a full replacement, Revo can now be sold a la carte:

• power dialer replacement
• sequencing replacement
• enrichment/prospecting layer
• AI-native CRM
• forecasting/reporting workflows

This let the company meet customers where they are rather than forcing a total platform migration.

Why this works

Customers can now start with the highest-value workflow first, then expand over time.

ICP and Market Positioning

Revo’s core ICP is the mid-market, though the company also serves segments on either side of it.

Segment behavior David sees

SMB / early-stage startups

• Often still searching for ICP and product-market fit
• More willing to use external vendors for outbound or discovery
• Can create false validation because they adopt quickly but churn more easily

Enterprise with technical sophistication

• Interested in AI pilots
• Often want to absorb the learning and build in-house later
• Riskier for durable revenue because IP can get “copied” internally

Enterprise without deep technical sophistication

• More durable use case
• More likely to adopt and retain if value is clear

Mid-market

• Best balance of urgency, scale, and openness to change
• Revo’s sweet spot

Founder-Led Sales, Trust, and Brand

David is candid that he is not naturally a great seller. He’s introverted and prefers factual, trust-based conversations over hype.

His philosophy on selling

• Don’t oversell what the product can’t do
• Don’t create a gap between promise and delivery
• Trust compounds through consistency over time

He wants Revo to be known not by his résumé, but by reliability:

• “the most trusted AI-native go-to-market platform”
• a company that delivers quickly and consistently

Advice and Notable Insights

1. Don’t outsource critical discovery too early

David warns founders not to hand off core ICP discovery to outside vendors too soon.

Why: if you don’t learn your customer yourself, you can build the wrong thing and create a self-fulfilling churn cycle.

2. Avoid “false validation”

A startup saying yes to your product is not always true market fit if the customer has weak retention, low switching costs, or no real buying discipline.

3. Build for the future, but sell for the present

You can have a long-term platform vision while still offering smaller entry points to reduce buying friction.

4. Don’t confuse flexibility with fragmentation

Revo’s a la carte model exists, but the company still focuses on a few high-value “golden workflows,” not an overwhelming menu of options.

Lightning Round Takeaways

Best business advice

• CEO = “current executive officer”
• Reminder to stay grounded and avoid ego until the company is truly real

Recommended book

• Man’s Search for Meaning by Viktor Frankl

Best money spent

• Longevity / biohacking
• He believes maintaining cognitive and physical peak is a business advantage for founders

Favorite productivity habit

• Canceling recurring one-on-ones
• He prefers organic communication over rigid standing meetings

Passion outside work

• He says he doesn’t really separate work from life
• Revo is his all-consuming focus

Final Takeaways

• Revo is betting that AI will enable a broad, deeply integrated GTM platform rather than another narrow point solution.
• David’s biggest lesson was not architectural—it was commercial: be rigid about the product vision, but flexible in how you land customers.
• The company’s early “all-in” sales pitch hurt conversion, but the newer a la carte approach gives prospects a practical on-ramp.
• The episode is especially valuable for founders building in crowded categories, where trust, timing, and positioning matter as much as product quality.

Contact and Product Info

• Product: Revo
• Website: revo.ai
• Contact: David at revo.ai