Tutorial

How Do You Write an ICP One-Pager for a New SDR?

Written by
Pravin Kumar
Published on
Oct 21, 2026

How do you write an ICP one-pager for a new SDR?

Write one page with six parts: the company profile, the buyer roles, the problem they feel, the signals that show timing, the disqualifiers, and two or three real examples. Use plain language, real customer names where you can, and specific details a rep can check in minutes. Keep it to one page so it gets read and reused.

New SDRs often get a slide deck about the market, a long persona document, and access to the CRM, then are asked to start prospecting. The information is technically there, but it is scattered. What they need on day one is a short reference they can keep open while building lists and writing emails.

This tutorial walks through writing that page in a Google Doc. It takes about two hours the first time, mostly spent pulling real examples from your closed-won deals.

Why does a new SDR need a one-pager rather than a full ICP document?

Because they will use it dozens of times a day, and a long document does not survive that. A full ICP document serves strategy. A new rep needs fast answers: does this account fit, who do I contact, and what do I say? A one-pager answers those in seconds, so it is the version that shapes their work.

It also creates consistency. When every rep works from the same page, list quality and messaging stay aligned. Without it, each rep forms their own idea of a good account, and pipeline quality drifts.

Finally, it speeds up ramp time. A rep who can quickly judge fit spends less time on bad accounts and gets to real conversations sooner. That is the fastest way to build confidence in the first month.

Step one: how do you describe the company profile?

Describe the companies that buy and succeed, using attributes a rep can check quickly. Include industry or vertical, size range in employees or revenue, business model, and any technology they typically use. Be specific. "B2B SaaS companies with 30 to 300 employees using HubSpot" is far more useful than "growing tech companies."

Base the profile on closed-won data, not on aspirations. Pull your best customers from HubSpot or Salesforce, the ones who bought quickly and stayed, and look for what they share. That shared pattern is your real ICP, even if it differs from what your pitch deck says.

If you already score accounts, link the one-pager to that rubric. My tutorial on writing an ICP scoring rubric in a spreadsheet covers how to build one, and the one-pager should summarize it in plain words.

Step two: which buyer roles should the page name?

Name the two or three roles involved in buying, and say what each cares about. Usually there is someone who feels the problem daily, someone who owns the budget, and sometimes someone who must approve the tool. For each role, write one line on what they care about and one line on what makes them respond.

Give real job titles, as they appear on LinkedIn. A rep searching for "VP of Revenue Operations" needs to know that "Head of RevOps" and "Director of Sales Operations" are the same buyer in different companies. List the common title variants for each role.

Also say who to contact first. In many B2B sales, starting with the person who feels the problem works better than starting with the budget holder. Make that recommendation explicit so the new rep does not have to guess.

Step three: how do you describe the problem in the buyer's words?

Write the problem in one or two sentences using the language customers actually use, not your marketing language. Pull phrases from discovery call notes, call recordings in tools like Gong, or customer interviews. A new SDR who uses the buyer's words in an email sounds like they understand the problem, not like they are reading a script.

Include what life looks like before your product. "Leads sit in a shared inbox for a day before anyone replies" is a concrete pain a rep can reference. "Inefficient lead management" is a phrase nobody says out loud.

If your product solves several problems, pick the one that most often starts a buying conversation. The one-pager is not the place to list everything. It is the place to name the problem that opens doors.

Step four: which timing signals should the page list?

List the events that suggest an account may be ready now, such as hiring for a related role, raising funding, a new leader in the buying function, or adopting a tool your product works with. For each signal, add one line on why it matters, so the rep can mention it naturally in outreach.

Keep this list short, usually three to five signals, and order them by how strongly they predicted deals in the past. A new rep should know which signal to prioritize when an account shows several at once.

Point to where each signal can be found. Some appear on LinkedIn, some in enrichment tools like Clay or Apollo, some on the company's own careers page. A signal the rep cannot find is not useful to them.

Step five: what disqualifiers should the page include?

List the clear reasons an account is not a fit, so the rep can skip it without debate. Common disqualifiers include being too small, using a tool you do not integrate with, being in a regulated industry you do not serve, or already being a customer or competitor. Disqualifiers save more time than any other section.

Write them as hard rules where possible. "Under 20 employees: skip" is easier to apply than "very small companies may not be a fit." Soft judgments slow new reps down because they feel they need to check with someone.

Include a short note on what to do with borderline accounts, such as flagging them for a manager rather than working them. That keeps the rep moving while still catching the occasional exception worth pursuing.

Step six: why add real examples, and how?

Real examples make the abstract concrete. Add two or three short descriptions of actual customers that fit the ICP, with the company type, the role who bought, the problem they had, and what triggered the purchase. A new SDR learns more from three real examples than from any list of attributes.

If customer names are confidential, describe them without naming. "A 120-person HR software company whose sales ops lead was manually routing leads" is still useful. The goal is pattern recognition, not name dropping.

Add one example of a bad fit as well. Showing an account that looked right but was not, and why, teaches judgment faster than any rule.

How do you keep the one-pager current?

Review it every quarter against recent closed-won and closed-lost deals. If new patterns appear, update the profile, signals, or disqualifiers. Date every version at the top so reps know how fresh it is. An ICP one-pager that drifts out of date quietly sends reps after the wrong accounts.

The quarterly review pairs well with turning sales notes into updates. My guide on turning closed-won notes into an ICP update covers how I run that review.

Make it part of onboarding too. A new SDR should read the one-pager on day one and walk through it with a manager. That conversation surfaces questions early, and it fits naturally into the broader process in onboarding a new SDR to your GTM stack.

What should you do next?

Open a Google Doc and create six headings: company profile, buyer roles, problem, timing signals, disqualifiers, and examples. Pull your ten best customers from your CRM and fill each section from what they share. Keep it to one page, date it, and walk your next new SDR through it on their first day.

The page will feel too simple. That is the point. Simple is what a new rep can use quickly and consistently.

If you want help defining your ICP or building the systems that keep reps working the right accounts, reach out. I build GTM systems for B2B teams and I am glad to help.

Get found, cited and the back office automated

Let's make your site the source AI engines quote and wire up the systems behind it.

Contact

Let's get your website found and cited by AI

Tell me what you're working on, whether AI search is skipping your product, your back office is buried in manual work, or you need a build that does both.

Got it, thanks. I read every message personally and reply within 1-2 business days.
Oops! Something went wrong while submitting the form.