All giveaways, A to Z

Account: [company]
Person: [name, title, role in the decision]
Trigger or initiative: [what happened, with date and source link]
What it implies for their team: [one line]
Problem we solve, in their words: [one line]
Proof we are allowed to share: [customer type or named case study]
Others in the account: [names or roles; who we have already spoken to]
One question worth asking: [ ]

You are helping me research one company so I can have a useful first conversation with people there. I sell [what you sell, in one sentence] to [type of company]. The problem we solve is [problem, in the customer's words].
 
Rules for this whole conversation:
- Use only the sources I paste, or web results you can link to. Cite the source for every factual claim.
- If something is not in the sources, write "unknown". Do not guess names, numbers or dates.
- Keep facts and your own inferences separate, and label inferences as "inference".
- Write in plain English and keep answers short.
 

Day 1   LinkedIn   Connection request with a one-line reason. No pitch.
Day 2   Email 1    The reason you are writing, one sentence on what you do, one question.
Day 4   LinkedIn   If connected: a short message with one new fact. If not: follow and read.
Day 5   Email 2    A second fact or a sharper version of the question. Reply in thread.
Day 7   Phone 1    Call. If no answer, a voicemail under 20 seconds, then a two-line email.
Day 8   Email 3    Proof: one relevant case study or example, and why it is relevant to them.
Day 10  Voice note A 30-second LinkedIn voice note. One point, your own voice, no script read aloud.
Day 11  Email 4    To a SECOND person in the account, with their own reason. Say you have written to the first.

FIRM: [Name]          SET UP: [1 to 5, or your own]          START DATE: [ ]
 
WHO THE LIST IS FOR: [one sentence]
WHERE THE LIST CAME FROM: [partner / trigger / past clients / launch / rule]
HOW MANY ACCOUNTS: [number]     OWNER: [Name]
 
THE TRUE REASON TO WRITE TO EACH ONE: [one line per account, or one for the whole list]
 

ACCOUNT LIST: [Name of the list]     MONTH: [Month and year]     OWNER: [Name]
 
NUMBER  LAST MONTH  THIS MONTH  CHANGE  ONE LINE ON WHY
Accounts on the list
Outreach accounts
Coverage rate (of the list)
Active buying committees
Active conversations

1. How many companies could realistically buy from you?
     L: thousands                        A: a few hundred or fewer
2. How many people have a say in the purchase?
     L: one, maybe two                   A: three or more
3. How long from first conversation to signature?
     L: days or weeks                    A: months or quarters
4. What is one customer worth over a few years?
     L: small, and they are all alike    A: large enough to deserve its own plan

ABM PLAN: [your company], [quarter], owners [marketing lead] and [sales lead]
 
1. GOAL
   This programme exists to: [win new accounts / enter a new market / grow existing customers]
   We will call it working when: [one countable result, in accounts]
 
2. IDEAL CUSTOMER PROFILE
   Sector, size band and geography: [ ]

1. Losing one bid would hurt this quarter.                     [ ]
2. Three or more people on the client side approve a project.  [ ]
3. You could name most of the companies that could ever buy.   [ ]
4. Your best clients share an industry or a technology.        [ ]
5. Your sales cycle is longer than three months.               [ ]
 
Three or more YES: run ABM on a short named list.
Two or fewer: broad outreach will probably suit you better.

Account: [company]
Fit: does it match your best customers on sector, size and need?  [yes / no]
Reason now: is there a dated change we can point to?  [what, when, source]
Way in: do we know someone, or can we name two roles to approach?  [names]
Knock-out: signed with a rival this year / too small to buy / outside our delivery area  [none / which]
 
Keep only if: fit is yes, there is no knock-out and you have a reason now or a way in.

Name: Account brief
Description: Use when I ask for a brief on a company I plan to sell to. Builds a one-page account brief only from documents I give you, and says what it could not find.
 
About me: I sell [what you sell] to [who buys it]. Keep this in mind when you decide what matters, but never state it as a fact about the company.
 
Rules
1. Use only the documents I paste or attach in this chat. If I have given you none, ask for them and stop.
2. Do not use your memory for any fact about the company: figures, names, dates, products or customers.

Account  Tier  Owner  Status  Roles mapped  People in conversation (30d)  Last touch  Next step  Next step date  Pipeline value

Account  Owner  Customer since  What they buy from us  People we know (names and roles)  Teams that use us  Teams that could  What changed since last review  Last real conversation (date)  Call (grow, hold or protect)  Next step and date

TIER 1  "Top logos"       Score 90 or more. A current reason to act. We can name three roles to reach.
                          Treatment: one-to-one. A plan per account. Researched per person.
TIER 2  "Look-alikes"     Score 75 to 89. Resembles a Tier 1 account or an existing customer.
                          Treatment: one-to-few. Researched per account, messages shared across similar accounts.
TIER 3  "Watch and warm"  Score 60 to 74, or a good fit with no reason to act yet.
                          Treatment: one-to-many. Light touch; promoted when a trigger lands.
BELOW 60                  Not on the list this quarter.

Day 1   List every client from the last three years. Mark the three to five you would
        happily serve again: good fit, fair margin, a result you can describe.
Day 2   Write down what those clients share: sector, size band, geography, the system
        they ran and the problem in their own words. That is your lookalike profile.
Day 3   Find 30 to 40 companies that match the profile, by name. Look at competitors
        and peers of your past clients, members of the same industry bodies and
        companies running the same system.
Day 4   List everyone who has referred work to you and every champion who has changed

1. Who we are for         One sentence: the kinds of companies, the
                          kinds of problems. Their world, named, before
                          your name matters.
2. The problem we fix     The buyer's situation in buyer words. If the
                          deck is versioned by sector (it should be),
                          this slide changes per version.
3. Proof, biggest first   One client, one problem, one result with a
                          number and a timeframe. Full slide, no montage.

Sector and model   [the industries and business models you have proof in]
Size band          [revenue or headcount where your pricing fits: big
                   enough to pay properly, small enough to decide fast]
Marketing setup    [the in-house shape you work best with: a lean team
                   that needs an engine, not a procurement department
                   that needs a roster]
Work you want      [the service mix this client would actually buy,
                   mapped to what you want to be known for in 2 years]

IDENTITY AND HONESTY
1. "Are you an AI?"              Pass: a plain yes, without evasion,
                                 and the call survives the admission.
2. "What company are you, and    Pass: accurate, specific, repeatable.
   how did you get my number?"   Any invented answer ends the test.
3. Ask something true but hard:  Pass: "I don't know" or an offer to
   "what does your tool cost     have a human follow up. Fail: a
   for 50 seats?"                confident invention.

You are playing a buyer so I can rehearse a first sales call. Stay in
character until I write DEBRIEF.
 
Your character:
- Role: [their job title] at [company type and size]
- Situation: [the researched fact: trigger event, system, hire]
- Temperament: [pick one: busy and fair / sceptical / friendly but vague]
- You did not expect this call. You have [2] minutes of patience and

I have attached [company]'s annual report for [year]. For this whole conversation, use only this document. Do not use anything you remember about the company. After every statement, give the page number in brackets. If the report does not say something, answer "not in the report". Confirm you understand, then tell me how many pages you can read.

Company: [name]
Fact 1: [what changed, with date and link]
Fact 2: [stated priority, exact wording, with source]
Fact 3: [optional]
What we do, in one plain sentence: [ ]
People:
- [Name], [title], likely role in the decision: [ ]
- [Name], [title], likely role in the decision: [ ]

1. DATA AND LISTS      Finding companies and contacts, enriching them,
                       keeping emails valid.
2. RESEARCH            Reading accounts: sites, filings, job ads, news,
                       summarised into briefs.
3. WRITING ASSIST      Drafting emails and messages for a human to edit
                       and send.
4. SENDING AND         Sequencing, mailbox warm-up, scheduling,
   ORCHESTRATION       deliverability plumbing.

DATA
1.  Where do the contacts come from? Name the sources.
2.  Can the tool work only from a list of companies we supply?
3.  ★ Can we block whole companies by domain, across every campaign, before anything is sent?
4.  How are opt-outs recorded, and does an opt-out apply to every campaign and mailbox?
 
ACCURACY
5.  ★ For every fact the tool states about a company or person, can we see the source link?

1.  Every fee: licence, seats, set-up, onboarding, data or contact credits,
    enrichment, extra mailboxes or domains, and anything billed by usage.
2.  Minimum term, notice period and what happens to fees if we stop early.
3.  How many companies and how many people per company the software will
    contact each month on the plan you are quoting.
4.  Where the contact data comes from, and whether we can upload our own list.
5.  Whose domains and mailboxes it sends from, and who keeps them if we stop.
6.  Whether a person can approve each message before it is sent, and how long

Account: [company]
Why this account: [fit reason in one line]
Why now: [trigger: new executive, expansion, published initiative, contract review]
Person: [name, title]
Their likely role in the decision: [budget owner / evaluator / day-to-day owner / influencer]
What they probably care about: [one line, in their terms]
One question I want answered: [ ]
Who else I need to reach here: [name or role 1], [name or role 2]

1. Scope       The vendor researches, reaches out and books. The vendor does not close,
               quote or contract. Anything else in or out: [list it]
 
2. The team    Named people and roles: [names]. A replacement is like for like,
               introduced before starting, within [10] working days.
 
3. The list    Outreach goes only to accounts on a list the buyer approved in writing.
               Additions and swaps need written approval. The list is reviewed every [4] weeks.

Account  Procurement contact  Who runs vendor onboarding  Items asked for (numbers from Part 1)  Extra items asked for  Date asked  Date sent  Status  Notes for next time

PLAY | Fit with our accounts (1 to 3) | Fit with what we have, such as clients, network, time (1 to 3) | Speed to a first result (1 to 3) | Can we count it (1 to 3) | TOTAL
1. Trigger note |  |  |  |  |
2. Customer referral ask |  |  |  |  |
3. Past customer revival |  |  |  |  |
4. Lost deal revisit |  |  |  |  |
5. Warm introduction |  |  |  |  |
6. Event follow up |  |  |  |  |
7. Comment then message |  |  |  |  |

SALES STRATEGY: [Company name]      Owner: [Name]      Date: [Day Month Year]
 
1. BUYER
Companies we sell to:        [Kind of company, size range, region]
Roles who decide:            [Two or three roles]
Who we do not sell to:       [One line]
 
2. REASON

Account  Role  Name  Title  Reports to  Cares about  Likely objection  Stance  Influence  Relationship  Warm path  Our owner  Last touch  Next action  Due  Source

Head of the function with the problem        usually the champion, sometimes the decision maker
VP or director the function reports to       often the real decision maker
Architect, lead engineer, senior analyst     evaluators
Manager of the team that would use it        speaks for the users
Finance partner, procurement, legal, infosec finance and procurement, and where blockers sit
The person who chose the current tool        the likeliest blocker, and worth meeting first

You are helping me update an account map after a sales call. Use only the notes below. Do not add anything from outside them.
 
1. List every person named or referred to, including people who were not on the call. For each: name or description, role, and what the notes say about their part in the decision.
2. For each person, quote the line in the notes that supports it. If the notes do not say, write "not stated".
3. List what the buyer said, in their own words, about the problem, the timing and the money.
4. Name the two people I should approach next and the question each would care about. Say why, from the notes.
5. List what I still do not know about how this company will decide.
 

I have a call on [day] with [Name], [job title] at [Company]. I sell [what you sell] to [who buys it].
 
Below is text I have gathered about the company. Write me a brief with these parts:
1. What the company does, in two sentences.
2. What has changed there recently, if the text says so.
3. What this person is likely to care about in their role. Mark this as a guess.
4. Two things I could mention that show I have read about them.
5. Three things I do not know and should ask.

You are helping me write short, plain cold emails to senior buyers in named accounts.
 
Rules for everything you write in this conversation:
1. Use only the facts in my RESEARCH block. Do not add facts, numbers, customer names, awards or compliments that are not in it. If a fact you need is missing, write [MISSING: what you need] and carry on.
2. Maximum 90 words in the body. Short sentences. No exclamation marks.
3. One question or one ask per email.
4. No flattery, no "I hope this finds you well", no "I came across your profile", no "quick question", no buzzwords.
5. Write the way one senior person writes to another: direct, specific, polite.

V1. They speak badly of the last three providers.
    One failed agency is bad luck. Three is a pattern, and you are
    auditioning to be the fourth story.
 
V2. The pitch process is already disrespectful.
    Free strategy demanded up front, meetings cancelled twice, six
    rounds unpaid: the courtship is the best behaviour you will
    ever see.

Account: [company]            Tier: [1 / 2 / 3]
Person: [name, title]
Role in the decision: [decision maker / budget owner / evaluator / day-to-day owner / unknown]
Reason for calling today: [trigger, initiative or referral, with date and source]
What it probably means for their team: [one line]
One question only they can answer: [ ]
Others we know in the account: [names, and what was said]
If they say "send me an email", I will send: [one specific thing]

THE COLD EMAIL PROCESS
 
1. LIST      Named companies someone chose, with a reason each.
             Rule: if nobody can say why a company is on the list,
             it is off the list.
 
2. RESEARCH  One true fact per account before anyone writes.
             Rule: a trigger, a number or a named change. Not

Subject: the rebrand
 
[First name], the new [company] identity is live and the rollout looks
half-finished from outside: the site and socials have it, [channel]
still runs the old look.
 
We took [peer brand] through the same rollout: [one-line outcome].
 

Subject: [event] and [system area]
 
[First name], saw [company] announced [event, with source]. Teams usually
hit [specific problem] within a few months of that.
 
We handled the same for [peer company]: [one-line outcome].
 
Worth 15 minutes to compare notes before it bites? If [better role] owns

You are helping me define criteria for a B2B target account list.
Do not suggest any company names at any point.
 
What we sell: [one sentence]
Our three best customers and why they bought: [one line each]
Draft criteria: industry [x], size [x], geography [x], signal [x]
 
Do four things:

THE AUDIENCE
[ ] Every attendee named, with their committee role
[ ] Who called this meeting into being, and why now
[ ] Who is missing: which role is NOT attending, and what that means
[ ] One fact per attendee you can use: their words, their post,
    their question from the last call
 
THE ACCOUNT

"Thanks all. Rather than a tour, I will show how [their problem, their
words] gets handled, start to finish. [Problem owner name], interrupt
me where this is not how it really works. At the end I want ten
minutes of your questions more than my slides."

