How to Build a B2B Sales Messaging Playbook Your Team Will Use

Most B2B companies we meet in the Gulf and Egypt already have sales messaging. It lives in the sales director’s head, in a senior rep’s WhatsApp history, in a proposal someone wrote two years ago and in a few voice notes forwarded between colleagues. The result is predictable: five salespeople describe the company five different ways, new hires take months to sound credible, and marketing campaigns promise one thing while the first call says another.

A sales messaging playbook fixes this by putting the words in one place. It should be a short, bilingual source of truth that covers what you say, what you ask, what you can prove and how you answer the objections you hear every week, adapted for the four channels your team actually uses: calls, WhatsApp, email and LinkedIn. This guide gives you the structure, worked Arabic and English examples, and a 30-day rollout plan built around adoption rather than publication.

What the playbook is for, and what it is not

Complex purchases are decided by a group, and Gartner’s research on the B2B buying journey shows buyers spending only a small share of their time with any one supplier’s rep. Most of the decision happens when those people repeat your message to each other, so if your team’s message is inconsistent, the version that reaches the general manager is the weakest one. Our guide to content for every member of the buying committee covers the roles in more depth.

So the playbook has one job: make sure every rep, in every channel, gives a clear, consistent and provable answer to the questions buyers ask. It is different from two neighbouring tools:

• A sales kit holds the assets: profile, catalogue, datasheets, case sheets. The playbook holds the words that go around those assets. If you distribute products, our guide to sales kits for distributor teams covers the asset side.
• A CRM process defines stages and fields. The playbook tells the rep what to say and ask at each stage, so the CRM fills with real information instead of guesses.

If your team already ignores the materials you have, start with the causes before writing anything new. Why your sales team ignores the marketing materials you paid for walks through that diagnosis.

The six blocks of a sales messaging framework

Keep the core document to something a rep can read in fifteen minutes. Every block below should exist in English and Arabic, side by side, with one named owner who approves changes.

A one-page playbook template you can copy

Copy this table into a shared document and fill one row at a time. Leave a cell empty until you have the words or the evidence; an empty proof-point cell is more useful than an invented one.

Owner: ________   Version: ____   Last updated: ________   Approved by (sales and marketing): ________

Two rules keep the template honest: a proof point with an empty evidence cell is removed before rollout, and a row without its Arabic version is not finished. Every change raises the version number, so a rep can check that the quick reply they are using is the current one.

Qualifying questions: borrow a structure, write your own words

Two recognised frameworks are useful here. Neil Rackham’s SPIN Selling, built on his team’s study at Huthwaite of more than 35,000 sales calls, groups questions into Situation, Problem, Implication and Need-payoff. BANT (Budget, Authority, Need, Timeline) is a widely used qualification checklist. They do different jobs: SPIN shapes the conversation, BANT tells you whether the opportunity is real. Use SPIN-style questions for discovery and make sure the answers cover the BANT points by the end of the second or third conversation.

Proof points: only what you can show

The quickest way to lose a technical buyer is an unprovable claim. For each proof point, record where it comes from (certificate, project handover letter, test report, published figure) and whether the client named has agreed to be named. If a rep cannot attach the evidence within a day, the claim does not belong in the playbook.

Worked example: one message in Arabic and English

The lines below were written for this article. They use a hypothetical company: a distributor of fire pumps selling to MEP contractors in Riyadh and Cairo. Replace every detail with your own.

Positioning line

EN: We supply and support fire pumps for contractors who cannot afford a delayed handover, with stock confirmed before you price and engineers who come to site for testing.

AR (written, Saudi market): نورّد مضخات الحريق ونقدّم دعمها الفني للمقاولين الذين لا يحتملون أي تأخير في التسليم؛ نؤكّد توفّر المخزون قبل أن تسعّروا، ومهندسونا يحضرون إلى الموقع للاختبار والتشغيل.

AR (spoken, Egypt): إحنا بنورّد طلمبات الحريق ونتابعها مع المقاول لحد التسليم، بنأكّد لك المخزون قبل ما تسعّر، والمهندس بتاعنا بينزل الموقع وقت الاختبار.

Notice the differences. The written Arabic uses clear, modern standard phrasing that reads well in an email or proposal anywhere in the region. The spoken Egyptian version uses طلمبة, the word many Egyptian contractors use for a pump, and a conversational rhythm. Your playbook should hold the written version as the reference and give each market’s reps a spoken version they actually recognise.

Discovery questions (SPIN structure)

Objection answer: “Your price is higher than the other quote”

Use the same five-step structure for every objection: acknowledge, clarify, answer, prove, ask for the next step.

EN: That is worth checking. Is the gap on the unit itself, or on delivery, testing and commissioning? Our price includes site testing and the commissioning report your consultant will ask for. I can send you a line-by-line comparison today that you can share with the consultant.

