Launchrecord

Research synthesis · 20+ practitioner sources

What a SaaS marketing strategy actually is

A field guide for building a product that generates one. Every pillar below is broken into the fields it is actually made of — and each field is tagged with whether a website can tell you. That last part is the constraint that should shape the product more than any framework does.

Contents
01

First, the test: is it even a strategy?

Richard Rumelt's kernel is the most widely accepted test of whether a document is a strategy at all. It has exactly three parts, and all three are load-bearing.

  1. Diagnosis

    What is actually going on — the single biggest obstacle to progress. Not a description of the situation; a claim about what is in the way.

  2. Guiding policy

    The overall approach to that obstacle. It constrains action without fully specifying it. If it rules nothing out, it is not a policy.

  3. Coherent actions

    Actions that reinforce each other and follow from the policy. A list of activities that do not cohere is not a strategy.

Rumelt also named four failure modes, and they map almost perfectly onto what founders complain about in AI-generated strategy:

  • Goals mistaken for strategy — “grow signups 20%” is a target, not an approach.
  • Fluff — abstraction that restates the obvious in longer words.
  • Failure to face the challenge — no diagnosis anywhere in the document.
  • A dog's dinner of objectives — a list of everything, with no trade-off.

MKT1 names the same anti-pattern from the practitioner side: “Random Acts of Marketing” — check-the-box work copied from other companies with no strategic alignment.

Strategy vs plan vs tactics

How strategy, plan and tactics differ by unit and by the question each answers
LayerUnitAnswers
StrategyAllocation decisionsWho we target, what we say, which channels carry it, what we explicitly decline
PlanCampaignsWhat runs when, who owns it, what it costs
TacticsIndividual motionsA webinar, a case study, a paid campaign
The single highest-leverage design rule

Every generated strategy must contain at least one explicit “we are not doing this” — a de-prioritised segment, a skipped channel, a claim deliberately abandoned. Make it a required field with a validator behind it. It is the cheapest and strongest defence against output that reads as generic, because generic output never makes a trade-off.

02

ICP, defined rigorously

“ICP” is used loosely enough to be useless. The distinctions below have broad practitioner consensus and each one changes what you store.

The unit of analysis and the question answered by target market, segment, ICP, persona and buying committee
TermUnitAnswers
Target market / TAMMarketThe full universe of plausible buyers
SegmentGroup of accountsA slice sharing characteristics
ICPCompany / accountWhich accounts are worth pursuing
PersonaPersonWho inside those accounts we talk to, and how
Buying committeeSet of rolesWho must say yes

The clearest formulation: an ICP describes a company; a buyer persona describes a person. Personas live inside your ICP. The ICP guides go-to-market; personas guide messaging, content and sales conversations.

April Dunford's twist is worth honouring, because it disciplines the whole thing: her best-fit customer is defined by characteristics that predict caring about your differentiated value — not by firmographics for their own sake. A firmographic filter that does not predict value-fit is noise.

The buying committee — six roles

Load-bearing for messaging, because the homepage usually speaks to the champion or the user, while the pricing and security pages speak to the economic buyer and the blocker.

  • Champion — feels the pain most, advocates internally. Usually an IC or manager, not the economic buyer.
  • Economic buyer — approves budget. VP or C-level.
  • Technical evaluator — fit and integration. CTO, head of IT, architect.
  • End user — daily use; determines whether it sticks.
  • Operations owner — owns the process being changed.
  • Blocker / gatekeeper — procurement, legal, security, finance.

The anti-ICP is required, not optional

Strong consensus here, best put as: an ICP without disqualifiers is a wish list. Typical axes — wrong tech stack, no budget authority, size outside range, a regulatory blocker, wrong region, a buying motion you cannot service, free or student domains.

The composite field schema

Synthesised from MKT1, FullFunnel and the ICP-scoring literature. Tags show what a website can supply.