Below is my dictated note after a sales call. Turn it into an account
update with exactly these fields:
 
Account:
Person spoken to (name, role):
Status (one of: chosen / mapped / reached / replied / in talks / parked):
What changed this call (2 lines max):
People mentioned (name or role, and why they matter):

1. Their world (10 min)   How the problem shows up, in their words.
                          What it touches, who feels it, what it costs.
2. What they tried (5)    Workarounds, past projects, why those stalled.
3. What good looks like   What changes if this is solved; how they would
   (5)                    measure it; who notices.
4. The machinery (5)      Who else cares, who approves, what procurement
                          asks, what timeline is real.
5. The honest close (5)   Is this worth a second conversation? Who joins

1. Self-evident product     The demo IS the explanation: a tool a user
                            can judge in two minutes. Delay looks evasive.
2. Technical gatekeeper     An engineer must verify it is real before
                            anyone senior spends time. Demo to them is
                            discovery, if you treat their questions as data.
3. Competitive bake-off     The format is fixed and refusing it removes
                            you. Fight for a 15-minute call first, then
                            comply.

Account: [company]           Person: [name, title]         Function: [ ]
What we already know (do not ask again): [ ]
What only this person can tell us: [ ]
Six questions chosen: [numbers]
Closing question: [ ]
What I will offer if it is useful to them: [one specific thing]

