Growth flow · the map behind lanes 01 and 02

Pre capture to post capture, end to end.

This is the reference model the principal reads sales and marketing against when they are read together. Seven acquisition systems on the left, one capture event in the middle, and the post capture lattice on the right, nurture, lifecycle, qualification, sales and the loop back.

Pre capture

Nobody knows you. Nobody knows the brand. Some know a little and are not in the funnel. Seven systems working on that, each with its own strategy, campaign types, calls to action and data validation.

The capture event

A record is created in the system of record, Salesforce, HubSpot or whichever CRM the company runs. Every lane on the left terminates here. Everything on the right begins here.

Post capture

How the record is nurtured, how sales interfaces with that nurture, and how a contact is progressed through lifecycle stages to a closed deal and back into the loop.

The atlas, every node, end to end

Seven acquisition systems · one capture event · one post capture lattice

Nothing is summarised out. Hover any channel lane to isolate its path through the entire model. Scroll the panel sideways to follow it past the capture line.

Land Expand Capture
Scroll rightto follow a lane past the capture line
PRE-CAPTURE
Strategy
Campaign type
CTA · land / expand
Data validation
Paid Social
CPL · CTR · thumb stop rate
ICP tiers + exclusions
Creative brief & hooks
Budget pacing by tier
Demand gen, cold
Retargeting, site + video
Lookalike from closed won
Thought leadership
Demo request
Content download
Webinar registration
Upsell offer
UTM schema enforced
Form field mapping
Bot & junk filtering
Paid Search
CPC · impression share · CVR
Keyword tiering
SERP intent mapping
Bid strategy by tier
Brand terms
Competitor conquest
Category non brand
Long tail / question
Pricing page
Demo request
Free trial start
Renewal landing
Match type audit
Negative keyword pass
Call tracking attach
Email Outreach
Reply rate · meetings set
List sourcing + verify
Persona message matrix
Deliverability warm up
Cold sequence
Nurture sequence
Event invite
Re engagement
Book a call
Case study request
Event RSVP
Account review
Suppression sync
Bounce handling
Reply routing to owner
ABM · SLG
Account engagement score
Target account list
Buying committee map
Account tiering 1/2/3
1:1 bespoke
1:few cluster
1:many programmatic
Field & events
Executive briefing
Assessment offer
Working session
Land & expand plan
Account matching
Intent signal ingest
SLA to named AE
3rd-party review
Category rank · referral CVR
Category placement
Review velocity program
Profile completeness
G2
Capterra
Peer insights
Directory listings
Comparison page
Quote request
Renewal proof point
Referral param capture
Lead dedupe on email
Experiment tool
Lift · stat significance
Hypothesis log
Test prioritisation
Guardrail metrics
Pricing test
Landing page variant
Offer test
Onboarding test
Variant CTA
Gated calculator
Plan upgrade prompt
Sample size check
Significance gate
Holdout preserved
Organic Web
Non brand sessions · assisted revenue
Topic cluster plan
Technical health
Internal link graph
Blog & editorial
Resource hub
Docs
Solution & pricing pages
Newsletter opt in
Demo request
Docs sign up
Community join
Attribution model
Self reported source
Page level source tag
The capture event
CRM record created

Salesforce, HubSpot, whichever system of record. Every lane to the left terminates here. Everything to the right begins here.

1 · Dedupe against existing
2 · Enrich firmographic
3 · Account match
4 · Route to owner
5 · Stamp lifecycle stage
6 · Apply source attribution
POST-CAPTURE
Nurture tracks · segment × cadence
Net new education
Welcome + orientProblem framingMethod explainerProofOffer
Champion enablement
Internal business caseROI modelPeer storyExec one pager
Economic buyer
Category POVCost of inactionReference callPricing conversation
Recycled / cooldown
21-day pauseLow frequency valueTrigger watchRe entry
Customer expansion
Adoption checkNew use caseMulti team rolloutRenewal prep
Lifecycle progression
Subscriber
Opted in, no intent
Lead
Captured record
MQL
Score / flag met
SQL
Sales accepted
Opportunity
Pipeline created
Customer
Closed won
Expansion
Second sale
MQL gate · triggers
Lead score at threshold
SLG activity threshold
Hot lead flag, demo, pricing, sign up
PQL, product usage signal
Routing outcomes
Accepted → SDR sequence → meeting held
Recycled → back to nurture, cooldown timer
Disqualified → suppression, reason coded
Account matched → routed to named AE
Sales flow
Phase 01
Discovery
Pain & process
People & power map
Timing / compelling event
Meeting held logged
Phase 02
Qualification
MEDDIC fields complete
Mutual action plan
Budget confirmed
Champion identified
Phase 03
POC
Success criteria signed
Technical validation
Scoped timeframe
Exit review
Phase 04
Procurement
Security review
Legal / MSA
Pricing approval
Signature
Phase 05
Post sale
Onboarding kickoff
Health scoring
Expansion trigger
Loop to nurture
The loop
Nothing exits the system. It re enters nurture with a reason attached.
Recycled, no engagement
21 days silent → cooldown timer starts
Cadence drops to low frequency value
Trigger watch stays live on the record
Re entry at nurture, score preserved
Closed lost, reason coded
No budget → re approach next cycle
Lost to competitor → displacement track
No decision → champion re enablement
Bad fit → suppression, never re worked
Expansion, back to the top
Usage ceiling hit → upgrade motion
New department identified → land again
Renewal at ninety days → account review
Advocacy → referral becomes a new lane
returns to nurture tracks, above
Why it is on the site

Because the Diagnostic reads sales and marketing against the same board pack, and this is the shape the two departments have to agree on before either number means anything.

How it is used

In week one, the company’s own systems are laid over this model. Where a node is missing, that is a finding. Where two nodes disagree about a definition, that is usually the constraint.

What it is not

A recommendation. No company should run every node. The model exists so the ones a company does run can be named, owned and measured.

Lay your systems over this map.

That is week one of the Diagnostic. The gaps are usually visible by Wednesday.

Start with a diagnostic