Each ICP field group, whether a website can supply it, and the fields it contains
GroupSourceFields
FirmographicsW?Industry, sub-vertical, employee band, revenue band, funding stage, geography, business model
TechnographicsWRequired integrations, competing tools in stack, platform dependency, data maturity
SituationW?The process they are running or outcome they are chasing
JobsW? CFunctional job (solution-free), emotional and social jobs, desired outcomes
PainsWFrom the site's problem section — the founder's hypothesis, not evidence
GainsWDesired outcomes as stated
TriggersF CFunding round, new exec hire, missed target, migration, compliance deadline, renewal
Buying committeeW?Per role: title patterns, what they care about, their objection, where they hang out
QualificationFNon-firmographic patterns that predict a good fit
DisqualifiersFThe anti-ICP. Weakly inferable from a pricing floor
Priority tierFCore / Scaling / Testing / Not now
Watering holesF CCommunities, newsletters, podcasts, events, subreddits, analysts
Buying processCCycle length, how they discover, how they evaluate, who signs
03

Positioning

Dunford's definition: how your product is a leader at delivering something that a well-defined set of customers cares a lot about. Her five components matter less than the order she derives them in — the order is the method.

  1. Competitive alternatives

    What customers would do if you did not exist. Includes spreadsheets, manual process, in-house builds — and doing nothing. List only alternatives that actually appear in deals.

  2. Unique attributes

    Capabilities you have that the alternatives lack.

  3. Value, and proof

    The “so what?” of each attribute, as a business outcome, with evidence.

  4. Best-fit characteristics

    Who cares a lot about that value. Note this is an output of the previous steps, not an input.

  5. Market category

    The frame of reference that makes the value obvious.

  6. (+1) Relevant trend

    Optional. Layer it on carefully — a trend that overshadows the category is a liability.

Geoffrey Moore's template is the same six slots without the derivation attached:

For [target customer] who [need], the [product] is a [category] that [key benefit]. Unlike [primary alternative], our product [differentiation].

On market category strategy there are three choices — head-to-head in an existing category, “big fish, small pond” (a subsegment you can lead), or creating a new category. Dunford is emphatic that new-category creation is usually the wrong call: roughly 90% of recently-public tech companies positioned into existing markets.

Field schema

competitive_alternatives[] name, type (status quo | manual | in-house | point tool | suite | do nothing), why_considered, trade_off unique_attributes[] attribute, is_truly_unique, evidence value_themes[] theme, attributes[], business_outcome, proof[] (metric | quote | logo | cert) best_fit_characteristics[] characteristic, why_it_predicts_caring market_category label, strategy, why_this_frame relevant_trend optional; flag if it overshadows positioning_statement rendered from the above anti_positioning what we are NOT, and who we are NOT for
Hierarchy worth keeping straight

Vision (where we want to be) → Strategy (how we get there, in stages) → Positioning (why buy us today). Positioning changes as strategy progresses. And positioning is an input to messaging, not messaging itself — messaging without positioning is decoration.

04

Messaging architecture

The “message house” shape is near-universal: one value proposition as the roof, three to five pillars as the columns, proof under each.

core_value_proposition one sentence — the roof pillars[] (3–5) the columns ├ name ├ claim a benefit tied to a buyer pain ├ supporting_capabilities[] ├ proof_points[] metric | quote | case study | logo | │ benchmark | certification | demo └ audience_variants[] per persona / per ICP segment differentiation_statement vs named alternatives objections[] objection, response, risk_reversal, proof narrative change, stakes, promised land, gifts, evidence vocabulary words we use / words we never use

Wynter's five layers make it scorable

Peep Laja's team derived these from thousands of message tests. They are diagnostic-ordered: failure at layer N makes layer N+1 irrelevant. That turns messaging from a document into a set of pass/fail gates, each with a named remedy.

Each message layer, the buyer question it answers, and what satisfies it
LayerBuyer questionWhat satisfies it
Clarity“What is this and what does it help me do?”Plain category label, primary promise, no unexplained jargon
Relevance“Is this for a priority I have now?”Role-specific use cases, a vivid problem statement
Value“Is the outcome worth pursuing?”Concrete future state; capability → result link
Differentiation“Why this instead of what I do now?”Named alternatives, a distinctive capability, credible proof
Conversion“Yes, you!”One clear next action

Two ideas that punch above their weight

MKT1's Perceptions. Three to five narratives you want to drive, written from the audience's point of view, each of which must fail a single test: could a competitor claim this? If yes, it is not a perception. This is the best generic-output filter in the entire body of research, and it is directly implementable as a validation step.

