How to Roll One Positioning Hub Out to Every Buyer Role and Channel in a B2B Rebrand, With the Hub-Spoke Methodology

I have been part of 6+ rebrands, with agencies including Wolff Olins, JWT, Brand Union, Digitas, DDB Mudra and Grey, and I led two of them: QuantumStreet AI and Airtel B2B. On QuantumStreet AI we rebranded a $7Bn AUM AI investment fund from Equbot, with Digitas and IBM. At Airtel I worked with Wolff Olins on the new B2B brand identity, and during my years there, from June 2007 to October 2011, Airtel Data Centers and Managed Services grew 4x.

The risk I watch for in any rebrand is the same. An agency's job is the identity: the name, the look, the voice. Translating the new story into what a CISO, an evaluator and a daily user each need to hear is a separate job, and if nobody on the client side owns it, every team writes its own version. A buyer halfway through a deal then hears two companies.

The positioning guide covers finding the message. This one covers rolling it out without losing the deals already in flight.

The hub is small on purpose: one statement, one named alternative and the proof, each figure with a source. Every spoke can change the measure, the length and the call to action, but never the claim. That rule keeps a homepage, a deck and a cold email saying the same thing.

The IMPACT full audit reads the old line first. The IMPACT message tool writes the hub and, in the same output, the role spokes. The IMPACT channel tool writes the channel spokes. Revenue Enablement drafts the seller's note for live deals, the first switch-over step, and CRAFT Content handles the long-form spokes.

The switch-over order alongside is my own working rule. The IMPACT channel tool ranks channels for reaching buyers in this sector, cold email first and the website fourth, because "The order follows how deals usually run in cybersecurity, cloud security". That is not a switch-over order. It agrees with mine on one point, outbound before the website, and differs on the deck and demo, which it ranks third and fifth and I switch first. The same output notes that "budget often follows an audit finding or an incident", so my rule is to announce before the audit season of your target accounts. Where they have no clear audit season, ask the champion when the next audit or board risk review falls, and announce a few weeks before the earliest of those across your live deals.

Step 1. Read the old line before you change it

Cloudmoat's old line was a contrast: "Cloudmoat shows which cloud risks matter first, unlike long rule lists." Input to the IMPACT full audit: that line; target "CISOs and cloud security leads at mid-size fintech and SaaS companies on two or more clouds"; alternatives "long rule lists from cloud scanners" and "periodic manual audits"; both example results as customer feedback.

What came back: an input completeness score of 74/100 (grade C), which measures "how complete and specific your inputs are, not whether your positioning is right". Map Alternatives scored 65 because "you named 2". The word check on the old line, alongside, found that it names an alternative but states no result. Its recommended positioning put "Critical exposures down 70% in one quarter" into the "That" line.

How to read it: the buyer check passed because the line "shares a word with your target customer", and "cloud" appears in both. In guide 02 the same line failed against a target that said "clouds", not "cloud". Read it as a word match, not a judgement. The real gap is the missing result, so the hub leads with the outcome. It keeps rule lists as the named alternative because, in my view, existing customers already know that comparison.

Step 2. Lock the hub

Input to the IMPACT message tool: the same target; need "lose days working through long rule lists with no order to fix them"; benefit "Fix critical cloud exposures first"; alternative "long rule lists from cloud scanners"; and, because this tool has no field for results, the 70% typed into the differentiation field after the capability.

What came back, as the complete statement: "For CISOs and cloud security leads, Cloudmoat is a cloud security monitoring platform that helps them fix critical cloud exposures first. They lose days working through long rule lists with no order to fix them. Unlike long rule lists from cloud scanners, Cloudmoat offers exposure-based ranking of every misconfiguration across AWS, Azure and Google Cloud." The proof reached pillar 2 marked "(your figure, source not stated)".

How to read it: the proof field trick works, with one cost. The tool also built "Cloudmoat offers at one customer, critical exposures down 70% in one quarter." into pillar 2 and the evaluator line. Delete that sentence, keep the proof line, and write the source next to the figure in the hub document, because every spoke copies it from there.

Step 3. Read the role spokes off the hub

The same output wrote one line per buying role. Both lines alongside keep the claim: the champion line changes the frame ("instead of living with long rule lists"), and the CISO line changes the measure, which is the Hub-Spoke rule in practice. A CISO who reads "fix critical cloud exposures first" on the new homepage and then hears "we check more rules than anyone" from a seller has heard two companies.

The line headed "For the technical evaluator (risk, compliance and audit)" came back as a stub: "On risk, in your words: "cloud security monitoring platform". For the technical review: Cloudmoat offers at one customer, critical exposures down 70% in one quarter. Cloudmoat is a cloud security monitoring platform." The last sentence repeats the first; delete both with the stub. Article 1 of the series in step 7 names who has to agree: risk, compliance and audit "review the evidence it produces", and the CIO or CTO checks integration. My rewrite, with brackets for facts the product team must confirm: "For your audit and integration review: Cloudmoat produces [the audit evidence your auditors ask for] from the same view the team works in, and connects to [the SIEM and ticketing tools available today]. Test both in the proof of value."

Step 4. Build the channel spokes

