Book a Call → mycocoon.life
Go-To-Market Cohort · 2026

6 weeks. The strategy, and the machine that runs it.

Most GTM training stops at the strategy deck. Most automation training skips why any of it matters. This does both: three weeks deciding where revenue comes from, then three weeks building the data, automation and AI systems that actually deliver it — the GTM engineering discipline that has quietly become the most in-demand role in revenue teams.

6 Weeks
Two halves, one system
18 Modules
Strategy then execution
20 Max
Per cohort
1 Live System
Running when you leave
2

disciplines, taught as one. GTM strategy without execution is a deck. GTM engineering without strategy is expensive automation pointed at the wrong people.

18

modules across market definition, channel economics, pricing, launch, the GTM data stack, AI-assisted outbound, workflow automation, attribution and forecasting.

1

working GTM system you built yourself — CRM data model, enrichment, signals, an automated workflow and a dashboard that reports on it. Live, not a mockup.

Decide where revenue comes from.
Then build the thing that gets it.

Go-to-market is two jobs that are usually held by two people who do not talk. The strategist picks the segment, the channel and the price. The operator wires up the CRM, the enrichment, the sequences and the reporting. When those two are disconnected, you get beautifully argued plans that nothing executes, and heavily automated motions aimed at people who were never going to buy.

This programme deliberately puts both in the same head. By week six you will have a GTM plan you can defend to a board and a running system that executes part of it — because you built it in the room.

For whoever owns the number.

Founders, revenue leaders, marketers and the increasingly common person whose job is to make the revenue stack actually work.

Right For You If this is your problem

  • You are a founder doing GTM yourself and guessing at most of it
  • You lead sales or marketing and your pipeline maths does not hold up
  • You are in RevOps and want the strategy context behind the systems you run
  • You want to move into GTM engineering — a role that barely existed three years ago
  • Your outbound works less every quarter and you do not know which part broke
  • You have tools stacked on tools and no single source of truth

Not A Fit If this sounds like you

  • You want a list of growth hacks
  • You want to send high-volume cold email and do not care about consent or deliverability
  • You will not touch a CRM, a spreadsheet or a workflow builder
  • You want strategy only, and would skip the build weeks
  • You have no product and no market to take it to

A plan on one page.
A system that runs.

Three artefacts from the strategy half, three from the engineering half. All built on your own business.

01
Your GTM Plan, One Page

Motion, ICP, channels, pricing and the revenue maths behind them. Short enough to be read by a board and specific enough to be argued with.

02
An ICP & Segmentation Model

Who you sell to, who you deliberately do not, and the observable signals that tell the two apart in your data rather than in your head.

03
Channel Economics You Can Defend

CAC by channel, payback period, LTV:CAC and the honest sensitivity analysis underneath — including which assumptions are guesses.

04
A Working GTM Data Stack

CRM object model, enrichment, signal capture and deduplication, configured on your own data. The unglamorous foundation everything else fails without.

05
An Automated Workflow You Built

A live pipeline from signal to research to personalised outreach to CRM record — built to be compliant and deliverable, not just clever.

06
A Reporting & Forecast Layer

Attribution that admits its own limits, pipeline hygiene rules, and a forecast you would be willing to be held to next quarter.

AI made outbound cheap.
That is exactly the problem.

Anyone can now generate ten thousand personalised emails before lunch, and buyers have noticed. The advantage has moved from volume to judgement: better targeting, real signals, genuine research, and restraint.

What we teach: using AI to research accounts properly before you contact anyone, to enrich and score against real signals, to draft outreach that references something true, and to build internal tools that used to need an engineer.

What we will not teach: scraping people who never consented, evading spam filters, mass-sending to bought lists, or any tactic whose only defence is that it has not been caught yet. We cover consent, GDPR and PDPA obligations, and deliverability as a first-class subject — partly because it is right, and mostly because the alternative destroys your domain and your pipeline within a quarter.

6 weeks. 18 modules.
Strategy, then the build.

Weeks 1–3 decide what should happen. Weeks 4–6 build the system that makes it happen. You need both halves; that is the entire point.

Part One · Market & ICP

Theme: almost every failed GTM traces back to a market decision made casually in week one. We make it deliberately.

W1 / Session A
Choosing Your GTM Motion
Sales-led, product-led, community-led, partner-led
  • What each motion demands of price point, sales cycle and org structure
  • Why copying a motion from a company with different economics fails
  • Hybrid motions, and the specific ways they go wrong
  • Matching motion to your actual contract value and buying committee
Capstone

A written motion decision for your business, with the economics that justify it and what you are giving up.