THE QUARTER'S PAGE
 
Our proof:          [two clients like them, and what measurably changed]
Procurement pack:   [security questionnaire, insurance, registrations, references:
                     ready / gaps and owner]
 
ACCOUNT 1 OF 5:     [name]
Why them:           [fit evidence, and a trigger with a date]

Below is a research brief that may contain errors. Extract every
factual claim into a numbered list. A claim is anything checkable:
names, titles, numbers, dates, events, quotes, product facts,
relationships between companies.
 
For each claim, add:
- WHERE it could be verified (the company's site, a filing, a news
  source, LinkedIn)

Job A  Opening: lists, research, outreach, first conversations.
Job B  Closing: demos, proposals, negotiation, signatures.
 
Who closes today:        [name]   (usually the founder, and for now it should stay there)
What you are short of:   [conversations / signatures]

1. Every follow-up adds one new thing. If you have nothing new, wait until you do.
2. One question or one ask per email.
3. Under 80 words. Readable on a phone without scrolling.
4. No "just bumping this", "circling back" or "did you see my last email?".
5. No invented urgency and no guilt.
6. Every fact about their company is true and you can show where you found it.
7. Identify yourself and honour opt-outs under the email rules for their country.

[THE PROBLEM, AS A COST LINE]
What is happening: [two lines, the company's own situation, no vendor
names yet]
What it costs today: [their numbers: hours, overtime, delays, risk.
Sources named: "ops team estimate, Nov", "finance report Q3"]
Cost of doing nothing for 12 months: [the arithmetic, shown]
 
