03 Messaging & Positioning
How Customers Actually
Read You
People interpret more than companies realise.
The perception system
Message
What the company intends to communicate
Perception
What the customer actually receives
Trust signals
Evidence that shapes belief
Interpretation
The impression formed from all inputs
Customers don't read messaging. They interpret it — through language, structure, evidence, and context. What they form is an impression, not a reception of intent.
Why this matters
Customers form impressions from signals the company often doesn't realise it's sending.
When a company writes its messaging, it controls the words. But the customer's interpretation is formed from more than words: the visual density of the page, the specificity of the claims, the presence or absence of proof, the language register, the complexity of the navigation, the quality of the case studies, and whether the product description matches the problem they recognise as theirs.
Companies that understand this — that their positioning is experienced as a collection of signals, not as a transmitted message — design their communication accordingly. Every signal either builds or erodes the impression the company wants to create. The signals that are unintentional are often as influential as the ones that are deliberate.
The most common gap: companies believe they've communicated something because they've written it. Customers receive an impression formed from everything around the writing as much as from the writing itself. Understanding this changes how positioning and messaging work is approached.
Founder reality
Audit the signals customers are actually receiving:
If a prospect experienced only the visual design and structure of the homepage — without reading the words — what impression would they form?
Are the claims in the messaging backed by specific evidence — and is that evidence visible close to the claim or buried in a different section?
Does the language register (formal/casual, technical/accessible) match the register the target customer uses and trusts?
What signals does the company send about its stage, size, and stability — and are those signals accurate and intentional?
What is the first question most prospects ask in a first meeting — and what does that question reveal about the impression formed before the meeting?
The first-meeting question is the clearest window into the impression formed pre-meeting. If prospects consistently ask 'so what exactly do you do?' the impression formed was insufficient — regardless of what the messaging said.
The signal map
Four signal categories that shape customer perception
Audit each category independently. Each one contributes to the impression independently of the others.
01
Language signals — what the words communicate beyond their literal meaning
Language communicates register, expertise, and confidence beyond its literal content. Vague language ('innovative solutions', 'powerful platform') signals low confidence or unclear thinking. Specific language ('reduces deployment time from 4 hours to 12 minutes') signals operational reality and depth. The specificity of language is itself a trust signal — independent of whether the specific claim is positive or negative.
02
Evidence signals — what proof exists and where it appears
Claims without evidence are interpreted as marketing assertions. Claims with specific, named, contextualised evidence are interpreted as operational reality. The placement of evidence matters: evidence adjacent to the claim it supports is more persuasive than evidence in a separate 'case studies' section. Proof proximity — how close the evidence is to the claim — is a significant trust variable.
03
Structure signals — what the organisation of information communicates
The order and hierarchy of information communicates what the company values and believes is most important. A homepage that leads with technical architecture signals that the company is thinking about the product, not the buyer. A homepage that leads with the buyer's problem signals that the company is thinking about the customer. Structure is an argument — one that readers absorb without consciously reading it.
04
Consistency signals — whether all touchpoints agree
When a prospect encounters inconsistency between the homepage, the pitch deck, and the founder's LinkedIn — different language for the same product, different claims, different audience emphasis — the inconsistency itself is a signal. It suggests either that the company isn't sure what it is, or that different parts of it are saying different things. Consistency across touchpoints is a trust signal. Inconsistency is the opposite.
Common mistakes
01
Evaluating messaging by whether the team is satisfied with the language
The team is too close to the product to evaluate its own messaging objectively. The language that seems clear internally often seems opaque externally — because the team brings context the customer doesn't have. Test the impression on people without context. Their interpretation is the one that matters.
02
Treating unintentional signals as neutral
A homepage with broken links signals carelessness. A case study with vague metrics signals uncertain evidence. A job description that contradicts the homepage's audience description signals internal inconsistency. None of these are neutral. Design all signals deliberately — or audit them regularly to identify the unintentional ones.
03
Separating the messaging audit from the customer journey
Messaging is often audited in isolation — reviewing the homepage copy, the pitch deck language, the content tone. The more useful audit follows the customer journey: what is the accumulated impression formed by a prospect who encounters the company through a piece of content, visits the homepage, reads a case study, and joins a demo? The impression is formed by the journey — not by any individual touchpoint.
04
No perception measurement
If the impression customers actually form is never measured — through comprehension tests, first-meeting question analysis, or prospect interviews — the company can only guess whether its signals are creating the intended perception. Measure what customers believe, not just what the company communicates.
Example scenario
A B2B SaaS company. Leadership confident in the messaging. Sales team consistently hearing 'we need to think about it' after demos. Exit interview conducted with 6 non-converting prospects.
The perception audit
Exit interviews revealed: all 6 prospects had understood the category but not the specific value proposition.
Specific finding: the homepage leading claim ('the only platform built for compliance-first teams') was not supported by any evidence until the third section.
Prospect interpretation: the claim felt like marketing rather than operational reality — because it was unsupported at the point of encounter.
The claim was true. The signal — no adjacent evidence — made it read as aspiration rather than fact.
The signal redesign
Evidence moved: specific customer proof (a named company, a specific compliance scenario, a measurable outcome) placed directly adjacent to the differentiation claim.
Structure redesign: the leading claim now followed immediately by 3 lines of specific evidence, not 2 sections of feature description.
Language audit: 4 vague claims replaced with specific, demonstrable equivalents.
The outcome
'We need to think about it' response in demos: reduced by 40% in the following quarter. Demo-to-proposal conversion: improved 26%. The messaging hadn't changed in substance. The signals surrounding it had been redesigned to support the impression the messaging intended to create.
Takeaway
Customers don't receive your message — they interpret your signals.
Audit language specificity, evidence proximity, information structure, and cross-touchpoint consistency. Every signal either builds or erodes the impression you're trying to create. Design them all deliberately.
Related thinking
Continue reading
Founder Language vs Marketing Language