How-to guide

How to run an ABM pilot that proves pipeline, not just engagement

An ABM pilot is the fastest way to find out whether account-based marketing will work for your company before you spend six figures on a platform like 6sense or Demandbase and reorganize two teams around it. The pilot that works is small, tightly scoped, and brutally honest about measurement. It picks a short list of named accounts, agrees on how success will be judged before anyone runs an ad, and runs for a fixed 90 days with a scheduled retro at the end. This guide walks through the 8 steps that keep an ABM pilot from drifting into a vague brand campaign and ending with no clear decision at the finish line.

Before you start

What you need.

Time: 90 days

  • A written ICP that defines firmographics, technographics, and the trigger events that make an account a fit right now
  • A target account list of 25 to 50 named companies agreed in writing by sales leadership and marketing leadership
  • Sales and marketing aligned on one shared pipeline goal for the pilot and the account tier each rep will cover
  • Written success criteria with a baseline and a target for engagement, meetings booked, and sourced pipeline
  • A tracking plan that defines how each metric is measured, where the data lives, and who runs the weekly report
Run an account-based marketing pilot with sales and marketing aligned on 25 to 50 target accounts

Step by step.

  1. 1

    Pick 25 to 50 target accounts with sales in the room

    The pilot stands or falls on the account list. Build it with sales, not in a vacuum. Start from your ICP and layer in intent signals, product fit, and territory coverage, then sit with the AEs who will own the accounts and ask them to defend or veto each one. The goal is a list of 25 to 50 companies that sales genuinely wants to win and that marketing can realistically influence in 90 days. Smaller than 25 and the pilot cannot produce statistically meaningful engagement signal. Larger than 50 and marketing cannot personalize for every account at a level that moves the needle. Lock the list in writing before anything else happens so neither side can quietly swap accounts mid-pilot to make the numbers look better.

    • Pull a long list of 150 to 300 ICP-fit accounts from your CRM and enrichment tools.
    • Score each account on fit, intent, and open-opportunity status, then rank the list.
    • Review the top 60 with the AEs owning the territory and let them cut or add with reasons.
    • Freeze the final 25 to 50 in a shared doc with the AE, SDR, and marketer named on each.
    Tip: Treat the account list like a budget: fixed, visible, and audited. If an account drops off, document why in writing. Silent swaps are the single most common way an ABM pilot stops being measurable.
  2. 2

    Agree on 1:1 versus 1:few coverage per account tier

    Not every target account gets a bespoke microsite. Split the list into tiers before you start building anything. A typical pilot runs 5 to 10 accounts as 1:1 with deep personalization, 15 to 25 accounts as 1:few in small clusters that share an industry or use case, and the remainder as 1:many with programmatic ads and standard content. Pick the split with sales so AEs know which accounts they are expected to work manually and which marketing is driving. The split also drives budget: 1:1 campaigns typically consume 3 to 5 times the content and ad spend per account of a 1:few campaign, so getting the tiering right in week one is what keeps the pilot inside its budget envelope by week nine.

    • Define the three tiers with a specific content and spend budget for each.
    • Place each named account into exactly one tier with the AE's agreement.
    • Document the plays that run against each tier: ads, direct mail, outbound sequences, events.
    • Confirm who owns execution on each play so nothing lands with no owner.
    Tip: If sales wants every account in the 1:1 tier, that is a budget conversation, not a strategy conversation. Agree on the per-account cost of 1:1 up front and let the economics drive the tiering.
  3. 3

    Build account research the whole team can use

    A good ABM pilot runs on shared account intelligence, not scattered notes. Before any campaign ships, build a one-page research brief for every tier 1 and tier 2 account that covers the buying committee, recent 10-K or funding commentary, strategic initiatives, current tech stack, trigger events, and any Strkr relationships or past engagement. The brief lives in the CRM on the account record so AEs, SDRs, and marketers all read from the same source. This is where ABM separates from generic demand gen. Without shared research, personalization devolves into dropping the company name into an email subject line, and the pilot cannot defend its spend when sales leadership asks what the extra effort bought.

    • Pick a one-page template with sections for committee, initiatives, stack, triggers, and relationships.
    • Assign a researcher per cluster of accounts, either an SDR, a marketer, or an intern on a timeline.
    • Refresh the brief monthly during the pilot so it does not go stale by week six.
    • Store the brief on the CRM account record, not in a shared drive the team forgets to open.
    Tip: If you have intent data from a vendor like Bombora, 6sense, or Demandbase, pull the top three surging topics per account into the brief. That is the single highest-leverage data point for personalizing a campaign.
  4. 4

    Define a pilot playbook of 3 to 5 touches per account

    The pilot needs a repeatable play, not a one-off burst. Design a 3 to 5 touch sequence per tier that marketing and sales execute together over 60 to 75 days inside the 90-day window. A workable tier 1 play might be a personalized LinkedIn ad flight, a direct mail package timed to a trigger, a custom landing page with industry proof, an SDR sequence that references the ad and the mail, and an AE breakout meeting invitation once engagement crosses a threshold. Document the exact assets, timing, and handoff rules so every account in the tier gets the same treatment. The playbook is what you are actually testing. If the playbook works, you scale it. If it does not, the pilot tells you which step to redesign.

    • Map the 3 to 5 touches on a timeline that fits inside days 10 through 75 of the pilot.
    • Specify the asset, channel, owner, and trigger for each touch in a shared doc.
    • Define the handoff rules: what engagement score moves an account from marketing to SDR to AE.
    • Dry-run the full play on 2 or 3 accounts in week one to catch broken links and bad data.
    Tip: Resist the urge to run a different custom play per account. The pilot's purpose is to learn whether a repeatable playbook works, which requires enough accounts going through the same play to see a pattern.
  5. 5

    Align sales and marketing on one weekly cadence

    ABM dies in the gap between sales and marketing. Close the gap with a single 30-minute weekly meeting that both teams attend from kickoff through retro. The agenda is fixed: engagement signal on each tier 1 and tier 2 account, meetings booked in the last week, blockers from either side, and the next week's priorities. Use the same scoring and the same dashboard both teams see. If the AE says the engagement data looks wrong and the marketer says the AE is not following up on surging accounts, that is the exact conversation the weekly meeting exists to have. Keep the meeting narrow and the dashboard real. Status theater kills ABM pilots as fast as weak account lists.

    • Book the weekly meeting on the calendar from week zero through week 14 with the same attendees.
    • Build one shared dashboard with engagement, meetings, and sourced pipeline by account.
    • Open every meeting on the account list, closed every meeting on next-week commitments.
    • Escalate missed handoffs or stalled accounts in the meeting, not in Slack side-channels.
    Tip: Keep the meeting invite small. Core attendees are the pilot lead on each side, one AE from the territory, and the SDR. Larger meetings turn into status readouts and lose the direct accountability that makes ABM work.
  6. 6

    Launch the pilot on a fixed start date

    Pick a start date and launch everything in a two-week ramp. Trying to ramp slowly over four weeks blurs the measurement window and makes the end-of-pilot retro harder. In the first two weeks ship the ad flights, the direct mail waves, the landing pages, the SDR sequences, and the AE touches. From that point the pilot is live for the next 10 weeks and the dashboard runs weekly. Flag the launch internally so leadership knows the clock has started. The launch date is also what makes the 90-day boundary enforceable at the retro. Without a launch date on the calendar, pilots quietly stretch into six months and nobody can defend their outcome.

    • Set the launch date in writing and share it with sales, marketing, and leadership.
    • Front-load creative, ad trafficking, direct mail, and SDR sequence setup into weeks minus-two to zero.
    • Spot-check the full play on 2 or 3 accounts on day one to confirm all touches fire correctly.
    • Announce the launch internally so account owners know their accounts are now live.
    Tip: Build a small escape hatch in week one for emergency fixes: a broken landing page, a direct mail misdelivery, a mis-targeted ad. Fix fast, document the fix, and keep the clock running.
  7. 7

    Measure engagement, then meetings booked, then pipeline

    Every ABM pilot gets judged on three questions in order: are the target accounts engaging more than before, are those engagements converting to real meetings, and are those meetings turning into pipeline. Report in that order every week. Engagement without meetings is a signal that the handoff is broken or sales does not trust the data. Meetings without pipeline is a signal that the ICP is wrong or the play is reaching the wrong buyer. Keep the baseline measurements from before the pilot visible on the dashboard so the lift is honest. ITSMA research on ABM programs consistently shows that mature ABM programs produce multi-x improvements in pipeline from target accounts, but those gains only show up when all three layers are measured and reported together.

    • Define three metrics with a baseline and a target: account engagement rate, meetings booked per account, sourced pipeline per account.
    • Pull the baseline from the 90 days before the pilot so the comparison is apples to apples.
    • Report all three metrics weekly, never engagement in isolation.
    • Attribute meetings and pipeline to the pilot using CRM campaign fields on the account record.
    Tip: If engagement is up but meetings are flat for three consecutive weeks, the problem is almost always the SDR handoff. Fix the handoff before you touch the campaign.
  8. 8

    Run the 90-day retro and make a scale or kill decision

    Book the retro on the calendar at kickoff and hold it on day 90. The retro has four parts: results against the written success criteria, what the pilot proved about the playbook, what it taught about the account list and ICP, and a decision. The decision has three options. Scale, which means increasing the account list, hiring, and buying a platform like 6sense or Demandbase if the pilot proved out the economics. Iterate, which means running a second 90-day pilot with a redesigned playbook or a sharper ICP. Kill, which means ABM is not the right motion right now and the budget moves elsewhere. All three outcomes are legitimate. The failure mode is a retro with no decision, which is how companies end up running ABM pilots for four years without ever committing or walking away.

    • Prepare a results doc that walks each success criterion from baseline to final result.
    • Walk the playbook step by step and name which touches drove engagement, meetings, and pipeline.
    • Invite sales leadership, marketing leadership, and the pilot team to the retro.
    • End the meeting with a scale, iterate, or kill decision in writing with named owners for next steps.
    Tip: If the decision is scale, budget for the platform and the headcount in the same document that captures the retro. ABM programs that scale on borrowed capacity from the pilot team almost always regress inside two quarters.