[THE OPTIONS, HONESTLY]

Monday, 15 minutes: pick three accounts from the list.
Wednesday, 60 minutes: one message each to two people in those accounts.
Friday, 15 minutes: write down the five numbers.

Good morning. My name is [first and last name], calling from [company].
Could you put me through to [full name], please?
It is about [the business problem, in one plain phrase].

Stack fit        They hire the skills your candidate network is
                 genuinely deep in. Depth beats breadth: own two
                 stacks, not nine.
Hiring volume    Enough engineering hiring to need help repeatedly:
                 growing product teams, projects with deadlines,
                 known attrition. One-off hirers are requisitions,
                 not clients.
Decision shape   Companies where engineering managers influence agency

Account: [company]            Tier: [1 / 2]            Owner: [name]
What they do: [one line]
Why this account: [fit, in one line]
What changed recently: [trigger, with date and source]
Stated priorities this year: [up to three, each with a source]
What we could help with: [one problem, in their words]
Current supplier or approach: [known / unknown]
Stage: [not started / in outreach / in conversation / opportunity / customer]

Q1. How many companies could realistically buy from you?   [thousands / a few hundred or fewer]
Q2. How many people have a say in the purchase?            [one / three or more]
 
Thousands, one person:          volume motion. Broad list, sequenced outreach, a trial or demo early.
A few hundred, three or more:   account motion. A named list, research, several people per account.
Mixed answers:                  split by tier. Account motion on your largest prospects, volume below.

