Blog

Account plan example for a technical deal

Short answer: An account plan example shows what a finished plan looks like: a tier with one reason, fit with sources, dated reasons to call now, named roles, a split between what you know and guess, and one next step. The example below uses an invented company so you can copy the shape.

Templates are easy to copy and hard to picture. This page shows one account plan, filled in, for a technical deal. Read it once to see how long each section runs, what a good "why now" line looks like, and where guesses go.

The company, its people and every date below are invented. Nothing here is a fact about a real business. The plan follows the account plan template; if you want the empty version, start there. If you want the idea behind it, read what account planning is.

The situation

You sell reliability tooling to engineering teams. Your best customers are tired of alerts nobody acts on. You have a list of accounts to work. Tidewater Freight Systems, an invented logistics software company, is one of them. You have 20 minutes to build its plan before a first note goes out.

The plan

Account plan: Tidewater Freight Systems (invented)

1. Account and tier
Tidewater Freight Systems, tidewater.example. Tier: act now. First staff reliability role posted; the platform team owns on-call.
2. Fit
Runs its services on Kubernetes (engineering article, September 12). Engineering team of 80 or more, judging by the careers page (October 24). Blocker to check: no public note of how it reviews new vendors.
3. Why now
October 6: job post for a staff reliability engineer, duties include "redesign the on-call rotation". September 12: article on moving to Kubernetes. September: status page shows four incidents. Undated lead: a conference talk on alert noise, date not shown.
4. People
Director of platform engineering, named as hiring manager in the October 6 post (checked October 24). Staff site reliability engineer who gave the alert-noise talk (checked October 24). Reviewer: unknown.
5. Known and unknown
Known: the hire, the migration, the incidents. Guess: they have no dedicated alerting tool, because the migration article names none. Not found: who reviews new vendors, and whether the talk was recent.
6. Next step
Note to the staff engineer about the talk, by Friday. Fallback: the director on Monday.
7. Log
October 24: plan written. No contact yet.

The people table

Section 4 reads better as a table once you have more than two names. This is the same section with the role in the deal and the reason each person cares.

PersonRole in the dealWhy they careChecked
Director of platform engineeringTeam ownerPosted the reliability role; owns on-callOct 24
Staff site reliability engineerFeels the problemGave a talk on alert noiseOct 24
UnknownReviewerAsk who reviews new tools-

Why each section reads the way it does

  • The tier has a reason. "Act now" alone is an opinion. "First staff reliability role posted" is something you can check next month.
  • Fit lists a blocker. A plan that only lists reasons to buy is a pitch to yourself. The unknown review process is the thing most likely to slow this deal.
  • Every why-now line has a date. The talk has none, so it is labeled an undated lead and doesn't carry the plan. The guide to buying signals explains how to treat each age.
  • People have a check date. Names go stale. The date tells you whether to confirm before you write.
  • The guess is marked. "They have no dedicated alerting tool" came from what an article didn't say. It tells you what to ask, not what to state.
  • The next step is one action. One person, one date, one fallback.

What this plan leaves out on purpose

There is no company history, no funding story, no list of the product's features and nothing about anyone's private life. None of it changes what you do next. Anything that would be true of any logistics company stays out. The pre-call research checklist has a short list of what to skip.

Make it yours

  1. Copy the section names, not the contents.
  2. Fill each section from public sources, and write the date next to each fact. If you can't find one, write "none found" and leave it. That is a useful answer.
  3. For a deal with several teams, add a stakeholder map after the people section.
  4. Set a weekly review. After each contact, add one dated line to the log and change the sections it affects.

Where Repclose fits

Repclose writes plans like this one for each account on your list. Its plans have sections such as At a glance, Why now, Green flags and Supporting sources, and each point links to its source with the publication date where available. Points that come from your notes are labeled as yours, and guesses as inferred. See a real one in the sample brief, or start with your first 5 plans free.

Common questions

What does a good account plan example include?

A tier and the reason for it, fit with a source for each point, dated reasons why now, the roles you plan to reach, what you know and what you guess, one next step with a fallback, and a log.

Is the company in this example real?

No. Tidewater Freight Systems is invented, and so are its dates and people. In your own plan, every statement needs a real source and date.

How often should I update the plan?

After each contact, add a dated line to the log and update the sections it changes. Once a week, review the plans for the accounts you are working.

Related guides