Avoid

Common mistakes.

  • Picking 200 accounts instead of 25 to 50 because sales leadership did not want to leave any territory out. The pilot stops being measurable the moment the list is too big to personalize.
  • Letting marketing build the account list without sales in the room, then watching AEs ignore the list in week three because none of their real deals are on it.
  • Reporting engagement in isolation. A dashboard that shows account engagement up 40 percent and does not show meetings or pipeline is not an ABM dashboard, it is a vanity metric.
  • Running the pilot without a baseline. Without the 90 days of data before the pilot, the retro turns into a debate about what the numbers would have been anyway.
  • Skipping the retro or holding it with no decision. A pilot without a scale, iterate, or kill call at day 90 produces no learning and no mandate for the next 90 days.
FAQ

Frequently asked questions.

How many accounts should an ABM pilot cover?

25 to 50 named accounts is the right range for a first pilot. Fewer than 25 and the engagement data is too thin to detect a pattern. More than 50 and marketing cannot personalize at a level that justifies the extra spend over standard demand gen. Lock the list in writing before launch and audit any mid-pilot changes.

How long should an ABM pilot run?

90 days is the standard. The first two weeks are a launch ramp, the middle 10 weeks are campaign execution, and the final two weeks cover measurement, the retro, and the scale or kill decision. Pilots shorter than 60 days rarely produce enough meetings or pipeline signal to defend a scale decision. Pilots longer than 120 days tend to lose focus and sponsor attention.