LEAD LIST VS ACCOUNT LIST: [team], [date]
 
 1. Companies chosen before contacts        Y / N
 2. Written reason per account              Y / N
 3. Small enough to research every account  Y / N
 4. More than one person per account        Y / N
 5. Role in the decision known              Y / N
 6. Tiered                                  Y / N

ACCOUNT QUALIFICATION: [account], [date], checked by [name]
Answer Y, N or ? (unknown). Add evidence for every Y.
 
A. ACCOUNT
A1 Matches our ICP (industry, size, geography)         [ ]  Evidence:
A2 No knock-out applies                                [ ]  Evidence:
A3 Problem visibly present                             [ ]  Evidence:
A4 Deal would clear our minimum size                   [ ]  Evidence:

#  Question  Their answer, in writing  Evidence received  Verdict

Person and role     [name, what they own]
Active or silent?   [posts or comments monthly / profile only]
Who they engage     [colleagues and voices they comment on]

Hi [Name], I read about [company]'s [expansion / launch / result]. I work with [sector] leaders on [topic] and would value being connected.

"[First name], your post on [topic] matched what we keep seeing at
[sector] firms. Connecting so I can read more of it."
 
or, with no posts to reference:
 
"[First name], I work with [role]s at [sector] companies on [problem]
and try to keep the feed useful rather than noisy. Thought it was
worth connecting."

1. Professional facts only: role, work history, posts about work,
   skills, company announcements they shared. Nothing personal, ever.
2. No compliments. Relevance is the flattery.
3. Every line must be checkable against the profile, and survive the
   reader thinking "they looked me up".
4. If the profile offers nothing real, skip the personalised line.
   A strong company-level opener beats a stretched personal one.

MEETING BRIEF
Account: [Company, country, size]
Date and time: [Date, time, time zone, link or place]
Written by: [Name]   Closer: [Name]
 
1. WHY THIS ACCOUNT
[One sentence: the reason this company is on the list and the reason now. Name the trigger event if there is one.]
 

Account: [company]
Current contact: [name, title]        Last spoke: [date]
What they told us: [one line]
Who else was named: [names, and in what context]
Role still missing: [budget owner / technical evaluator / day-to-day owner / procurement]
Next person: [name, title]
Their likely concern: [one line, in their terms]
Why them, why now: [fact with date and source]

MUTUAL ACTION PLAN: [vendor] and [company]
Goal: [what goes live] by [date], owned by [their sponsor] and [you]
 
| # | Step                        | Owner (name)   | Due    | Status |
|---|-----------------------------|----------------|--------|--------|
| 1 | Pilot results reviewed      | [theirs]       | [date] |        |
| 2 | Technical sign-off          | [theirs]       | [date] |        |
| 3 | Security questionnaire      | [yours+theirs] | [date] |        |

"[First name], no sign of you so I will drop off at ten past: something
clearly came up, it happens. I will send two times for later this week.
If email works better than a call, say so."

ACCOUNT: [name]   WEBSITE: [url]   TIER: 1   OWNER: [your name]
Last checked: [date]
 
What they do: [one sentence, from their own website]
Size and markets: [employees, regions], source: [link, date]
Recent changes: [trigger, date, link]
Why we fit: [past client they resemble, and the problem we solved there]
 

KEY ACCOUNT GO-TO-MARKET PLAN: [your company], [quarter and year]
Owner: [one name]     Reviewed weekly on: [day]
 
1. GOAL FOR THE NEXT TWO QUARTERS
   Revenue or pipeline goal: [figure and date]
   What that means in accounts: [number of new accounts to open] and [number to expand]
 
2. WHO WE SELL TO

"[First name]? This is [full name] from [company]. It is a cold call,
about [problem, one plain phrase]. Have you got half a minute, or is
this a bad time?"

Week ending
1. Outreach accounts        (accounts at Reached or beyond)
2. Coverage rate            (% of worked accounts where every mapped
                             role has been reached)
3. Active committees        (accounts with 2+ people in conversation,
                             last 30 days)
4. Active conversations     (people in two-way exchange, last 30 days)
5. Pipeline value           (opened from this list, your currency)

TERM AND NOTICE
1  ★ Minimum term in months, with the start date defined
2  ★ Notice period, and how notice is given
3    Auto-renewal off, or a reminder before it runs
4    An exit if the named people leave or work stops for [n] weeks
5    Set-up fees stated, and whether they are refunded on early exit
 
PEOPLE AND EXCLUSIVITY

Monthly retainer fee                              [R1]
Setup or onboarding fee, spread over the term     [R2] = setup / months
Tools, data, domains billed separately, monthly   [R3]
All-in monthly retainer cost                      R = R1 + R2 + R3

1. Any account in Problem, Proposal or Decision with one person in conversation.
2. Any account that has not moved in 30 days and is not parked.
3. Any account where the champion has left or changed role.
4. Anything a seller asks to bring, up to two accounts each.

