Enterprise sales strategy

I worked with a sales advisor named Max Gilbert through most of 2024. His main intervention was simple. Stop explaining the product. Start naming the exact moment the buyer's workflow breaks.

That sounds obvious. It is not. Most enterprise software founders, myself included, default to explaining what the product does. Max retrained me to explain what breaks without it. The difference sounds subtle. In practice it changed how I write outbound, how I run discovery calls, and how I follow up.

The first rule I internalized: ground every message in the buyer's own words. Pull the transcript from the last call. Use their language, not ours. "Risk register" becomes "issues list." "Automated extraction" becomes "reads every document." Speak in native M&A terms. IC-ready. Workstream. If the buyer has to translate your jargon into their own vocabulary, you have already lost.

The second rule: stop writing one story for everyone. I pushed back on a generic funding-stage deck and redirected to three persona-specific decks. Corp dev teams care about IC-ready outputs and workstream speed. PE firms care about finding deal risks and deal-breakers early. Transaction advisors care about fitting into an existing client workflow without creating friction. One deck for all three is lazy and it does not work.

Wedge selling became the most reliable pattern. Instead of asking someone to buy software, I offer to rerun a past deal as a backtest. With CLEAResult (Vista portfolio), we proposed a 455-file historical backtest. With Nordson it was rerunning a past deal called "Spartan." With Zeta Global it was the same shape. The idea is simple: prove value inside their actual workflow before asking them to change how they work. Low commitment, verifiable accuracy, no live-deal risk.

I also learned to sequence features deliberately. For the Sikich pilot, I built an 8-day email cadence that spaced features to avoid overlap. Gap analysis and entity risk screening did not land until Day 8, after the prospect had already absorbed the basics. Showing everything at once overwhelms. Showing too little loses momentum. Pacing matters.

In mature accounts the question is rarely whether no tools exist. It is whether we fit alongside the systems already there. At Duane Morris, Harvey was already deployed. At Husch Blackwell, Legora was firm-wide. In both cases I positioned Colabra as complementary. SOC 2 Type 2, an Outputs disclaimer, AI subprocessor authorization, and a data loss liability cap turned out to be part of go-to-market, not overhead. Without that procurement language, enterprise deals stall at legal review and never come back.

I developed strict cold outreach rules. Under 100 words. Cause-and-effect pain structure. Pain framed as "finding deal risks and deal-breakers," not logistical tracking. Drop "I'm Aoi" in the first message. Never use "asks to see the source" in PE follow-ups. Every outreach message runs through the same framework, built on the 30 Minutes to President's Club five-stage methodology: Problem Agreement, Solution Agreement, Power Agreement, Commercial Agreement, Vendor Approval. Tier 1 ICP is mid-market corp dev teams doing 3 or more deals per year, 150-plus document data rooms, $40-80K ACV.