Use the Champion Equation. A champion is not someone who likes your demo. A champion is someone with pain, influence, and a reason to spend political capital for change.
1. Pain: What problem do they personally feel?
2. Power: Whose opinion do they shape internally?
3. Personal win: How does solving this make their job, status, or team better?
4. Proof: What evidence can they use when you’re not in the room?
No personal win, no real champion.
🎯 Try this today: Pick one “champion” in your pipeline and fill in the four parts. If one is blank, ask about it on your next call.
Single-threaded deals don’t die all at once — they go quiet when your only contact gets busy, blocked, or political. Multi-threading isn’t “going around” your buyer; it’s protecting the initiative by understanding who will live with the decision, approve it, or object to it.
🎯 Try this today: Pick one open opportunity and write three names or roles you’re missing: economic buyer, daily user, and potential blocker. Ask your current contact, “Who else will have a strong opinion on this before it moves forward?”
Most follow-ups are just disguised neediness: “Checking in” really means “Please make me feel better about this deal.” Earn the next reply by making the buyer smarter every time you show up.
Use the Useful-Then-Ask loop:
1. Recall: “You mentioned ___ was becoming a concern.”
2. Add value: Share a benchmark, checklist, article, customer pattern, or sharp question.
3. Translate: “This may matter because ___.”
4. Invite: “Worth applying this to your situation on a quick call?”
This is Cialdini’s reciprocity in action: useful first, ask second.
🎯 Try this today: Replace one “just checking in” email with a 4-line Useful-Then-Ask follow-up tied to something the buyer already told you.
Your champion is not your messenger unless you give them a message worth forwarding. After a good call, don’t send a generic recap—send the exact internal language they can use to explain the problem, impact, and next ask without sounding like they’re pitching for you.
🎯 Try this today: Pick one active deal and write a 5-line “forwardable recap” your champion could send internally: problem, impact, why now, proposed next step, and who should weigh in.
Multi-threading works best when it feels like risk reduction, not a land grab. Instead of “Who else should be involved?” try: “Since adoption will sit with Ops, it may be worth pressure-testing the rollout plan with Priya before we get too far.”
🎯 Try this today: Pick one single-threaded deal and write one sentence naming the stakeholder you need and the business reason they should be included.
Use the Champion Stress Test. A real champion doesn’t just like you—they can create motion when you’re not in the room.
1. Pain: Can they explain the business problem in their own words?
2. Power: Can they name who signs, blocks, influences, and uses?
3. Personal win: Do they care enough to spend political capital?
4. Proof: Can they tell your story internally without forwarding your deck?
🎯 Try this today: Pick one “champion” and score them 1–4 on the test. If they miss one, ask one question to strengthen it on your next touch.
ALLY Map — a 4-step loop that turns senior colleagues into quiet champions
1. Authority: List one person whose opinion shapes your next promotion or project green-light.
2. Lift: Note the live problem or metric that’s keeping them up (listen in meetings, read their Slack rants).
3. Leverage: Spot a bite-size way you can move that metric this week—share a data point, intro a contact, grab an orphaned task. Do it unasked.
4. Yield: When the help lands, send a two-line recap: result + credit (“Your churn insight shaved 3 hrs off the fix—team’s rolling it out now”). They see impact, you stay on their radar without bragging.
🎯 Try this today: Open your calendar, pick the highest-stake meeting on it, run steps 1–3 for the most senior attendee, and queue the two-line Yield email draft—send once your assist hits.
Executives can’t champion what they don’t hear about. Before you log off, drop a two-line update in a public Slack or email: “Shipped the self-serve cancel flow—average ticket time already down 12 minutes. Big assist from @Alex on QA.” It’s impact + gratitude, so it feels like service, not self-promotion, and your name rides the data upward.
🎯 Try this today: Write a Result-Ripple-Credit update (one sentence each) for your biggest win this week and post it in the team channel before you close your laptop.
People champion what they help create. Next time you need another team’s buy-in, send them a near-final draft with two highlighted blanks (“Tagline idea?” “Risk we’re missing?”). Once they add even a word, Cialdini’s commitment principle flips them from critic to co-owner.
🎯 Try this today: Grab one proposal waiting for approval, insert two clear fill-in prompts, ping the stakeholder for a “quick gut check,” and let their own edits lock in their support.
E.C.H.O. Reach-Out — the 4-step note that builds genuine connections without the ick
1. Earned hook: open with a line proving you’ve done homework (“Your talk on zero-downtime releases solved our rollout pain”).
2. Common ground: name one shared thread—mission, alma mater, mutual colleague (“We both started in QA before product”).
3. Help first: offer a bite-sized give—resource, intro, data point (“Happy to share our post-mortem template if useful”).
4. Open loop: propose a tiny next step that respects time (“If 15 min next week works, I’ll bring two questions and be done by :15”).
No vague flattery, no “pick your brain.” Just relevance, reciprocity, and a clear runway.
🎯 Try this today: Draft an E.C.H.O. message to one person you admire but rarely speak with—send it before lunch and calendar the follow-up if they bite.
SPOT Ping — the 4-line update that builds your brand without sounding like a braggart
1. Success – name the concrete thing you shipped (“Launched the new pricing calculator”).
2. Proof – one data point or quote that shows it matters (“Cut checkout time by 18 % in A/B test”).
3. Others – spotlight at least one collaborator (“Huge assist from Priya on the API fix”).
4. Trajectory – state the very next move (“Rolling to 100 % of traffic on Tuesday”).
Result, evidence, gratitude, momentum—execs see impact, teammates feel valued, and you stay top-of-mind.
🎯 Try this today: Draft a SPOT Ping in Slack or email, drop it in your team channel before the day ends, and note how many thumbs-ups and follow-up questions it earns.
N.O.T.E. Recap — the 4-line follow-up execs love
1. Net outcome: the single sentence on what got decided or delivered.
2. Ownership: who’s got the ball, bold their name.
3. Timeline: the exact date the next milestone lands.
4. Escalation need: one line on any blocker the leader must clear.
Four bullets, no narrative. Reads in 15 seconds, saves a week of “wait, who’s doing what?” threads.
🎯 Try this today: After your next meeting, draft a N.O.T.E. Recap in Slack or email and hit send before anyone leaves the room.
LIFT Email — the 4-line ping that grows your network minus the awkward small talk.
1. Lob praise: open with a specific, genuine compliment (“Your Q3 churn teardown was razor-sharp.”).
2. Identify overlap: tie their work to yours (“I’m rebuilding onboarding flows and hit a similar retention wall.”).
3. Float a question: one bite-size ask that fits a 15-min chat (“How did you spot the ‘silent churn’ users so fast?”).
4. Tee up next step: offer two concrete times or invite an async reply (“Free Thu 10:00 or Fri 2:30—happy to adapt if Slack’s easier.”).
Four sentences, zero schmooze, instant rapport.
🎯 Try this today: Target one person you admire inside the org, write a LIFT Email in under two minutes, and press send—you’ll plant a relationship seed that compounds all year.
Your team isn’t psychic—your “done” may be their “halfway.” Before ending any hand-off, state crystal clear finish criteria: “Ship the deck that has 3 competitor slides, our price slide, and speaker notes—ready for legal by Friday 3 PM.” One sentence like this kills 90% of follow-up pings and rework.
🎯 Try this today: Pick one task you’ve delegated. DM the owner a single “We’ll call this done when…” line that defines the outcome in concrete terms.