W1 / Session B
Operational ICP & Market Sizing
An ICP you can run as a query
  • Turning a written ICP into observable attributes that exist in your data
  • Disqualifying criteria as filters, not as a paragraph nobody applies
  • TAM / SAM / SOM built bottom-up, and how to spot a top-down fantasy
  • Testing your ICP against closed-won and closed-lost, and being wrong in public
The qualitative side — Jobs to Be Done interviews, personas, objections — is Product Marketing, Week 1. This session turns that into something a database can answer.
Capstone

An ICP definition expressed as filters you could actually run against a database.

W1 / Session C
Value Proposition & Buying Committee
Who signs, who blocks, who has to live with it
  • Mapping the buying committee: champion, economic buyer, blocker, end user
  • The different value each of them needs to hear
  • Compelling events — what makes a deal urgent instead of pleasant
  • Why deals stall at "no decision" more often than at a competitor
Capstone

A buying-committee map with the value argument and likely objection for each role.

Part One · Motion & Channels

Theme: channels are an economic decision before they are a creative one. This week is mostly arithmetic, and it is the arithmetic most teams avoid.

W2 / Session A
Channel Selection & Economics
CAC, payback, and what you can actually afford
  • Building a channel model: volume, conversion, cost, cycle length
  • CAC by channel, payback period, LTV:CAC and where each misleads
  • Which channels compound and which stop the moment you stop paying
  • Sequencing channels instead of running six badly at once
Capstone

A channel model for your business with named assumptions and a sensitivity check on the shakiest one.

W2 / Session B
Price Point & the Revenue Model
What your price permits you to do
  • How price point dictates the motion you are allowed to run — and kills the ones you cannot fund
  • Contract value against cost to serve: where a motion quietly stops working
  • Land-and-expand economics, and modelling expansion revenue honestly
  • Building the revenue model that the rest of the plan has to satisfy
Setting the price itself — value metric, tiering and willingness-to-pay research — is taught in depth in Product Marketing, Week 3. Here we take a price as given and test whether the motion can carry it.
Capstone

A revenue model for your chosen motion, showing the price point at which it stops being viable.

W2 / Session C
Funnel & Lifecycle Design
Including everything after the signature
  • Stage definitions with exit criteria that two people would apply identically
  • The post-sale half: onboarding, adoption, renewal, expansion
  • Where revenue actually leaks, and how to find it in your own numbers
  • Lifecycle triggers that are worth automating later
Capstone

A full funnel and lifecycle map with stage definitions and the current drop-off at each.

Part One · Launch & Revenue Plan

Theme: turning three weeks of decisions into one page somebody would fund, and a sales motion that can carry it.

W3 / Session A
Market Entry
New geography, new segment, new motion
  • Entering a market you have no history in — what transfers and what does not
  • Beachhead selection, and resisting the urge to enter three markets at once
  • Local proof: references, partners and regulatory reality in a new region
  • Entry economics: the cost of the first ten customers versus the next hundred
Launch mechanics — tiering, readiness gates, cross-functional plans and internal launch — are Product Marketing, Week 3. This session is about choosing which market to enter at all.
Capstone

A market entry case for one new segment or geography, with entry economics and a beachhead named.

W3 / Session B
Designing the Sales Motion
Qualification, stages and forecast hygiene
  • Qualification frameworks — MEDDPICC, BANT and when each is overkill
  • Designing a repeatable discovery call for your buying committee
  • Pipeline hygiene rules that make a forecast mean something
  • Handoffs between marketing, sales and success without dropped context
Capstone

A sales motion document: stages, exit criteria, qualification standard and handoff rules.

W3 / Session C
The One-Page GTM Plan
Everything so far, made defensible
  • Assembling motion, ICP, channels, pricing and funnel into a single page
  • The revenue model beneath it, and which inputs it is most sensitive to
  • Presenting to a sceptical board or investor without hand-waving
  • Naming your riskiest assumption out loud, before someone else does
Capstone

Your one-page GTM plan, presented and stress-tested by the cohort.

Part Two · The GTM Data Stack

Theme: the boring half that everything else stands on. Bad data does not produce slightly worse automation — it produces confidently wrong automation at scale.

W4 / Session A
CRM as the Source of Truth
Object model, hygiene, and the discipline to keep it
  • Designing an object model that survives contact with a real sales team
  • Required fields, picklists and validation — the unglamorous saviours
  • Auditing an existing CRM and triaging what is salvageable
  • Why every reporting problem is usually a data-entry problem
Capstone

A documented CRM data model plus an audit of your current one with a remediation list.

W4 / Session B
Enrichment, Signals & Intent
Knowing who is worth a human's time
  • Enrichment sources, what they genuinely know, and where they invent
  • Signals that actually predict a buying window — and vanity signals that do not
  • Scoring models built from closed-won data rather than intuition
  • Cost control: enrich on trigger, not on everything
Capstone

An enrichment and scoring design, implemented against a real sample of your accounts.