AR (spoken, Saudi market): من حقك تقارن. الفرق في سعر المضخة نفسها، ولا في التوريد والاختبار والتشغيل؟ سعرنا يشمل الاختبار في الموقع وتقرير التشغيل اللي يطلبه الاستشاري. أقدر أرسل لك اليوم مقارنة بند بند تشاركها مع الاستشاري.

The answer does not defend the price or attack the competitor. It moves the conversation to scope, which is where a better offer is usually won, and ends with a concrete next step.

Adapting the message to calls, WhatsApp, email and LinkedIn

The substance stays the same across channels; length, order and format change. Build one section of the playbook per channel with ready-to-edit templates. For WhatsApp, the full sequence is set out in a WhatsApp sales flow from first message to quotation.

WhatsApp needs extra care: in our experience it is often the main sales channel in the region, and its rules are strict. Under the WhatsApp Business Messaging Policy, you may only contact people who have given you their number and opted in to receive your messages, you must respect requests to stop, and outside the 24-hour customer service window you can only send approved message templates. A playbook that encourages reps to forward broadcast offers to every contact in their phone puts the company’s number at risk.

Data protection law adds a second layer. Saudi Arabia’s PDPL Implementing Regulations require consent for direct marketing and an easy way to opt out, and SDAIA opened a public consultation in October 2026 on revising that consent framework; Egypt’s executive regulations under Law No. 151 of 2020 require prior explicit consent for electronic direct marketing, and the UAE has Federal Decree-Law No. 45 of 2021. Our explainer on PDPL consent for direct marketing in Saudi Arabia covers the detail. The practical rule for the playbook: follow-ups go to people who contacted you or agreed to hear from you, and every template makes it easy to say no.

Writing the Arabic version: adapt, do not translate

A playbook written in English and translated at the end usually sounds wrong in Arabic. Write both versions together, and settle these decisions early:

• Register. Use clear modern standard Arabic for written material that crosses borders, and market-specific spoken versions for calls and voice notes. In our experience, Gulf and Egyptian buyers notice quickly when a script was written for the other market.
• Technical terms. Decide which terms stay in English (model numbers, standards, many engineering terms) and which have an accepted Arabic word in your sector. List them in a short glossary so every rep uses the same ones.
• Forms of address. Agree how reps address engineers, owners and procurement officers in each market, and how formal the first message should be.
• Numbers and units. Choose one convention for digits, currency and units in written Arabic and apply it everywhere, including quotation emails.
• Review by sellers, not only translators. Have one strong rep in each market read every line aloud. If it does not sound like something they would say, rewrite it.

A 30-day rollout and sales team training plan

Most playbooks fail at rollout, not at writing. Plan the first month as a training programme with the playbook as its material.

1. Days 1 to 7: collect. Interview three or four top reps and the sales director. Listen to recorded calls or read real WhatsApp and email threads (with customer details removed). List the questions buyers ask and the objections that come up most. Gather proof points with their evidence.
2. Days 8 to 14: draft and test. Write the six blocks in both languages. Run two role-play sessions where reps use the draft on a colleague playing a difficult procurement officer. Cut anything nobody would say out loud.
3. Days 15 to 21: launch with practice. Hold a working session, not a presentation. Each rep delivers the positioning line, runs the four discovery questions and answers two objections. Load the channel templates where reps work: saved WhatsApp Business quick replies, email templates, a pinned document in the team’s shared folder.
4. Days 22 to 30: coach in the field. The sales director reviews two real conversations per rep each week against the playbook and gives one specific improvement. Collect new objections and phrases that worked, and record them for the first update.

Adoption checklist: is the playbook actually being used?

Publishing the document proves nothing. Check these points at the end of the first month and every quarter after:

• Every rep can say the positioning line from memory in their working language.
• Qualifying answers appear in the CRM for new opportunities, not only names and phone numbers.
• The WhatsApp quick replies and email templates in use match the current playbook version.
• Sales managers use the playbook in weekly pipeline or call reviews.
• New hires are trained on it in their first week and tested in a role-play before handling live inquiries.
• Marketing campaigns, the website and the playbook make the same promise.
• One owner approves changes, and the document shows the version and date of the last update.
• The objection list has been updated with something heard in the field this quarter.

If three or more items fail, the issue is usually ownership: nobody is accountable for keeping marketing and sales saying the same thing. For GCS, a new fire-safety and engineering-systems brand in Saudi Arabia, RX’s sales enablement work included prepared WhatsApp replies for the most common inquiries, message flows from first contact to quotation request, and tone and structure guidance the whole team could follow.

To find where your own message breaks, bring two real WhatsApp threads and your last lost quotation to a business diagnosis session. We will show where the wording changes between the campaign, the first reply and the proposal, and which part of the playbook to write first.