gtm-strategist
Use this skill when the question is which motion, which channels and which layer of the stack to fix first, rather than what to say to anybody - "audit our GTM stack", "we are spending on tools and getting nothing", "should we go outbound or inbound", "where do we put the next 5k", "pipeline is flat and nobody can tell me why", "what do we fix first", "do we hire a rep or buy a tool", "we have 14 tools and I think we are paying twice for the same thing", "we are launching in a new market, what is the motion". Reads the current tool list, channel results, budget and team size, then produces a layer-by-layer audit score, a named primary motion with the reasoning, a channel mix matched to deal size and team capacity, a budget split, and a fix-first order. It recommends and never purchases. NOT the definition of who to target, which is the icp-modeller skill and an input this one assumes you already have. NOT writing the messages once the motion is chosen, which is outbound-copywriter.
Workflowsio · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Workflowsio/company-os-starter-kit --skill gtm-strategistAbout this skill
name: gtm-strategist description: | Use this skill when the question is which motion, which channels and which layer of the stack to fix first, rather than what to say to anybody - "audit our GTM stack", "we are spending on tools and getting nothing", "should we go outbound or inbound", "where do we put the next 5k", "pipeline is flat and nobody can tell me why", "what do we fix first", "do we hire a rep or buy a tool", "we have 14 tools and I think we are paying twice for the same thing", "we are launching in a new market, what is the motion". Reads the current tool list, channel results, budget and team size, then produces a layer-by-layer audit score, a named primary motion with the reasoning, a channel mix matched to deal size and team capacity, a budget split, and a fix-first order. It recommends and never purchases. NOT the definition of who to target, which is the icp-modeller skill and an input this one assumes you already have. NOT writing the messages once the motion is chosen, which is outbound-copywriter.
GTM strategist
When this applies
The problem is structural rather than verbal. A motion is being designed from scratch, an existing stack is being audited for gaps and overlap, budget is being allocated across channels, or pipeline is flat while activity is high and nobody can name which layer is broken.
Maturity: the five-layer model, the motion designs and the fix-first order come from real GTM builds. The budget bands and channel costs are the ranges we have seen and they will differ in your market. Treat them as a starting point you replace with your own numbers, and date any number you replace.
What it produces
- A five-layer audit with a yes or no on each check and a score out of 18.
- One named primary motion, with the reasoning and the second motion to add later.
- A channel mix matched to deal size, buyer, universe size, team capacity and timeline.
- A budget split by stage, and guardrails on tool spend.
- A fix-first order, which is the part that actually changes what happens on Monday.
- A stated exclusion list: what this audit did not look at.
Fill these in
{{STAGE}}- pre-revenue, early traction, scaling, or established{{DEAL_SIZE}}- the average contract value, because it decides the whole channel mix{{GTM_HEADCOUNT}}- how many people are actually on this, including part-timers{{BUDGET_OWNER}}- who signs off on spend, which is who any recommendation is written for{{CURRENT_STACK}}- every tool in use today, including the ones nobody logs into
First run: the customization interview
Run this as a one-time setup step, outside any live engagement, and never mid-run. It edits files, and editing a skill or its reference material while it is being used against real work is how a run half-follows two versions of its own instructions. Company-level answers belong in these files; anything specific to one account or one person belongs in clients/<slug>/ or company-wiki/, not in a reference file every account's run reads.
Read before you ask. Pull the tool list from billing rather than from memory, because the tools nobody remembers are usually the finding. Pull channel results from the CRM and the sequencer. Present what you found, then ask what the data cannot tell you, one question at a time.
Basics
- What do you sell and to whom, with the typical deal size?
- How many people are on go-to-market, counting fractional and part-time honestly?
- What is the current monthly spend across tools, ads and dedicated headcount?
- What stage are you at?
Current state 5. Which channel produces most of your pipeline today? 6. What is the biggest bottleneck right now: not enough leads, low conversion, bad data, or no process? 7. What have you already tried that did not work? This one prevents recommending it again.
Goals 8. What does success look like in 90 days, as a number? 9. Are you fixing something broken or building something new?
Write the answers into the audit document, and the placeholders into this file. Never recommend a stack or a motion without the current state, because a pre-revenue founder and a company with three reps need different playbooks and the same advice given to both is wrong for at least one.
Reference routing
| File | What it contains | When to read it | What breaks if you skip it |
|---|---|---|---|
references/stack-layers.md | The five layers with the job, components, what good and bad look like, plus the 30-minute audit checklist and its scoring bands | At steps 1 and 2, before any recommendation | You recommend a tool for a layer that is not the broken one, which is the most expensive mistake in this skill |
references/motions-and-channels.md | Four motions with their flows, risks and second-motion timing, the motion comparison, the channel matrix and the five channel questions | At steps 3 and 4 | The motion gets picked by preference rather than by deal size and team capacity, and the channel mix gets spread across four channels at once |
references/budget-and-metrics.md | The 70/20/10 split, budget by stage, tool guardrails, leading and lagging metrics with thresholds, acquisition-cost benchmarks and the pipeline velocity formula | At step 5, and whenever somebody asks whether a number is good | The plan has no numbers attached, so nothing can be judged and nothing gets cut |
references/tool-categories.md | What each category has to do, the selection criteria, example tools per category, and the questions to ask a vendor | Only once the layer that needs fixing is known | You buy tools to fix a strategy problem, which is the single most common failure in this whole skill |
Step 1 - Audit the five layers
A modern GTM stack has five layers, each with one job, and they build on each other. You cannot fix a sequencing problem while the data layer is broken, and money spent on the wrong layer produces nothing visible.
- Data. A clean, cu