Playbook · For Account Executives

Most AEs do not fail to multithread. They never try.

Not because they do not know they should. Because they are not sure who to ask, when to escalate, or how. Rudy maps the committee at deal creation, finds the route to each member, and puts the asks in a plan you agree every week.

Try for free Book a demo

B ####

# deal-klarna5 members

R

RudyAPPFriday 4:58 PM

Four things on this deal next week. The committee has two people nobody has spoken to and one of them signs.

Reach the economic buyer at KlarnaNo route used yet. Two exist.

Map

Warm up security before reviewThey blocked the last one. Your CTO knows theirs.

Thread

Brief before Thursday’s callTwo new names on the invite.

Thread

Decide on the board askACV clears $500K. Worth spending, or not.

Advance

Agree the planChange something

Co-owned goals

Three things you and Rudy both own.

Not three features. Three goals with a name on each, which is the difference between a tool you remember to open and a colleague who turns up.

01

Map

Know who is actually in the room. A committee has six to ten people and most deals are run against two of them.

02

Thread

Get to the ones nobody has touched, through whoever can reach them. Procurement asking a question nobody warmed up is how good demos lose.

03

Advance

Spend the right capital at the right stage. A board ask on a $60K deal is not a clever move, it is a withdrawal you cannot make twice.

The operating rhythm

A tool waits to be opened. A colleague has a standing agenda.

This is the part nobody else does. Rudy is not a stream of notifications you triage between calls. He works to a rhythm you both keep, and it produces something you can point at.

1ONCE A WEEK

☰This week’s planagreed Friday

Four things, in priority orderRudy proposes. You cut what does not belong.

Planned

Each one has a reason attachedNot a feed. A short list you both signed off.

Planned

Owner and date on every itemSo nothing is technically everyone’s job.

Planned

Anything you rejected stays rejectedHe does not quietly re-propose it on Tuesday.

Noted

2EACH MORNING

☰Today3 items

First item already movedSent 09:14. Reply came back before standup.

Done

Second needs your readDrafted and waiting. Two minutes of your time.

Now

Third is teed upEverything he needed is attached.

Today

3EACH EVENING

☰Closed outnothing dropped

Two closedOutcome logged against the record, not a spreadsheet.

Closed

One sent, no reply yetWhich is fine on day one. He will chase it.

Sent

One replannedSomething changed on the account. Reason attached, moved to next week.

Replanned

And then it repeats. Nothing carries over silently. Anything unfinished goes back into next week’s plan with a reason attached, which is why this survives a busy quarter instead of quietly stopping.

Map

Ten people decide. You are running it against two.

Rudy maps the committee when the opportunity is created, not when it stalls. Every member, what they care about, and whether anyone on your side can reach them. It lives on the opportunity, so nobody has to go looking.

Klarna, $240KACCOUNT

DetailsRelatedContactsBoomerang

Rudy · buying committee, live

IS

Ingrid SandbergVP RevOps. Economic buyer. Never contacted.

No route

SK

Sam KelleherSecurity. Blocked the last vendor. Your CTO knows him.

1 hop

NW

Nadia WhitfieldFinance. Joins at contract. Nobody has met her.

Gap

TO

Tom OyelaranYour champion. Engaged, and two levels below Ingrid.

Engaged

Thread

Stuck at one stage for thirty days.

A deal that has not moved is usually a deal running on one relationship. Rudy notices before the forecast call does, and brings the members nobody has touched with the route to each, rather than a reminder that the deal is stuck.

☰Klarna, stage 3day 31

this has not moved in a month and it is running on tom alone

EB

Economic buyer untouchedIngrid signs and has never heard from you.

Priority

SE

Security route foundYour CTO worked with Sam Kelleher at Monzo.

1 hop

FI

Finance joins at contractNadia Whitfield. No route yet, worth building now.

Build

Thread

Two new names on Thursday’s invite.

Someone joins the committee mid-cycle and nobody knows who they are. Rudy briefs you before the call: who they are, what they have bought before, and who in your orbit already knows them. Ask him wherever you work, including inside Claude.

ClaudeBOOMERANG MCP

who are the two new people on the Klarna call Thursday

C

Both joined the invite yesterday. Sam Kelleher runs security and blocked a vendor at this stage in 2024. Your CTO Dan Okafor worked with him at Monzo. Nadia Whitfield is finance and typically joins at contract.

WORTH OPENING WITH

Sam, Dan Okafor mentioned you two worked through the Monzo rollout. He said the thing you cared about was evidence before the review, not after it.

boomerang.get_committee boomerang.search_paths boomerang.get_history

Advance

A board ask is a withdrawal.

AEs get more latitude than SDRs because they own the deal relationship, and the gate sits higher to match: the board pillar unlocks at $500K, not $250K. Rudy applies it before surfacing anything, so the decision you are shown is one you are allowed to make.

# deal-klarnagate applied

R

RudyAPP10:41 AM

This deal clears the board gate. Worth spending, or hold it for the renewal cycle where it might matter more.

ESCALATION CHECK

DEALKlarna, $540K expected

GATEBoard pillar unlocks at $500K

ROUTEVia the CEO. Board members are not asked directly

ALSO AVAILABLEOne team route, unused

Request the board ask Use the team route first Hold it, revisit at contract

The trigger comes from your stack. Rudy does the relationship work.

Salesforce, HubSpot and Attio Clay Common Room and Outreach Your own calendars and call recordings

And he shows up where the work already happens.

Slack On the account record Claude and Codex, over MCP REST API and webhooks

The rules Rudy keeps

Connector capital is a budget, not a tap.

Every pillar has a different cost and a different refill rate. The limits are set per source, and Rudy applies them before anything is surfaced, so the only asks anyone sees are the ones they are allowed to make.

Your own team

YESAlways, and it is the AE’s first stop rather than a fallback.

NEVERNothing. Never skipped when a path exists.

Customer champions

YESDirectly. The AE owns the deal relationship and Rudy does not insert a layer that is not needed.

NEVERWhen the customer relationship is fragile. Then it routes through the CSM.

Partners

YESRouted through the Partner Manager, who talks to the partner.

NEVERDirect outreach. Same rule on every playbook.

Board and investors

YESAt $500K ACV and above, routed through the CEO.

NEVERBelow it. Board capital is for the deals that move the number.

The connector contract

You will say yes or no to every ask. No silence.

Every connector agrees to one rule. Someone who ghosts three asks is telling you they would rather not be a connector, and that is a fine answer. Better than silence, because silence is what trains the next person to stop asking. Both sides protected.

YesNot nowWrong personI’d rather not

On the scoreboard