Moesta's four forces. A switch happens only when push (dissatisfaction with today) plus pull (appeal of the new) outweighs anxiety (fear of the new) plus habit (comfort of today). Founders over-index on push and pull and ignore the other two — which is precisely why objection handling and risk reversal belong in the schema as first-class fields rather than an appendix. The forces that lose deals are the ones nobody writes down.

05

Channel strategy

Two credible camps, and they genuinely disagree. Both force a trade-off, which is the part that matters.

Bullseye — rank, then focus

From Traction. Three rings: brainstorm all 19 channels and generate a plausible idea for each (the discipline is that you may not skip one because it “feels wrong”); rank the ~3 most promising on expected impact, confidence and cost-of-test; then commit resources to the one showing real signal. The core claim is that at any given stage one channel dominates, and the job is to find it cheaply.

Tests are structured: hypothesis (if / then / because), action steps, a fixed deadline, and a success metric chosen in advance.

MKT1 — build a mix

Explicitly contradicts Bullseye. Channels reinforce each other like a team with different roles, organised as six growth engines rather than 19 tactics: Inbound, Outbound, Product Virality, Events, Ecosystem, Lifecycle. Selection is driven by GTM motion — self-serve leans inbound and product-led; sales-led leans outbound, events and ecosystem.

Field schema

gtm_motion PLG | sales-led | hybrid | community-led engines[] ├ channel ├ rationale tied to ICP watering holes + advantages ├ role primary | supporting | experiment | NOT DOING ├ hypothesis if / then / because ├ first_test actions[], cost, deadline, success_metric └ expected CAC, volume, time-to-signal explicitly_not_doing[] with reason — the trade-off field sequencing what runs now vs next quarter

Stage advice is consistent across sources: under roughly $1M ARR, founder-led outbound, referrals and founder-led social dominate. SEO and content pay back over 6–18 months and need sustained investment. Pre-PMF, the purpose of a channel is learning, not volume. The most-cited mistake is picking channels because they worked at a previous company.

06

Content strategy

Content pillars are the end of a chain, not the start of one. Getting the chain right is what stops a content calendar from masquerading as a strategy.

ICP jobs & pains → messaging pillars what we must be believed about → perceptions narrative throughlines → content pillars topic areas we have authority in → topic clusters pillar page + 15–25 cluster pages → calendar dated instances

Three distinctions that are easy to collapse and expensive to collapse:

  • Messaging pillar ≠ content pillar. A messaging pillar is a claim about you; a content pillar is a topic area you have authority in. They overlap; they are not the same object.
  • Perception ≠ content pillar. Pillars are chapters; perceptions are throughlines that run across chapters.
  • Strategy ≠ calendar. A content calendar presented as a strategy is the single most common fake deliverable in this category.

Two MKT1 rules worth encoding: the 30% juice rule — about 30% of content is product-centric, 70% is problem, market and vision — and mileage, which splits repurposing (one idea, many assets) from distribution (many channels). Both are required, both are planned at creation time, and there are no dead ends: every asset leads to a next one.

Roadmap item fields — adopt verbatim

audience / ICP · funnel stage · perception it advances · revenue lever · primary distribution channel · effort · impact

With coverage checks across the set: ICP coverage map, funnel-stage distribution, and the 30% juice ratio.

07

What a website can and cannot tell you

This is the constraint that should shape a website-input product more than any framework on this page. Most of a strategy is derivable. The parts that are not are not evenly distributed — they cluster in exactly the places that make a strategy specific.