My first run of the IMPACT channel tool used the short one-line statement from the example inputs. The difference came back as "Cloudmoat offers cloudmoat ranks every misconfiguration by real exposure so the team fixes what matters first.", and with no alternative named the deck fell back to "the current security tools plus manual review by analysts (the usual alternative in this sector)". The tool said what was missing: the alternative "written in the statement as "Unlike X"".

The second run took the full hub statement, with the 70% added to the benefit field. It carried the hub into every channel, as alongside: the alternative on the differentiation slide, the 70% on the results slide marked "(your figure, source not stated)", and "Start a time-boxed proof of value" as the primary call to action.

How to read it: the hero shows the 70% as a benefit point, but the proof strip still reads "no customer count, result or recognition was typed, so none is shown". Fill that strip yourself with a sourced result.

Step 5. Write the seller's note to live deals

This is switch-over step 1. Input to the email sequence tool in Revenue Enablement: warm follow-up to a CISO; the hub benefit and mechanism as the value proposition; both example results; the ask "a 30-minute call to walk through what changes and what stays the same for your evaluation"; consultative tone.

What came back: three emails (same day, day 3 and day 7) using both results "as you gave it". My first run put a sentence about the evaluation in the sender field, and the tool printed it as the signature, so the second run used a name, "Sam Example (fictional), Account Executive, Cloudmoat", and changed the pain field from "Your team loses days working through long rule lists with no order to fix them" to "days lost working through long rule lists with no order to fix them". The pain text is reused as a subject fragment and as a "When ..." clause. The first run's subject read "Next step on Your team"; the second fixed the subject ("Next step on days lost") but broke the day 3 question: "When days lost working through long rule lists with no order to fix them, what does it cost the team in a week, and who picks it up?" So type a clause that starts with a short noun phrase. A third run with "alert triage takes days because long rule lists give no order to fix them" gave the subject "Next step on alert triage" and a clean day 3 question.

How to read it: the tool writes an after-the-call sequence and knows nothing of the rebrand, so the announcement sentence is yours. My edit of email 1: "Thank you for the time on your evaluation. Next month Cloudmoat changes how it describes itself, and I want you to hear it from me first. The product and your evaluation plan stay the same. The new line is: fix critical cloud exposures first, with exposure-based ranking of every misconfiguration across AWS, Azure and Google Cloud. Would a 30-minute call next week to walk through what changes be useful?"

Step 6. Turn the announcement into long-form spokes

Input to the CRAFT Content repurposer: a 124-word announcement post I wrote from the hub, key message "Fix critical cloud exposures first", and five formats. Its wording is close to the hub but not identical: it says "so your team fixes critical exposures first", where the hub says "fix critical cloud exposures first".

What came back: all five, each built from whole sentences of the source "in its order". It left out one sentence, the old contrast ("For years cloud security tools have"), which suits a rebrand. The 70% sentence appears in every piece, yet the header says "Not given: a proof line", because the tool looks for a line that starts with "Proof:" or "Results:".

How to read it: the repurposer keeps your sentences as written, so my looser wording went into every piece. That makes it a good Hub-Spoke tool only if the source copies hub sentences word for word. Do that, and put the result on its own line that starts "Results:" with its source.

Step 7. Draft the CISO series, one objection per article

Input to the series tool: topic "How to prioritise cloud misconfigurations"; my take "A cloud security team should be judged by critical exposures closed, not by how many rules its scanner checks"; reader CISOs at mid-size fintech and SaaS companies on two or more clouds; both proof points; three contrarian articles.

What came back: three drafts of about 470, 406 and 366 words, each answering one sector objection, as alongside, with a promotional post each and a publishing order.

How to read it: these are skeletons, and the substance is yours to add. The byline reads "By Co-founder of Cloudmoat, a cloud security monitoring company", because the author field fills it, so type a name there. Article 3 is headed "One Customer's Case" but holds a test plan, and Article 2 repeats the heading "A result on record".

1. Run the full audit on your old line and note which word checks fail.
2. Write the hub on one page, with each proof point's customer, period and approval, and get the CEO and the sales leader to sign it.
3. Rewrite the evaluator line from facts the product team confirms, and run the channel tool with "Unlike" in the statement.
4. List every live deal past discovery and send each one its seller's note before anything goes public.
5. Set the announcement date against your target accounts' audit season, then repurpose the announcement and draft the CISO series.

1. Changing the identity before the hub is locked.
2. Letting each team write its own spoke. Spokes may change the measure and the length, never the claim.
3. Announcing before sellers have briefed live deals. A buyer should hear the new story from their seller first.
4. Dropping the category words buyers search for. Keep "cloud security monitoring" next to the name on every page.
5. Shipping figures without sources. Every spoke copies the hub.

• From the Buyer Who Champions You to a Message Sales Will Use: Positioning With IMPACT, CRAFT Content and Revenue Enablement
• How to Turn One Verified Customer Result Into a Case Study, a LinkedIn Post and a Newsletter in the Founder's Own Voice
• From Selling Tokens or Hours to Selling Outcomes: An Outcome Pilot Workflow for AI-Native and IT Services Firms
• All 15 guides