A landing page is usually written the wrong way round. Someone opens a template, fills sections with features, then tries to find a headline that covers them. The page ends up saying everything and promising nothing, and the visitor who clicked an ad for one thing finds a page about five.
This guide shows you a SaaS landing page messaging framework you can use before you write or design a word. You will get a six line brief, a fill in template, a worked example, a section map and a test.
Key takeaways
Write the page from one promise. Every section either supports it or goes.
Fill six lines before any copy: buyer, trigger, promise, proof, objection and action.
Match the page to the source. A visitor from an ad or email should see the same promise they clicked.
Answer the doubt that stops the buyer, not every possible question.
Test the brief on a stranger before you build the page.
What is a landing page messaging framework?
A landing page messaging framework is a short structure that decides what a page says before anyone writes it. It turns a loose idea into a few decisions you can check.
A homepage serves many visitors with many questions. A landing page usually serves one group arriving from one source, such as a search ad, a campaign email or a partner link, for one purpose. That narrower job means the message can be much sharper.
If you have not settled who the product is for, do that first. See Positioning an AI Agent Product and Product Messaging for AI Startups.
What is the Six Line Page Brief?
The Six Line Page Brief is six sentences, one per line. Together they hold everything the page needs to say.
Line | The question it answers | Example form |
|---|---|---|
1. Buyer | Who is this page for? | “Operations leads at 50 to 500 person companies” |
2. Trigger | What made them look today? | “Month end close takes them a week” |
3. Promise | What will change? | “Close the books in two days” |
4. Proof | Why believe it? | A customer, number or screen |
5. Objection | What stops them? | “Will it work with our ERP?” |
6. Action | What should they do next? | “See it on your data” |
The promise is the center. Lines 1 and 2 decide who hears it and when. Lines 4 and 5 make it believable, and line 6 turns belief into a step.
Pro tip: Write the six lines as plain sentences with no marketing words. If a sentence would sound odd said aloud to a customer, rewrite it.
How do you match the page to where the visitor came from?
Repeat the promise the visitor clicked, in the same words, near the top of the page. A mismatch between the ad and the page is one of the quickest ways to lose a visit.
Source | What the visitor expects | What the page should do |
|---|---|---|
Search ad or result | The answer to their query | Echo the query in the headline |
Campaign email | The offer described in the email | Lead with that offer |
Partner or review site | Context from the referrer | Mention the context and the fit |
Social post | The idea in the post | Pick up the same idea in the first line |
If you run several sources to one page, the page will blur. Make one page per promise where it pays off, even if the pages share most of their sections.
How do you turn the six lines into sections?
Give each line a section, in the order a buyer asks the questions. Then cut any section that does not serve the promise.
Section | Built from | Job |
|---|---|---|
Hero | Buyer, promise, action | Say who it is for and what changes |
The problem | Trigger | Show you understand their situation |
How it works | Promise | Show the product doing the job |
Proof | Proof | Back the promise with evidence |
Doubts | Objection | Answer the one that stops them |
Final action | Action | Repeat the step, with reassurance |
Pages that grow past this usually carry a second promise. Make it a second page.
What does a worked example look like?
This example uses an invented product, Tallyfold, a made up month end close tool. It is not a real company, and the numbers are illustrative.
Line | Tallyfold brief |
|---|---|
Buyer | Finance and operations leads at mid sized companies |
Trigger | The monthly close takes more than a week and ends in a rush |
Promise | Close the books in two days |
Proof | A customer story with before and after close times (illustrative) |
Objection | Will it connect to our accounting system? |
Action | See it on your own data |
From this, the hero reads: “Close the books in two days. Tallyfold matches transactions and flags exceptions for finance teams at mid sized companies.” The doubts section opens with the objection: “Works with the accounting systems you already use.” Nothing else on the page needs to exist unless it serves the promise.
What should go in the headline?
The headline states the promise from line 3 in the buyer’s words, and the subhead names the buyer from line 1 and how the product does it.
For everything else the first screen must carry, read Above the Fold for SaaS.
Why does landing page messaging fail?
It usually fails because the page starts from features, makes two promises or does not match the ad the visitor clicked. Six mistakes in detail:
Starting from features. The page describes the product, not the change.
Two promises on one page. Neither lands.
No message match. The visitor does not see what they clicked.
Answering every doubt. The page grows and the real objection is buried.
Proof far from the claim. Evidence the visitor never connects to the promise.
A vague action. “Learn more” does not say what happens.
How do you test the brief before you build?
Read the six lines to five people who match your buyer, then ask them three questions.
Say the promise and ask: would that matter to you, and why?
Say the objection and ask: is that what would stop you?
Say the action and ask: would you do that, or something else first?
Pass if four of five react to the promise and name your objection.
Rewrite the lines they did not react to, then build.
Pro tip: If the buyer names a different objection from yours, believe the buyer. The real objection is often about trust or effort, not features.
Also read: AI Homepage Messaging Mistakes: 7 Fixes From Three Real Teardowns, SaaS Website Messaging Audit.
To see messaging and design built together, read our ORYN AI agent monitoring landing page case study, or browse all of our case studies.
What is the one promise of your page?
Send us a page and we will write its six line brief. Book a messaging review · See our work
SaaS landing page messaging FAQs
It is a short structure that decides what a landing page says before it is written. A good one fixes the buyer, the trigger, the promise, the proof, the objection and the action, so every section supports one message and the page does not drift into a list of features.
Fill a six line brief first: buyer, trigger, promise, proof, objection and action. Turn each line into a section in the order a buyer asks questions, state the promise in the headline in the buyer’s words and show the product beside it. Cut anything that does not support the promise.
As long as it takes to answer the buyer’s questions in order, and no longer. Many strong pages have six sections or fewer, because they carry one promise. If a page keeps growing, it probably holds a second promise and should become two pages.
Message match means the page repeats the promise the visitor clicked, in the same words, near the top. If an ad says one thing and the page says another, visitors feel they landed in the wrong place and leave. Make one page for each distinct promise.
Yes. Kraftbase is a product messaging and UI/UX design studio for AI and B2B SaaS companies. We write the message and design the page together, so the promise, proof and layout come from one brief.
A homepage serves many visitors with many questions, while a landing page usually serves one group, from one source, for one purpose. That narrower job lets a landing page be shorter and sharper, with one promise and one action.
Read the brief to five people who match your buyer and see whether they react to the promise and name your objection. After launch, compare conversion against a baseline from the same source. Change one thing at a time so you know what moved the result.
About the author
Dhaval Agrawal is the founder and CEO of 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
Six Line Page Brief: Kraftbase framework, not a published standard
Tallyfold is an invented example, not a real company
Messaging review
What is the one promise of your page?
Send us a page and we will write its six line brief.
A landing page is usually written the wrong way round. Someone opens a template, fills sections with features, then tries to find a headline that covers them. The page ends up saying everything and promising nothing, and the visitor who clicked an ad for one thing finds a page about five.
This guide shows you a SaaS landing page messaging framework you can use before you write or design a word. You will get a six line brief, a fill in template, a worked example, a section map and a test.
Key takeaways
Write the page from one promise. Every section either supports it or goes.
Fill six lines before any copy: buyer, trigger, promise, proof, objection and action.
Match the page to the source. A visitor from an ad or email should see the same promise they clicked.
Answer the doubt that stops the buyer, not every possible question.
Test the brief on a stranger before you build the page.
What is a landing page messaging framework?
A landing page messaging framework is a short structure that decides what a page says before anyone writes it. It turns a loose idea into a few decisions you can check.
A homepage serves many visitors with many questions. A landing page usually serves one group arriving from one source, such as a search ad, a campaign email or a partner link, for one purpose. That narrower job means the message can be much sharper.
If you have not settled who the product is for, do that first. See Positioning an AI Agent Product and Product Messaging for AI Startups.
What is the Six Line Page Brief?
The Six Line Page Brief is six sentences, one per line. Together they hold everything the page needs to say.
Line | The question it answers | Example form |
|---|---|---|
1. Buyer | Who is this page for? | “Operations leads at 50 to 500 person companies” |
2. Trigger | What made them look today? | “Month end close takes them a week” |
3. Promise | What will change? | “Close the books in two days” |
4. Proof | Why believe it? | A customer, number or screen |
5. Objection | What stops them? | “Will it work with our ERP?” |
6. Action | What should they do next? | “See it on your data” |
The promise is the center. Lines 1 and 2 decide who hears it and when. Lines 4 and 5 make it believable, and line 6 turns belief into a step.
Pro tip: Write the six lines as plain sentences with no marketing words. If a sentence would sound odd said aloud to a customer, rewrite it.
How do you match the page to where the visitor came from?
Repeat the promise the visitor clicked, in the same words, near the top of the page. A mismatch between the ad and the page is one of the quickest ways to lose a visit.
Source | What the visitor expects | What the page should do |
|---|---|---|
Search ad or result | The answer to their query | Echo the query in the headline |
Campaign email | The offer described in the email | Lead with that offer |
Partner or review site | Context from the referrer | Mention the context and the fit |
Social post | The idea in the post | Pick up the same idea in the first line |
If you run several sources to one page, the page will blur. Make one page per promise where it pays off, even if the pages share most of their sections.
How do you turn the six lines into sections?
Give each line a section, in the order a buyer asks the questions. Then cut any section that does not serve the promise.
Section | Built from | Job |
|---|---|---|
Hero | Buyer, promise, action | Say who it is for and what changes |
The problem | Trigger | Show you understand their situation |
How it works | Promise | Show the product doing the job |
Proof | Proof | Back the promise with evidence |
Doubts | Objection | Answer the one that stops them |
Final action | Action | Repeat the step, with reassurance |
Pages that grow past this usually carry a second promise. Make it a second page.
What does a worked example look like?
This example uses an invented product, Tallyfold, a made up month end close tool. It is not a real company, and the numbers are illustrative.
Line | Tallyfold brief |
|---|---|
Buyer | Finance and operations leads at mid sized companies |
Trigger | The monthly close takes more than a week and ends in a rush |
Promise | Close the books in two days |
Proof | A customer story with before and after close times (illustrative) |
Objection | Will it connect to our accounting system? |
Action | See it on your own data |
From this, the hero reads: “Close the books in two days. Tallyfold matches transactions and flags exceptions for finance teams at mid sized companies.” The doubts section opens with the objection: “Works with the accounting systems you already use.” Nothing else on the page needs to exist unless it serves the promise.
What should go in the headline?
The headline states the promise from line 3 in the buyer’s words, and the subhead names the buyer from line 1 and how the product does it.
For everything else the first screen must carry, read Above the Fold for SaaS.
Why does landing page messaging fail?
It usually fails because the page starts from features, makes two promises or does not match the ad the visitor clicked. Six mistakes in detail:
Starting from features. The page describes the product, not the change.
Two promises on one page. Neither lands.
No message match. The visitor does not see what they clicked.
Answering every doubt. The page grows and the real objection is buried.
Proof far from the claim. Evidence the visitor never connects to the promise.
A vague action. “Learn more” does not say what happens.
How do you test the brief before you build?
Read the six lines to five people who match your buyer, then ask them three questions.
Say the promise and ask: would that matter to you, and why?
Say the objection and ask: is that what would stop you?
Say the action and ask: would you do that, or something else first?
Pass if four of five react to the promise and name your objection.
Rewrite the lines they did not react to, then build.
Pro tip: If the buyer names a different objection from yours, believe the buyer. The real objection is often about trust or effort, not features.
Also read: AI Homepage Messaging Mistakes: 7 Fixes From Three Real Teardowns, SaaS Website Messaging Audit.
To see messaging and design built together, read our ORYN AI agent monitoring landing page case study, or browse all of our case studies.
What is the one promise of your page?
Send us a page and we will write its six line brief. Book a messaging review · See our work
SaaS landing page messaging FAQs
It is a short structure that decides what a landing page says before it is written. A good one fixes the buyer, the trigger, the promise, the proof, the objection and the action, so every section supports one message and the page does not drift into a list of features.
Fill a six line brief first: buyer, trigger, promise, proof, objection and action. Turn each line into a section in the order a buyer asks questions, state the promise in the headline in the buyer’s words and show the product beside it. Cut anything that does not support the promise.
As long as it takes to answer the buyer’s questions in order, and no longer. Many strong pages have six sections or fewer, because they carry one promise. If a page keeps growing, it probably holds a second promise and should become two pages.
Message match means the page repeats the promise the visitor clicked, in the same words, near the top. If an ad says one thing and the page says another, visitors feel they landed in the wrong place and leave. Make one page for each distinct promise.
Yes. Kraftbase is a product messaging and UI/UX design studio for AI and B2B SaaS companies. We write the message and design the page together, so the promise, proof and layout come from one brief.
A homepage serves many visitors with many questions, while a landing page usually serves one group, from one source, for one purpose. That narrower job lets a landing page be shorter and sharper, with one promise and one action.
Read the brief to five people who match your buyer and see whether they react to the promise and name your objection. After launch, compare conversion against a baseline from the same source. Change one thing at a time so you know what moved the result.
About the author
Dhaval Agrawal is the founder and CEO of 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
Six Line Page Brief: Kraftbase framework, not a published standard
Tallyfold is an invented example, not a real company
Messaging review
What is the one promise of your page?
Send us a page and we will write its six line brief.