BootcampCapstone · Deliverable 1

ICP & Prospect List (Account Plan)

Builds on Topic 5.

What you'll produce

A one-page Ideal Customer Profile (ICP) plus a researched list of 10 target accounts — each with named contacts, a specific "why now" trigger, and the buying-committee role (champion, economic buyer, user) you'd open with. This is the artifact an SDR builds on day one of a new territory and rebuilds every quarter: it's the difference between spraying 200 generic emails and landing 10 relevant conversations. It proves the core Topic 5 skill — prospecting the right people, not everyone — and it feeds your entire capstone: every later artifact (outreach sequence, discovery call, demo, forecast) is run against accounts on this list. Get this wrong and you spend the rest of the program selling to companies that were never going to buy.

Instructions

You are the new SDR at Lumadesk (AI-powered support helpdesk — shared inbox, ticketing, AI reply drafting, ~$40/agent/month, ~$18k–$60k ARR per deal). Your territory: mid-market (50–500 employees) e-commerce and online-services companies whose support teams are drowning in tickets. Build the account plan you'd actually hand your manager.

  1. Write the one-page ICP — define fit before you build any list. Capture, in tight bullets: firmographics (industry, employee count, geography, business model — e.g., DTC e-commerce, 50–500 staff); the team you sell into (support / customer-experience org, typically 5–40 agents); the problem you solve (ticket volume outpacing headcount → slow response times → churn and bad reviews); and 3–4 observable "qualifying signals" that mean a company likely has this pain right now (hiring support agents, order-volume spikes, public complaints about response time, no modern helpdesk).
  2. Write 2–3 disqualifiers (the anti-ICP). Be explicit about who you'll qualify out before wasting a touch — e.g., under 50 employees (no budget/no team), no support function, or already on a strong incumbent they just bought. This is Topic 4's "qualifying out" applied at the top of the funnel.
  3. Name the buying committee for this product. Map the three roles from Topic 3 to real job titles at your accounts: the champion (feels the pain daily — Head of Support / CX Manager), the economic buyer (controls budget — VP Customer Experience / COO / CFO at smaller orgs), and the user (support agents / team leads). Note who you open with and why.
  4. Build the list of 10 accounts. Lead with GearGrid (your named target), then 9 look-alike accounts that fit the ICP. For each: company name, employee count, why it fits the ICP in one line, and a specific, evidenced "why now" trigger — a hiring post, a funding round, a season, a public review complaint, a tooling gap. "They're growing" is not a trigger; "posted 3 support-agent roles last week and Trustpilot reviews cite 48-hour reply times" is.
  5. Add a target contact + role for each account — sourced the way a real SDR sources. For every account, identify the person you'd open with: their title, which buying-committee role they play, and the one-line opener angle tied to their trigger, not your features (Topic 5: lead with their problem). Find the actual human the way an SDR does — search the company on LinkedIn (filter the company's people by titles like "Head of Support," "CX Manager," "Customer Experience"), or check the team/about page. When you find them, use their real name. When you can't confirm a real name, do not invent one — write a placeholder title instead (e.g., "Head of Customer Support (name TBD — confirm on LinkedIn)"). A real, specific title and angle on a real account is worth far more than a made-up full name: the title tells you who to find, the fake name just creates a person who will bounce the moment you actually hit send.
  6. Prioritize the list into tiers. Rank the 10 into Tier A (work first — strongest fit + hottest trigger), Tier B, Tier C. A real SDR doesn't work 10 accounts equally; they sequence them. State the one-sentence logic for your Tier A picks.
  7. Keep it honest and specific. Use real companies and triggers you could actually find on LinkedIn / a company careers page / Trustpilot — no "Company X," no generic stand-ins for accounts or triggers. Contacts are the one place a placeholder is correct, not lazy: when you can't verify a real name, a placeholder title ("Head of CX — confirm on LinkedIn") is the honest, usable answer; a fabricated full name on a real-named company is the one thing that looks polished and fails in the field. Never pair a made-up person's name with a real company you'd actually email.

Worked example

(Product sold: Lumadesk. Territory: mid-market DTC e-commerce & online services, 50–500 employees, support teams overwhelmed by tickets.)