W4 / Session C
Identity, Dedupe & Data Governance
One company, one record, one truth
  • Identity resolution across domains, subsidiaries and free-mail signups
  • Deduplication and merge rules that do not destroy history
  • Consent capture, retention periods and lawful basis under GDPR and PDPA
  • Building a system you could show an auditor without flinching
Capstone

Dedupe and identity rules, plus a consent and retention policy for your GTM data.

Part Two · Automation & AI Execution

Theme: the build weeks. You will leave each session with something running, not a diagram of something that could run.

W5 / Session A
Workflow Automation
Wiring the stack together
  • Automation platforms compared — where each stops being the right tool
  • Event-driven design: triggers, branching, retries and idempotency
  • Error handling and alerting, so silent failure does not cost you a quarter
  • Documenting a workflow so a colleague can maintain it
Capstone

A live automation: signal in, enriched and routed, CRM updated, team notified.

W5 / Session B
AI-Assisted Outbound That Is Not Spam
Research first, volume last
  • The research layer: what to gather before a human or model writes anything
  • Personalisation that references something true and checkable
  • Deliverability as engineering — authentication, domain strategy, warmup, volume discipline
  • Consent, suppression lists and honouring opt-outs properly
Capstone

A research-to-outreach pipeline for twenty real accounts, with a deliverability and consent checklist applied.

W5 / Session C
Building Internal GTM Tools
The part that used to need an engineer
  • Small internal tools: account research briefs, territory views, QBR generators
  • Using AI coding assistants to build things you could not have built last year
  • When to buy, when to build, and when to leave it as a spreadsheet
  • Security basics: where API keys live, and who can see customer data
Capstone

One working internal tool that removes a recurring manual job from your week.

Part Two · Measurement & Scale

Theme: making the system legible to the people who fund it — and honest about what it cannot prove.

W6 / Session A
Attribution Without Fiction
Measuring what you can, admitting the rest
  • First touch, last touch, multi-touch — what each quietly hides
  • Self-reported attribution, and why it often beats the tracking
  • Incrementality thinking and simple holdout tests you can genuinely run
  • Reporting uncertainty in a way that increases trust rather than losing the argument
Capstone

An attribution approach for your business, with its blind spots written down explicitly.

W6 / Session B
RevOps: Forecasting & Hygiene
A number you would stake your quarter on
  • Forecast methods and the failure mode of each
  • Pipeline coverage, velocity, stage conversion and slippage
  • Territory, quota and capacity planning at small-company scale
  • The weekly operating rhythm that keeps data trustworthy
Capstone

A forecast model and dashboard driven by your live pipeline data.

W6 / Session C
Capstone: The System, End to End
Plan and machine, presented together
  • Connecting the one-page plan to the system that executes it
  • Demonstrating your running workflow to the cohort
  • A ninety-day roadmap for what you build next
  • Structured critique from trainers and peers
Capstone

Your complete GTM system: strategy on one page, working automation demonstrated live, and a ninety-day plan.

Six weeks. Two disciplines.
One system that runs.

Longer than our other cohorts because it covers two jobs. You need both, and separating them is the reason most GTM fails.

What's included

Live instruction, every template, and build time with someone experienced looking over your shoulder.

  • 6 live weekly sessions with practitionersPeople who have owned a revenue number and built the systems underneath it.
  • Every template and reference buildChannel model, GTM plan, CRM data model, scoring design, workflow blueprints and dashboards.
  • Build support in the engineering weeksHands-on help while you wire your own stack — the difference between understanding it and having it.
  • All session recordingsYours permanently. Useful precisely when you hit the problem months later.
  • Community accessCohort channel and alumni network of people running comparable stacks.
  • Certificate of completionCocoon Go-To-Market. Issued on the capstone system, not on attendance.

What this is not

A growth-hacking course — there are no tricks in here
A tool tutorial — tools change; the design principles are the point
Strategy only. If you would skip the build weeks, this is the wrong programme
Permission to spam — consent, deliverability and data protection are taught as requirements
An accredited qualification — it is a practitioner programme, and we say so plainly
Next cohort
Forming now
Maximum 20 participants. Bring a real business and access to its CRM.
Apply Now →

Taught by practitioners.
Not theorists.

"We have both written the GTM plan and been the person at midnight working out why the automation stopped writing to the CRM. Teaching them apart is how you end up with strategists who cannot ship and operators who cannot explain why any of it matters."
— Cocoon Trainers
Cocoon Go-To-Market · 2026

A plan nobody executes is a document.
Build the machine too.

Six weeks: three deciding where revenue comes from, three building the data, automation and AI systems that go and get it.

Join the Next Cohort → Book a Discovery Call →
18 hands-on modules Max 20 participants Strategy + engineering A live system you built