Key Takeaways
- A brand messaging framework is a working reference for explaining the business, not a collection of impressive-sounding adjectives.
- Start with a specific buyer situation, then connect the offer to a useful outcome and evidence you can support.
- Keep the main message, supporting points, proof and service limits separate so writers can use them in different formats.
- Include the questions customers ask before buying and a clear description of what happens after an enquiry.
- Test the wording with relevant people, then give one person responsibility for keeping the framework current.
To write a brand messaging framework for a service business, capture what you help people do, who the offer suits, why they should consider you and what evidence supports the promise. Then show your team how to use those answers in actual copy.
The document doesn't need to be long. It needs enough substance that a colleague can write an introduction without inventing a new version of the business. A designer should also be able to see which message leads and which information belongs underneath it.
We'll build the framework using a fictional company called Cedar Office IT. Every detail in this example is illustrative, not a MattDarm client or a claim about an existing supplier. Use the structure, then replace the example facts with verified information from your own business.
Start with the buying situation
“Small businesses” is too wide to help somebody write a useful page. A company choosing its first IT provider has different questions from one replacing a supplier after years of poor support.
For our example, Cedar's priority buyer is the operations manager at a small professional firm that already has business computers and needs an organised support arrangement. The buying trigger is repeated uncertainty over who handles problems, account access and staff changes.
Record that situation in plain language. Note what customers have tried, what they find difficult and who else influences the purchase. Use enquiry notes or customer conversations where you have appropriate permission, rather than assuming that every buyer thinks like the founder.
Our guide to testing a brand message with customers covers the research exercise. Here, the job is to turn what you learn into a reference that the website and sales teams can use.
Write the offer before the slogan
Describe the service in one factual sentence. For Cedar: “We provide ongoing IT support for small professional firms, with an agreed support scope and a named contact.”
That sentence leaves room for the detail, but it tells the reader what kind of help is available. It avoids making unsupported claims about being the fastest, cheapest or most advanced provider.
Then state the intended benefit in the buyer's language. In our fictional example, the benefit is knowing who to contact and how requests will be handled. That is more concrete than “confidence through digital excellence”. It must still match the service the business can deliver. Our guide to brand positioning helps you explain where that offer fits among the buyer's alternatives.
If the team can't settle a straightforward offer sentence, a brand strategy session may need to come before copywriting. Changing adjectives won't resolve uncertainty about which customers and services the business wants to prioritise.
Separate a promise from its proof
List the statements a buyer might reasonably ask you to demonstrate. “Experienced”, “responsive” and “easy to work with” need context before they help someone choose.
For each claim, name the supporting material. It might be a documented support process, an approved case study, a genuine qualification or a sample report. A claim without support can be narrowed, investigated or removed. The guide to social proof, reviews and case studies helps you choose evidence appropriate to the point you are making.
The ASA's substantiation guidance explains that objective advertising claims need evidence before publication. A customer's praise doesn't automatically prove a broader effectiveness claim. Keep the wording proportionate to the evidence available.
Our example business can describe its agreed process, but we haven't supplied measured response times or customer results. Its messaging therefore shouldn't promise either. In your own framework, link to the evidence record and name who can approve the claim.
Fill the core framework
The table below is a worked example, not ready-to-publish copy for a real company. The service details would need confirmation before anybody used them commercially.
| Field | Illustrative Cedar Office IT entry |
|---|---|
| Main buyer | Operations managers at small professional firms |
| Buying situation | Existing IT support feels unclear, and responsibility is spread across suppliers |
| Service | Ongoing support with an agreed scope and named contact |
| Main benefit | A clear route for requests, account changes and planned maintenance |
| Supporting point | An initial review records systems, owners and known issues |
| Supporting point | The support agreement explains inclusions and escalation |
| Supporting point | Staff changes follow a documented access checklist |
| Evidence needed | Sample review, support scope and access checklist, approved for sharing |
| Boundary | Projects and out-of-scope work are quoted separately |
| Next step | Send a short outline of the current setup for an initial discussion |
Notice that the framework includes boundaries. A prospect who needs a different service should be able to recognise that. Hiding exclusions creates extra sales work and can leave customers expecting something the business never intended to supply.
Add your own facts in this format before trying to make the headline memorable. The first pass should be understandable to somebody outside the company.
Build a message hierarchy
The main message should identify the offer and its relevance. Supporting messages explain the reasons to consider it. Proof sits beside the claims it supports, and detailed information answers the questions needed to make a decision.
For Cedar, a possible illustrative homepage introduction is: “IT support for professional firms that need a clear point of contact.” The next paragraph can explain scope and the initial review. A service page can then cover the actual support arrangements in more detail.
Don't force every point into the opening sentence. If the headline lists all services, audiences, values and locations, it becomes hard to understand. Decide what the reader needs first and what they can learn next.
This hierarchy helps content marketing too. An article can answer one specific buying question and link to the relevant service, without repeating the whole company pitch in every introduction.
Turn objections into useful answers
Write down the questions that come up before a purchase. They might concern cost, timing, ownership, compatibility, responsibility or how much work the client must do.
For the example business, useful questions include whether it supports an existing setup, how a previous supplier hands over access and what happens when a request falls outside the plan. Each answer should point to a real decision or process.
Avoid labelling every concern an objection to overcome. A prospective client asking about exclusions is doing sensible buying research. Clear answers may reveal that your service doesn't fit, which is better than a difficult relationship built on ambiguity.
Add a short answer, the page where more detail lives and an internal owner. If the answer changes between sales and delivery, resolve the service rule before polishing the wording.
Define tone with examples
“Friendly and professional” doesn't give a writer much direction. Show what it means in a sentence your business uses regularly.
For Cedar, “Tell us which account you can't access, and we'll check the next step” is clearer than “Our experts will optimise your digital productivity”. One describes a practical conversation; the other could appear on almost any technology website.
The GOV.UK guidance on clear language recommends familiar words and explaining necessary specialist terms. That is useful discipline for a service business, even though your personality and commercial purpose differ from a government page.
Keep three or four short before-and-after examples in the framework. Include a service introduction, an explanation of a limitation and a next-step invitation. Our article on human brand voice explores how to keep that language recognisable when more people or tools help write it.
Adapt the framework to different pages
A homepage needs to orient the visitor. A service page needs enough detail to support a buying decision. An About page needs to explain who is behind the work. Use the same underlying facts without making all three pages sound identical.
Create a small application sheet. For each page, note the main reader question, leading message, relevant proof and next action. That sheet becomes a better design brief than telling the team to copy the same paragraph everywhere.
Sales material may need a different emphasis again. A proposal follows a conversation and can refer to a specific scope. It shouldn't quietly introduce stronger claims than the website or promise something excluded from the delivery agreement.
When the framework informs brand guidelines, include these examples alongside the visual rules. Staff need to understand both what the business says and how the identity looks.
Review with the people who deliver the promise
Ask someone from sales, delivery and customer support to check the draft. Each sees a different part of the relationship. The aim is to find unsupported promises, unclear scope and wording that creates the wrong expectation. A focused brand strategy workshop can give those people a shared space to settle conflicting messages.
Then ask a few suitable readers to explain the offer in their own words. Listen for what they infer as well as what they remember. A phrase that sounds clear internally may imply unlimited work or a guaranteed result outside the business.
Treat those conversations as qualitative feedback, not a market-wide statistic. Revise the misunderstandings and keep a note of the decisions. If the audience or service is complex, more formal research may be appropriate.
Keep the framework useful after approval
Put a name and review date on the document. Keep the latest approved version easy to find, with links to evidence and service details. Archive earlier wording so it doesn't return through an old presentation.
Review it when the offer, audience, delivery process or proof changes. You don't need to rewrite the whole brand because one service has a new exclusion, but you do need to update the affected messages and pages.
Start by filling the core table for one service you want to sell. Mark unknown facts rather than filling them with confident copy. Once those gaps have owners and answers, write the homepage introduction and one service-page section from the framework, then check that both describe the same business.
If you would like help turning the framework into website copy, get in touch and tell us which pages come first.
Frequently Asked Questions
What is a brand messaging framework?
It is a working reference for explaining your audience, offer, value, supporting proof, common questions and next step. It gives writers and designers consistent source information without requiring every page to use identical wording.
How long should a messaging framework be?
Make it as short as possible while remaining usable. A core page plus examples and links to supporting evidence can be enough for a focused service. Several audiences or complex offers may need separate application notes.
Is a messaging framework the same as a tone-of-voice guide?
No. The framework defines what you need to communicate and the evidence behind it. Tone of voice explains how that information should sound. They work together, but a distinctive tone cannot replace a clear offer.
What if we don't have case studies or results yet?
Use accurate descriptions of your process, scope and relevant expertise, supported by material you can verify. Don't invent outcomes. Record the missing proof and plan how to gather it with appropriate permission.
Who should approve the framework?
The business decision-maker should approve it with input from the people responsible for sales and delivery. Claims, scope and service promises need operational confirmation, and one person should own later updates.




