Icon

AI

Icon

Messaging Framework Template: From Positioning to Website Copy

·

By Jenish

Kraftbase thumbnail: Messaging framework template, template

One document decides how your company talks about its product.

A messaging framework is the one document that decides how your company talks about its product: who it's for, the core message, the three or four reasons to believe it, the proof behind each one, and the exact words to use. Sales, the website and every deck pull from the same page, so people stop telling slightly different stories.

Here's the eight-block template we use with clients, a worked example for a made-up product, a map of where each block ends up on your website, and a straight answer on who should fill it in. There's no sign-up. Just copy it off the page.

A team placing sticky notes on a printed customer journey map

Key takeaways

  • The framework is the source. Website copy, decks and emails come out of it.

  • It has eight blocks: positioning, audiences, core message, pillars, proof, objections, words and boilerplates.

  • A pillar with no proof is just a claim. Every one needs some.

  • The product marketer owns it. Sales, product and real customer language feed into it.

  • Map each block to a section of the website before you brief a designer or writer.

What is a messaging framework?

Short version: it’s where your positioning gets turned into actual words. Positioning is the decision about where you compete and for whom. Messaging is how you say it, and the framework is where you write that down once instead of re-arguing it every time somebody builds a deck. (If you can’t tell which of the two is broken, positioning vs messaging is the better place to start.)

It’s not copy. Please don’t paste it onto the homepage as is. It’s closer to a reference sheet that writers, designers, sales and founders keep open while they work. You’ll know it’s doing its job when someone reads the homepage, gets on a sales call the next day, and hears the same story both times.

What should a messaging framework include?

We call ours the Eight Block Messaging Framework, mostly because we needed a name for it in workshops. The order matters. Block 5 is hard to write if block 4 is wobbly, and so on down the list.

#

Block

What goes in it

Length

1

Positioning statement

For [buyer] who [situation], [product] is a [category] that [main outcome]. Unlike [main alternative], it [key difference]. (Adapted from Geoffrey Moore’s template in Crossing the Chasm.)

1 to 2 sentences

2

Audiences

The buyer, the main user, and the person who can block the deal. For each: their goal, their pain, the words they use.

3 short profiles

3

Core message

The one idea you want every reader to leave with. Then a headline version of it.

1 sentence + 1 headline

4

Pillars

The three or four reasons the core message is true. Each one a benefit, not a feature.

3 to 4 lines

5

Proof

For each pillar: the feature that delivers it, plus a customer story, number, demo or source that shows it.

1 to 3 items per pillar

6

Objections

The doubts buyers raise and your honest answer to each.

3 to 6 pairs

7

Words

Terms to use, terms to avoid, and how to name the product and its parts.

A short list

8

Boilerplates

The description at 10, 25, 50 and 100 words, ready to paste.

4 versions

The messaging framework template

Drop this into a doc and write in plain sentences, the kind you’d say across a table. You’ll hit a box that nobody in the room can fill. Don’t skip it. In our workshops that awkward box is usually where the team learns the most.

1. POSITIONING STATEMENT

For [buyer] who [situation or trigger],

[product] is a [category] that [main outcome].

Unlike [main alternative, including “doing nothing”],

it [key difference].

2. AUDIENCES

Buyer: goal / pain / words they use

User: goal / pain / words they use

Blocker: what they worry about / what reassures them

3. CORE MESSAGE

One sentence:

Headline version (under 10 words):

4. PILLARS (3 to 4)

Pillar 1:

Pillar 2:

Pillar 3:

5. PROOF (per pillar)

Pillar 1: feature that delivers it / proof (story, number, demo, source)

Pillar 2: feature / proof

Pillar 3: feature / proof

6. OBJECTIONS

“[Objection]” -> [Answer]

“[Objection]” -> [Answer]

“[Objection]” -> [Answer]

7. WORDS

Use:

Avoid:

Product and feature names:

8. BOILERPLATES

10 words:

25 words:

50 words:

100 words:

Owner: Last reviewed: Next review:

Who fills in the messaging framework?

Someone has to own it, and that’s normally the product marketer. Smaller company with no PMM? It falls to the founder or whoever runs marketing. Owning it doesn’t mean writing it alone. It means being the person who breaks the tie when sales and product disagree, and who remembers to open the doc again in three months.

