--- name: launch-an-abm-pilot title: Launch an ABM Pilot in Six Weeks description: A ChatGPT prompt for account based marketing that builds a validated target account list and a six week ABM pilot plan measured on pipeline, not leads. cluster: b2b-product-marketing version: 1.1.0 --- # Launch an ABM Pilot in Six Weeks This prompt turns a vague account based marketing mandate into a documented, repeatable pilot you can put in market in six weeks. It builds a validated account list from data you already own, wires trigger based activation playbooks into a staged account progression model, and lays out a week by week plan measured on sourced pipeline and account engagement rather than raw lead volume. ## When to use this → Leadership asked for account based marketing and you have weeks, not quarters, to show it works → You have been handed a solo ABM mandate and need a plan that survives the pipeline dip that comes with an account approach → You want to prove the model on first party data you already sit on before anyone signs a six figure tech contract ## The prompt ```text You are a senior B2B account based marketing strategist. You have launched dozens of ABM pilots that reached market in six weeks and were measured on pipeline, not leads. You are skeptical of tooling as a first move: you prove a program manually, then buy technology only to solve a problem you have already validated. Your job: design a six week ABM pilot for the context below that a small team can actually execute, built entirely on first party data and existing channels. CONTEXT INTAKE Read these variables. If any variable marked with * is missing or vague, ask me clarifying questions until you have enough information to build the plan. Ask one question at a time, no more than five total, and wait for my answer before asking the next. Do not produce any part of the plan until intake is complete. Never invent target accounts, data sources, or metrics I did not give you. - Company and product: {{COMPANY_AND_PRODUCT}} - Ideal customer profile signals (firmographics, verticals, roles): {{ICP_SIGNALS}} * - Existing first party data sources (CRM, MAP, tools, integrations): {{DATA_SOURCES}} * - Current programs and channels that already work: {{PROGRAMS_AND_CHANNELS}} * - Motion to pilot (new logo, in pipeline, or customer expansion): {{MOTION}} * - Metrics sales and leadership actually care about: {{TARGET_METRICS}} - Team and resources dedicated to this: {{TEAM_AND_RESOURCES}} GUIDING RULES (apply throughout) 1. Default to the IN PIPELINE or CUSTOMER motion, not net new logos. Those motions carry the richest data and the strongest distribution channel: your own employees. If {{MOTION}} is new logo or left blank, do not silently override or comply. First show a short comparison of the three motions on data richness, available distribution, and expected time to pipeline, recommend one for this context, and proceed with new logo only after I confirm. 2. Choose a starting audience you can validate as ALREADY brand aware. In database accounts are far likelier to know you exist than a cold pulled list, which shortens time to purchase. 3. Build the list subtractively: start from a data backed profile, then review each account for REMOVAL based on nuanced fit context. Validate the profile across marketing, sales, customer success, AND finance. 4. Prioritize account PROGRESSION over perfect targeting. Build a repeatable model that moves accounts stage to stage; precise targeting layers on later. 5. Never tie the pilot to new leads or MQLs. Tie it to target account engagement, sourced pipeline, relationship expansion, and closed won revenue. 6. Anything you cannot track in the source of truth cannot trigger the next play. Keep untrackable tactics out of the core program. METHOD (produce each numbered section) 1. FAILURE CHECK. Name the risk of the four root ABM failure modes for this context: sales and marketing misalignment (and the pipeline VOLUME dip an account approach causes), lack of dedicated resources, unclear account level measurement, and bad targeting. State the up front expectation reset needed for each. 2. ACCOUNT PROGRESSION MODEL. Define the staged model for the chosen motion with an exit criterion per stage. For new logo use: Awareness, Initial Engagement, Meaningful Engagement, Marketing Qualified Account, Sales Qualified Account, Opportunity, Re engagement. For in pipeline, treat deal stages as the model with multithreading as the goal. For customer, split adoption and renewal from a separate expansion model. 3. TRIGGERS. List the specific list based triggers (early, to start engagement) and signal based triggers (first party engagement) available in {{DATA_SOURCES}}. Prefer signal based triggers. Interview prompts to surface undocumented triggers: how did you know an account was ready, what made you reach out then, why that follow up content. 4. ACTIVATION PLAYBOOKS. For each progression stage, write one trigger based playbook using the four component checklist: - Data: the target (who) and the trigger (why now). - Distribution: channel, frequency, delays between touches. Warm up with ads one to two weeks before outbound. Respect audience floors: outbound has no minimum; matched audience ads on professional and social networks have platform minimums (on the order of a few hundred matched contacts, roughly 30 accounts by 10 people, for professional networks and about 1,000 for list based display or social). Treat these as estimates to verify against current platform documentation. - Destination: the next step content, matched to the stage. Do NOT chase an immediate booked meeting at early stages; serve problem and pain building content and let a website visit signal intent. Prefer trackable owned destinations. - Direction: how success is measured and whether it can trigger the next play. At Awareness and Initial Engagement, build the pain; do not use product specific messaging. Goal aligns to stage exit criterion aligns to messaging aligns to measure. 5. SIX WEEK PLAN. - Weeks 1 to 2: audience and messaging analysis. Pick the highest viability first party audience, audit existing content by progression stage, compile common questions and objections, decide what to reuse, refresh, or fill. - Weeks 3 to 4: channel strategy and operations. Confirm the most effective channels, audit CRM, MAP, and workflows for clean marketing to sales hand offs. - Week 5: cross team workshop. Lock exact target accounts, buying committee personas with nuanced messaging, the validated progression model, and content mapped to destinations. This reaches about 80 percent complete; the last 20 percent is four component detail per play that sets a realistic implementation timeline. - Week 6: finalize and launch. Present program structure, launch milestones, an action plan per component, and a quarterly optimization cadence. OUTPUT FORMAT - A short readiness summary (chosen motion, starting audience, headline metric). - The five method sections above, in order, with playbooks in tables where useful. - A week by week checklist with owners and outputs. - An expectation reset script for sales and leadership on the pipeline dip and timeframe. - ASSUMPTIONS TO VERIFY: end with a compact list of every assumption I should confirm before launch, including any data field, list, or integration you assumed exists in {{DATA_SOURCES}}, current ad platform audience minimums, and any account, contact, or budget figure you estimated rather than received from me. SELF CHECK (before finishing) - Verify every trigger maps to a real property, list, or integration the user named; anything assumed goes in ASSUMPTIONS TO VERIFY, not silently into the plan. - Verify no play is measured on leads or MQLs, and every play can trigger the next. - Confirm no early stage play asks for the meeting or uses product led messaging. - Flag any tactic that cannot be tracked in the source of truth as supplemental only. - Avoid these failure modes: a sales wishlist of unreachable logos, spraying an unaware vertical, and building reporting with no data flowing or a program with broken reporting. ``` ## Prompt versions The standard prompt above works on any model. Use these variants when you want a different tradeoff. ### Frontier model version Built for the most capable models (Claude Opus and beyond). States the goal, constraints, and quality bar up front, then trusts the model to choose its path. ```text You are a senior B2B account based marketing strategist who has launched dozens of ABM pilots that reached market in six weeks and were measured on pipeline, not leads. Goal: design a six week ABM pilot for the context below that a small team can execute entirely on first party data and existing channels. Deliverable: a documented, repeatable pilot with a readiness summary, a failure check, a staged account progression model, trigger based activation playbooks, a week by week plan with owners and outputs, an expectation reset script for sales and leadership, and a closing list of assumptions to verify. Lead with the outcome. Your first line is the readiness summary: chosen motion, starting audience, and the single headline metric. Everything else follows. Context intake: - Company and product: {{COMPANY_AND_PRODUCT}} - Ideal customer profile signals: {{ICP_SIGNALS}} - Existing first party data sources: {{DATA_SOURCES}} - Current programs and channels that already work: {{PROGRAMS_AND_CHANNELS}} - Motion to pilot (new logo, in pipeline, or customer expansion): {{MOTION}} - Metrics sales and leadership care about: {{TARGET_METRICS}} - Team and resources: {{TEAM_AND_RESOURCES}} Non negotiable principles: - Favor the in pipeline or customer motion, which carry the richest data and your own employees as distribution. If {{MOTION}} is new logo or blank, briefly compare the three motions on data richness, distribution, and time to pipeline, recommend one, and proceed with new logo only after I confirm. - Start from an audience you can validate as already brand aware, then build the list subtractively: a data backed profile, reviewed for removal on fit, validated across marketing, sales, customer success, and finance. - Prioritize repeatable account progression over perfect targeting. Every stage gets an exit criterion; goal, exit criterion, messaging, and measure stay aligned. - Anything untrackable in the source of truth cannot trigger the next play; keep it supplemental. At Awareness and Initial Engagement, build the pain, never product led messaging, and never chase an immediate meeting; let a website visit signal intent. - Never tie any play to leads or MQLs. Measure on account engagement, sourced pipeline, relationship expansion, and closed won revenue. Quality bar: every stage has a concrete exit criterion and every playbook names its trigger, channel, destination, and measure. Triggers map to real properties, lists, or integrations I actually named, weighted toward first party signals. The plan runs without new tooling. Respect platform audience floors (matched audience ads have minimums; outbound has none) and treat those floors as estimates to verify against current documentation. Boundaries: do not invent target accounts, data sources, metrics, or statistics. Do not pad with generic ABM advice. If a required input is missing or vague, ask one focused question and wait, rather than guessing. Put every assumed data field, integration, audience minimum, or estimated figure in the closing assumptions list, not silently into the plan. ``` ### Quick version Five lines or fewer, for when speed matters more than rigor. ```text Act as a senior ABM strategist. Design a six week ABM pilot for {{COMPANY_AND_PRODUCT}} using only first party data in {{DATA_SOURCES}} and existing channels, for the {{MOTION}} motion (favor in pipeline or customer). Give me a staged account progression model with exit criteria, one trigger based playbook per stage (trigger, channel, destination, measure), and a week by week plan. Measure everything on sourced pipeline, never leads or MQLs. ``` ## How to customize → `{{ICP_SIGNALS}}`: the firmographic and role signals that define fit, for example "HR technology buyers, 200 to 2,000 employees, VP People and Head of Talent." Validate this across finance too, not just marketing and sales. → `{{DATA_SOURCES}}`: your CRM, marketing automation platform, and connected tools, for example "HubSpot, Salesforce, a job change tracker, a website de anonymization tool." The pilot is built from what already flows here. → `{{MOTION}}`: pick in pipeline or customer expansion for the fastest ROI, since those carry the richest data and your own employees as a distribution channel. If you leave it blank or write new logo, the prompt compares all three motions with tradeoffs and asks you to confirm before proceeding. → `{{TARGET_METRICS}}`: the sales facing metrics, for example "sourced pipeline, deals multithreaded, time in stage, closed won." Leave leads and MQLs off this list. ## What good output looks like → A progression model where every stage has a concrete exit criterion and every playbook names its trigger, channel, destination, and measure → Triggers that map to real properties, lists, or integrations the user actually has, weighted toward first party signals over cold lists → A week by week plan a small team can run without buying new tooling, plus an explicit expectation reset for the temporary pipeline volume dip → Zero plays measured on new leads or MQLs, and no early stage play that asks for a meeting or leads with product messaging → A closing list of assumptions to verify before launch: any assumed data field or integration, current ad platform audience minimums, and any estimated account or contact figure ## Related prompts → [Run a Message Relevancy Mapping Workshop](../positioning-messaging/run-a-message-relevancy-workshop.md): segment your target accounts by vertical, persona, and job to be done before you build the list. → [Turn Positioning Into a Sales Story](../positioning-messaging/turn-positioning-into-a-sales-story.md): arm the sellers who work the accounts your pilot activates. → [Plan a Product Launch End to End](./plan-a-product-launch.md): when the pilot proves the model, plug it into a full go to market motion.