From the Buyer Who Champions You to a Message Sales Will Use: Positioning With IMPACT, CRAFT Content and Revenue Enablement

I have been part of 6+ rebrands and led two of them: QuantumStreet AI, where we rebranded a $7Bn AUM AI investment fund from Equbot with Digitas and IBM, and Airtel B2B, where I worked with Wolff Olins on the new B2B brand identity. Whatever the brand, positioning has to answer one question: what does the buyer compare you with? Usually it is doing nothing, the way they cope today, or the vendor they already pay.

Most positioning work goes wrong at both ends. It is written for the person who signs, when someone else carries the case to the signer, and it stops at a statement and a tagline. Sellers then write their own lines.

The workflow below stops only when the message exists as objection answers and discovery questions. Rolling it out to every role and channel is guide 11.

The order matters more than any one tool. The champion comes first because they repeat the message. The alternatives come second because an "unlike" line needs something real on the other side. Proof comes before wording, because a message without proof turns into adjectives.

One thing to plan for: the IMPACT tool that writes the message has no field for customer results. The proof you pin in the value step does not travel on its own, so you carry it across by hand, or type it into the benefit or differentiation field as that tool's own advice says.

The hand-offs at the end are where most teams stop too early. Every tool here reads only what you give it, so I state each input change between runs in the steps below.

Step 1. Find the person who will carry your case

Input to the champion tool: Cloudmoat, cloud security monitoring that ranks misconfigurations by real exposure; problem "too many cloud alerts and slow audit preparation"; target mid-size fintech and SaaS companies on two or more clouds; price $3,750 per month; sector set to cybersecurity.

What came back: the champion is the "SOC or cloud security lead", the economic buyer is the "CISO", and the "CIO or CTO checks integration". It also named two groups that teams often forget: risk, compliance and audit, who "rarely champion a purchase, but each can stop one", and security engineers as daily users, with the note that their answer to what a good week looks like "is your first proof point".

How to read it: the champion's measures are your vocabulary: time to prepare an audit, alerts per analyst, audit findings and critical exposures open. The cloud security lead will use those words in the CISO's office, so the message must use them too.

One layout quirk: the questions headed "Technical Influencer Discovery Questions" are printed after the reviewers paragraph. They belong to the CIO or CTO, not to audit.

Step 2. Map what the champion uses today

Input: competitors Competitor A, Competitor B, "periodic manual cloud audits" and "native cloud provider security consoles"; strengths "exposure-based ranking; one view across three clouds"; my notes on weaknesses, "Competitor A: long rule lists with no order to fix them" and "Competitor B: covers one cloud well and the others thinly".

What came back: "Cloudmoat is mapped against 3 competitors you named and 1 way your buyers cope without a vendor." It filed the manual audits as the status quo and the native consoles as a competitor card, noting they are "not a company name". It added do nothing as the alternative "every deal faces", and it said my strengths answered none of my notes: "your product text answers none of them by its words".

For the second run I changed two inputs: I dropped the native consoles, and I rewrote the strengths as answers ("ranks every misconfiguration in the order to fix it; one view that covers all three clouds"). It then mapped "2 competitors you named and 1 way your buyers cope without a vendor", and matched one note: for Competitor B, "your strength "one view that covers all three clouds" (your words) answers it". Read that line as a prompt to check your wording, not as a verdict on your product.

How to read it: the tool states that "nothing about a competitor was looked up", so every weakness is your own note and every question is neutral. My own reading: at a mid-size fintech, Cloudmoat most often replaces the manual audit plus the native consoles, not Competitor A, so the message in step 4 says "unlike periodic manual cloud audits".

Step 3. Pin the claim to proof

Cloudmoat's proof list holds two example results, both from one invented customer and, for this example, the same quarter: critical exposures down 70%, and audit preparation down from 3 weeks to 4 days. Input to the value tool: target "cloud security leads at mid-size fintech companies"; outcome "Fewer critical exposures"; capability "Exposure-based ranking of every misconfiguration"; and only the first result, "critical exposures down 70% in one quarter".

What came back: three versions of the claim, with a rule printed above them: "The "only" claim stays inside brackets until it is true and you can prove it." The value matrix opens with "This tool adds no figure of its own", places the 70% under critical exposures open, and lists measures with no figure yet: mean time to detect, mean time to respond, alerts per analyst and asset coverage. It also wrote a line per audience and per channel, in the table alongside.

How to read it: keep the outcome-first version and leave the bracketed "only" lines out until you can prove them. In my experience the technical evaluator tests every claim in the proof of value. The empty measures are your proof plan: one before-and-after figure for alerts per analyst gives the champion a second number.

One label to read past: the evaluator line here is headed "For the technical evaluator (risk, compliance and audit)", while step 1 named the CIO or CTO as the technical influencer. Treat it as the reviewer line.

Step 4. Write the message, then check the line you have today

Input to the message tool: need "lose days chasing low-risk cloud alerts"; benefit "Fewer critical cloud exposures"; alternative "periodic manual cloud audits"; the same differentiation and target as step 3.

What came back, as the complete statement: "For cloud security leads at mid-size fintech companies, Cloudmoat is a cloud security monitoring platform that helps them get fewer critical cloud exposures. They lose days chasing low-risk cloud alerts. Unlike periodic manual cloud audits, Cloudmoat offers exposure-based ranking of every misconfiguration." It added four taglines, such as "Fewer critical cloud exposures", three pillars and six objection answers. No pillar had proof to show, and the social proof variation declined to write a line: "No customer count, result or recognition was typed, so there is no honest proof line to write yet."

