Foundations / Project
ICP and Messaging Architecture
Every failed outbound programme I have audited failed here first. Not in the copy, not in the tooling, but in never deciding precisely who this is for and what specifically it does for them. Fix that and mediocre execution still produces meetings. Skip it and excellent execution produces nothing.
The problem
Ask five people in the company who the ideal customer is and you get five answers, all of them reasonable and none of them the same. The deck says mid-market, the sales team chases whoever replies, and the campaigns are written to a persona nobody has actually researched. The market cannot be blamed for not recognising itself.
WHO THIS IS FOR
- Companies whose outbound underperforms despite good execution
- Products that genuinely serve several segments and have never chosen a beachhead
- Teams whose buyer turned out to be someone other than who they were selling to
- Founders preparing to hire their first salesperson and needing something to hand them
Scope
What is included
Market selection
- Candidate segment mapping against pain sharpness, budget authority and sales cycle length
- Existing customer and user base analysis to find who actually converts and why
- Competitive positioning review inside the shortlisted segments
- A ranked recommendation with the reasoning shown, not just the conclusion
ICP definition
- Firmographic definition: size, sector, geography, technology, structure
- Qualifying and disqualifying signals, so the list builds itself against real criteria
- Trigger events that make an account worth contacting this month rather than someday
- Account scoring model your team can apply without me
Persona research
- Buying committee mapping: who feels the pain, who evaluates, who signs, who can veto
- Per-persona pain, priority and objection profiles
- Language capture from communities, reviews and calls, in the buyer's own words
Messaging architecture
- Positioning statement per segment, built on a defensible claim
- Value propositions per persona, tied to the pain rather than the feature list
- Proof points and objection handling mapped to each claim
- Message and channel matrix: what to say, to whom, where, at which stage
How it runs
3 phases
Research
Your data first: customers, users, closed-won and closed-lost. Then outside-in on the market. The DesignA11y engagement turned on exactly this step, where the user base disproved the assumption the whole go-to-market was built on.
Decide
Segments ranked, beachhead chosen, ICP and personas written down. Choosing means excluding, which is the uncomfortable part and the reason this is worth paying someone outside the company to facilitate.
Document
Everything lands in one working document with the scoring model, the claims, the proof and the objection handling, so the next campaign starts from proven language instead of a blank page.
Outcomes
What it produces
What you own at the end
You get a working document, not a slide deck. It is written to be used by whoever runs campaigns next, including a person you have not hired yet.
Questions
About this engagement
We think we already know our ICP. Is this still useful?
Do you talk to our customers?
Is this included in the GTM System Build?
What if the research says our market is wrong?
Proof
This work in practice
$40K in closed revenue from a cold outbound system built from zero: 12 demos booked and 4 deals closed at a $10K average.
400+ users and almost no revenue, until a data-driven targeting fix drove 20+ team and enterprise conversions at near-100% reply-to-paid.
Often paired with
Related services
Lead Research and Enrichment
Account and contact lists built against real criteria, enriched with the signals that make a first line land, and validated before anything sends.
Full GTM System Build
ICP, lead sourcing, sending infrastructure, sequences, LinkedIn layer, CRM and reporting, assembled as one connected system rather than six disconnected tools.
Next step
Interested in the ICP and Messaging engagement?
Start with a 30-minute discovery call. No pitch, just a clear conversation about your pipeline problem and whether this system fits it.
Typically replies within one business day