Ideal Customer Profile — Lumadesk (one page)

  • Industry / business model: Direct-to-consumer e-commerce and online-services brands (apparel, outdoor gear, beauty, subscription boxes, marketplaces) where customers contact support frequently — order status, returns, sizing, billing.
  • Company size: 50–500 employees (mid-market). Sweet spot 150–350: big enough to have a real support team and budget, small enough that the Head of Support can champion and buy without a 9-month enterprise cycle.
  • Team we sell into: The support / customer-experience org — 5–40 agents on a shared inbox or an aging helpdesk, often led by a single Head of Support or CX Manager who owns response-time and CSAT metrics.
  • Core problem we solve: Ticket volume is outgrowing headcount. Response times stretch to 24–48+ hours, agents copy-paste the same replies all day, and slow support shows up as 1-star reviews and churn. Lumadesk's AI reply drafting + shared inbox cuts handle time and response time without proportional hiring — the ROI story: one $40/agent tool that lets a 10-agent team handle the load of 14.
  • Qualifying signals ("why now" triggers to look for):
    1. Hiring support agents (3+ open "Customer Support / CX" roles = volume is hurting now).
    2. Order/traffic spike — recent funding, a viral moment, a peak season (holiday, summer for outdoor gear), or "doubled volume" language in press/LinkedIn.
    3. Public complaints about response time — Trustpilot / G2 / app-store reviews citing slow or no replies.
    4. Tooling gap — running on a shared Gmail inbox or a legacy/basic helpdesk, no AI assistance (visible from job posts, tech-stack tools, or careers-page mentions).
  • Disqualifiers (anti-ICP — qualify out early):
    • Under ~50 employees — usually 1–2 person support, no budget, founder still answers tickets. Too small to land $18k+ ARR.
    • No real support function — pure B2B with a handful of named accounts, or self-serve only; the pain we solve isn't there.
    • Already on a strong, recently-bought incumbent (e.g., just rolled out Zendesk + an AI add-on last quarter) — timing is wrong; revisit at renewal, don't burn touches now.
  • Buying committee (who I'm selling to):
    • Champion → Head of Support / CX Manager / Support Team Lead. Feels the pain every day, owns the metrics that hurt, gets the win if it's fixed. This is who I open with.
    • Economic buyer → VP Customer Experience / COO (or CFO at leaner orgs). Controls budget, needs the ROI/business case. I reach them through the champion once value is proven.
    • User → Support agents / team leads. Live in the tool daily; their adoption and enthusiasm make or break the deal. I bring their voice into discovery and the demo.
  • Open-with logic: Lead with the champion (Head of Support), tied to their trigger, because they own the pain and the metrics. Earn their buy-in, then multi-thread up to the economic buyer.

Prospect list — 10 accounts

Contact column convention (how a real SDR fills this): a name only when LinkedIn / the team page confirms it; otherwise the title plus "(confirm on LinkedIn)" — a real to-do, not a fake person.

#Account~EmployeesFit (why it's ICP)"Why now" triggerTarget contact (title — name if confirmed)Committee roleOpener angle
1 ⭐GearGrid220DTC outdoor-gear retailer, growing support teamDoubled order volume; hiring 3 support agents; Trustpilot reviews cite slow response timesHead of Customer Supportconfirmed on LinkedIn (name on file, owns CSAT per profile)Champion"Saw you're adding 3 agents after doubling volume — most DTC teams hit a wall on response time before headcount catches up. How are reply times holding?"
2TrailLoop Outfitters180DTC outdoor apparel, peak summer season2 open CX agent roles; summer-season volume surgeCX Manager — name TBD; confirm on LinkedIn (filter people by "CX")Champion"Heading into peak season with the team you have — curious how you're planning to keep reply times down without over-hiring."
3NestBox140Subscription home-goods box, recurring billing ticketsSeries A $12M raise 6 weeks ago; scaling opsHead of Support — name TBD; check LinkedIn + team pageChampion"Congrats on the raise — fast scaling usually means ticket volume jumps before the team does. How's support keeping up?"
4VeloKit260DTC cycling-gear marketplaceTrustpilot: multiple "waited 3 days for a reply" reviews this monthCustomer Experience Lead — name TBD; confirm on LinkedInChampion"Noticed a few reviews mention multi-day reply waits — that's almost always a volume problem, not a team-effort one. Worth a quick look?"
5GlowRoutine110DTC beauty/skincare, high return rateHiring Support Team Lead + 2 agents; running on shared Gmail inboxOperations Manager — name TBD; lean org, may double as buyer — confirm on LinkedInEconomic buyer (lean org)"Building out a support lead role is the moment most beauty brands outgrow a shared inbox — happy to share what teams your size move to."
6PantryClub300Online grocery/subscription, high ticket frequencyHoliday volume + 5 open support rolesVP Customer Experience — name TBD; confirm on LinkedInEconomic buyer"5 support openings going into your busy quarter signals real volume pressure — there's usually a way to cut the hiring you need in half."
7FitForge95DTC fitness-equipment, shipping/returns heavyRecent warehouse expansion → shipping-query spikeSupport Manager — name TBD; confirm on LinkedInChampion"Warehouse expansions tend to flood support with shipping questions — how's your team absorbing that?"
8PetPantry240DTC pet-food subscription, billing/delivery ticketsMigrating off a legacy helpdesk (mentioned in a job post)Head of CX — name TBD; check the hiring manager named on the job postChampion"Saw you're re-platforming support tooling — good moment to look at AI drafting before you lock in the next 2 years."
9LumenHome320DTC smart-home devices, technical support loadProduct recall last quarter → ticket surgeDirector of Customer Support — name TBD; confirm on LinkedInChampion → economic buyer"Recalls hammer support teams for months — curious how reply times have held since, and whether the team's been able to recover."
10SnackDrop75Subscription snack box, simple billing ticketsHiring 1 agent; small but growingFounder / Ops owner — name TBD; founder likely on team pageEconomic buyer"At your size the founder usually still touches support — there's a point where that stops scaling; happy to flag the signs."

Tiering (work order)

  • Tier A (work first): #1 GearGrid, #4 VeloKit, #3 NestBox. Strongest fit and hottest, most-evidenced triggers (doubled volume + hiring + public complaints; live review complaints; fresh funding). A clear champion is identifiable at each. These get my best personalization and the full outreach sequence first.
  • Tier B: #2 TrailLoop, #6 PantryClub, #8 PetPantry, #9 LumenHome. Solid fit, real but slightly softer or seasonal triggers. Worked right after Tier A.
  • Tier C: #5 GlowRoutine, #7 FitForge, #10 SnackDrop. Smaller or earlier-stage; #10 borders the disqualifier line (75 employees, founder-led support) — I keep it as a low-priority watch, not a priority touch.
  • Logic: GearGrid is #1 because it stacks three independent triggers (volume, hiring, reviews) on a textbook-ICP company with a named champion — the highest-probability conversation in the territory, so it gets worked first and hardest.

Rubric

The app's AI scores your submission against these criteria and gives feedback. Levels: Needs work (1) / Solid (2) / Excellent (3). Passing = every criterion at Solid or above; revise and resubmit until it passes.

  • ICP fit & qualifying signals — 1: vague ("any company that needs support software") or missing observable signals · 2: clear firmographics plus the problem and 2–3 signals · 3: sharp ICP with 3–4 observable qualifying signals an SDR could actually find, and a stated sweet spot/reason it matters.
  • Disqualifiers (anti-ICP / qualify-out) — 1: none, or only restates the ICP · 2: 2–3 real disqualifiers · 3: precise disqualifiers tied to why each kills the deal (no budget, no pain, wrong timing), reflecting Topic 4 qualifying-out.
  • Buying committee mapped to real titles — 1: roles missing or generic · 2: champion/economic buyer/user mapped to plausible titles · 3: roles mapped to specific titles and a clear, justified "who I open with" decision.
  • 10 accounts with specific, evidenced "why now" triggers — 1: fewer than 10, or triggers are generic ("they're growing") · 2: 10 ICP-fit accounts each with a real trigger · 3: 10 tight-fit accounts with specific, evidenced triggers (a hiring post, a review, a raise, a season) you could verify, GearGrid clearly led.
  • Sourced contacts (right title + role) + opener that leads with the problem — 1: no contact target, openers pitch the product, or invented full names pinned to real-named accounts (a fabricated person on a company you'd actually email — the habit this artifact exists to break) · 2: each account has a realistic title mapped to the right committee role, an honest placeholder ("name TBD — confirm on LinkedIn") wherever the name isn't verified, and a relevant angle · 3: every account names the right title and committee role, shows real sourcing discipline — a confirmed name where one was findable, an honest title-placeholder elsewhere, never a made-up name on a real account — and a one-line opener that leads with their trigger/problem, never Lumadesk's features.
  • Prioritization (tiering) — 1: list is undifferentiated · 2: accounts grouped into tiers · 3: A/B/C tiers with explicit logic for the Tier A picks (fit × trigger strength × reachable champion).