Discovery first. Player-coach second. Team last.
A three-property model for crossing the chasm from founder-led selling to a repeatable revenue engine — refined across 25 years of B2B SaaS GTM.
Customer discovery first.
The first thirty days of any engagement are spent in interviews — with the last twenty buyers who said yes, the last twenty who said no, and the last twenty who never answered.
Win/loss analysis is not a deck. It's a discipline. Out of that work comes a refined ICP, a sharpened positioning statement, and a list of trigger events that actually drive enterprise urgency.
Only then is it time to build outbound. Hiring an SDR before this work is done produces motion without conversion — pipeline that looks busy but doesn't close.
Player-coach, not advisor.
The next sixty days are spent in the work. I personally run discovery calls. I sit in the demos. I walk procurement through redlines. I write the security review responses.
The founder watches, participates where it matters, and reclaims the calendar capacity needed to focus on product.
By the end of the sprint, the founder has seen the motion run — they know exactly what "good" looks like and they can recognize it in the next hire. This is the part that separates fractional CRO work from advisory work.
Founders don't need another voice telling them what to do. They need someone who will pick up the phone, run discovery on the next ten accounts, sit through the security review, and close the deal.
Build the system. Then build the team.
Hiring an AE before the playbook exists is a guaranteed failure. The AE will improvise, the founder will be frustrated, and the AE will leave inside six months.
Build the playbook first. Document it. Test it. Only then — typically around month four — hire the first AE, and onboard them into a system that produces predictable results.
The transition from founder-led selling to scalable selling is not an event. It is a sequence.
The founder-to-CEO transition.
There is a quiet thing that happens around the time a startup crosses two or three million in revenue. The founder, who has been the entire revenue engine for two years, has to learn how to stop being it.
This is harder than it sounds. Most technical founders are conflict-averse with their early teams — they are grateful, they want to be liked, they hate the idea of being seen as the boss who criticizes. So they avoid the deal reviews. They sit in pipeline meetings and ask gentle questions instead of hard ones.
Part of the work I do is coaching that transition. Not coaching the AE — coaching the founder. How to run a deal review that actually advances deals. How to deliver hard feedback without breaking trust. When to fire and when to coach. How to read pipeline rhythm so a thirty-day forecast is actually a forecast and not a wish.
This work doesn't show up in any pitch deck, but it is the difference between a founder who scales into a CEO and a founder who plateaus at five million in revenue and never recovers.
Writing worth your time.
The thinking behind the work — frameworks and field notes from 25+ years building enterprise revenue.
Framework
The Seven C’s of Selling
A deal-dynamics model for enterprise sales — the seven forces that decide whether a complex deal closes, and when. Read →
Essay
Founders Don’t Fail on Product
Why most Seed–Series B startups stall on the chasm between founder-led selling and a repeatable revenue motion. Read →
Read the full thinking.
The approach above is the operating model. The full article — Founders Don't Fail on Product — walks through why most fractional GTM hires fail and what to look for instead.
Read the article →