Account-Based Plays Without Burning SDR Hours: Account Plan, Competitive Traps, Lookalikes and Roundtable Follow-Up

I was Director of Product Marketing at Seclore from July 2016 to October 2017. In that time Seclore had 225+ sales meetings across its target accounts, and Rs 2.35 Cr TCV in 6 months came through account-based marketing.

Account plays waste time in the joins between teams. An SDR researches the account in a notes field, a product marketer keeps a battle card on a wiki, and marketing operations sends the event follow-up from a list. The SDR re-researches what the account manager already knows, the battle card answers a competitor this account never mentioned, and a customer who came to the roundtable gets the same nurture email as a cold prospect.

The fix is an order of work on one account, in which each tool takes the previous tool's output as its input. The tools do the drafting, so the SDR hours go into calls.

Five steps on one account, in the order in the table alongside. Each uses what the one before it produced.

On a real account, run Account research from the B2B Research plugin first. The account plan builder "does not look the account up", so it is only as good as your notes. Account research writes a one-account brief in TOPS order (technographics, organisation, person, situation), gives every field a source and a verified or unverified status, and stops when a source you named fails. Copy only the verified facts into the plan. I did not run it on Example Logistics Co: an invented account has no public footprint, so I would expect every field back unverified or empty.

The account plan then names the people, the whitespace and the competitor. The competitor feeds the trap setter, the champion and signer titles feed the lookalike search, the ranking decides which new accounts get worked first, and the account's customer status decides how the event follow-up treats its people. The owner line in each step is my own working split, not the tools'.

Step 1. Build the account plan

Input to the account plan builder in Revenue Enablement: Example Logistics Co, third-party logistics, $36,000 ARR, "Lanehop route planning in 3 of their 12 cities". Contacts: Head of Last-Mile Operations (likely champion), CFO (approves spend above $50,000), Head of IT. Whitespace: the other 9 cities and one dispatch view. Competitor A in the account. Notes: about 1 in 6 deliveries fail on the first attempt, and each city plans routes in its own spreadsheet.

What came back: one row per contact, as in the table alongside, with the champion marked "Champion, as you said" and the other two "read from the title". It named the usual buying roles none of my contacts covers (Chief Operating Officer, Head of Supply Chain, Head of Logistics) and a 90-day plan dated from the day I ran it: map and listen by 25 November 2026, prove the next step by 25 December, decide and widen by 22 January 2027.

How to read it: the Growth tier comes from "this tool's rule on ARR alone", and the tool adds "that is a rule on the number, not a view of the account". Read the gap list instead. My contacts give a champion, a finance reviewer and a technical reviewer, but nobody in the roles it lists as missing, and its own first task is to "Ask who signs, and ask for that person by name." That gap decides the first 30 days. Adjust one line: the CFO question, "Which finance numbers are late or reworked each period", suits a finance buyer; this CFO approves spend above $50,000, so ask what proof they need before that line.

The first run asked for objections in account_notes, starting with "Objections:", so I ran it again with three. For "IT has no capacity for another integration this quarter" it said to answer "system by system" and offer a technical call with their IT owner. For "the CFO wants proof before spend goes above $50,000" it offered "a time-boxed proof on the buyer's own environment with the success measure agreed in writing first". For "Competitor A says it can cover all 12 cities in one contract" it wrote no answer: "Your inputs hold no fact that answers this question". Find that fact before the call.

The ABM lead owns this step, with the account owner, which saves the SDR from re-researching a customer the account owner already knows.

Hand-off: Competitor A and the IT objection go to the trap setter.

Step 2. Set the competitive traps

Input to the competitive trap setter, also in Revenue Enablement: "Competitor A", mid-stage, every trap type, the Head of Last-Mile Operations as evaluator, my three strengths, its two weak points from my notes, and three buyer priorities: fewer failed first-attempt deliveries, one dispatch view across all 12 cities, no new IT project this quarter.

What came back: discovery questions, criteria to agree early, reference call questions, requirement and scenario traps, cost points and stage tactics. The tool says "The weak points are your notes and are never read out": a question may name the topic, such as unstructured addresses, but never the competitor's weakness, as in the table alongside. My three strengths became the criteria to agree before anyone is shortlisted, each tested with one question: "can it show this on one of your own cases?" Its requirements list then accepts each one only when "Shown live on your own case", on one condition: it is "shown live and the Head of Last-Mile Operations signs off the result".

How to read it: the most useful line ties back to Step 1. The priority "no new IT project this quarter" became "Which option has shown you that on your own data, and what did it measure?" That is the account plan's IT objection, turned into a test that Lanehop's six-week set-up without IT help is meant to pass.

Two quirks to read past. The placeholder name was read as a type of tool: it shortened "Competitor A" to "Competitor", "a kind of tool rather than one named vendor" with "no single contract or reference list to ask about", so use the real name. And it paired the setup-time landmine with "Then show: Re-plans routes during the day". My own call: show "Live in six weeks without IT help" instead, because it answers that question.

This one belongs to the product marketer. SDRs get questions to ask instead of writing competitor lines from memory.

Hand-off: the champion and signer titles and the buyer priorities go to ICP Intelligence.

Step 3. Find more accounts like it

Three things went from Steps 1 and 2 to the lookalike signal generator in ICP Intelligence. The champion titles: Head of Last-Mile Operations from the account plan, and Head of Logistics, whom the trap setter's sector note names as the usual champion. The signer titles from that note, COO and Head of Supply Chain, as a trigger: a new COO or Head of Supply Chain hire. And two buyer priorities, recast by me as events visible from outside: one dispatch view became expansion into new cities, and fewer failed deliveries became a new e-commerce or retail delivery contract. Firmographics: third-party logistics and courier companies, 201 to 5,000 employees, India, with transport and warehouse management systems.