How to read it: that refusal is correct, because this tool never received the 70%. Put the result under pillar 1 yourself, or rerun with it in the benefit field, as its "To sharpen this" line asks. The evaluator line came back as a stub ("On risk, in your words: "cloud security monitoring platform"."), so write that one yourself: what evidence Cloudmoat produces for an audit, and where the data stays.

Then I ran the full audit on the current homepage line, "Cloudmoat shows which cloud risks matter first, unlike long rule lists." Its inputs differ from the steps above: target "CISOs at mid-size fintech and SaaS companies running on two or more clouds"; competitors Competitor A, Competitor B and "periodic manual audits"; and both results as customer feedback. It scored the inputs 77/100 (grade B), which measures "how complete and specific your inputs are, not whether your positioning is right". The part I use is the word check alongside: the line names an alternative but not the buyer, and states no result. The audit's own recommended positioning fixes the result gap, carrying "Critical exposures down 70% in one quarter" into its "That" line.

Closing the loop on step 1, my own revised statement, not a tool's: "For cloud security leads at mid-size fintech companies who answer for time to prepare an audit and alerts per analyst, Cloudmoat ranks every misconfiguration by real exposure, so the team fixes critical cloud exposures first. Unlike periodic manual cloud audits, it keeps audit evidence ready from the same view. Example result: critical exposures down 70% in one quarter."

Step 5. Turn the message into the seller's lines with CRAFT Content

Input to the CRAFT Content sales kit: three value lines from steps 2 to 4; both example results from step 3 as proof; three sector objections; the alternative typed as "Why not keep our periodic manual cloud audits"; discovery stage.

What came back: a pitch order, one script per objection, a competitive response, discovery questions and follow-up emails. For exposure-based ranking, the thing Cloudmoat is built on, it wrote "none of your proof points speaks to this one, so none is borrowed for it". The pitch order is headed "Lead with Strongest" but came back in the order I typed, so put the line with proof first yourself.

How to read it: two pairings in the objection table alongside need your judgement. The integration objection was given the audit preparation result, which does not answer it; use the answer pattern instead, "Name the integrations available today and test them in the proof of value." Type the alternative as a plain noun, not a question, or its trap line reads "When you looked at keep our periodic manual cloud audits".

I also ran the content improver on the homepage line. It scored it 7/10 and made no edit: "No automatic edits were found." Its priority fix was "The goal needs the reader to do something, but no ask was found", and it asked for one specific result to lead with. My own rewrite, proof first: "Critical exposures down 70% in one quarter at one customer (example result). Cloudmoat ranks every misconfiguration across AWS, Azure and Google Cloud by real exposure, so cloud security leads fix critical exposures first. Book a proof of value on your own accounts."

Step 6. Turn the alternatives into discovery questions

Input to the trap setter in Revenue Enablement: competitor "periodic manual cloud audits"; my strengths, including "Audit evidence ready from the same view"; my notes on its weak points; buyer priorities "fewer critical exposures open; faster audit preparation"; early stage; cloud security lead.

What came back: it read the alternative correctly as "the buyer's current approach", "a way of working and not a vendor". It opened with the buyer's own priorities: "You told me this matters: fewer critical exposures open. How would you judge that each option delivers it?" For the audit evidence note it added a "Then show" line.

How to read it: one landmine came back garbled ("Is a snapshot that out of date within days in each option?"), and one fell back to a generic line. Rewrite those two in the buyer's words; mine for the first is "How old is the picture of your cloud on the day you act on it?" The third, in the table alongside, asks about time to first result rather than evidence gathering, so it does not test that note; its "Then show" line does fit.

My first run differed: competitor "Competitor A", mid stage, strengths that included "One view across AWS, Azure and Google Cloud", and my two notes on rule lists and single-cloud coverage. The output shortened the name to "Cloudmoat vs Competitor" and read it as "a kind of tool rather than one named vendor". In real use, type the competitor's actual name. Each answer on the call then confirms the "unlike" line or sends you back to step 2.

1. Run the champion tool and check the champion's title and measures with two customers.
2. Map every alternative, including the status quo, and phrase your strengths as answers to your notes.
3. Pin one result with its period and source, and keep "only" claims in brackets until proved.
4. Write the message against the alternative you meet most, and carry the result into the pillars by hand.
5. Build the sales kit, fix any wrong proof pairing, and give sellers the trap setter questions.

1. Writing for the signer only. The cloud security lead carries the case to the CISO, so use that person's measures.
2. Positioning against the vendor you fear instead of the habit you replace.
3. Shipping an "only" claim before it is proved. The technical evaluator will test it in the proof of value.
4. Assuming proof travels between tools. The message tool never saw the 70%; check every pillar for a result and a source.
5. Stopping at the statement. Without objection scripts and questions, sellers write their own lines.

• How to Roll One Positioning Hub Out to Every Buyer Role and Channel in a B2B Rebrand, With the Hub-Spoke Methodology
• How I Pick the Lead B2B Go-To-Market Motion With EPIC, Then Size and Anchor It
• From Selling Tokens or Hours to Selling Outcomes: An Outcome Pilot Workflow for AI-Native and IT Services Firms
• All 15 guides