Most of what goes in it comes from elsewhere:

  • Sales calls. How buyers describe the problem, which objections keep coming up, where deals stall. Recorded calls are the best raw material you’ve got.

  • Customers. Quick interviews with recent customers: what they were trying to fix, what else they tried, why they picked you.

  • Product. What the product really does today, what’s coming, and what it should never be described as doing.

  • Leadership. Sign-off on positioning, since that decides who you won’t sell to.

Once there’s a draft, send it to sales and product with a single question: “Is anything here untrue, or something a buyer would never actually say?” Whatever they circle, fix that before you polish anything else.

Filling it in, step by step

  1. Collect real language. Five to ten sales calls and customer conversations is plenty. You’re listening for the way buyers describe the problem before they know your product exists.

  2. Write the positioning statement. One honest sentence. Stuck on the main alternative? Stop and sort that out, because everything below depends on it.

  3. Profile the audiences. Three lines each, using the buyers’ words, even the clumsy ones.

  4. Write the core message. Write ten versions, on a whiteboard if you can. The keeper is whichever one a buyer could repeat to their boss without wincing.

  5. Pick three or four pillars. They need to hold up the core message and matter to the buyer. If a pillar is really just a feature wearing a hat, cut it.

  6. Attach proof to every pillar. Nothing to show yet? Write “gap” in the box. Better that than three adjectives pretending to be evidence.

  7. List objections and answers. Sales will rattle off their top five without thinking.

  8. Write the boilerplates last. They’re secretly a test. If the 25-word version won’t come, something earlier isn’t finished.

A filled-in example

To show how the blocks connect, here’s the template filled in for Ledgerline. Ledgerline is a made-up product, not a client, and every detail below is invented.

Block

Ledgerline (illustrative)

Positioning

For finance teams at mid-size companies who close the books with spreadsheets and email, Ledgerline is accounts payable software that gets invoices approved and paid without chasing. Unlike adding AP to the ERP, it is set up in a week and approvers never need to log in.

Buyer

Finance controller. Goal: close on time. Pain: invoices stuck with approvers. Words: “chasing approvals”, “month-end crunch”.

User

AP clerk. Goal: fewer manual entries. Pain: retyping invoices.

Blocker

IT. Worry: another system to secure. Reassured by: SSO, access controls, a security page.

Core message

Invoices get approved and paid on time, without anyone chasing. Headline: “Stop chasing invoice approvals.”

Pillars

1. Approvals happen where people already work. 2. Invoices enter themselves. 3. You can see every invoice’s status at any moment.

Proof

1. Approve from email or Slack, demo video. 2. Invoice capture, sample before and after. 3. Live status dashboard, screenshot. Customer proof: [none yet, gap to close].

Objections

“We already have an ERP.” Ledgerline sits on top and syncs both ways. “Approvers won’t adopt it.” They never log in.

Words

Use: approvals, on time, chasing. Avoid: “revolutionise”, “AI-powered” as a headline, “seamless”.

25 words

Ledgerline is accounts payable software for mid-size finance teams. Invoices enter automatically, approvers sign off from email or Slack, and nothing waits on a reminder.

Draw it as a messaging house and the core message is the roof, the pillars are the columns, and proof is the foundation. Notice the proof row has a gap. We left it there deliberately. A real framework shows its gaps, so the team knows exactly which customer story to go and get.

How does a messaging framework become website copy?

Most templates stop right here, and it’s also where a lot of website projects go wrong. Before anybody designs a page, map each block to the place it’ll show up.

Framework block

Where it goes on the website

Core message, headline version

Homepage H1

Core message, full sentence

Homepage subhead, meta description

Buyer profile

Who the homepage speaks to; the first solutions page

Pillars

Homepage feature sections, one per pillar, in order

Proof

Next to each pillar: screenshots, demo clips, customer quotes, numbers

Objections

FAQ sections, pricing page, demo page, security page

Blocker profile

Security or trust page, integrations page

Words to use and avoid

The brief for every writer and designer

10-word boilerplate

Social bios, directory listings, page titles

50 and 100-word boilerplates

About page, press page, review sites, partner listings