What came back: copy-ready Sales Navigator searches, a Boolean title string, Google Ads keywords, intent platform and ZoomInfo or Apollo filters, and one signal per trigger, as in the table alongside.

How to read it: the lead search uses only the champion titles, so add Chief Operating Officer and Head of Supply Chain to it by hand. The signal for the new-leader trigger watches for "A new Head of Last-Mile Operations or a related leader" rather than a new COO, so set a job-change alert on the signer titles yourself. A transport management system is a category, and technology filters list named products, so name the systems your customers run. The output's own warning: "This tool generates targeting CRITERIA, not actual data."

Marketing operations build and save these searches, so no SDR builds a list by hand.

Hand-off: the accounts the searches return go to account prioritization, which the output names as the next step, and the firmographics become the account definition Step 5 asks for.

Step 4. Rank the accounts the searches return

Input to account prioritization in ICP Intelligence: three accounts the searches might return, all invented. Fit uses my own working rule, 25 points for each of the four lookalike criteria met, so Example Courier Co scores 100, Example Freight Co 75 (about 6,000 employees, outside the band) and Example Parcel Co 75 (no system confirmed). Intent uses my own working points: 50 for one of the three triggers in the last 90 days, 30 for a reply or call from a champion title, 10 for each other sign. Relationship (50, 40 and 20) and timing (now, later and soon) are example inputs, and I kept the tool's default weights.

What came back: the ranking in the table alongside, with tiers at 80%, 60% and 40% of the highest possible score. For Tier A it says "Personal outreach from the account owner this week, with executive involvement", for Tier B "Targeted outreach this week, multi-touch sequence", and every weight is marked "Example figures: replace with your own."

How to read it: Example Freight Co ranks first on a new COO, a reply from its Head of Logistics and a "now" timing, despite the weakest fit. The tool labels it "High buying intent" while showing that "the most points come from fit 75 × 40% = 30 points of 80"; trust the numbers beside the label. The tool puts Example Courier Co in Tier B with a sequence this week. I would override that: a perfect fit with "later" timing is a reason to invite its Head of Logistics to the roundtable first, and to sequence only if they engage.

The SDR manager runs the ranking, and SDRs stop working accounts in the order they arrive.

Hand-off: the top accounts' champions and signers get roundtable invitations, and the list goes to Step 5's account gate.

Step 5. Spec the roundtable follow-up

Input to the Event follow-up engine skill, from the B2B Events, PR and Launches plugin, in spec mode: Lanehop's last-mile operations roundtable, in person in Bengaluru on Thursday 12 November 2026. On the list: Example Logistics Co's Head of Last-Mile Operations, who attended, its Head of IT, who registered and did not come, and prospects.

What came back: a restatement and a Yes or No question first, with the spec under it marked "draft; depends on your Yes; redone if No". It ends with 7 tests; every weight, threshold and timing is a "[User to set: ...]" placeholder and the stage names are "[User to add]". It keeps opens out of engagement ("Opens alone never make a contact engaged") and states that it does not build, import or change anything in a marketing platform or CRM.

How to read it: the active customer check sends both Example Logistics Co people to the account owner instead of into nurture, including the Head of IT who did not come. The account plan already wants a technical call with the Head of IT, so that no-show is the plan's next meeting. The spec names this account as the test case for the coordinated account play "if you keep this section in the pilot", and leaves open whether that play is in the pilot at all; decide before you build. For prospects, the gate asks for your ideal customer definition, which Step 3's firmographics already give you.

One line to answer before the roundtable, not after it, from the spec's consent section: "What the registration form told attendees about follow-up: [User to add: quote from the form]." You write that form, so write the follow-up promise into it.

Marketing operations own the spec with the account owners, and SDRs no longer send event follow-up to customers or to people who already had a personal message.

Hand-off: after your Yes, the spec goes to your platform admin as a build brief; the skill builds nothing itself.

1. Pick one account with real whitespace and run Account research on it before anyone writes an email.
2. Build the account plan, then run it again with an "Objections:" line. If it lists the signer as missing, that is the first meeting to get.
3. Run the trap setter against the competitor by its real name, and agree the criteria with your champion early.
4. Turn the account into lookalike searches, add the signer titles, and rank what comes back.
5. Before your next roundtable, write the follow-up promise into the registration form, spec the follow-up with the account gate first, and decide who owns customers who attend.

1. Researching an account you cannot verify. A brief full of unverified fields gives the SDR nothing to use; confirm the facts on a call first.
2. Reading the tier as a judgement. The account plan's tier is a rule on ARR, and the gap list is where the judgement sits.
3. Fighting the competitor under a placeholder name. A real name gets you questions about its contract and its references.
4. Searching only for champions. The lookalike lead search uses your champion titles, so add the people who sign.
5. Putting customers into event nurture. A customer who attends a roundtable belongs to the account owner, with one plan for the whole account.

• How to Size Your B2B Market Bottom-Up and Score Target Accounts Without Inflated Analyst Numbers
• One B2B Deal From MEDDPICC Discovery to a CFO-Ready ROI Case and a Dated Close Plan
• Trust-Led Enterprise Selling in Fintech and Cybersecurity: Buying Group, Landmines and a Risk Brief
• All 15 guides