Playbook
The first-90-days GTM playbook for seed-stage founders.
What an embedded revenue operator actually does in the first ninety days — and why the goal is never the deals you close, but the system you leave behind.
TODDYANCEY.COM
A fractional revenue leader who spends ninety days personally closing deals has done the founder a favor. One who spends ninety days building a motion the founder’s next ten hires can run has done the company a favor. Only the second one compounds.
Seed-stage founders bring in an operator when the thing that got them to their first customers — conviction, relationships, and the founder’s own calendar — stops scaling. The instinct is to ask that operator to go sell. The better mandate is to ask them to build the system that makes selling repeatable. Here is the playbook I run.
The mandate: leave a system, not a streak
The first conversation with a founder is about expectations. A good quarter of bookings is satisfying and forgettable; a documented, teachable revenue motion is an asset that shows up in the next board deck and the next raise. I set the success metric up front: by day ninety, a competent new hire should be able to inherit this motion and run it without me. Everything below serves that one outcome.
Days 1–14: diagnose before you prescribe
Every founder believes they know why deals win and lose. The data usually disagrees. I start with win/loss interviews across recent closed and lost deals, a teardown of current pricing and discounting, and an honest audit of the pipeline — how much of it is real, how much is wishful, and how much only moves when the founder personally intervenes.
Out of that comes the first scored ideal-customer profile: not a persona slide, but a ranked definition of who you win, who you lose, and which signals predict each. Almost every early pipeline is carrying accounts that will never close. Naming them is the fastest revenue win available, because it frees the team to spend its hours where they convert.
Days 15–45: install qualification first
Before stages, before a CRM cleanup, before a single new outbound sequence — qualification. I install MEDDIC/MEDDPICC as the discipline that runs underneath every deal: the metrics that matter to the buyer, the economic buyer who signs, the decision process and criteria, the paper process, the identified pain, the champion, and the competition. Qualification is what turns a hopeful forecast into a reliable one, because it forces every deal to earn its place in the number.
With qualification in place, the pipeline architecture follows naturally: stages defined by buyer behavior rather than seller optimism, each with explicit exit criteria, plus coverage targets tied to the plan. Now “pipeline” is a word that means something specific to everyone who uses it.
Days 30–60: build a forecast people trust
A forecast is a promise the company makes to its board and its bank account. I build the model — weighted by stage and qualification, not by hope — and pair it with the operating cadence that keeps it honest: a weekly revenue meeting where every committed deal is inspected against its qualification, and every slip has a named reason and a next step. Forecast accuracy is a habit, not a spreadsheet, and the habit is the deliverable.
Days 45–75: open channels only after the core works
Founders are tempted to bolt on partnerships early because partner pipeline feels like free pipeline. It isn’t — an alliance motion grafted onto a broken direct motion just multiplies the chaos. Once the direct engine converts predictably, I open the first partner, marketplace, and channel relationships that genuinely add reach: hyperscaler marketplaces, strategic ISVs, and the few alliances that match your ICP. Sequencing is the whole game here.
Days 75–90: the handoff
The engagement ends well when the founder no longer needs me. That means hiring against a scorecard rather than a résumé, a comp plan aligned to the motion, and a first revenue hire onboarded onto a system that already runs. The test is simple: take the operator out of the room and watch whether the number still moves. If it does, the foundation is real.
The one principle underneath all of it
Build to be replaceable. The founder-led phase ends the day the company stops depending on any single person to make revenue happen — including the operator who built the system. That’s the work: not a streak of closed deals, but a commercial foundation that compounds long after the engagement is over.
The same playbook, run live
FluidCloud: idea to a running company
At FluidCloud I built the founding ICP, customer-discovery framework, and MEDDIC discipline — the first repeatable playbook the company could hire against — and installed the KPI-driven revenue cadence that improved forecast accuracy and pipeline velocity across an enterprise Infrastructure-as-Code platform. This playbook isn’t theory. It’s the build, written down.
Building the foundation for your next stage?
Todd Yancey · Fractional CRO
I embed with seed-stage founders and build the commercial foundation — ICP, motion, pricing, pipeline, forecast, and the first repeatable playbook — then hand off a system that runs without me.
TODDYANCEY.COM