Working on a single landing page? The SaaS landing page messaging framework shows the order these go in. For the whole site, the SaaS website structure guide covers which pages need to exist first.

Building it by audience

You don’t need a separate framework for every buyer. Keep the positioning statement and core message as they are, then add a column per audience for pillars, proof and objections. That’s what most people mean by a messaging matrix. It pays off when buyers want different things from the same product, and a finance controller and a CIO often do. One warning sign: if you’re on your fourth audience column, you may actually have two products, or two positions, and that’s a bigger conversation.

Messaging house, matrix or canvas: which should you use?

  • Messaging house: core message on the roof, pillars as columns, proof as the foundation. Best for one product and one main buyer.

  • Messaging matrix: the same blocks with a column for each audience. Best when there are several buyers.

  • Value proposition canvas (from Strategyzer): maps customer jobs, pains and gains onto your product. Handy for working out pillars before you write the framework.

The Eight Block template works as a house. Add audience columns to blocks 4 to 6 and you’ve got a matrix.

Where messaging frameworks go wrong

  • Writing it from the product team’s side. Lots of features, no benefits anywhere. Start from how buyers talk.

  • Pillars without proof. Every claim needs a demo, a number, a story or a source.

  • Too many pillars. Get to five and nobody remembers a single one.

  • No owner. Written once for a launch, then never opened again.

  • Never tested. The team loves it. Buyers have never laid eyes on it.

Also read: Product Messaging for AI Startups, SaaS Website Messaging Audit, How to Explain Your AI Product on Your Website.

Keeping it current

A framework nobody opens goes stale fast. Put a quarterly review in the calendar, plus an extra one whenever something big moves (a new product, buyer, competitor or price). The owner’s name and the next review date go at the bottom, where nobody can miss them.

Before a website launch, test it on real people. Five who look like your buyer is enough. Show them the core message and pillars and ask them to explain the product back to you. The places they hesitate are the places to rewrite.

Want help turning your framework into a website?

Send us your messaging framework, finished or half done, and we’ll show you where each block should live on your site. Book a messaging review · See our work

Messaging framework FAQs

1. What is a messaging framework?

Think of it as the rulebook for how a company talks about its product. Ours has the positioning statement, audiences, a core message, three or four pillars with proof, objections and answers, words to use and avoid, and ready-made descriptions at a few lengths. It stays internal. The copy comes out of it.

2. What should a messaging framework include?

We use eight blocks: positioning statement, audience profiles, core message, three or four pillars, proof for each pillar, common objections with answers, words to use and avoid, and boilerplates at 10, 25, 50 and 100 words. Leave one out and it usually shows up later as an argument.

3. Who owns the messaging framework?

Usually the product marketing manager. Without one, the founder or head of marketing takes it on. Sales, product and customer interviews supply the material, and leadership signs off on the positioning part.

4. What is a messaging house?

It's a way of drawing the framework. The core message is the roof, the pillars hold it up, and the proof points are the foundation. It's at its best for one product sold to one main buyer.

5. What is the difference between a messaging framework and a positioning statement?

The positioning statement is a sentence or two on who the product's for, what it is and how it's different. The framework starts from there and adds everything else you need to talk about the product: pillars, proof, objections, wording.

6. How long should a messaging framework be?

For most B2B companies, two to four pages does it. Any longer and people quietly stop reading. Keep each block tight and link out to the detail, like full customer stories.

7. How often should you update a messaging framework?

Look at it quarterly. Update it whenever something big shifts, like a new product, buyer, competitor or pricing change. Write the owner and next review date at the bottom so it doesn't get forgotten.

8. How do you test messaging before a website launch?

Show the core message and pillars to five people who look like your buyer and ask them to explain the product back. Listen to sales calls for objections that keep resurfacing. Whatever people misread, fix it before anyone writes page copy.

About the author

Jenish is a designer at Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.

Sources

  • Eight Block Messaging Framework and the block-to-website map: Kraftbase framework, not a published standard. The positioning statement format is adapted from Geoffrey Moore, Crossing the Chasm.

  • Ledgerline is a made-up product used for illustration

Messaging review

Want help turning your framework into a website?

Send us your messaging framework and we will show you where each block should live on your site.

