A prospect dossier template is a fixed set of fields a rep fills in about one buyer at one account before outreach, where every field carries a value, its source and an as-of date. This one has five blocks, Who, Why them, Why now, Who else and What to say, plus a confidence level per field, so a reader can tell a verified fact from a guess.
Disclosure, date and method
Bob Generale is President of Percepture, which is related to Lead Seeker, the publisher of this page. Alex Mannine, Global Head of Strategy & AI at Percepture, reviewed the confidence ladder and the readiness gate. This template was written on September 24, 2026 after reading the prospect-research and pre-call templates that rank for the query and the primary sources listed at the end: the U.S. Bureau of Labor Statistics on employee tenure, Articles 5 and 14 of the GDPR, the California Attorney General's CCPA guidance, and the SEC, Companies House and U.S. Department of Labor pages that publish the events a dossier records. Shelf-life defaults in the tables are editorial judgement and are labelled as such; they are not measured benchmarks.
Prospect Dossier Template: The Short Answer
- One buyer, one account, one page. The unit is a person in a role at a company, not a company profile and not a contact row. Account-only research templates skip the person; contact lists skip the reason.
- Every field earns three columns. Value, source and as-of date. A field without a source is an opinion; a field without a date is a rumour with good posture.
- Confidence is written down, not implied. Five rungs: Verified, Corroborated, Reported, Inferred, Unknown. Only the top two may appear in a message as fact.
- The dossier has an expiry. Contact channels, roles and signals age at different speeds, so the template records when each block must be re-checked, and the whole dossier is "ready" only when the Why now block is inside its window.
The prospect dossier template, ready to copy
Paste this into your notes tool, CRM record or a spreadsheet with four columns. Keep it to one screen; add rows only when evidence requires it. The completed example further down shows what a finished one reads like.
PROSPECT DOSSIER
(one buyer, one account)
0. META
Dossier owner:
Created / last reviewed:
Expires (earliest block expiry):
ICP segment:
Lawful-basis / notice status:
Status: draft | ready | hold | killed
For every field below, record:
value
source (type + link)
as-of date
confidence: Verified | Corroborated
| Reported | Inferred | Unknown
1. WHO (the person)
Full name:
Current title:
Team / function:
Reports to (role):
Work email:
Direct line or switchboard:
Public profile URL:
Location (city or region, work):
2. WHY THEM (fit)
Company legal name + site:
Industry / sub-sector:
Headcount band:
Revenue band or funding stage:
Regions served:
Relevant systems in use:
ICP score + the fields it used:
Disqualifiers checked:
3. WHY NOW (timing)
Signal 1: event | date | source
| shelf life
Signal 2: event | date | source
| shelf life
Signal 3: event | date | source
| shelf life
What the signals do NOT prove:
4. WHO ELSE (buying group)
Likely economic buyer (role):
Likely evaluator (role):
Champion candidate (role):
Existing relationship in CRM:
Do-not-contact or legal flags:
5. WHAT TO SAY (angle)
Hypothesis (one sentence):
First line (Verified/Corroborated
fields only):
Proof to bring:
Question to ask first:
Style notes (optional, Inferred):
Next step you will propose:
The three-column rule and the confidence ladder
Most research templates ask for values. This prospect dossier template asks for three things per value, and the third is where the discipline lives.
The three-column rule. Each entry records its source (type and link: filing, company page, live posting, press release, a vendor database, a person's own public profile, or "direct check" for a deliverability test or a phone confirmation), its as-of date (the date the source was read or the check was run, not the date the event happened; the event date is part of the value), and its confidence rung. The as-of date is the field that makes a dossier reviewable a month later. Without it, a manager cannot tell whether "VP Operations" was true this week or last spring.
The confidence ladder. Five rungs, each with a rule about what it may be used for.
| Rung | Definition | What it may be used for |
|---|---|---|
| Verified | Confirmed against a primary source (the company's own page or filing, a live posting, a regulator's register) or by a direct check, within the field's shelf life | May be stated as fact in a message |
| Corroborated | Two independent secondary sources agree, or one secondary source matches a primary detail (a news item that names the same title the company's page shows) | May be stated as fact in a message, phrased to the source ("your careers page lists…") |
| Reported | One secondary source only: a vendor database record, a single news article, an aggregator | Shapes prioritisation and questions; does not appear in a message as a claim |
| Inferred | The analyst's judgement from other fields ("probably owns the budget because…") | Internal hypothesis only; tested on the call, never written to the prospect |
| Unknown | Deliberately left blank | Blank beats a guess; an Unknown in Who or Why now blocks readiness |
Two consequences follow. First, a dossier can be complete and still not ready: eight Reported fields are a research brief, not a reason to send. Second, the first line in block 5 can only be built from rungs one and two, which is the simplest defence against the opener that congratulates someone on a role they left in March.
Field definitions, sources and shelf lives
Shelf lives below are editorial defaults for when a field must be re-checked before it can stay Verified. They are starting points; your own CRM feedback should shorten or lengthen them. They are not measured decay rates, and no vendor's "data decays X% a year" figure is repeated here because none of the ones in circulation traces to a published method.
Block 1, Who: the person
| Field | Definition | Primary or best source | Default shelf life |
|---|---|---|---|
| Full name and current title | The name and title the person uses today, in the company's own words | Company leadership or team page; the person's own public professional profile; for officers of listed U.S. companies, Form 8-K Item 5.02 filings; for UK companies, the Companies House officers register | 90 days |
| Team and reporting line | Function and the role (not necessarily the name) they report to | Organisation pages, job postings that name the hiring manager, press releases | 90 days |
| Work email | A business address that accepts mail today | Direct deliverability check; company email pattern confirmed against a published address | 30 days |
| Direct line or switchboard | A business number that reaches the person or their team | Company contact page; the person's published business card details | 90 days |
| Public profile URL | The professional profile the person maintains | The profile itself | 12 months |
| Work location | City or region of the role, where relevant to territory or time zone | Company page, posting, profile | 12 months |
Role fields move faster than most templates assume. The U.S. Bureau of Labor Statistics reported that the median tenure of wage and salary workers with their current employer was 3.9 years in January 2024, the lowest since 2002. Tenure is not turnover, but a median that short means a title captured a year ago is a claim that needs re-checking, not a fact.
Block 2, Why them: fit
| Field | Definition | Primary or best source | Default shelf life |
|---|---|---|---|
| Company legal name and site | The entity you would contract with, not a brand or a subsidiary that shares the name | Regulator registers (SEC EDGAR for U.S. filers, Companies House for UK companies), the company's legal page | 12 months |
| Industry and sub-sector | The category your ICP is defined in, in your own taxonomy | Company site; filings for listed companies | 12 months |
| Headcount band | A range, never a point estimate, with the source that produced it | Company statements; filings; a vendor database counts as Reported | 6 months |
| Revenue band or funding stage | Public revenue range, or the last announced round and type | Filings; press releases; for U.S. private raises, the Form D notice | 6 months |
| Regions served | Markets the company sells into, where territory matters | Company site, filings | 12 months |
| Relevant systems in use | Only the systems that matter to what you sell | Job postings that name tools; the company's own engineering or documentation pages; a technographic database counts as Reported | 6 months |
| ICP score and inputs | The score and the exact fields it was computed from | Your own scoring model | Recompute whenever an input changes |
| Disqualifiers checked | Exclusions you tested: competitor, current customer, restricted industry, do-not-contact | CRM; your exclusion list | Every review |
A fit block that reads "mid-market, uses Salesforce" is a start. A fit block that reads "251 to 500 employees per the company's about page as of 12 Sep 2026 (Verified); Salesforce named in two live postings (Corroborated)" can be reviewed by someone who was not in the room. If your team has no shared scoring model, the method in ICP scoring that sales actually trusts explains how to make the inputs auditable before they land in block 2.
Block 3, Why now: timing
| Field | Definition | Primary or best source | Default shelf life |
|---|---|---|---|
| Posted role your product supports | A live posting for a function that would use or buy what you sell | Company careers page (job boards count as Reported until matched to the careers page) | While the posting is live, plus 30 days |
| Leadership change in the buying role | A new person in the role that owns your category | Press release; leadership page; Form 8-K Item 5.02 for officers of listed U.S. companies | 90 days from the effective date |
| Financing event | Round announced, with type and any filing | Press release; Form D for U.S. private issuers | By round type; treat as a reason to research, not proof of budget |
| Expansion or new location | A stated build-out, launch or entry into a market | Company announcement; regulatory notices | During the rollout |
| Operational stress | Layoffs, closures, missed forecasts | For qualifying U.S. plant closings and mass layoffs, state WARN notices under the Worker Adjustment and Retraining Notification Act; company statements | Handled by a human; often a later window |
| Public statement of the problem | A leader naming the problem you solve, in public | Earnings calls, conference talks, the company's own blog | Until the next quarterly narrative |
| What the signals do not prove | One sentence per signal on the alternative explanation | Analyst | Rewrite at every review |
The last row is the one most templates omit and the one that keeps the dossier honest. A posting can be evergreen, a new executive can inherit a frozen budget, and a round can be debt or a secondary sale that sends no new cash to the company. The field guide to B2B intent signals covers how strong and fresh each signal family tends to be; the workflow that moves a dated signal through verification to a booked meeting is in signal based prospecting.
Block 4, Who else: the buying group
| Field | Definition | Primary or best source | Default shelf life |
|---|---|---|---|
| Likely economic buyer | The role that would sign, named as a role until a person is Verified | Organisation pages; filings for listed companies; postings that describe reporting lines | 90 days |
| Likely evaluator | The technical, operations or security role that would test or block | Postings; documentation pages; case studies the company has published | 90 days |
| Champion candidate | The role with the problem, if different from the person in block 1 | Public statements; postings | 90 days |
| Existing relationship | Open opportunities, past deals, active sequences, mutual contacts recorded in your CRM | CRM | Every review |
| Do-not-contact and legal flags | Opt-outs, regional restrictions, contract clauses, competitor status | CRM; legal register | Every review |
Block 4 is written in roles first and people second on purpose. Naming three more people you have not verified triples the chance of a wrong claim; naming three roles gives the rep a map for the discovery call without inventing anyone.
Block 5, What to say: the angle
| Field | Definition | Rule |
|---|---|---|
| Hypothesis | One sentence connecting a Why now field to a problem your product addresses | Must cite the signal by its source and date |
| First line | The opening sentence of the first message | Built only from Verified or Corroborated fields; if none exists, the dossier is not ready |
| Proof to bring | One artefact relevant to the hypothesis: a short case, a benchmark you can defend, a one-page map | Nothing generic |
| Question to ask first | The diagnostic question that tests the hypothesis | One per hypothesis, not a script |
| Style notes | Optional observations about how the person communicates in their public professional writing or talks | Always Inferred; never a claim to the prospect; never a protected characteristic |
| Next step you will propose | What you ask for if the hypothesis holds | Specific and small |
For the questions themselves, the set in discovery call questions that actually qualify is built to confirm or kill what the dossier suggested rather than to re-ask what it already answered.
What does not belong in a dossier
A dossier is a business record about a business role. Three rules keep it that way, and each has a legal anchor as well as a courtesy one.
Record only what the outreach needs. Article 5(1)(c) of the GDPR requires personal data to be "adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed". In template terms: work contact channels, role, employer and public professional statements are in scope; home address, personal phone, family, health, beliefs, politics, private social accounts and anything read in a closed group are not, and the template has no field for them on purpose. The same article's accuracy principle, data "accurate and, where necessary, kept up to date", is the legal version of the as-of date, and its storage-limitation principle is the legal version of the dossier's expiry.
Know what your notice obligations are before you compile. When personal data has not been obtained from the person, GDPR Article 14 requires the controller to provide that person with specified information, including who the controller is, the purposes and legal basis of the processing, the categories of data and the recipients. The article sets its own conditions, timing and exceptions; whether it applies to a sales dossier about a professional in the EU, and how any notice is given, is a question for counsel, which is why block 0 carries a "lawful-basis / notice status" field that counsel completes, not the rep.
Do not assume business contacts are out of scope in the United States. The California Attorney General's CCPA guidance states that the exemptions for employment-related personal information and personal information reflecting business-to-business transactions expired on December 31, 2022. For a business the CCPA covers, business-contact data about California residents is no longer carved out simply because it is business data, so how dossiers are stored, shared and deleted, and how requests to know or delete are handled, can fall under the law. Whether your company meets the law's thresholds and which data its exclusions reach are questions for counsel, not assumptions for the template.
None of this is legal advice; it is the reason the template has an expiry, a notice-status field and no space for personal detail. If a field is not needed to decide whether and how to open a business conversation, leave it out.
When is a dossier ready to send?
Readiness is a gate, not a feeling. The dossier's status in block 0 is set from the table below at every review.
| Status | Conditions | What happens next |
|---|---|---|
| Ready | Work email or phone Verified within 30 days; title Verified or Corroborated within 90 days; at least one Why now signal Verified and inside its shelf life; the first line uses only Verified or Corroborated fields; no disqualifier or legal flag triggered | A human reads the dossier and approves, edits or kills the message |
| Hold | Any Who field only Reported; the newest signal past its shelf life; ICP score computed from a stale input; a Why now row without its "does not prove" sentence | Verify the specific field, then re-run the gate; do not send around it |
| Kill | Disqualifier triggered; do-not-contact or legal flag; the company is a customer, an open opportunity owned by someone else, or a competitor; the only signal is one your ICP says is negative | Record the reason so the account is not rebuilt next month |
The Hold row is where most of the value sits. The usual failure is not a wrong fact but a stale one, and the gate makes staleness visible before a prospect does.
A completed example (synthetic)
This is the prospect dossier template above, completed for a fictional account. The company, the person and the dates below are fictional. No real organisation or individual is described; the dossier is written from the point of view of a seller of demand-planning software.
Block 0, Meta. Owner: SDR, Central territory. Created 22 Sep 2026; reviewed 24 Sep 2026. Expires 22 Oct 2026 (email check). ICP segment: mid-market manufacturers with multi-site distribution. Lawful-basis / notice status: legitimate-interest assessment on file for U.S. business contacts; notice text linked. Status: Ready.
| Block 1, Who | Value | Source and as-of | Confidence |
|---|---|---|---|
| Name and title | Director, Supply Chain Systems (fictional person, name withheld here) | Named as hiring manager in a live careers-page posting, read 22 Sep 2026; same title on the person's own public profile, read 22 Sep 2026 | Corroborated |
| Team and reporting line | Supply chain function; reports to the VP Operations per the posting | Careers posting, 22 Sep 2026 | Verified |
| Work email | Business address | Deliverability check passed 22 Sep 2026; pattern matches the address on the company's press contact page | Verified |
| Phone | Switchboard only | Company contact page, 22 Sep 2026 | Verified |
| Work location | Ohio, United States | Posting and profile, 22 Sep 2026 | Corroborated |
| Block 2, Why them | Value | Source and as-of | Confidence |
|---|---|---|---|
| Company | Tallow Creek Packaging, Inc. (fictional), corrugated packaging manufacturer, four plants | Company about page and state business register, 22 Sep 2026 | Verified |
| Headcount band | 500 to 1,000 | Company about page states "more than 600 employees", 22 Sep 2026; a vendor database shows 740 | Verified (band); the point figure is Reported |
| Revenue band | Not published | No filing; private company | Unknown |
| Regions served | U.S. Midwest and Southeast | Company site, 22 Sep 2026 | Verified |
| Relevant systems | Legacy on-premise ERP; cloud ERP migration planned for 2027 | Stated in the careers posting, 22 Sep 2026 | Verified that the posting says so; the plan itself is Reported (single source) |
| ICP score | 8 of 10; inputs: sub-sector, headcount band, multi-site, region | Own model, recomputed 24 Sep 2026 | Derived from Verified inputs |
| Disqualifiers | Not a customer; no open opportunity; not on exclusion list | CRM, 24 Sep 2026 | Verified |
| Block 3, Why now | Value | Source and as-of | Confidence |
|---|---|---|---|
| Signal 1 | "Demand Planning Manager" posted 8 Sep 2026, reporting to the Director, Supply Chain Systems | Careers page, read 22 Sep 2026; shelf life: while live plus 30 days | Verified |
| Signal 2 | New CFO announced 26 Aug 2026 | Company press release, read 22 Sep 2026; shelf life: 90 days from effective date | Verified |
| Signal 3 | ERP migration planned for 2027 | Same posting as Signal 1; shelf life: 6 months | Verified as a statement in the posting; Reported as a plan |
| Does not prove | The posting may be a backfill rather than a new function; a new CFO may freeze discretionary spend for a quarter; the migration timeline is a hiring-copy statement, not a project plan | Analyst, 24 Sep 2026 | Inferred |
| Block 4, Who else | Value | Source and as-of | Confidence |
|---|---|---|---|
| Economic buyer | VP Operations (role) | Posting names the reporting line, 22 Sep 2026 | Verified as a role; person not yet identified |
| Evaluator | IT lead for the ERP programme (role) | Inferred from the migration statement | Inferred |
| Champion candidate | The incoming Demand Planning Manager, once hired | Posting | Inferred |
| Existing relationship | None in CRM; a former colleague of the AE worked at the company until 2024 | CRM and AE, 24 Sep 2026 | Reported |
| Flags | None | CRM, 24 Sep 2026 | Verified |
| Block 5, What to say | Value | Source and as-of | Confidence |
|---|---|---|---|
| Hypothesis | A director who is hiring a demand planner ahead of a stated 2027 ERP migration will want planning data that survives the migration | Signal 1 and Signal 3, careers posting read 22 Sep 2026 | Inferred (to be tested on the call) |
| First line | "Your careers page lists a Demand Planning Manager reporting to you, and the posting mentions a 2027 ERP move." | Both statements are read directly from the live posting, 22 Sep 2026; no reference to the CFO change | Verified (what the posting says); the line makes no claim that the migration will happen |
| Proof to bring | A one-page note on running demand planning alongside an ERP cut-over, with one named reference the AE has permission to use | Own material, permission confirmed 24 Sep 2026 | Verified |
| Question to ask first | "Is the new planner inheriting the current forecast process, or redesigning it before the ERP move?" | Written from the hypothesis, 24 Sep 2026 | Not applicable |
| Style notes | Public conference talk was structured and data-heavy; keep the message short and specific | Recorded talk, viewed 22 Sep 2026; internal only | Inferred |
| Next step | A 20-minute call with the Director before the planner's start date | Analyst, 24 Sep 2026 | Not applicable |
Read the example against the gate: email Verified within 30 days, title Corroborated within 90, one Why now signal Verified and live, first line built only from what the posting says, no flags. Status Ready. Note the distinction the first line keeps: the posting's mention of a 2027 ERP move is Verified as a statement, while the migration itself is Reported and stays out of the message as a claim. Note also what was left out: nothing about the person beyond role, employer and public professional activity, and no reference to the CFO, because a Verified appointment is still an Inferred budget effect.
Keeping a dossier current without rebuilding it
Rebuilding from scratch every quarter is why a prospect dossier template gets abandoned. Three habits keep the cost low.
- Review by block, not by dossier. The Who block expires fastest; re-check email and title and leave the fit block alone unless an input changed. The expiry in block 0 is the earliest block expiry, so the review queue sorts itself. The whole dossier still carries the cap described on the definitional page, where most teams retire a dossier after 14 to 30 days without contact; the per-block shelf lives here govern re-verification inside that window, and the 30-day contact check in the gate keeps the two consistent.
- Let events reopen the dossier. A new posting, a leadership change or a filing at the account should move the dossier back to review even if nothing has expired. A funding announcement in particular should reopen block 3 rather than trigger a message on its own.
- Push only four things into the CRM record. The verified-date of the contact channel, the name and date of the surfacing signal, the source link, and the dossier status. Everything else lives in the dossier itself, attached or linked. Fields the CRM cannot date should not become CRM truth.
If the same signal reappears without a new date, it is not a new signal. If a Verified field cannot be re-verified at review, it drops to Reported, and the gate does its job.
Where this fits with Lead Seeker
This prospect dossier template is deliberately tool-neutral; it works in a notes app or a spreadsheet, and the discipline is in the three columns and the gate, not the software. How the prospect dossier works in Lead Seeker follows the same shape: each saved contact arrives with retrieved contact data stamped with a freshness date, company context, the public signal that surfaced the person with a link to its source where one is available, a short communication read that is presented as guidance rather than fact, and an editable opening line. Treat the product's output as blocks 1 to 3 and the first draft of block 5, filled in, and keep the human at the gate. If you are new to the concept, what a prospect dossier is and why it replaces the contact list explains the unit of work; this page is the template for producing one.
Pre-send checklist
Copy this list under block 5 and tick it at every review.
- Every filled field has a source type, a link where one exists and an as-of date.
- Every field carries one of the five confidence rungs; nothing is blank without being marked Unknown.
- Work email or phone is Verified within 30 days.
- Current title is Verified or Corroborated within 90 days.
- At least one Why now signal is Verified, dated and inside its shelf life.
- Each signal has its "does not prove" sentence.
- The ICP score lists the fields it used, and none of them is stale.
- Disqualifiers, do-not-contact flags and existing CRM relationships were checked today.
- The first line uses only Verified or Corroborated facts and names its source.
- Nothing in the dossier concerns the person's private life, protected characteristics or non-public accounts.
- The lawful-basis / notice status field is completed for the person's jurisdiction.
- Block 0 status is set from the readiness gate, and a named human approved the send.
Frequently Asked Questions
What should a prospect dossier template include?
A prospect dossier template should include five blocks: the person (name, title, team, verified work contact channels), fit (legal entity, sub-sector, headcount band, systems that matter to you, ICP score and its inputs, disqualifiers checked), timing (dated public signals with their sources, shelf lives and what they do not prove), the buying group (roles before names, CRM relationships, legal flags) and the angle (hypothesis, first line, proof, first question, next step). Each field carries a value, a source, an as-of date and a confidence rung.
How is a prospect dossier different from an account research template?
An account research template describes a company: priorities, initiatives, technology, stakeholders. A prospect dossier is about one person in one role at that company and is built to decide whether and how to open a conversation with them now. It contains a fit block that an account brief would also contain, but adds verified contact channels, dated timing signals and a first line, and it expires.
How long should a prospect dossier stay valid?
Until its earliest block expires. As editorial defaults, a work email should be re-checked within 30 days, a title within 90 days, a posting-based signal while the posting is live plus 30 days and firmographics within six to twelve months. These are starting points for your own review cadence, not measured decay rates. A dossier whose Why now block has expired is a research file, not a reason to send.
What are confidence levels in a prospect dossier?
A written label on each field that says how it was established. This template uses five: Verified (primary source or direct check, inside the shelf life), Corroborated (two independent sources, or one secondary matching a primary detail), Reported (one secondary source), Inferred (analyst judgement) and Unknown (left blank on purpose). Only Verified and Corroborated facts may appear in a message.
Should a dossier record personal details about the buyer?
No. The template covers work contact channels, role, employer and public professional statements, and has no field for home address, personal phone, family, health, beliefs, politics or private accounts. GDPR Article 5 requires personal data to be limited to what is necessary for the purpose and kept accurate, and the California Attorney General states that the CCPA's business-to-business exemption expired on December 31, 2022, so business-contact data is no longer carved out for the businesses that law covers. Record what the outreach needs and nothing else.
How long does it take to fill in a prospect dossier?
It depends on how many fields start Verified. A dossier built on a live posting, a company page and a deliverability check can be short; one that starts from a vendor database row with no dated signal takes longer because most fields begin as Reported and have to be lifted. No time benchmark is offered here because none of the figures published by tool vendors traces to a described method. Track your own median and cut fields that never change a decision.
Can a prospect dossier be generated automatically?
The retrieval can be: contact data with a freshness stamp, company context, the surfacing signal with its source link where one is available and a draft first line are what sales intelligence tools, including Lead Seeker's dossier, produce. The readiness decision should not be. A human reads the dossier, checks the gate, and approves, edits or kills the message, and the reason is recorded either way.
Sources
- U.S. Bureau of Labor Statistics, Employee Tenure Summary, January 2024 (released September 26, 2024): median tenure of wage and salary workers with their current employer was 3.9 years, the lowest since January 2002
- Regulation (EU) 2016/679 (GDPR), Official Journal text: Article 5(1)(c) data minimisation, 5(1)(d) accuracy, 5(1)(e) storage limitation; Article 14 information to be provided where personal data have not been obtained from the data subject
- State of California Department of Justice, California Consumer Privacy Act (CCPA) FAQ: exemptions for employment-related and business-to-business personal information expired on December 31, 2022
- U.S. Securities and Exchange Commission, Form 8-K (PDF): Item 5.02, departure of directors or principal officers, election of directors, appointment of principal officers
- U.S. Securities and Exchange Commission, Form D (PDF) and EDGAR full-text search
- Companies House, Find and update company information: UK company officers and filings
- U.S. Department of Labor, WARN Act compliance assistance: advance notice in cases of qualified plant closings and mass layoffs
About the Author and Reviewer
Bob Generale is President of Percepture. He works across SEO, AI search, digital PR, sales intelligence and AI-powered revenue systems, with a focus on connecting visibility, buyer intent and sales action. The confidence ladder and readiness gate in this template were reviewed by Alex Mannine, Global Head of Strategy & AI at Percepture.
Disclosure: Lead Seeker is related to Percepture and Pyra. No vendor template or data provider named on this page was tested or engaged in the course of writing it, and nothing here is legal advice.
Next Steps
Rebuild your last ten first-touch messages as dossiers using this prospect dossier template and run each through the readiness gate; count how many fail on a Reported title or an expired signal, and fix those before touching the copy. Then see how the prospect dossier works when the same fields arrive filled in, dated and linked to their sources.