How a GTM Playbook gets built
Genesis of the Framework
Every deep-tech startup we have worked with hits the same wall at roughly the same point. The technology works and early customers have validated it. Then the limits start showing up and the pressure changes shape. The company needs to show scale, not just traction. The founders run out of hours to be in every deal. Sales, marketing and customer success may exist, but are disconnected. Investors seek visibility on the health of the business but nobody can provide it with confidence. And the next round is already on the horizon.
The product was never the problem. What was missing was a self-sustaining system underneath it. QuantWare, QuantrolOx, DigitalOcean. Different technologies, different markets, the same gap at roughly the same stage.
The 021 Playbook Framework is what came out of solving it repeatedly. Not a theory, but a sequence that has been run enough times to know which order the steps go in, and what breaks when you skip one. It draws on almost two decades of building and scaling commercial teams at Salesforce, DigitalOcean, and QuantWare, and on every deep-tech engagement since.
Steps of the Framework
The Playbook has six chapters. They describe what the startup ends up with. The Framework is how those chapters get built, and the order matters more than most teams expect. The Framework has five steps; each one produces something the next step depends on. Skip one and the work downstream gets built on an invalid assumption.
Step 1: Validate PMF
Product-Market Fit (PMF) is where the Framework starts, and it is a deliverable, not a gate.
Most founders believe they have achieved PMF because customers are buying. Sometimes that is true. Often, what they have is a handful of deals the founder closed personally, in markets that do not resemble each other, for reasons nobody has written down. That is traction. It is not yet fit. The work is to break the term into its three parts and answer each one in writing.
Product. What is the offering? What problem does it solve? What do customers use instead today?
Market. Who bought first? Where did they come from? What pain were they actually solving?
Fit. How well does the product match that market? What else is needed to make it whole? What does pricing look like, and what is the competition doing?
The answers come from customer interviews and a working session with the founding team. What comes out is a document the whole company can refer to.
Where the answers do not hold up, that is useful too. It is far cheaper to find an error at this stage than after hiring three salespeople against it.
Deliverable: PMF document covering the product, market, fit, and where the gaps are.
Step 2: Define ICP
The Ideal Customer Profile (ICP) answers one question: which companies are worth spending your limited time on – not only sales and marketing time, but also product development time?
Step 1 tells you who bought and why. Step 2 turns that into a filter. Industry, geography, segment, size, and whatever specific markers matter in your market. For a quantum hardware company that might be lab type, funding source, or which modality they work in. The markers are rarely the generic ones.
Inside the profile sit the personas. Who signs, who evaluates, who blocks. In deep tech these are rarely the same person, and the technical evaluator often carries more weight than the budget holder.
Sometimes the persona leads. If the product is audit software built for CFOs, you know the persona before you know the profile. Work in whichever direction the product leads you.
Everything downstream inherits this. Campaigns, hiring, pricing, the CRM fields. Get it wrong and the team spends a quarter working hard against the wrong list. Get it right and the whole company can say who they sell to without hesitating.
Deliverable: ICP and Persona document.
Step 3: Create GTM Plan
This is the thinking step. Everything so far described the market. This step describes what you are going to do about it. Six things get decided, in this order.
Goals: What are you actually driving at? Pipeline to show traction, revenue against a target, or readiness for the next raise? Break it down into customers and average selling price, then across a timeline. A goal that has not been decomposed is a wish.
GTM motion: How do you reach these customers? Inbound, outbound, events, channel, or some mix. In deep tech the answer is rarely pure inbound, and it is often channel in markets you cannot cover directly.
Marketing mix: The motions determine the marketing strategy and needs. Inbound-leaning means marketing carries the load. Outbound-leaning means the sales team does while marketing supports. Channel means neither, and partner enablement becomes the real work.
Sales process: How does a lead become a customer? What counts as closed? Who does what at each stage?
Customer success: How do customers get value after signing, and where do expansion and referral come from? In a small market, your existing customers are also your best route to the next ones.
People and tools. The motions determine the roles you hire and the stack you need. A CRM is the minimum. Everything else follows from the choices above, not from a software shortlist.
Deliverable: GTM plan, covering goals, motions, processes, people, and tools.
Step 4: Execute
This is where the plan meets the market and the assumptions made are validated or invalidated.
Hire against the roles the plan defined. Set up the stack. Put the rhythm in place: daily activity, weekly review, monthly against target. Break the goal down to the role-level.
The plan is built on assumptions. Which segment responds. What the sales cycle actually runs. Whether the price holds. Whether the channel partner sells or just signs. The job in execution is to test those assumptions fast and cheaply, before the company has committed a year of headcount to them.
Run short experiments first. Two campaigns, not twenty. Learn what works, then scale that rather than scaling everything at once.
Deliverable: Revenue, sales and pipeline growth.
Feedback loop
Steps 3 and 4 do not run in sequence, but in a continuous loop. What the team learns in the field goes back to the plan, and the plan changes how the team executes. Set a rhythm to review both, fortnightly or monthly at first. The same loop feeds into the product team.
“In a startup, everyone is a salesperson.”
From the CEO to the intern, from engineering to customer success, everyone needs to hear the customer’s voice and act accordingly.
Step 5: Make it Visible
By this point, the GTM engine is running. The question the board asks next is how well. This is where the investor-founder disconnect is the most obvious. Most deep-tech startups struggle to provide end-to-end visibility of the health of the startup. Deals live in the founder’s head, marketing reports on activity nobody connects to revenue, and finance sees the number only once the invoice goes out. Everyone has a partial view and nobody has the whole one.
Lead-to-cash visibility closes that gap. One view across the full cycle, from the first touch to the cash landing:
- What is the current revenue, forecast, sales and pipeline
- What was sold against what was billed and collected
- Where leads come from and which sources actually convert
- How long the cycle takes, and where deals stall
- Which customers expand, and which quietly do not
This is not reporting for its own sake. It is what lets the startup and investor get in sync, and it is what turns the next raise into a conversation about evidence rather than ambition.
Deliverable: Lead-to-cash reporting.
The Framework is not the Playbook
The framework is exactly that – a framework. It is not your playbook. Each company is unique and needs its own. What the Framework does is guide the process of building it.
That process is where we work. We write the playbook, install it, and run it alongside your team until it works without us.