One document decides how your company talks about its product.

A messaging framework is the one document that decides how your company talks about its product: who it's for, the core message, the three or four reasons to believe it, the proof behind each one, and the exact words to use. Sales, the website and every deck pull from the same page, so people stop telling slightly different stories.

Here's the eight-block template we use with clients, a worked example for a made-up product, a map of where each block ends up on your website, and a straight answer on who should fill it in. There's no sign-up. Just copy it off the page.

A team placing sticky notes on a printed customer journey map

Key takeaways

  • The framework is the source. Website copy, decks and emails come out of it.

  • It has eight blocks: positioning, audiences, core message, pillars, proof, objections, words and boilerplates.

  • A pillar with no proof is just a claim. Every one needs some.

  • The product marketer owns it. Sales, product and real customer language feed into it.

  • Map each block to a section of the website before you brief a designer or writer.

What is a messaging framework?

Short version: it’s where your positioning gets turned into actual words. Positioning is the decision about where you compete and for whom. Messaging is how you say it, and the framework is where you write that down once instead of re-arguing it every time somebody builds a deck. (If you can’t tell which of the two is broken, positioning vs messaging is the better place to start.)

It’s not copy. Please don’t paste it onto the homepage as is. It’s closer to a reference sheet that writers, designers, sales and founders keep open while they work. You’ll know it’s doing its job when someone reads the homepage, gets on a sales call the next day, and hears the same story both times.

What should a messaging framework include?

We call ours the Eight Block Messaging Framework, mostly because we needed a name for it in workshops. The order matters. Block 5 is hard to write if block 4 is wobbly, and so on down the list.

#

Block

What goes in it

Length

1

Positioning statement

For [buyer] who [situation], [product] is a [category] that [main outcome]. Unlike [main alternative], it [key difference]. (Adapted from Geoffrey Moore’s template in Crossing the Chasm.)

1 to 2 sentences

2

Audiences

The buyer, the main user, and the person who can block the deal. For each: their goal, their pain, the words they use.

3 short profiles

3

Core message

The one idea you want every reader to leave with. Then a headline version of it.

1 sentence + 1 headline

4

Pillars

The three or four reasons the core message is true. Each one a benefit, not a feature.

3 to 4 lines

5

Proof

For each pillar: the feature that delivers it, plus a customer story, number, demo or source that shows it.

1 to 3 items per pillar

6

Objections

The doubts buyers raise and your honest answer to each.

3 to 6 pairs

7

Words

Terms to use, terms to avoid, and how to name the product and its parts.

A short list

8

Boilerplates

The description at 10, 25, 50 and 100 words, ready to paste.

4 versions

The messaging framework template

Drop this into a doc and write in plain sentences, the kind you’d say across a table. You’ll hit a box that nobody in the room can fill. Don’t skip it. In our workshops that awkward box is usually where the team learns the most.

1. POSITIONING STATEMENT

For [buyer] who [situation or trigger],

[product] is a [category] that [main outcome].

Unlike [main alternative, including “doing nothing”],

it [key difference].

2. AUDIENCES

Buyer: goal / pain / words they use

User: goal / pain / words they use

Blocker: what they worry about / what reassures them

3. CORE MESSAGE

One sentence:

Headline version (under 10 words):

4. PILLARS (3 to 4)

Pillar 1:

Pillar 2:

Pillar 3:

5. PROOF (per pillar)

Pillar 1: feature that delivers it / proof (story, number, demo, source)

Pillar 2: feature / proof

Pillar 3: feature / proof

6. OBJECTIONS

“[Objection]” -> [Answer]

“[Objection]” -> [Answer]

“[Objection]” -> [Answer]

7. WORDS

Use:

Avoid:

Product and feature names:

8. BOILERPLATES

10 words:

25 words:

50 words:

100 words:

Owner: Last reviewed: Next review:

Who fills in the messaging framework?

Someone has to own it, and that’s normally the product marketer. Smaller company with no PMM? It falls to the founder or whoever runs marketing. Owning it doesn’t mean writing it alone. It means being the person who breaks the tie when sales and product disagree, and who remembers to open the doc again in three months.