WDerivable from the website, high confidence
W?Inferable, but a guess that needs confirming
FRequires founder input
CRequires customer or sales-call evidence
For each strategy field, whether a website can supply it and where on the site it comes from
FieldSourceWhere it comes from
Market category (claimed)WHero copy, meta description, nav labels
Market category (should be)W?Requires competitive judgement
Capabilities / attributesWFeatures pages
Which attributes are genuinely uniqueFNeeds a competitor crawl, and still a judgement
Competitive alternatives (named)W?Comparison pages, “vs” pages, “alternative to” SEO pages, migration guides
Competitive alternatives (real, from deals)CIncludes “do nothing” — which never appears on a website
Value themesWBenefit copy — but asserted, and unranked
Which value theme matters mostCRequires customer evidence
Proof pointsWLogos, metrics, testimonials, case studies, certifications
Target segment (claimed)W“For sales teams”, industry pages, use-case pages
FirmographicsW?Pricing tiers, “for teams of X”, enterprise tier, customer logos
TechnographicsWThe integrations page is the single richest ICP signal on a site
Buying committee rolesW?Persona pages; security page → blocker; pricing page → economic buyer
Buying triggersF COccasionally in case-study intros; otherwise absent
PainsWProblem sections — the founder’s hypothesis, not evidence
Anxieties / objectionsW?FAQ, security page, migration and onboarding pages, refund policy
Habits / status quoF CRarely stated anywhere
Disqualifiers / anti-ICPFWeakly inferable from a pricing floor and tier gating
GTM motionW“Start free” vs “Book a demo”; pricing transparency; self-serve signup
Marketing advantagesW?Founder audience, OSS repo, community, data asset, notable investors
Existing channels in useWBlog, changelog, community link, newsletter CTA, careers page
Existing content pillarsWBlog categories and their volumes
Content gaps vs pillarsWHigh value, fully automatable — compare blog coverage against derived pillars
Messaging consistency across pagesWHigh value, fully automatable — hero vs pricing vs about vs blog
Strategic narrativeFNeeds founder conviction about a market change
Vision, stage, goalsFAn about or careers page sometimes hints at stage

The three structural gaps

These are not gaps you can close with a better crawler or a better prompt. They are gaps in what a website is.

Triggers

Nearly absent from websites, and central to a real ICP. A site says what it does; it does not say what was happening the week someone started looking.

Anxiety and habit

Websites over-state push and pull by design. The forces that actually lose deals — fear of the new, comfort with today — are invisible on a page written to sell.

Prioritisation

A site asserts many values with no ranking. Which one customers actually buy on is precisely what a website cannot tell you. “Do nothing” as a competitive alternative never appears either.

The honest product shape

Not “your marketing strategy” but a strategy hypothesis derived from your site, with named gaps and the cheapest way to close each. A named gap with a one-week plan to close it reads as rigour. A confident fabrication destroys trust on first read, because the person reading knows their own business.

Five founder questions that unlock the rest

Ranked by value added ÷ effort to answer. Everything else can be inferred and marked as hypothesis.

  1. What do customers use instead of you — including doing nothing?Unblocks the first and most important step of positioning, and it is the one thing a website structurally cannot supply.
  2. Describe your last three won deals and last three lost deals, one line each.Yields best-fit characteristics and disqualifiers from real evidence rather than inference.
  3. What triggered your best customers to start looking?The single largest ICP gap. Turns a static profile into a targetable moment.
  4. Which customer type gets value fastest?Resolves prioritisation — the ranking a website can never give you.
  5. Who must sign off, and who tries to block it?Populates the buying committee and, with it, the objection set.
08

Where the experts genuinely disagree

These are not ambiguities to resolve by picking the more popular source. Each one is a real fork with consequences for what you build.

Segment first, or value first?
DunfordDerive alternatives → attributes → value → then who cares. The segment is an output.
MKT1, Pierri, MooreChoose the audience first and position against them. The segment is an input.
Sets your agent execution order and what the founder form has to ask for. Value-first is the more rigorous path, but it depends on competitive alternatives — the weakest thing to get from a website.
One channel, or a mix?
BullseyeOne dominant channel per stage. Find it cheaply, then pour resources in.
MKT1Build a mix. Channels reinforce each other; different roles on one team.
Both force a trade-off, which is the part that matters. A mix with exactly one named primary and at least one explicit decline satisfies both.
Narrative altitude
RaskinLead with a big, undeniable change in the world.
Fletch, WynterLead with concrete clarity. Vague vision copy is the #1 homepage failure.
The sharpest fork for a generated product. Make altitude a parameter gated on GTM stage, not a constant: pre-PMF needs clarity, category creation needs narrative.
Create a new category?
Category-design schoolCategories are created, and creating one is the prize.
DunfordUsually a mistake. ~90% of recent tech IPOs positioned into existing markets.
Default to an existing category or “big fish, small pond”, and treat new-category output as a flag requiring justification.
09