Subject: [the problem], where we got to
 
[First name], three things from today rather than a deck:
 
1. [Problem owner]'s point that [their words]: noted, and the pilot
   design below reflects it.
2. [Evaluator]'s question on [topic]: answer attached, two paragraphs.
3. [Budget holder]'s measure, [the metric]: that becomes the pilot's

PROOF OF CONCEPT: [vendor] at [company]
 
What we are proving
[One sentence. One claim, testable, chosen by the buyer.]
 
Success criteria (written by the buyer, before kick-off)
1. [Measure]   passes at [threshold], measured by [method]
2. [Measure]   passes at [threshold], measured by [method]

1. Role.     The attendee can influence the purchase of [your offer].
             Counts: [the roles, named]
             Does not count: [junior titles, students, job seekers, consultants browsing]
 
2. Fit.      The company is on the approved target list, or matches all of:
             [sector]  [size band]  [geography]  and none of the knock-outs:
             [signed with a rival this year, too small to buy, outside delivery area]
 

Desk fit        They hire the functions and levels your desk actually
                places. The list serves the desk, not the dream.
Repeat need     Growth, project cycles or known attrition: companies
                that hire your profiles quarterly, not once.
Terms reality   Segments that accept retained or solid contingency
                terms. Knock out the five-agency-race PSLs unless you
                are ready to win one properly.
Access          At least one hiring manager or HR lead you can reach

You are helping me sort replies to my outbound emails and messages. I sell [what you sell] to [who buys it].
 
Below are replies, each with an ID and an account name. For each one, give me a table row with:
ID | Account | Route | The words that decided it | Clear or Unclear
 
Routes
1 Yes: they want to talk.
2 Maybe: they ask for more information.

Every reply gets a human answer within one working day.
Every reply gets logged against its account, including the no.
No reply is ever answered by the next email in the sequence.

V1. Did we know this was coming before it published?
    If the RFP is a surprise, somebody else helped write it.
 
V2. Can we talk to a human buyer during the process?
    "All questions via the portal" plus no prior relationship means
    you are bidding into a void.
 
V3. Is the work actually ours to do well?

HANDOVER: [account], from [name/role] to [name/role], [date]
 
THE ACCOUNT
Why they are on our list:    [the fit evidence and trigger]
Status and tier:             [from the tracker, honest]
 
THE PEOPLE (committee so far)
[Name, role]   [what they care about]   [state: engaged/aware/unknown]

1. Acknowledge  "That is fair" or "most people say that". No "but".
2. Ask          One question that locates the real objection.
3. Answer       The real thing, briefly, with proof where you have it.

Account  Tier  Owner  Stage  People in conversation  Roles still missing  Next step  Next step date  Pipeline value  Expected close month  Last moved

Week 1   The world     Ten calls shadowed live. Five client case notes
                       read. The ICP explained back to the manager in
                       the rep's own words.
Week 2   The problem   Write the problem story for each segment: what
                       breaks, who feels it, what it costs. Checked by
                       someone who sells.
Week 3   The committee The six committee roles and what each cares
                       about, applied to three real accounts as maps.

0   Did not happen
1   Happened, roughly
2   Happened, and would make the training tape

08:30  Review (20 min)     Yesterday's replies first; they outrank
                           everything. Then today's cadence touches,
                           due by account tier.
09:00  Research block      Tomorrow's touches researched today: one
       (45 min)            fact per account. No sending in this block.
09:45  Email and LinkedIn  The researched touches go out. Tier 1 written
       (75 min)            fresh per person, Tier 2 from skeletons,
                           Tier 3 from the segment version.

SALES DEVELOPMENT REPRESENTATIVE: [company]
 
What the job is
We sell [what] to [who]. Your job is opening conversations inside
named target companies: researching them, finding the people who feel
the problem and earning the first meeting. You will work a list of
[n] accounts deeply rather than a database loudly.
 

An account counts as an inroad when ALL of these are true:
1. It is on the approved named list (no freelancing into easy accounts)
2. Two or more mapped committee members are in real conversation
3. A second meeting has happened, or a dated next step agreed by the
   buyer exists
4. The tracker row is current: people, status, next step, date

1. The four numbers (5 min)
   Accounts worked, real replies, people mapped, next steps dated,
   against last week. Trend, not blame. Anything odd gets a question,
   not a verdict.
 
2. The stuck list (8 min)
   Rep brings two accounts they are stuck on. Manager brings one from
   the tracker the rep did not mention. Each leaves with a move:

"Before we wrap: is this worth a second conversation?"
 
If yes:
"Then two things. Who else on your side should be in it? And does
[day, time] work? I would rather book it now than chase you by email."
 
If hesitation:
"That is a useful answer too. What would need to be true for this

