Thirty-four things make a go-to-market work. Find out how many you have.
Not everything you’re missing. The one thing that’s blocking the rest.
What comes back
A mark on every one of the 34
Each mark says one of three things.
I found it, or I read for it and did not find it, or I cannot see it from outside.
A quote behind every found mark
If I say you have it, the readout shows the sentence from your page that proves it.
The URL it came from sits next to the quote.
The pages I read, listed
Usually between 12 and 40 pages, taken from your sitemap.
The list is in the readout, so you can check what I looked at.
Where to start
One output, named, with the reason it comes first.
Not a list of everything you are missing.
A real one
This is a run on this site, so you can see the shape of a readout before you start one.
The quote behind mark 04
Every timing claim you could make, tested against one question: could you have said this two years ago? Sourced from regulations, cost changes and measured behaviour shifts, wherever your market’s changes are published.
The honest part
14 I can find evidence for. 8 I have to infer. 12 I cannot see from outside.
Some outputs leave a public trace. Others are internal work and never reach a web page. The map only reads what is public, so it can only speak about the first kind.
A messaging framework is an internal document and I will never see it. Message drift shows up the moment two pages say different things about the same product.
The readout marks those 12 as unseeable rather than as missing, because a company can have all 12 and show none of them.
The method
- 01Read the sitemap.
- 02Pick the pages that matter.
- 03Read each one, as a crawler does, without running JavaScript.
- 04Check each of the 34 against what is on those pages.
- 05Quote the sentence that proves it, or say nothing.
- 06Name one place to start.
All 34, linked
Every output has its own page, with a worked specimen. Nothing is gated.
Research
- 01Voice of customer. What buyers said, in their own words.
- 02Win / loss. Why deals were won and why they were lost.
- 03Market report. How big this is, counted two ways.
- 04Why now. Why this matters now and not two years ago.
- 05Assumption log. What the plan takes on faith, written down.
- 06Pre-mortem. How this fails, imagined before it does.
Competition
- 07The Fifty. Fifty rivals, read and ranked.
- 08Table-stakes read. What every buyer expects before they listen.
- 09AI visibility. What an assistant says about your category.
- 10Competitor monitor. What competitors changed, week by week.
Segment, position and price
- 11ICP and segments. Who to sell to and who to leave alone.
- 12Use cases. The jobs people hire the product for.
- 13Buying committee. Who signs, who blocks, who has to be convinced.
- 14Positioning. What you are and who it is for.
- 15Packaging and pricing. What you sell and what you charge.
- 16Deck spine. The argument the sales deck has to make.
Message
- 17Messaging framework. One claim set every team writes from.
- 18Claim check. Every claim tested against evidence.
- 19Landing page review. The homepage read as a stranger reads it.
- 20Message drift. Where pages disagree about the same product.
Launch and enable
- 21Launch tiers. How big a launch this is, and what that buys.
- 22Launch brief. One page that runs the launch.
- 23Channel and funnel. Which channels carry it and what happens next.
- 24Product Oracle. One place with the answer to every product question.
- 25Sales enablement. What sales needs to have the conversation.
- 26FAQ. The questions people ask, answered.
- 27Onboarding journey. The first week, from sign-up to value.
- 28Release notes. What shipped and why anyone should care.
Measure and maintain
- 29Product funnel metrics. Where people drop out of the product funnel.
- 30Launch post-mortem. What the launch did, checked after the fact.
- 31Trust metrics. Proof a buyer can hold, and how it moves.
- 32Customer case studies. Customers, named, with numbers.
- 33Half-Life Map. How long each piece stays true.
- 34Six-stage readout. The whole function, read in six stages.
The limits
- Pages that need JavaScript to show their text may read as empty.
- A private document is invisible whether it exists or not.
- This reads what is public today, not what you have.
- It is a reading, not a verdict.
- I have been wrong about roughly one row in twenty.
Questions
- What does it cost?
- Free while I am testing it on the first fifty companies. €1,500 after that.
- How long does it take?
- About ninety seconds. The map fills in while it runs.
- Does it store anything?
- It stores the address, the pages it read and the marks it made, so the readout has a URL you can return to.
- Is the readout public?
- No. The link is unguessable and it is not indexed. Ask me and I will make it public.
- What if it cannot read the site?
- You get told, not an empty map. Mail me and I will read it by hand.
- How is this different from the Deep Map?
- The GTM Map reads public pages. The Deep Map is paid work: I read the internal documents too, and interview the team.
- Do I need to give you an email address?
- No. Nothing on this page asks for one.
- Can I run it on a competitor?
- Yes. It only reads pages anyone can read. Five runs a day.
Find out how many of the 34 you have.
Put in an address. The map fills in while you watch.