Most of what goes in it comes from elsewhere:

  • Sales calls. How buyers describe the problem, which objections keep coming up, where deals stall. Recorded calls are the best raw material you’ve got.

  • Customers. Quick interviews with recent customers: what they were trying to fix, what else they tried, why they picked you.

  • Product. What the product really does today, what’s coming, and what it should never be described as doing.

  • Leadership. Sign-off on positioning, since that decides who you won’t sell to.

Once there’s a draft, send it to sales and product with a single question: “Is anything here untrue, or something a buyer would never actually say?” Whatever they circle, fix that before you polish anything else.

Filling it in, step by step

  1. Collect real language. Five to ten sales calls and customer conversations is plenty. You’re listening for the way buyers describe the problem before they know your product exists.

  2. Write the positioning statement. One honest sentence. Stuck on the main alternative? Stop and sort that out, because everything below depends on it.

  3. Profile the audiences. Three lines each, using the buyers’ words, even the clumsy ones.

  4. Write the core message. Write ten versions, on a whiteboard if you can. The keeper is whichever one a buyer could repeat to their boss without wincing.

  5. Pick three or four pillars. They need to hold up the core message and matter to the buyer. If a pillar is really just a feature wearing a hat, cut it.

  6. Attach proof to every pillar. Nothing to show yet? Write “gap” in the box. Better that than three adjectives pretending to be evidence.

  7. List objections and answers. Sales will rattle off their top five without thinking.

  8. Write the boilerplates last. They’re secretly a test. If the 25-word version won’t come, something earlier isn’t finished.

A filled-in example

To show how the blocks connect, here’s the template filled in for Ledgerline. Ledgerline is a made-up product, not a client, and every detail below is invented.

Block

Ledgerline (illustrative)

Positioning

For finance teams at mid-size companies who close the books with spreadsheets and email, Ledgerline is accounts payable software that gets invoices approved and paid without chasing. Unlike adding AP to the ERP, it is set up in a week and approvers never need to log in.

Buyer

Finance controller. Goal: close on time. Pain: invoices stuck with approvers. Words: “chasing approvals”, “month-end crunch”.

User

AP clerk. Goal: fewer manual entries. Pain: retyping invoices.

Blocker

IT. Worry: another system to secure. Reassured by: SSO, access controls, a security page.

Core message

Invoices get approved and paid on time, without anyone chasing. Headline: “Stop chasing invoice approvals.”

Pillars

1. Approvals happen where people already work. 2. Invoices enter themselves. 3. You can see every invoice’s status at any moment.

Proof

1. Approve from email or Slack, demo video. 2. Invoice capture, sample before and after. 3. Live status dashboard, screenshot. Customer proof: [none yet, gap to close].

Objections

“We already have an ERP.” Ledgerline sits on top and syncs both ways. “Approvers won’t adopt it.” They never log in.

Words

Use: approvals, on time, chasing. Avoid: “revolutionise”, “AI-powered” as a headline, “seamless”.

25 words

Ledgerline is accounts payable software for mid-size finance teams. Invoices enter automatically, approvers sign off from email or Slack, and nothing waits on a reminder.

Draw it as a messaging house and the core message is the roof, the pillars are the columns, and proof is the foundation. Notice the proof row has a gap. We left it there deliberately. A real framework shows its gaps, so the team knows exactly which customer story to go and get.

How does a messaging framework become website copy?

Most templates stop right here, and it’s also where a lot of website projects go wrong. Before anybody designs a page, map each block to the place it’ll show up.

Framework block

Where it goes on the website

Core message, headline version

Homepage H1

Core message, full sentence

Homepage subhead, meta description

Buyer profile

Who the homepage speaks to; the first solutions page

Pillars

Homepage feature sections, one per pillar, in order

Proof

Next to each pillar: screenshots, demo clips, customer quotes, numbers

Objections

FAQ sections, pricing page, demo page, security page

Blocker profile

Security or trust page, integrations page

Words to use and avoid

The brief for every writer and designer

10-word boilerplate

Social bios, directory listings, page titles

50 and 100-word boilerplates

About page, press page, review sites, partner listings

Working on a single landing page? The SaaS landing page messaging framework shows the order these go in. For the whole site, the SaaS website structure guide covers which pages need to exist first.

Building it by audience