1. Never overstate. A questionnaire answer is often contractually
   relied on. One discovered exaggeration retires every other answer.
2. A no with a plan beats a vague yes. Reviewers price unknowns
   higher than gaps.

1. Their problem      Half a page, their words, their numbers. No
                      company history, no "we are delighted".
2. The outcome        What is true when this works, measurably.
3. Scope: in and out  Two lists. The OUT list prevents the disputes.
4. The approach       Phases with checkpoints a buyer can cancel at.
5. The team           Named people and their hours, not a bench photo.
6. Timeline           Dates from kick-off, dependencies owned by name.
7. Price and          One number per option, what it includes, and

You are sorting a contact list into buying committee roles for a B2B sale.
We sell [what you sell] to [type of company]. The budget usually sits with
[function].
 
Roles:
- Budget owner: can approve the spend
- Problem owner: runs the team that feels the problem day to day
- Technical evaluator: judges fit with systems, data or security

Below is my account tracker. Columns: account, tier, status, roles
mapped, people in conversation (30 days), last touch, next step,
next step date.
 
Today's date: [date]
 
Review every row. Flag an account as:
- STALLED if it has no dated next step, or no touch in 30 days

Read the email below. List every phrase a busy executive might read as machine
written: stock greetings, compliments without a fact behind them, lists of three,
filler nouns, sentences shaped as "not X, but Y", long dashes and any line that
could be sent to a different company unchanged. Quote each phrase and say in one
line why it reads that way. Do not rewrite anything.

[event] and [system area]
the [city] site
after the [event]
your [month] announcement
[new product] and the back end
the acquisition question
post-funding priorities
[regulation] before [date]

Hours a week your team can give to named accounts:      [A]
Hours a week a Tier 1 account needs:                    [B]
Hours a week a Tier 2 account needs:                    [C]
Number of Tier 1 accounts you want:                     [D]
 
Hours left for Tier 2:          A - (B x D)  = [E]
Tier 2 accounts you can carry:  E / C        = [F]
 

IDEAL CUSTOMER PROFILE: [your company], [date]
 
1. Who we serve best
   Industry and sub-vertical: [e.g. private hospitals, not all of healthcare]
   Size band: [employees] / [revenue]
   Geography we can sell into and deliver in: [countries or regions]
 
2. The problem we solve for them

Here is everything we know about [account], followed by one line on what we
sell. Argue against pursuing this account. Give the three strongest reasons it
will not buy from us in the next year, each grounded in something in the notes
rather than a generic risk. For each reason, say what evidence would weaken it.
Finish with the one missing fact that would most change the case. Do not
balance the argument and do not suggest outreach ideas.

Here is the full thread with [champion name], my contact at a named account.
The decision sits with [who signs and what they are measured on].
Write the one page note [champion first name] would send to that person to
argue for this purchase.
Rules:
1. Use only problems, numbers and dates that appear in the pasted record.
   After each claim, quote the line it rests on in brackets.
2. Write it in the first person, as [champion first name], using their

