Sales Messaging Framework: Build One From Your Website and Documents

A sales messaging framework is a written record of how your company talks about itself: what you do, who you do it for, the proof behind it, how you answer objections and which words you use or avoid. Many companies never write theirs down. Founders carry it in their heads, and every new rep, agency or AI tool invents its own version. AvairAI's Knowledge Base builds a first draft from your website and documents in a few minutes, checks every claim against your own material and uses the result in every email and call script it writes.

Key takeaways

• A framework is a working document. It earns its place only when outreach reads it.
• You already have the raw material. Your website, decks, one-pagers and customer stories hold most of the answers.
• Every claim needs a source. A figure, a customer name or a competitor weakness that your material does not support should be left out.
• Gaps should become questions. What cannot be confirmed goes on a list for a person to answer, not into a message.

Why outreach drifts without a messaging framework

Ask three people on a sales team to describe what the company does and you will often get three answers. The founder leads with the problem. The newest rep leads with a feature. The agency writing the emails leads with whatever the last client liked.

The cost shows up in outreach. Emails make claims that do not match the website. A rep quotes a number that marketing dropped a year ago. An AI writing tool fills a gap with a confident statistic that nobody measured. Each one is small, and together they teach prospects that your messages cannot be trusted.

The usual fixes have their own problems:

| Approach | Where it falls short | |---|---| | Agency messaging project | Weeks of interviews and a large fee, then the document goes stale | | Wiki page or slide deck | Written once and never read by the tools that write outreach | | Brand guidelines | Cover tone and logos, not buyer problems, proof or objections | | Prompting an AI tool by hand | Every rep writes a different prompt, and unverified claims slip through |

What a sales messaging framework should contain

Published guides agree on the core. Close's guide to sales messaging lists the pain points your prospects face, a product description of three sentences or fewer, a value proposition, proof that the product solves the main pain points, evidence of value from current customers and responses to common objections. It also suggests starting with an ideal customer profile and writing a separate document for each segment, no more than two at first.

AvairAI's framework covers the same ground in more detail. It has 19 sections, which fall into five groups:

• Who you are. Positioning, brand lines and boilerplate, voice and tone and what you believe.
• What you say. Differentiators ranked by how hard they are to answer, solutions written for the economic buyer, use cases and buying triggers.
• Who you say it to. Personas, the ideal customer, who the product is not for and the buying committee.
• Why anyone should believe it. Proof with a source on every figure, customer outcomes and objections in the buyer's own words, each with an answer.
• How it gets used. Words to use and words never to say, outbound assets such as subject lines and opening lines, pricing notes and the open questions.

A useful test for any section is to ask whether a new rep could use it on their first call. If the answer is no, the section is too vague.

Build it from material you already have

The slow part of a messaging project is the interviews. Most of the answers already exist in places your company has published or shared.

AvairAI reads those places in order of trust:

1. A messaging document you upload, if you have one.
2. Your other documents, such as decks, one-pagers and pricing sheets.
3. Your website, up to 20 pages per build.
4. Your Use Case library and company profile.

The steps are short. Open Account, then Knowledge Base, then Messaging, and click Build from website and documents. If your Messaging tab is empty, the first build starts on its own after AvairAI reads your website. A build takes a few minutes, and you can leave the page while it runs. When it finishes, each section shows Generated, Edited or Empty. The tab opens on the first section with a question for you.

The Knowledge Base around it holds the rest of what every campaign needs: a company profile, a library of customer stories, your documents and default campaign settings. You tell AvairAI about your company once, and every campaign starts from it. Each company in an account has its own Knowledge Base, so an agency's clients never mix.

Check every claim, not only the tone

Most drafting tools check grammar and tone. A messaging framework needs a stricter test, because what it says ends up in front of buyers.

Brand risk is one reason. The law is another. In the United States, the FTC's advertising substantiation policy expects a company to have a reasonable basis for an objective claim before it makes the claim. A made-up percentage in a cold email is the kind of claim that rule is aimed at.

AvairAI drafts each group of sections and then has every item checked against a fact sheet taken from your own material. Each item passes, is fixed or is left out. Three rules apply:

• A figure stays only if your material states it.
• A customer is named only if your material names them.
• A competitor weakness is never invented.

Here is a worked example. Your website says customers "cut onboarding time by 40%" and gives no source. The build does not put that figure into the proof section. It leaves it out and adds a question to the Open questions list: where does the 40% come from? Once someone in marketing adds the source and approves the row, the figure can appear in outreach. Until then, it cannot.

