Discover your motion
Founder-led, pre-PMF. Your job is discovery and documentation, not scale. Understand who you're selling to, choose the right motion, and land your first customers before you build a team around you.
This blueprint builds a behavioral Ideal Customer Profile through at least ten switching-moment interviews, not a demographic guess. Findings go into a four-dimension canvas covering firmographics, trigger event, pain intensity, and behavioral signals. The ICP then gets revisited on a fixed cadence as new conversations and closed deals come in.
PLG or sales-led? The answer isn't a preference - it's determined by your ACV, your buyer persona, your product's self-serve potential, and your market. Getting this wrong early means building the wrong team, hiring the wrong first rep, and burning runway on a motion that can't compound. This blueprint walks through the decision framework used by operators who've run both - including the European context where PLG adoption lags the US and the conditions that change the calculation.
Warm intros are politeness-biased. Inbound is too slow. At pre-PMF, outbound is the only motion that gives you the honest signal you need - because non-friendly parties won't pretend to be interested. Are you running structured outbound as a calibration exercise, or are you hoping referrals and inbound will get you to 20 customers? This blueprint covers the Clay-powered founder outbound system built for €0–€1M ARR - designed for a list of 300, not 3,000.
The first 10 customers are not a revenue milestone - they are a research programme. The goal is to close them, then document exactly why they bought, what problem they had before, and what would make them leave. Most founders treat early customers as wins to celebrate rather than data to extract. Do you have a documented picture of why your first 10 customers said yes - and what that tells you about the next 100? This blueprint builds that extraction and documentation system.
Hiring a VP of Sales before two AEs are hitting quota is one of the most common and expensive mistakes in early-stage SaaS. Hiring the wrong AE profile - someone from a big company with scaffolding - is the second. Do you know the exact profile you're hiring for, what their ramp should look like, and what success looks like in the first 90 days? This blueprint covers the hiring framework, compensation structure, ramp expectations, and the signals that tell you whether the problem is your rep or your process.
Scale beyond yourself
Systematise what's working. Build a sales motion that runs without you on every call. If you started PLG, this is where you layer in sales on top of product signal.
Most founders don't realise they've become the bottleneck until the pipeline stalls. Every deal needs your context, your credibility, or your calendar. Are you the only person in your company who can explain why your last five deals closed? This blueprint gives you the diagnostic and the 30-day plan to remove yourself from the critical path - without conversion dropping.
Hiring your first AE is one thing. Getting them to close without you is another. Most first hires spend 90 days on context that was never written down, running discovery that doesn't qualify, losing deals that should have been won. Do you have a structured path from hire date to first unaided close - or are you hoping they figure it out? This blueprint builds that path, adapted to the way you sell.
Outbound run manually doesn't scale. Without a repeatable system, your team sends generic sequences that get ignored - or spends hours on personalisation that isn't tracked or compounded. If your best SDR left tomorrow, would the outbound motion keep running? This blueprint builds the Clay-powered engine that answers yes - tuned to your ICP, your market, and your current team capacity.
Every successful PLG company eventually layers sales - the question is when and how. PQL-to-paid conversion runs at 10%+ versus 2–4% for cold outbound, which means your first sales hire in a PLG motion should always sell into product signal, never bolt on classical outbound from day one. Are you routing product usage signals to the right person at the right time - or is your self-serve funnel and your sales team operating as two separate pipelines? This blueprint builds the bridge between them.
Most founders add channel partnerships before their direct motion is repeatable - which means there's nothing for a partner to replicate. The result is a long list of signed agreements and no incremental revenue. Before entering Scale 02, you need to know whether you're actually ready to scale through others. Are you a category leader or strong challenger? Do you have a dedicated partnerships owner? Can you give partners a reason to prioritise you? This blueprint gives you the honest readiness scorecard before you invest in channel.
A VP of Sales hired too early destroys the motion you've built. Hired too late, and the team stalls without leadership. Most founders make this hire based on gut feel and a strong interview - not on a clear picture of what the role requires at their exact stage. Do you know the difference between a VP who can build versus one who can only run? Do you have the scorecard to tell them apart before you make the offer? This blueprint covers the full hiring framework adapted to your current ARR and org structure.
Build the internal machine
Build the internal infrastructure - leadership, compensation, reporting - before adding channel complexity. A revenue operator system your investors can trust starts here.
Compensation design is strategy. The wrong structure creates the wrong behaviour - reps who chase deal size over retention, AEs who avoid difficult accounts, or commission cliffs that cause attrition at exactly the wrong moment. Is your current comp plan driving the behaviours that compound revenue, or the ones that look good in a single quarter? This blueprint builds the compensation architecture for an AE team at €5M–€10M ARR, including quota-setting, accelerators, clawback provisions, and the base/variable split that aligns with your growth model.
Most founders approach channel reactively - signing agreements with the wrong partners, offering margin without structure, measuring nothing. The result is a long list of NDAs and no incremental revenue. Do you have a written profile of what a good partner looks like at your stage - and a reason why they should prioritise you over the ten other vendors in their portfolio? This blueprint builds the partner identification system and commercial structure that generates the first five revenue-generating deals.
Investors and board members aren't just reading your numbers - they're reading your ability to understand your numbers. A team that arrives at a board meeting with a single ARR figure and no supporting data on pipeline health, cohort behaviour, or leading indicators loses credibility fast. Can you explain in five minutes exactly where your revenue came from last quarter, what drove it, and what you expect next quarter? This blueprint builds the reporting infrastructure that makes that conversation confident and consistent.
At €5M ARR, the org design question isn't just who reports to whom - it's what handoffs exist between marketing, sales, CS, and partnerships, and where revenue gets lost in the gaps. Most GTM breakdowns at this stage aren't hiring problems; they're structural problems that hiring makes worse. Do you have clarity on where each euro of pipeline is owned, and who is accountable for each stage of the customer journey? This blueprint maps the right org structure for your motion and builds the handoff architecture that prevents leakage.
Scale the revenue you've won
New logo growth is only half the story. These blueprints help you protect, expand, and monetise the revenue you've already earned - turning your CS function into a revenue engine that investors can model.
Most churn is visible long before it happens - in product usage data, support tickets, and the absence of executive engagement. The problem is that without a signal model, these indicators reach the wrong person too late or not at all. Could you name your five highest-risk accounts right now and point to the data that told you? This blueprint builds the early warning system, adapted to your product signals and CS team structure.
QBRs structured around what happened last quarter don't generate expansion revenue. When the conversation looks backwards, commercial opportunities stay invisible and CSMs stay order-takers. Does your QBR process reliably produce an expansion conversation - or does it produce a satisfaction score? This blueprint redesigns the format around revenue, built to work with your existing accounts and CS motion.
Gross and net revenue retention are the numbers Series B investors look at first. Most teams arrive at a board meeting with a single NRR figure and no supporting data on the cohort behaviour behind it - which creates more questions than it answers. Can you explain to an investor, in under five minutes, exactly where your NRR comes from and what will move it next quarter? This blueprint builds the reporting system that makes that conversation straightforward.
Expansion revenue doesn't come from asking at the right time - it comes from knowing when the right time is before the customer does. Without a signal model, CSMs rely on gut feel and annual renewal conversations. Do you know which product actions, hiring events, or business milestones correlate with accounts that expand - and are those signals routed to anyone? This blueprint maps your expansion triggers and builds the response system around them.
Joint webinars are one of the most underused channel acceleration tools. Most are run ad hoc, attract the wrong audience, and end without a follow-up that converts attendance into pipeline. Are you creating joint pipeline with your partners - or just co-authoring content that disappears after the event? This blueprint turns the webinar format into a repeatable pipeline source, adapted to your partner mix and audience.
For founders whose product can acquire and activate users before a human gets involved. Covers the full arc from motion selection through PQL conversion to the enterprise layer - with operator context on where PLG works in Europe and where it doesn't.
PLG is not a strategy choice - it's a product and market reality. Only about 23–25% of SaaS companies have a product that genuinely supports a self-serve motion, and Europe skews further sales-led at early ARR due to lower self-serve culture in DACH and France. Is your product capable of delivering enough value before a human gets involved - or are you using PLG as a reason to avoid building a sales motion? This diagnostic tells you honestly which side of the line you're on.
A Product Qualified Lead is not a user who signed up - it's a user who has experienced enough value that a sales conversation has a meaningful chance of converting. PQL-to-paid conversion runs at 10%+ versus 2–4% for cold outbound, but only if you're calling the right users at the right moment. Can you define, right now, what a PQL looks like in your product - the exact usage events, frequency, and depth that predict conversion? This blueprint builds that definition and the scoring model that feeds your sales team.
Free-to-paid conversion in PLG is rarely a pricing problem - it's an activation problem. Most free users never reach the moment where the product's value is undeniable, which means they never feel the pull to upgrade. What is the single action in your product that, when a user completes it, predicts conversion at 3x the baseline rate? This blueprint identifies your activation moment, maps the friction between signup and that moment, and builds the in-product and outbound interventions that move users through it.
Every successful PLG company eventually layers sales - Figma hired their first sales rep at €1M ARR, Datadog layered enterprise after their Series D, Slack grew to €2B with enterprise sales built on top of the PLG core. The question isn't whether to add sales, it's when and how. Are your self-serve funnel and your sales team operating as two separate pipelines - or is product signal actively feeding your AEs with accounts who are already halfway to yes? This blueprint builds the PQL routing, sales process, and compensation model that bridges both motions.
The enterprise motion in a PLG company is different from classical enterprise sales. Your best AEs are evangelists of the product with a quota - not hunters from SAP or Oracle. The deal starts in the product, not in a cold email. But enterprise deals still need procurement, security reviews, executive sponsors, and MSAs. Do you have a motion that uses bottom-up product adoption to create top-down enterprise deals - or are your two go-to-market segments competing with each other for the same accounts? This blueprint designs the enterprise layer that sits on top of your PLG core.
A dedicated track for founders ready to build a channel that generates material revenue. Runs alongside Scale 02–03 once your direct motion is solid and your first partners are signed. Covers the full partner lifecycle from profile to profitability.
Most channel programs fail not because of poor enablement - but because the wrong partners were signed in the first place. A reseller with no access to your buyer, a systems integrator without your use case in their practice, or a tech partner whose customers don't overlap with yours will never generate revenue regardless of how good your kit is. Do you have a written definition of what a good partner looks like - firmographic, motion-based, and incentive-aligned - that your team can use to qualify before you invest? This blueprint builds the IPP framework from your existing customer and prospect data.
Channel economics only work if both sides make money. VAR margins run 20–30%, reseller margins 5–10%, and tech alliance economics look entirely different again. Before you invest enablement time and a partnership manager's attention in a specific partner, can you model the expected revenue contribution versus the cost to enable and support them? This blueprint builds the partner profitability model - covering sourced versus influenced pipeline, conversion assumptions, enablement cost, and the revenue threshold that justifies tier investment.
Partners who can't explain your product won't sell it. Most enablement programmes take months to build and are outdated before they're used. The bar is lower than you think - most competitors are sending PDFs and hoping for follow-through. Could a partner AE give a confident, accurate demo after four hours of preparation? This blueprint produces the modular kit that makes that possible - structured to your product and partner type, built to be maintained without a dedicated channel team.
Without a structured review cadence, channel relationships go quiet after signing. Partners deprioritise vendors who don't measure them. Do you have a consistent way to hold partners accountable to a number - and have the conversation when performance falls short? This blueprint builds the quarterly review model that keeps partners generating pipeline, not just consuming attention. Includes the scorecard, talk track, and the pipeline commitment process that creates a shared number both sides are accountable to.
Co-selling is the highest-trust, highest-conversion partner motion - and the most difficult to operationalise. It requires your AEs and partner AEs to work the same deal together without stepping on each other, with clear rules on sourcing, influence, commission, and escalation. Do you have a co-sell motion that your internal team and your partner AEs can follow without ambiguity - or does every joint deal become a negotiation about who owns what? This blueprint builds the co-sell rules of engagement, deal registration process, and joint pipeline tracking system.
For founders building revenue through hyperscalers and complementary software vendors rather than through resellers and systems integrators. Runs alongside the Partner Sales Growth Track for companies whose product sits naturally inside a cloud marketplace or a category leader's ecosystem. Covers the full motion from marketplace listing through co-sell to joint go-to-market with Independent Software Vendors (ISVs).
AWS Marketplace, Azure Marketplace, and Google Cloud Marketplace let a customer buy your product against a cloud commitment they've already made, instead of opening a new procurement process. That single mechanic can turn a six-month security review into a private offer signed in weeks. Is your product listed, and does your pricing model actually work against a customer's committed cloud spend, or is the listing sitting unused while deals still route through a separate purchase order? This blueprint builds the listing strategy, private offer structure, and the internal process for treating marketplace as a real channel, not a checkbox.
Cloud provider co-sell programs, AWS's ISV Accelerate, Microsoft's Co-sell IP program, Google Cloud Partner Advantage, put a hyperscaler's own sales force to work alongside yours on shared accounts. The programs are free to join and mostly ignored: most vendors register a handful of opportunities and never build the account mapping or seller relationships that make the channel produce pipeline. Do you have a systematic process for identifying overlap accounts, briefing hyperscaler sellers, and tracking sourced versus influenced deals, or is co-sell a line on a partnerships slide with no pipeline behind it? This blueprint builds the account mapping process, seller engagement cadence, and the deal registration discipline that turns program membership into closed revenue.
Independent Software Vendor (ISV) partnerships work through a different mechanic than reseller or hyperscaler channels: the value is a technical integration that makes both products stickier, not a sales referral. A listing on Salesforce AppExchange, HubSpot's App Marketplace, or a direct API integration with a category leader in your customers' stack extends your reach without a partner sales team in between. Does your integration solve a problem the ISV's own roadmap hasn't addressed, and is it built to survive their next platform update, or is it a one-off connector nobody maintains? This blueprint builds the integration prioritization framework, the technical partnership agreement, and the marketplace listing that turns the integration into a lead source.
An integration without a joint go-to-market motion behind it is a feature, not a partnership. The vendors that generate real pipeline from ISV relationships build shared content, co-branded launches, and a bundled offer that gives both sales teams a reason to bring the other into a deal. Crossbeam's 2023 State of Partnerships report found deals with a partner overlap close 46% faster and at a 53% higher rate than deals without one, but only if both sides actually know the overlap exists before the deal is won. Do your reps have a way to see which accounts your ISV partners are already in, or does the overlap only surface after the deal has closed one way or the other? This blueprint builds the co-marketing calendar, the bundled offer structure, and the account overlap process that puts the integration to work.
This blueprint builds a behavioral Ideal Customer Profile through at least ten switching-moment interviews, not a demographic guess. Findings go into a four-dimension canvas covering firmographics, trigger event, pain intensity, and behavioral signals. The ICP then gets revisited on a fixed cadence as new conversations and closed deals come in.
PLG or sales-led? The answer isn't a preference - it's determined by your ACV, your buyer persona, your product's self-serve potential, and your market. Getting this wrong early means building the wrong team, hiring the wrong first rep, and burning runway on a motion that can't compound. This blueprint walks through the decision framework used by operators who've run both - including the European context where PLG adoption lags the US.
Every successful PLG company eventually layers sales. PQL-to-paid conversion runs at 10%+ versus 2–4% for cold outbound, which means your first sales hire in a PLG motion should always sell into product signal, never bolt on classical outbound from day one. Are you routing product usage signals to the right person at the right time - or are your self-serve funnel and sales team two separate pipelines? This blueprint builds the bridge.
PLG is not a strategy choice - it's a product and market reality. Only about 23–25% of SaaS companies have a product that genuinely supports a self-serve motion, and Europe skews further sales-led at early ARR. Is your product capable of delivering enough value before a human gets involved - or are you using PLG as a reason to avoid building a sales motion? This diagnostic tells you honestly which side of the line you're on.
A Product Qualified Lead is not a user who signed up - it's a user who has experienced enough value that a sales conversation has a meaningful chance of converting. PQL-to-paid conversion runs at 10%+ versus 2–4% for cold outbound, but only if you're calling the right users at the right moment. Can you define what a PQL looks like in your product right now? This blueprint builds that definition and the scoring model that feeds your sales team.
Free-to-paid conversion in PLG is rarely a pricing problem - it's an activation problem. Most free users never reach the moment where the product's value is undeniable. What is the single action in your product that, when a user completes it, predicts conversion at 3x the baseline rate? This blueprint identifies your activation moment and builds the interventions that move users through it.
Every successful PLG company eventually layers sales. Figma, Datadog, Slack all ran this play. The question is when and how. Are your self-serve funnel and your sales team operating as two separate pipelines - or is product signal actively feeding your AEs with accounts already halfway to yes? This blueprint builds the PQL routing, sales process, and compensation model that bridges both motions.
The enterprise motion in a PLG company is different from classical enterprise sales. Your best AEs are evangelists of the product with a quota - not hunters from SAP or Oracle. Do you have a motion that uses bottom-up product adoption to create top-down enterprise deals - or are your two segments competing for the same accounts? This blueprint designs the enterprise layer that sits on top of your PLG core.
Warm intros are politeness-biased. Inbound is too slow. At pre-PMF, outbound is the only motion that gives you honest signal - because non-friendly parties won't pretend to be interested. Are you running structured outbound as a calibration exercise, or hoping referrals will get you to 20 customers? This blueprint covers the Clay-powered founder outbound system built for €0–€1M ARR - designed for a list of 300, not 3,000.
The first 10 customers are not a revenue milestone - they are a research programme. The goal is to close them, then document exactly why they bought, what problem they had before, and what would make them leave. Do you have a documented picture of why your first 10 customers said yes - and what that tells you about the next 100? This blueprint builds that extraction and documentation system.
Outbound run manually doesn't scale. Without a repeatable system, your team sends generic sequences that get ignored - or spends hours on personalisation that isn't tracked or compounded. If your best SDR left tomorrow, would the outbound motion keep running? This blueprint builds the Clay-powered engine that answers yes - tuned to your ICP, your market, and your current team capacity.
Joint webinars are one of the most underused channel acceleration tools. Most are run ad hoc, attract the wrong audience, and end without a follow-up that converts attendance into pipeline. Are you creating joint pipeline with your partners - or just co-authoring content that disappears? This blueprint turns the webinar format into a repeatable pipeline source, adapted to your partner mix and audience.
Hiring a VP of Sales before two AEs are hitting quota is one of the most common and expensive mistakes in early-stage SaaS. Do you know the exact profile you're hiring for, what their ramp should look like, and what success looks like in the first 90 days? This blueprint covers the hiring framework, compensation structure, and the signals that tell you whether the problem is your rep or your process.
Most founders don't realise they've become the bottleneck until the pipeline stalls. Every deal needs your context, your credibility, or your calendar. Are you the only person who can explain why your last five deals closed? This blueprint gives you the diagnostic and the 30-day plan to remove yourself from the critical path - without conversion dropping.
Hiring your first AE is one thing. Getting them to close without you is another. Do you have a structured path from hire date to first unaided close - or are you hoping they figure it out? This blueprint builds that path, adapted to the way you sell.
A VP of Sales hired too early destroys the motion you've built. Hired too late, and the team stalls without leadership. Do you have the scorecard to tell a VP who can build from one who can only run - before you make the offer? This blueprint covers the full hiring framework adapted to your current ARR and org structure.
Compensation design is strategy. The wrong structure creates the wrong behaviour - reps who chase deal size over retention, AEs who avoid difficult accounts, commission cliffs that cause attrition at exactly the wrong moment. Is your comp plan driving the behaviours that compound revenue, or the ones that look good in a single quarter? This blueprint builds the compensation architecture for an AE team at €5M–€10M ARR.
At €5M ARR, the org design question isn't just who reports to whom - it's where revenue gets lost in handoffs between marketing, sales, CS, and partnerships. Do you have clarity on where each euro of pipeline is owned, and who is accountable for each stage? This blueprint maps the right structure for your motion and builds the handoff architecture that prevents leakage.
Most founders add channel partnerships before their direct motion is repeatable. Before entering Scale 02, you need to know whether you're actually ready. Are you a category leader or strong challenger? Do you have a dedicated partnerships owner? Can you give partners a reason to prioritise you? This blueprint gives you the honest readiness scorecard before you invest in channel.
Most founders approach channel reactively - signing the wrong partners, offering margin without structure, measuring nothing. Do you have a written profile of what a good partner looks like at your stage - and a reason why they should prioritise you over ten other vendors? This blueprint builds the identification system and commercial structure that generates the first five revenue-generating deals.
Most channel programs fail because the wrong partners were signed in the first place. A reseller with no access to your buyer will never generate revenue regardless of how good your kit is. Do you have a written definition of what a good partner looks like that your team can use to qualify before you invest? This blueprint builds the IPP framework from your existing customer and prospect data.
Channel economics only work if both sides make money. Before you invest enablement time and a partnership manager's attention, can you model the expected revenue contribution versus the cost to enable and support? This blueprint builds the partner profitability model covering sourced versus influenced pipeline, conversion assumptions, enablement cost, and the revenue threshold that justifies tier investment.
Partners who can't explain your product won't sell it. Could a partner AE give a confident, accurate demo after four hours of preparation? This blueprint produces the modular kit that makes that possible - structured to your product and partner type, built to be maintained without a dedicated channel team.
Without a structured review cadence, channel relationships go quiet after signing. Do you have a consistent way to hold partners accountable to a number - and have the conversation when performance falls short? This blueprint builds the quarterly review model that keeps partners generating pipeline, not just consuming attention.
Co-selling is the highest-trust, highest-conversion partner motion - and the most difficult to operationalise. Do you have a co-sell motion that your internal team and partner AEs can follow without ambiguity - or does every joint deal become a negotiation about who owns what? This blueprint builds the rules of engagement, deal registration process, and joint pipeline tracking system.
AWS, Azure, and Google Cloud Marketplace let a customer buy against a cloud commitment they've already made, turning a six-month security review into a private offer signed in weeks. Is your product listed, and does your pricing model actually work against committed cloud spend, or is the listing sitting unused? This blueprint builds the listing strategy, private offer structure, and the process for treating marketplace as a real channel.
AWS ISV Accelerate, Microsoft Co-sell IP, and Google Cloud Partner Advantage put a hyperscaler's own sales force to work on shared accounts, free to join and mostly ignored. Do you have a systematic process for mapping overlap accounts and briefing hyperscaler sellers, or is co-sell a line on a slide with no pipeline behind it? This blueprint builds the account mapping process and deal registration discipline that turns program membership into revenue.
Independent Software Vendor (ISV) partnerships run on technical integration, not sales referral. A listing on Salesforce AppExchange, HubSpot's App Marketplace, or a direct API integration extends your reach without a partner sales team in between. Does your integration solve a problem the ISV's own roadmap hasn't addressed, or is it a one-off connector nobody maintains? This blueprint builds the prioritization framework, partnership agreement, and marketplace listing that turns the integration into a lead source.
An integration without a joint go-to-market motion behind it is a feature, not a partnership. Crossbeam's 2023 State of Partnerships report found deals with a partner overlap close 46% faster and at a 53% higher rate, but only if both sides know the overlap exists before the deal is won. Do your reps have a way to see which accounts your ISV partners are already in? This blueprint builds the co-marketing calendar, bundled offer structure, and account overlap process that puts the integration to work.
Investors aren't just reading your numbers - they're reading your ability to understand your numbers. Can you explain in five minutes exactly where your revenue came from last quarter, what drove it, and what you expect next quarter? This blueprint builds the reporting infrastructure that makes that conversation confident and consistent.
Most churn is visible long before it happens - in product usage data, support tickets, and the absence of executive engagement. Could you name your five highest-risk accounts right now and point to the data that told you? This blueprint builds the early warning system, adapted to your product signals and CS team structure.
QBRs structured around what happened last quarter don't generate expansion revenue. Does your QBR process reliably produce an expansion conversation - or does it produce a satisfaction score? This blueprint redesigns the format around revenue, built to work with your existing accounts and CS motion.
Gross and net revenue retention are the numbers Series B investors look at first. Can you explain to an investor, in under five minutes, exactly where your NRR comes from and what will move it next quarter? This blueprint builds the reporting system that makes that conversation straightforward.
Expansion revenue doesn't come from asking at the right time - it comes from knowing when the right time is before the customer does. Do you know which product actions, hiring events, or business milestones correlate with accounts that expand - and are those signals routed to anyone? This blueprint maps your expansion triggers and builds the response system around them.