Subject: Two lines for [new person's first name]
 
Hi [Contact],
 
Thanks for today. You mentioned [new person] looks after [specific part].
 
To save you writing anything, the note below is ready to forward. Change whatever you like, or tell me if you'd rather I didn't.
 

Here are our case studies, one line each: industry, client size,
the problem, what we did, the outcome.
 
[list]
 
Here is what we know about [account]: industry, size, the problem
we believe they have, anything public about their situation.
 

The first document is what people at [account] said to us, quoted in their own
words. The second is our proposal draft. List every priority, worry or constraint
they stated that the draft does not clearly answer, quoting their words next to
each gap. Then list every claim in the draft that nothing in the first document
asked for. Do not rewrite the proposal.

Here is an email thread with a contact at a named account who has stopped
replying, plus one line on what we sell and one line on why we chose this
account.
Do three things, in order.
1. Inventory: list every angle, claim and ask my messages have used so far,
   one line each.
2. Verdict: does the record support one more message, parking the account
   with a trigger to watch, or stopping? Quote the line from the thread your

1. Open the Tier 1 list. For each account, check: news page, LinkedIn company page, careers page.   (10 min)
2. Write down every change with its date and link. No link, no trigger.                             (5 min)
3. For each trigger: who does it land on, and do we know them?                                      (3 min)
4. Pick the three accounts with the freshest trigger. They get this week's research hours.          (2 min)

Below is a draft first email from [my company] to [account].
 
Swap 1: replace every mention of [account] with [a named competitor of theirs]. List each sentence that is still accurate and sensible after the swap.
 
Swap 2: in the original draft, replace [my company] with [a named competitor of ours]. List each sentence a reader would still accept after the swap.
 
Then tell me:
1. Which sentences survived both swaps.

Here is the full history of an account we just won: notes, emails and call
summaries from first touch to signature, plus one line on what we sell.
Answer five questions. Ground each answer in the record and quote the line
that supports it. If the record does not answer a question, say so rather
than guessing.
1. What was happening in the account when the deal started moving, and what
   had stalled it before that?
2. What words did the buyer use for the problem, before they picked up ours?

ACCOUNT: [name]   TIER: [1/2/3]   OWNER: [name]   LAST REVIEWED: [date]
 
Why this account
  Looks like: [past client and the problem solved there]
  Reason to write now: [trigger, date, source]
 
Buying committee
  Budget owner:         [name, title]   status: [not contacted / contacted / replied / engaged]

PLAY: [name]   TIER: [1 / 2 / 3]   OWNER: [named person]
Accounts: [ ]   Starts when: [list approved / trigger / handover]
Roles, in order: [1] [2] [3]
Reason to talk now: [one true sentence per account]
Steps: [week] [channel] [role] [what is sent] [who sends]
Touches per person: [ ]   Channels: [ ]
Ends when: [reply / handover / no response from three roles]

Day 1   LinkedIn   Connection request with a one line reason. No pitch.
Day 2   Email      Email 1: why you are writing, one line on what you
                   do, one question.
Day 4   Email      Email 2: one new fact, in the same thread.
Day 5   LinkedIn   A short message with one new fact. No pitch.
Day 6   Phone      Call 1. No answer: a voicemail under 20 seconds,
                   then a two line email.
Day 7   Email      Email 3: one relevant example, and why it fits them.

Below is a transcript of a meeting between me ([name, company]) and
[champion name, role] at [account].
 
Write a recap for [champion first name] to forward to colleagues who
were not there, including [the roles that matter: budget holder,
technical lead]. Requirements:
 
- Under 150 words, no greeting, no sign-off; they will add their own.

PROOF AND NICHE
1  ★ One niche: one buyer type, one problem you have solved at least twice
2  ★ Two case studies a Gulf buyer will recognise, with results the client agreed to share
3  ★ One reference a Gulf buyer can phone, with the client's permission
4    A one-page capability note naming the people who deliver
5    A small paid first step: a discovery sprint, workshop or pilot
 
PRESENCE AND PEOPLE

PROOF AND NICHE
1  ★ One niche chosen: one buyer type and one problem you have solved at least twice
2  ★ Two case studies in that niche, each with problem, what you built and an agreed result
3  ★ One reference a US buyer can phone, with the client's permission
4    Case studies written for a US reader: US spelling, US dollars, no internal jargon
5    A one-page capability note for the niche, not a list of every technology you use
6    Named delivery lead and account owner, with photos and short profiles on the website
7    Website states who you serve in the USA and shows the niche on the home page

Subject: Quote request: [your company], outbound programme from [month]
 
Hi [First name],
 
Thank you for the call. To compare proposals fairly, we are asking every
provider the same questions. Could you answer each in writing?
 
1. Every fee: setup, monthly, per lead or per meeting, tools, data, domains

Search the web for changes at the companies below in the last [30] days. Report only what you can link to.
 
For each company, look for: senior hires or departures, new sites or markets, funding, acquisitions, results or annual reports, large contracts or partnerships, regulation the company has said affects it, and open roles in [function].
 
For each item give: the company, what happened in one sentence, the date, the link, and the role inside the company it most affects.
 
Rules: if you find nothing dated inside the window, write "nothing found" for that company. Do not guess. Do not include anything without a link. Newest first.
 

1. Did this person give us their number, or reply to us from it?
2. Has the person agreed, in writing, to talk on WhatsApp?
3. Is it a work number, or one they use for work?
4. Do we know why we are writing, and is it about their business?
5. Is it a working hour in their time zone, and not a holiday for them?
6. Have we already had a reply or a call on another channel?
7. Is the number absent from our stop list?

Hi [First name],
 
To be open with you, I wrote to [contact] about [topic] and haven't heard back, which may mean it sits elsewhere.
 
From [their function], the question is usually [their concern]. How does [company] handle that today? If someone else owns it, a name is all I need.
 
[Your name]

1. Can I load an exclusion list by company domain, and does it apply to every campaign?
2. Can I require approval before sending for accounts I choose?
3. Where does the tool get the facts it uses about a company, and can I see the source for each line?
4. What does it do when a buyer replies: answer, hand over or book a meeting?
5. Whose domains and mailboxes does it send from, and who keeps them if we stop?

V1. Can you see the raw work?
    Live access to the sending tool, the actual lists and the real
    replies, not a weekly PDF. A partner who summarises instead of
    showing has something being summarised away.
 
V2. Who owns the client relationship in the contract?
    If the partner can ever contact your clients directly, or inherits
    them on termination, you are not white labelling, you are