After each build AvairAI tells you what it left out ("We left out N items we could not confirm against your material") so you can add back anything that is right.

This is the same idea Pam Didner gives for any framework: have the product team vet the draft so that features and benefits are described accurately, and expect legal review where claims rest on benchmark data. The difference is that the first pass happens in minutes and the questions come with the draft.

Open questions beat hidden gaps

Every framework has holes. A weak one hides them behind confident wording. AvairAI turns each hole into a question.

If your material has no proof for a differentiator, the section says so. If it cannot tell who the economic buyer is, you get a question about that. You answer in the app or in the Word document, and the next build uses your answers.

You can also export the framework. Download (.docx) produces a structured Word document with a cover, a contents page, one section per page, a status line on each section and fill-in lines for what only your company can supply. Complete it, upload it back as a Messaging framework document and the next build treats it as its most trusted source. It also works as a one-document briefing for a new rep, agency or partner.

Put the framework to work in every email and call script

A framework in a shared drive does not change what gets sent. Dock's guide to sales messaging makes the same point from the sales side: a framework does not fix messaging on its own, and consistency comes from building it into the tools and workflows reps already use.

That is the job the Knowledge Base does inside AvairAI. For each new email and call script, the writer gets your positioning, personas, differentiators, approved proof, objection answers, pricing notes and your lists of words to use and words never to say. The campaign's own Use Case, angle, call to action and content style still come first.

Three details matter here:

• Proof reaches outreach only once approved. A figure you write yourself is approved when you save it. A figure AvairAI found waits for someone on your team.
• Some sections stay internal. Competitors, who the product is not for, the buying committee, voice and tone and the open questions never reach outreach. Competitors are used to choose angles and are never named in a message.
• Replies use the same material. When a campaign is set to write a reply for a rep to approve, the draft can use your objection answers, pricing notes, documents and Use Cases, and nothing else. A prospect who asks about price can be answered from your own pricing notes.

The framework also shapes the rest of the platform. Persona titles feed contact selection, and your solutions, triggers and personas feed the Playbook. Which accounts to target is still decided by Pain-Signal Targeting. The framework shapes what your outreach says and to whom it speaks.

Keep it current without a project

Frameworks go stale because updating them is a project. Here, it is a rebuild.

• Add a document or update your website, then build again.
• A build fills only empty or generated sections. Sections you edited are marked Edited and are kept unless you choose Replace my edits.
• Proof you approved is always kept.
• Admins build and edit the framework. Everyone on the team can read and download it.

When several people create campaigns, team roles keep the edits with Admins, and every new campaign still starts from the same checked facts. The campaign setup checklist and the Launch Readiness score then check the campaign you build from it.

Where a framework does not help

Here is what it does not do:

• It does not choose your target accounts. That comes from Pain-Signal Targeting.
• It does not replace judgment. A person still needs to read the draft, answer the open questions and approve the proof.
• It cannot confirm what your material does not say. If your website and documents are thin, the first draft will be short and the question list long.
• Several sections, such as what you believe, fill the framework and the Word document but do not feed emails today.

How to start

1. Open Account, then Knowledge Base and enter your website.
2. Click Read my website and fix anything in the profile that is wrong.
3. Upload your best deck, one-pager or pricing sheet on the Documents tab.
4. Open Messaging and click Build from website and documents.
5. Answer the open questions, approve the proof you want used and save.
6. Create a campaign and read the first email against the framework.

The Knowledge Base and the Messaging Framework are part of Company Knowledge on every plan, including the trial. Start a free trial and see what your own website says about you.

Frequently asked questions

What do I need to build a messaging framework in AvairAI?

Only your website. Documents such as decks, one-pagers and an existing messaging document make the result richer.

How long does a build take?

A few minutes. You can leave the page while it runs.

Will AvairAI make up claims about my product?

No. Each item is checked against your own material. Numbers, customer names and competitor names that your material does not support are removed and listed.

If I build again, will it overwrite my edits?

No. A build fills only empty or generated sections. Your edited sections and approved proof are kept unless you choose Replace my edits.

Are my competitors named in outreach?

No. The Competitors section is internal and is used only to choose angles.

How do figures get into my emails?

Only after someone on your team approves the proof row. A figure you write yourself is approved when you save it.

Can I use the messaging document I already have?

Yes. Upload it as a Messaging framework document. The next build treats it as its most trusted source.

Can I keep each brand's messaging separate?

Yes. Each company in your account has its own Knowledge Base and its own framework.