Do I need a platform like 6sense or Demandbase to run an ABM pilot?

No. A pilot can run on your existing CRM, a marketing automation platform, LinkedIn ads, and a shared account list in a spreadsheet. The point of the pilot is to prove the motion works at your company before you commit to a six-figure platform purchase. If the pilot succeeds and you scale, that is when a dedicated ABM platform usually earns its cost.

What is the right success criteria for an ABM pilot?

Three criteria with baselines and targets: account engagement rate on the target list, meetings booked per account, and sourced pipeline per account over the 90 days. All three measured against the 90 days before the pilot started. Reporting any one of these without the other two makes it very hard to make an honest scale or kill decision at the retro.

Who owns an ABM pilot inside the company?

Co-ownership between a marketing lead and a sales lead works best. Marketing owns campaign design, assets, and reporting. Sales owns the account list, the AE and SDR execution on each account, and the handoff rules. A single weekly meeting between both leads with the AEs covering tier 1 accounts is the forum where the pilot actually gets steered.

How much budget does a 90-day ABM pilot usually need?

A workable range for a 25 to 50 account pilot is 50,000 to 150,000 dollars covering ad spend, direct mail, content production, and any contracted creative or research. The number varies with industry and tier mix. The honest answer is that budget matters less than the discipline on account list, playbook, and measurement. A tight 60,000 dollar pilot can outperform a loose 200,000 dollar pilot by every metric that matters.

See it in Strkr

Related product surfaces.

Strkr Marketing Strkr CRM Strkr platform features

Run a tighter ABM pilot with sales and marketing on one record

Strkr keeps your target account list, buying committee, engagement signal, meetings, and sourced pipeline on the same account record so your pilot retro answers the scale or kill question with real data, not slide theater.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.