The model
Go-to-market is the system through which a company takes an offering to a market and turns demand into revenue, and then into revenue that repeats. It is not a department and not a channel. It is the whole path, and it has 12 stages.
The stages matter less than the joins between them, which is where revenue is actually lost.
Each of these is a part of go-to-market. Treating any one as the whole is the most common way a company ends up optimising a stage that was never the constraint.
Twelve stages is the working map. Five is what fits in a sentence: demand becomes leads, leads become intent, intent becomes opportunity, opportunity becomes revenue.
Each stage states what it is, what should move forward out of it, and what commonly breaks. The boundaries shift between businesses. The point of the map is not taxonomy, it is finding where a specific commercial system is losing money.
Everything that happens before anyone has identified themselves.
What moves forward. A described segment, not an average.
What commonly breaks. The market is assumed rather than described, so every downstream decision is aimed at a buyer who does not exist.
What moves forward. A claim a buyer can agree or disagree with.
What commonly breaks. Positioning describes the product rather than the buyer's situation. There is nothing to disagree with, so there is nothing to remember.
What moves forward. Recognition, and an association.
What commonly breaks. Reach without recall. It is measured in impressions, and an impression does not carry an opinion.
What moves forward. Attention that has not identified itself yet.
What commonly breaks. Demand is captured as volume rather than as a situation, so the reason they came is discarded at the moment of capture.
Attention becomes a record someone could act on.
What moves forward. An identity and a channel.
What commonly breaks. The form captures the identity and drops the context: the page they were on, the question they asked, the thing they compared you against.
What moves forward. A record with a reason attached.
What commonly breaks. The record exists and nobody follows up. The tail gets abandoned, and the reason it stalled is never revisited even after the business fixes it.
Which of these records is actually in market, and why.
What moves forward. A signal with a timestamp.
What commonly breaks. Intent is present but not detected, because it appears in a system nobody has joined to the CRM.
Lead Response Engine
What moves forward. A decision, and the evidence behind it.
What commonly breaks. Qualification is encoded as a score with no rationale. Nobody downstream can act on it, and nobody can argue with it.
A live deal, and the work of getting it decided.
What moves forward. A commitment to evaluate.
What commonly breaks. Intent exists but is not routed. It lands in a queue instead of with the person who could have answered it that afternoon.
What moves forward. A proposal, and an objection worth recording.
What commonly breaks. A qualified prospect waits days for a document that reads like the last one, and the objection that killed it is never written down.
Proposal-to-Close
Money in, and whether anything was learned from it.
What moves forward. A closed deal and its cause.
What commonly breaks. The outcome is recorded. The reason is not.
What moves forward. Evidence about which deals were worth having in the first place.
What commonly breaks. Nothing returns to the top. The loop that should tell positioning what actually converted is never closed, so the same assumptions get funded again next quarter.
Revenue Intelligence
Not inside the stages. At the joins between them. At every meaningful transition there are four questions, and revenue leaks when any one goes unanswered.
The next stage needs to know why this person is here, not just that they are.
Something has to be judged worth doing, with a reason that survives being questioned.
The decision has to become a specific thing done by a specific system or person.
The result has to travel back far enough to change the next decision.
Revenue leakage is demand a business has already paid to create, which then fails to convert for reasons that have nothing to do with the buyer losing interest.
Acquisition to Leads
What it looks like. Sales opens a record with a name, an email and nothing else. The first call starts by asking questions the visitor already answered.
What is actually wrong. The form captured the identity and discarded the situation: the page they were on, the question they asked, what they compared you against.
Demand to Leads
What it looks like. Someone raises their hand at 9am and hears back the next afternoon, by which point they have spoken to two competitors.
What is actually wrong. Routing depends on a person noticing a queue. Nothing is wrong with the system; nobody is watching it at 9am.
Lead Response Engine
Leads to Intent
What it looks like. A database of leads that were interested once, went quiet, and have not been contacted since. Everyone knows it is there. Nobody wants to open it.
What is actually wrong. The reason each one stalled was recorded by sales, and the thing that would resolve it shipped in product or marketing. Nobody joins those two records, so a company ships exactly the thing that lost it forty deals and never tells those forty people.
Dormant Lead Revenue Recovery
Intent to Qualification
What it looks like. A prospect visits pricing three times in a week and nobody knows. The signal exists in a product, a support ticket or a review site.
What is actually wrong. The signal lives in a system nobody has joined to the CRM. It is a plumbing failure that presents as a demand problem.
Opportunity to Revenue
What it looks like. A qualified prospect waits days for a proposal, and the document that arrives reads like the last one because it is the last one.
What is actually wrong. Producing the artefact is manual, so it queues behind everything else, and the objection that eventually kills the deal is never written down.
Proposal-to-Close
Revenue to Market
What it looks like. Everyone can report what closed. Nobody can say which change caused it, so next quarter funds the same assumptions.
What is actually wrong. The loop that should carry the outcome back to positioning was never closed. This is not a broken handoff, it is a handoff that does not exist.
Revenue Intelligence
At the joins, not inside the stages, and one join at a time. Each service is built into the CRM and automation a business already runs. There is no platform to log into and nothing to migrate. Teams usually start with Dormant Lead Revenue Recovery, at the leads stage, where a record exists and nobody follows up.