You don’t need a separate framework for every buyer. Keep the positioning statement and core message as they are, then add a column per audience for pillars, proof and objections. That’s what most people mean by a messaging matrix. It pays off when buyers want different things from the same product, and a finance controller and a CIO often do. One warning sign: if you’re on your fourth audience column, you may actually have two products, or two positions, and that’s a bigger conversation.

Messaging house, matrix or canvas: which should you use?

  • Messaging house: core message on the roof, pillars as columns, proof as the foundation. Best for one product and one main buyer.

  • Messaging matrix: the same blocks with a column for each audience. Best when there are several buyers.

  • Value proposition canvas (from Strategyzer): maps customer jobs, pains and gains onto your product. Handy for working out pillars before you write the framework.

The Eight Block template works as a house. Add audience columns to blocks 4 to 6 and you’ve got a matrix.

Where messaging frameworks go wrong

  • Writing it from the product team’s side. Lots of features, no benefits anywhere. Start from how buyers talk.

  • Pillars without proof. Every claim needs a demo, a number, a story or a source.

  • Too many pillars. Get to five and nobody remembers a single one.

  • No owner. Written once for a launch, then never opened again.

  • Never tested. The team loves it. Buyers have never laid eyes on it.

Also read: Product Messaging for AI Startups, SaaS Website Messaging Audit, How to Explain Your AI Product on Your Website.

Keeping it current

A framework nobody opens goes stale fast. Put a quarterly review in the calendar, plus an extra one whenever something big moves (a new product, buyer, competitor or price). The owner’s name and the next review date go at the bottom, where nobody can miss them.

Before a website launch, test it on real people. Five who look like your buyer is enough. Show them the core message and pillars and ask them to explain the product back to you. The places they hesitate are the places to rewrite.

Want help turning your framework into a website?

Send us your messaging framework, finished or half done, and we’ll show you where each block should live on your site. Book a messaging review · See our work

Messaging framework FAQs

1. What is a messaging framework?

Think of it as the rulebook for how a company talks about its product. Ours has the positioning statement, audiences, a core message, three or four pillars with proof, objections and answers, words to use and avoid, and ready-made descriptions at a few lengths. It stays internal. The copy comes out of it.

2. What should a messaging framework include?

We use eight blocks: positioning statement, audience profiles, core message, three or four pillars, proof for each pillar, common objections with answers, words to use and avoid, and boilerplates at 10, 25, 50 and 100 words. Leave one out and it usually shows up later as an argument.

3. Who owns the messaging framework?

Usually the product marketing manager. Without one, the founder or head of marketing takes it on. Sales, product and customer interviews supply the material, and leadership signs off on the positioning part.

4. What is a messaging house?

It's a way of drawing the framework. The core message is the roof, the pillars hold it up, and the proof points are the foundation. It's at its best for one product sold to one main buyer.

5. What is the difference between a messaging framework and a positioning statement?

The positioning statement is a sentence or two on who the product's for, what it is and how it's different. The framework starts from there and adds everything else you need to talk about the product: pillars, proof, objections, wording.

6. How long should a messaging framework be?

For most B2B companies, two to four pages does it. Any longer and people quietly stop reading. Keep each block tight and link out to the detail, like full customer stories.

7. How often should you update a messaging framework?

Look at it quarterly. Update it whenever something big shifts, like a new product, buyer, competitor or pricing change. Write the owner and next review date at the bottom so it doesn't get forgotten.

8. How do you test messaging before a website launch?

Show the core message and pillars to five people who look like your buyer and ask them to explain the product back. Listen to sales calls for objections that keep resurfacing. Whatever people misread, fix it before anyone writes page copy.

About the author

Jenish is a designer at Kraftbase, a product messaging and UI/UX design studio in Vadodara, India, that helps AI and B2B SaaS teams in the US, UAE and India explain and design what they’ve built.

Sources

  • Eight Block Messaging Framework and the block-to-website map: Kraftbase framework, not a published standard. The positioning statement format is adapted from Geoffrey Moore, Crossing the Chasm.

  • Ledgerline is a made-up product used for illustration

Messaging review

Want help turning your framework into a website?

Send us your messaging framework and we will show you where each block should live on your site.