Actionable vs useless

What founders actually complain about in AI-generated strategy, and the design rules that fall out of each complaint.

The complaints

  • Trendslop — whatever buzzwords are currently popular, in place of a trade-off.
  • No trade-offs — it lists everything. Rumelt's dog's dinner.
  • No business context — generic because the input was generic.
  • Reformulated inputs — it hands back your own website copy as if it were insight.
  • Undifferentiated claims — fails the competitor-claim test on every line.
  • Stops at “what” — no how, no owner, no first step, no metric.

The rules

  1. Emit a diagnosis, not a description.One named primary obstacle, argued from evidence.
  2. Force at least one explicit trade-off.A deprioritised segment, a skipped channel, a claim abandoned. A required field with a validator.
  3. Cite the evidence.Every derived claim links to the page and sentence it came from. The strongest available answer to “this is generic” — it demonstrably is not, because it quotes their own site.
  4. Run the competitor-claim test on every message.If a competitor could say it, flag it.
  5. Separate asserted from verified.Website-derived hypothesis vs founder-confirmed vs customer-validated. Never present an inference as a finding.
  6. Give every pillar a first action.With an owner, an effort estimate, and a success signal.
  7. Name the alternatives specifically.Wynter’s data is unambiguous: unnamed alternatives mean a failed differentiation layer.
  8. Refuse to invent.An empty, named gap beats a confident fabrication every time.
10

The composite object model

Everything above, assembled. The shape of a strategy that would survive a founder reading it closely.

MarketingStrategy ├── diagnosis the single primary obstacle + evidence ├── guiding_policy the approach, with the trade-off named ├── context │ ├── gtm_motion, stage, pricing_model, acv_band │ └── marketing_advantages[] ├── icp[] tiered: Core / Scaling / Testing / Not now │ ├── firmographics, technographics, situation │ ├── jobs[], pains[], gains[] │ ├── triggers[] usually a GAP │ ├── buying_committee[] role, cares_about, objection │ ├── qualification[], disqualification[] │ └── watering_holes[] usually a GAP ├── positioning Dunford's five, in derivation order ├── narrative Raskin's five; altitude gated on stage ├── messaging message house + Wynter layer scores ├── channel_plan engines, incl. explicitly_not_doing[] ├── content_strategy pillars → clusters → calendar ├── measurement KPIs / Projects / Ops └── provenance ├── per field: source_url + quoted_evidence + confidence ├── per field: website-derived | founder-confirmed | │ customer-validated | GAP └── gaps[] with "the cheapest way to close this"
The part that makes it not generic

The provenance block is doing more work than any single framework on this page. It is what lets the document quote the founder's own sentences back at them, admit what it does not know, and tell them how to find out. It is also the part almost no competing AI tool has.

Sources

Practitioner-primary where reachable. MKT1's template library, Fletch's resource pages and Traction itself are paywalled or offline; those are synthesised from secondary coverage and noted as such above.

  • Emily Kramer — MKT1 Field Guide to B2B Startup Marketing, Parts 1 & 2
  • April Dunford — A Quickstart Guide to Positioning; Positioning vs Strategy vs Vision; Obviously Awesome; Sales Pitch
  • Richard Rumelt — Good Strategy Bad Strategy (via Lenny’s Newsletter, Alex Murrell)
  • Peep Laja / Wynter — Messaging Hierarchy; B2B Message Layers Framework
  • Andy Raskin — The Greatest Sales Deck I’ve Ever Seen
  • Gabriel Weinberg — The Bullseye Framework; Traction
  • Geoffrey Moore — Positioning statement template; Crossing the Chasm
  • Anthony Pierri / Fletch PMM — homepage positioning; via Growth Unhinged
  • Bob Moesta / Rewired Group — Jobs To Be Done, the four forces
  • Tony Ulwick / Strategyn — outcome-driven job statements
  • Strategyzer — the Value Proposition Canvas
  • Sangram Vajre / GTM Partners — the MOVE framework
  • Userlist — April Dunford 10-step positioning case study
  • FullFunnel.io — seven-step ICP guide and template
  • Traction Complete — mapping the B2B buying committee
  • Dave Gerhardt — story as strategy