How we build a B2B messaging framework and put it to work in 90 days

Your homepage rewrite is waiting on a sentence your leadership team still can't agree on.

You could put another meeting on the calendar. You could ask AI for twenty versions. Neither gives you a way to decide which version is true.

That's where a messaging engagement should start: with the disagreement underneath the sentence. Who needs you? What are they struggling with? Why would they change what they're doing? What can you prove?

At PitchKitchen, we use the first month of a 90-Day Magnetic Messaging Sprint to answer those questions and document the answers in a Magnetic Messaging Framework. The second month turns that framework into a homepage, a sales deck and an AI Brand Twin. The third puts the agreed assets into use and teaches the team to work from them.

Here's how the work moves from one phase to the next, including what you should be able to inspect before moving on. These week ranges describe our working sequence. The signed scope, access to your team and the speed of decisions determine your actual calendar.

Week 1: What is your company telling buyers today?

We begin with the materials already doing the talking: your website, sales deck, proposals, relevant customer evidence and recorded sales conversations you can share.

We read them together. A homepage can sound reasonable on its own and still contradict the explanation your best salesperson gives on a call. A deck can describe the product accurately while leaving the buyer to figure out why the problem deserves attention this quarter.

The Messaging Audit and Sales Engagement X-Ray make those gaps visible. We look for claims without support, different descriptions of the same offer, a category that puts you beside the wrong alternatives, and a problem that your team assumes the buyer already understands.

Your job in this phase is to give us access to the real material. Include the proposal that lost and the call that went nowhere. An archive of your best performances leaves out the evidence we need.

What you can inspect: a diagnostic tied to actual pages, slides and conversations. You should be able to point to each finding and see what produced it.

Weeks 2-3: What does each person know that isn't in the company story?

We work with the people who hold different parts of the truth. That usually includes the founder, sales leadership, marketing and product. The roles matter more than the titles.

The shared workshop surfaces the questions the team must settle. Confidential one-on-one Messaging Therapy intakes give people room to explain what they actually believe, including where they disagree with the public version.

We ask what buyers were doing before they hired you. We ask which alternatives they considered, what made staying put costly, and what changed after they bought. Where customer interviews are part of the agreed scope, those conversations test the internal account. Existing customer evidence also helps distinguish a belief from a supported claim.

This work can challenge the founder's favorite explanation. A technical advantage may be real without being the reason someone signs. A phrase everyone inside understands may mean nothing to the person approving the budget.

What you can inspect: a clear account of the buyer's problem, the alternatives, your defensible difference and the disagreements still open. An unresolved issue gets named. It doesn't disappear into polished copy.

Week 4: What goes into the Magnetic Messaging Framework?

The Magnetic Messaging Framework turns those decisions into a source the whole company can use.

It defines the category you want buyers to understand, the problem you're taking on, the change from the old way to the new way, and the outcome you can credibly help create. It connects those decisions to your positioning, key messages, proof, voice and sales language.

A useful framework explains why a message is there. If the document simply lists three attractive headlines, the next person who writes your homepage has to make the strategic decision again.

We review the framework with the people who will stand behind it. Disagreement now is useful. Discovering the same disagreement after the homepage is built means paying to change the same decision in several places.

A practical review question: can a salesperson explain why a buyer should act, using the framework, without asking the founder to join the call?

What you can inspect: the written framework, the evidence behind important claims and the decisions your leadership team has accepted. It becomes the approved source for the next phase. For the underlying structure, read What is the Magnetic Messaging Framework, and how is it different from positioning or brand strategy?.

Weeks 5-6: How does the framework become a homepage and sales deck?

We translate the approved story into the assets a buyer and a salesperson will actually use.

The homepage has to work when nobody from your company is there to explain it. It needs to establish who the offer is for, the problem that makes it relevant, why your approach deserves consideration and what the visitor can do next.

The sales deck has a different job. Our Discovery Prompter deck helps the salesperson investigate the buyer's situation and connect the story to it. Reading the homepage aloud in a meeting would miss that opportunity.

Both draw from the same framework. They don't need identical sentences. They need consistent answers.

The contracted scope matters here. A homepage wireframe, approved copy, a built site and a public launch are different deliverables. Before kickoff, make sure your agreement says which you're buying, who controls the website and who approves launch. A design sitting in a review folder hasn't replaced the old story yet.

What you can inspect: the homepage and deck beside the framework. For every major claim, you should be able to trace the reasoning back to an agreed decision.

Weeks 7-8: How do we teach AI to use the same messaging?

Once the framework is approved, we use it to configure your AI Brand Twin: an assistant with your company's messaging, voice, evidence and working instructions as context.

Your team can use the supported AI tools where it already works. The important part is maintaining the same approved source and testing the outputs. Sharing a framework across tools doesn't give them a shared memory or guarantee that every answer will be accurate.

We test with real work: a follow-up email, an explanation of the offer, an objection from a sales call, a short piece of content. We check whether the answer represents the buyer correctly, uses supported claims and sounds like your company.

We also test what happens when information is missing. An assistant that invents a customer result to finish a paragraph needs correction before it handles more work.

Someone on your team owns changes to the source. Otherwise, a revised promise can reach one assistant while the others keep repeating last month's version. How do we get every AI tool our team uses to follow our messaging framework? explains that maintenance problem in more detail.

What you can inspect: a configured assistant, representative test outputs and a named person responsible for keeping its source current.

Weeks 9-11: Where will buyers encounter the new story?

The third month puts the agreed messaging into the channels included in your scope.

That can include a problem-focused scorecard, a useful downloadable resource, an email sequence, a thought-leadership webinar format and an answer-engine content plan. The selection follows your buyer and the job you need those assets to do.

A lead magnet should help someone understand their problem. An email needs a reason for that particular reader to care. A webinar should develop an argument worth discussing. Producing all three doesn't establish that any of them will generate qualified conversations.

Each asset therefore needs an owner, an intended audience, a review decision and a way to tell whether it worked. Launch also means checking the practical details: the form, the destination, access, follow-up and who will respond.

The same care applies to AI visibility. Clear, supported content gives answer engines better material to find and describe. It doesn't give us control over whether an engine recommends your company.

What you can inspect: the agreed assets and their operating plan. A prepared email sequence is ready for review. It isn't sent merely because the copy is finished.

Week 12 and the final days: Can your team use this without you translating it?

We teach the team to work with the framework, the deck and the AI Brand Twin in real situations. A recording gives people a way to revisit the training, but using the tools is the test.

Ask a salesperson to prepare for an actual opportunity. Ask marketing to draft something from the framework. Have the person maintaining the AI assistant make a small approved update and check its effect. Where someone gets stuck, clarify the source or the workflow.

Then review what exists, what has been approved, what is live and what still needs an action. Those are different states. Every remaining action needs an owner.

Agree on what you'll measure after launch. Buyer comprehension, qualified conversations, progression through the sales process and win rate can inform that review. Changes in those numbers have several possible causes. Finishing a messaging sprint doesn't prove that messaging caused a revenue change.

You should leave with the agreed assets, access to them and a team that knows how to use and maintain them.

That's the job of the 90-Day Magnetic Messaging Sprint: carry a defensible company story through the decisions, the materials and the people responsible for bringing it to buyers.

Start with your current homepage. The Brand Signal Score gives you a concrete place to examine what it's saying today.