# Deep Research for RFP Response

Research a buyer and a live bid before you respond. Builds an evidence-backed customer brief from authorised facts, runs public-source research on the buyer and the offering, fills the internal half from first-party records, and profiles the competitors likely to bid. Use for RFP responses, security questionnaires, DDQs and proposals in any industry.

This file is the Agent Skills standard package flattened for clients that take instructions rather than a Skill folder. Keep workflow files in Instructions. Upload business source documents and optional assets as Knowledge only when needed.

## SKILL.md

# Deep Research for RFP Response

Use the smallest workflow that satisfies the request. Keep Claim IDs and evidence status whenever work moves between workflows, so a later stage can pick up the earlier work without re-researching it.

## Start with the bid

Confirm the buyer, the offering being bid, the deadline, the deliverable (brief, research report, battlecard or a full pack), and which sources the user is authorised to use. Ask only for details that materially change the result. If the user asks you to use only supplied facts, do not hold up the work with questions. Mark omissions as `Not provided` and list them as open gaps.

## Select a workflow

- Create the account brief from authorised facts: read [Customer Brief Setup](references/customer-brief-setup.md).
- Discover public sources for this offering and write the full trust-classified report in one run: read [External Research](references/external-research.md).
- Research the gaps in the brief and buyer priorities, using the editable worksheet: read [Customer Brief Research](references/customer-brief-research.md).
- Fill the internal half from first-party CRM, email, meeting and call records: read [Internal Research](references/internal-research.md).
- Profile the competitors likely to bid, with a battlecard for the bid: read [Competitor Intelligence](references/competitor-intelligence.md).

For a multi-stage run, follow [the integrated workflow](references/WORKFLOW.md). Use [the shared handoff schema](references/HANDOFF_SCHEMA.md) for every intermediate artifact, so each file has the same name and sections wherever it is used.

Recommended order for a full run: Customer Brief Setup, then External Research and Internal Research in either order, then Customer Brief Research to close the gaps, then Competitor Intelligence. Skip any stage the request does not need.

## Evidence rules

- Map every material claim to a source and Claim ID.
- Treat search results as leads until their underlying sources are validated.
- Mark unsupported statements as `Needs evidence`. Never present them as facts.
- Mark explicit user or authorised internal facts as `Provided` unless independently verified.
- Mark invented content in fictional or hypothetical scenarios as `Illustrative`. Never present it as verified evidence.
- Retain dates, qualifiers, geographies, sample sizes and units.
- Use only public or authorised material. Keep relationship information professional and relevant to the bid.
- Competitor weaknesses are quoted from linked, dated sources. Do not characterise them.

If browsing is unavailable, return a research plan, discovery queries and evidence gaps instead of unsupported findings. If file creation is unavailable, return each requested artifact inline under its specified filename.

## Included resources

- `assets/Customer-Brief-Research-Worksheet.docx`: editable research worksheet for Customer Brief Research.

## Notes on related skills

Two stages mention skills that ship separately: the merge step in Internal Research points to Completed Insight Brief, and the Competitor Intelligence workflow points to the AI Go/No-Go Analyzer. Both are optional. Without them, keep each stage's own output and merge by hand using the handoff schema.

If a stage needs optional tooling that is not available, complete the research and evidence ledger, and say clearly which output was not produced. Never block the rest of the workflow on optional tooling.

## Competitor Intelligence

Source: `references/competitor-intelligence.md`

# Competitor Intelligence for RFP & Sales

Researches competitors and produces structured intelligence profiles that directly inform RFP win strategy, bid positioning, and sales conversations. This is not generic market research -- it is tactical intelligence designed to help you win specific deals.

## Works Well With

- **AI Go/No-Go Analyzer** - Competitive landscape understanding improves the accuracy of Go/No-Go scoring

## How Competitive Intelligence Feeds RFP Work

Competitor intelligence serves three purposes in the bid process:
1. **Win theme development** - Understanding competitor weaknesses helps you position your strengths as differentiators
2. **Objection anticipation** - Knowing what competitors claim helps you preempt evaluator questions
3. **Trap-setting** - Understanding where competitors fall short lets you include requirements or proof points in your response that they cannot match

## Workflow

### Step 1: Define the Intelligence Need

Ask the user what they need:

**Option A: Specific competitor deep-dive**
- "I need to understand [Competitor Name] for an upcoming bid"
- Research that specific competitor in depth

**Option B: Competitive landscape for a deal**
- "Who are we likely competing against for [opportunity/sector]?"
- Identify likely competitors, then profile each one

**Option C: Battlecard update**
- "Update our intelligence on [Competitor Name]"
- Refresh existing knowledge with current information

Also ask:
- What is the deal or RFP context? (Sector, requirements, geography)
- Do you already have intelligence on this competitor, or starting from scratch?
- Are there specific areas you need to focus on? (Pricing, technical capabilities, security posture, implementation approach)

### Step 2: Research

Use web search to gather intelligence from these source categories:

**Official sources:**
- Competitor's website (product pages, pricing, case studies, documentation)
- Press releases and news articles
- Job postings (reveal technology stack, expansion plans, and capability gaps)
- SEC filings or Companies House data (if public)
- Patent filings (reveal R&D direction)

**Third-party sources:**
- G2, Gartner Peer Insights, TrustRadius reviews (real user feedback)
- Analyst reports and market guides
- Industry publications and trade press
- LinkedIn (company size, growth trajectory, key hires)

**Community sources:**
- Reddit, community forums, Stack Overflow discussions
- Conference presentations and webinar recordings
- Podcast appearances by competitor leadership

**RFP-specific intelligence:**
- Public contract awards (government procurement databases)
- Case studies that reveal their implementation approach
- Partner ecosystem (who they integrate with, who they resell through)

For each piece of intelligence, note the source and how recent it is. Intelligence older than 12 months should be flagged as potentially outdated.

### Step 3: Build the Intelligence Profile

Organize findings into this structure:

```
## Competitor Intelligence: [Competitor Name]

### Company Overview
- Founded, HQ, headcount, funding/revenue (if known)
- Target market and ICP
- Growth trajectory (hiring trends, funding rounds, market expansion)

### Product & Capabilities
- Core product description
- Key features and modules
- Deployment model (SaaS, on-prem, hybrid)
- Technology stack (if known)
- Integration ecosystem
- Recent product launches or roadmap signals

### Strengths (Be Honest)
What they genuinely do well. Ignoring competitor strengths leads to bad strategy.
- [Strength 1] - Evidence and source
- [Strength 2] - Evidence and source

### Weaknesses & Vulnerabilities
Where they fall short, with evidence.
- [Weakness 1] - Evidence (user reviews, known limitations, architectural constraints)
- [Weakness 2] - Evidence

### Pricing & Commercial Model
- Pricing structure (per user, per transaction, platform fee, etc.)
- Typical deal sizes (if known from reviews or contract databases)
- Common commercial terms or restrictions
- Free tier or trial availability

### Security & Compliance Posture
- Known certifications
- Data residency capabilities
- Notable security incidents or gaps

### Customer Base & References
- Named customers (from case studies, press releases)
- Sectors they are strongest in
- Customer sentiment from review sites (summarize patterns, not individual reviews)

### Key Personnel
- CEO, CTO, VP Sales -- relevant for understanding strategy and approach
- Recent leadership changes that signal strategic shifts

### Win/Loss Intelligence
If the user has any internal win/loss data or anecdotal knowledge, incorporate it here.

### RFP Positioning Recommendations

Based on this intelligence, specific tactical recommendations:

**Lead with:**
Areas where you have clear advantages over this competitor

**Neutralize:**
Areas where the competitor is strong -- how to minimize the gap in the evaluator's mind

**Trap questions:**
Requirements or proof points to emphasize in your RFP response that this competitor cannot easily match

**Language to use:**
Phrases that highlight your differentiators without naming the competitor directly (RFP responses should never name competitors)

**Watch out for:**
Claims this competitor is likely to make that you should be prepared to counter
```

### Step 4: Validate and Refine

Present the profile to the user and ask:
- Does this match your experience with this competitor?
- Is there internal intelligence (from lost deals, customer feedback, partner channels) that contradicts or supplements anything here?
- Are there specific areas where you need deeper research?

Refine based on their input. Internal intelligence from the user's own experience is often more valuable than public sources.

## Output Format

- Quick competitive overview: structured markdown in conversation
- Full intelligence profile: create as `.md` file
- If user requests a formal battlecard: create as `.md` or `.docx`

## Important Principles

- Be honest about competitor strengths. A competitive profile that only lists weaknesses is useless -- it leads to overconfidence and poor positioning. Know what they do well so you can neutralize it.
- Cite sources for every claim. "They have poor customer support" is worthless. "They have a 3.2/5 rating for customer support on G2 based on 150+ reviews, with common complaints about response time for technical issues" is actionable.
- Distinguish between facts and inferences. If a job posting for "Senior On-Prem Engineer" suggests they are building an on-prem offering, say that explicitly rather than stating it as fact.
- Intelligence has a shelf life. Flag anything older than 12 months and recommend refreshing it before a major bid.
- Never recommend naming competitors in RFP responses. The positioning recommendations should help the user highlight their advantages without direct competitor references, which evaluators typically view negatively.
- This skill can be used for your own competitive positioning too, not just RFP-specific intelligence. If a user wants to understand their market generally, the same framework applies.

## Customer Brief Research

Source: `references/customer-brief-research.md`

# Customer Brief Research

Consume `customer-brief.md`; create `research-pack.md`; and use [the editable worksheet](../assets/Customer-Brief-Research-Worksheet.docx) as the structured work surface.

## Workflow

1. If `external-source-report.md` is present, start from its verified claims, buyer language, and open gaps. Otherwise start with sources appropriate to the organisation type and jurisdiction: official websites, reports, filings, regulators, government records, product documentation, newsroom material, or authorised internal sources.
2. Log direct URLs, exact findings, supported brief field, Claim ID, source type, confidence, and status.
3. Identify three to seven relevant priorities in the organisation's own language, plus document search terms.
4. Mark unsupported facts as `Needs evidence` and unknown fields as `Not provided`.
5. Record open evidence gaps. Use Build Google Dork only to generate public discovery leads; validate those leads before logging them as evidence.
6. Adapt the worksheet headings to the user's business and complete its five-bullet summary.

If browsing is unavailable, do not invent research findings. Produce a source plan, copy-ready discovery queries, and open evidence gaps for later validation.

## Handoff

Send verified claims and search terms to PDF Insight Finder; source-backed context to Response Insight Enricher; and unresolved evidence gaps to Build Google Dork.

## Customer Brief Setup

Source: `references/customer-brief-setup.md`

# Customer Brief Setup

Create `customer-brief.md` from user-supplied or authorised internal information.

## Default sections

- Account context
- Business relevance: need, use case, alternatives or competition, and measurable value
- Stakeholders and professional relationships: role context and relevant references
- Operational and commercial context: relevant scale, spend, growth, constraints, or delivery model
- Decision criteria and success measures
- Open gaps

Adapt these sections to the user's industry and objective. Omit a default field when it is irrelevant and add domain-specific fields when they affect the decision or deliverable.

For every material fact, retain its source, owner, Claim ID, and status. Mark explicit prompt or authorised internal facts as `Provided`; use `Not provided` for relevant missing information. In fictional scenarios, label invented examples `Illustrative`. Never infer relationships, buying authority, budget, competition, or customer facts. Keep relationship information professional, authorised, and relevant.

## Handoff

Send the brief and open public gaps to External Research or Customer Brief Research. Send verified account context to PDF Insight Finder and Response Insight Enricher.

## External Research

Source: `references/external-research.md`

# External Research

In one run, discover the right public sources for this offering, search them, and write the full trust-classified research report. Produce `external-source-report.md`.

Do not stop after listing sources or queries. Do not deliver a source map as the result. Sources are a working step. The report is the deliverable: trustworthy research, buyer language, falsifiable facts and stats, and strategic priorities, each classified by trust.

## Start with context

Confirm the target organisation, the user's offering (the vendor and problem they sell), the intended deliverable, and the jurisdiction. Ask only for missing details that change what would count as proof.

If the user supplies authorised vendor facts (their own figures, case studies, or product claims), record them as `Provided`. Do not present them as independently verified.

Do not assume the industry, the offering, or a fixed second set of sources. Learn the high-signal sources from this run.

## Discover sources, then use them immediately

Work in two layers: common sources that ground any organisation, then high-signal sources you infer from this offering. As soon as a source is named, search it. Do not wait for a complete catalogue.

### Common sources

Use these as a starting lens for foundational facts. They are not the output.

#### Website

Look for company values, history, and scale. Prefer the official site, about pages, and current leadership or location pages.

#### Investor Center

Look for annual reports, investor presentations, and statistics. Prefer investor relations, filings, and official results pages. Keep figures with dates, geographies, and units.

#### Job Ads

Look for objectives, areas of focus, and locations of focus. Prefer current careers pages and official job posts. Treat ads as signals of priority, not as proof of a live programme.

#### News

Look for legal and financial issues, brand damage, and initiatives. Prefer the organisation newsroom, named outlets, and dated official statements. Separate the organisation's own announcement from third-party commentary.

### High-signal sources

Infer these from the offering. They are the sources most likely to surface this organisation's real pains rather than generic industry trends.

Do not reuse a remembered industry list. Derive the set now:

1. State the category of pain the offering addresses, in one sentence, using the user's words.
2. Name the official registers, regulators, courts or tribunals, statutory reports, industry bodies, and buyer-side forums that publish proof of that pain in this jurisdiction.
3. Add authorised operating documents or contracts only when the user supplied them. Do not hunt for leaked internal files.
4. Search those sources against this organisation. Keep a source only if it returns material here. Drop the rest.
5. If a promising class of record exists but nothing is found, log it as an open gap. Do not invent the finding.

A useful high-signal source is official or statutory, specific to the offering's problem, and checkable. Reviews and forums are signals until a primary source corroborates them.

### Example only

The cards below show the method for a workforce-management offering such as Workforce.com. Use them only when the user's offering is actually about workforce, payroll, HR, or employment. Do not copy them onto any other deal.

- Employment court cases: underpayments, specific legal risks, penalties or enforcements. Prefer official court, tribunal, or regulator records in the named jurisdiction.
- Wage equality reporting: employee type breakdown, headcount growth, wage cost details. Prefer statutory pay-gap or equivalent public reports.
- Glassdoor reviews: key employee issues, opportunities, what is already working. Quote clusters, not single unverified posts.
- Employee handbooks (user-supplied only): day to day workflow, systems and processes, values and communication channels.
- Employment agreements (user-supplied only): applicable processes and laws, complexities, risks.

For a payments vendor the same method might surface regulator enforcement, scheme rules, and outage reports. For a cyber vendor it might surface breach notifications and assurance filings. Name the equivalents for this offering yourself.

## Search and write in the same run

For each source you kept, write one to three precise queries, run them if browsing is available, open the underlying pages or documents, and log the direct URL. Prefer official domains, `site:`, quoted phrases, `OR`, `filetype:pdf`, and exclusions only when they tighten the result.

```text
Website
site:organisation.example (about OR values OR "our story" OR leadership)

Investor Center
site:organisation.example ("annual report" OR "investor presentation" OR "full year") (filetype:pdf OR filetype:xlsx)

Job Ads
site:organisation.example (careers OR jobs) ("we are looking" OR "you will" OR "this role")

News
"Organisation Name" (investigation OR lawsuit OR "regulatory" OR initiative OR "strategic priority")
```

Build high-signal queries from the sources you just inferred. Point them at the regulator, register, statutory report, or buyer-side forum that applies. Replace every placeholder with this organisation's aliases, language, and jurisdiction.

Search results stay leads until you open the source and record a locator. Then keep going: classify the finding and place it in the report. Do not pause to hand the user a query list.

If browsing is unavailable, still write the report. Mark findings `Needs evidence`, list the queries you would run, and leave those items as open gaps. Do not invent URLs, case names, quotes, or figures.

For extra query precision on remaining public gaps, Build Google Dork can refine them later. Do not delay the report for that step.

## Classify by trust, then extract the foundation

Compare the same claim across source types. Classify every material finding. Then write the foundation sections from those classified findings. Do not write generic industry commentary.

### Trust bands

Use these bands in the source log. They sit on top of the shared evidence contract (`Claim ID`, source type, confidence, status).

| Band | What qualifies | Typical status |
|---|---|---|
| Official | Filings, statutory reports, court or regulator records, the organisation newsroom, the official website | `Verified` when the locator supports the scoped claim |
| Corroborated | Two or more independent source types agree on the same scoped fact | `Verified` |
| Independent | A named outlet, analyst, or third-party report that cites a primary source | `Verified` only after the primary source is checked; otherwise `Needs evidence` |
| Signal | Job ads, review-site clusters, a single news item, or an undated deck | Lead; quote as a signal, not as proof of a live programme |
| Unverified | A single comment, an undated claim, or no locator | `Needs evidence`; never present as fact |

Cross-check rules:

- An official first-party figure with a date, geography, and unit can be `Verified` from that one official source.
- Interpretive claims (pains, priorities, culture, risk) need a second source type before you call them `Verified`.
- When sources disagree, keep both wordings, record the conflict, and do not pick a winner.
- Review sites and job ads never graduate past Signal on their own.
- Retain dates, qualifiers, geographies, sample sizes, and units. Do not widen a claim.

### Foundation extracts

These sections are the report. Write them from classified findings, not from general knowledge.

#### Trustworthy Research

Use only Official or Corroborated findings about this organisation's real pains, constraints, and initiatives. Speak to what they are dealing with, not generic industry trends. Each bullet needs a Claim ID and a locator.

#### Buyer Language

Quote phrases the organisation uses for itself: values, role language, strategy labels, and how they describe the problem. Prefer wording that appears more than once. Cite the source. The aim is to speak as a peer already working with them, not as an outsider. Do not invent voice.

#### Falsifiable Facts and Stats

List dated, scoped figures you can check. Include their numbers from official sources and, when the user supplied them, the vendor's own numbers as `Provided`. Trust sits in the details (year, unit, geography, sample), not in generalities. Never invent a statistic.

#### Strategic Priorities

List three to seven priorities in the organisation's own language. Tie each to a source and a trust band. Job-ad objectives and investor themes are signals until an official strategy document or results commentary corroborates them.

Also capture, when the sources support them: risks, opportunities, and what is already working. Keep those labelled with their trust band.

## Output

Write the full report in this run as `external-source-report.md`:

```markdown
# External Source Report: [Organisation]
## Trustworthy research
## Buyer language
## Falsifiable facts and stats
## Strategic priorities
## Source log
## Open evidence gaps
```

The source log uses the shared evidence table plus a Trust band column. It supports the extracts. It is not a substitute for them.

If file creation is unavailable, return the same report inline under that filename.

## Boundary

Use only public or authorised material. Do not search for credentials, personal data, private systems, or access-control bypasses. Review sites, news, and job ads stay leads until the underlying source is validated.

## Handoff

The report is the handoff. Send verified claims, buyer language, and priorities to Customer Brief Research and Response Insight Enricher. Send remaining public gaps to Build Google Dork. Send supplied PDFs to PDF Insight Finder.

## HANDOFF SCHEMA

Source: `references/HANDOFF_SCHEMA.md`

# Shared Handoff Schema

Use these filenames and sections so every skill can pick up the prior work without re-researching it.

## `customer-brief.md`

```markdown
# Customer Brief: [Organisation]
## Account context
## Business relevance
## Stakeholders and professional relationships
## Operational and commercial context
## Decision criteria and success measures
## Open gaps
```

Adapt or omit subsections to fit the user's business and objective. Keep the title, evidence references, and open gaps consistent for downstream workflows.

## `external-source-report.md`

```markdown
# External Source Report: [Organisation]
## Trustworthy research
## Buyer language
## Falsifiable facts and stats
## Strategic priorities
## Source log
## Open evidence gaps
```

## `research-pack.md`

```markdown
# Research Pack: [Organisation]
## Official sources
## Research themes and search terms
## Source log
## Verified claims
## Open evidence gaps
```

## `public-discovery-queries.md`

```markdown
# Public Discovery Queries: [Organisation / Topic]
## Official and regulatory sources
## Topic-specific queries
## Results requiring validation
```

## `pdf-evidence-ledger.md`

```markdown
# PDF Evidence Ledger: [Organisation / Topic]
## Highlighted evidence
## Claim table
## Risks, opportunities, and quantified facts
```

## `response-insight-pack.md`

```markdown
# Response Insight Pack: [Question]
## Draft diagnosis
## Enriched response
## Claim-to-evidence map
## Open gaps
```

## `review-backlog.md`

```markdown
# Review Backlog: [Draft]
## Evaluator lenses
## Prioritised corrections
## Required evidence changes
## Re-review scope
```

Reference `Claim ID` and status values from the shared evidence contract in every source log, response evidence map, and review correction.

## Internal Research

Source: `references/internal-research.md`

# Internal Research

Use first-party records only. This skill fills the internal half of the customer-insight brief from what the team already knows. It does not score a draft. It does not pull public filings. Run External Research as a separate skill. Merge both into one completed document with Completed Insight Brief.

Works with a CRM connector, email, meetings, notes, and call recordings. If no connector is available, use a CRM export plus shared notes, or upload those files to ChatGPT, Claude, or Gemini. The output shape stays the same.

## Inputs

Require a named buyer and a live bid (deal, opportunity, or RFP). Optional: the RFP, a content library, an existing customer-insight brief.

Do not wait for a complete record. Run on what exists and mark the rest Missing.

## Completed document (reference)

Write so a bid manager can paste straight into the brief. This is the internal half of that document. Leave a box blank if you do not have the source.

```
CONTACT SO FAR
Name / stage / owner / close date
Who we have spoken to: name, title, source
Chronology: date, title, one line from the record

LANGUAGE THEY USE
Must use
Do not introduce

DRIVERS AND PAIN
Insight + source (meeting title and date). No product claims.

GAPS
Missing from contact history. Not a score.
```

External Research fills Buyer story, Falsifiable facts, and Evaluator flags. Do not fill those here. Completed Insight Brief is the merge step.

## Rules

- Use what is actually on the records. Do not invent stakeholders, quotes, dates, site counts, KPIs, or promises.
- If it is not in the CRM, email, meetings, notes, or call recordings, write Missing. Do not fill the gap from the RFP, a website, or an exec bio.
- Do not name public executives as contacts unless they appear on a CRM contact, email, or meeting record.
- Quote the buyer. Keep the speaker, date, and source next to every claimed phrase.
- Weak note: "buyer wants better scheduling." Good note: stated problem, speaker, meeting title, date.
- No evaluator scoring. No personas. No open-tensions block. No response edits.
- Government tender and procurement processes are out of scope.
- No pink-team, red-team, or colour-team language.
- Always AutoRFP.ai if the product is named. No emdash. No double hyphen. No hype words.

## Where to look

Use the CRM connector first. Then email, meetings, notes, and call recordings.

Look up:

1. Company
2. Deal or opportunity (name, stage, owner, close date if present)
3. Contacts on the deal
4. Meetings and call recordings
5. Notes
6. Email threads tied to the deal or those contacts

If a connector is missing, say which source you could not open.

## Output

A standalone internal research document in the completed-brief fields above.

### 1. Stakeholder map

For each person actually on the records: name, role or title, what they care about (quoted or clearly paraphrased from a source), and the record used (note, meeting, email, or contact). If the record does not say what they care about, write Missing. This map feeds Who we have spoken to. It is not a second contacts list.

### 2. Contact so far

Deal snapshot: name, stage, owner, close date if present.

Who we have spoken to: name, title, record.

Chronology: meetings, emails, and notes in date order. Each line: date, title or subject, one-line summary quoted or tightly paraphrased from the record.

### 3. Confirmed drivers and pain

Only items with a source. Each bullet: the stated driver or pain, then a short source (meeting title and date, email subject and date, or note).

If the CRM only has a slogan ("better scheduling"), list it as too weak to use and keep it out of confirmed drivers.

### 4. Language they use

Must-use: person, place, people-function, service model, and process nouns that appear on contacts, meetings, emails, or notes.

Do not introduce: vendor nouns that would replace those words.

If a source is silent on a noun, write Silent. Do not import language from the RFP or from public exec bios unless it also appears in these records.

### 5. Gaps

Anything a bid team would expect from contact history that the records do not cover. List as Missing. This is not a scorecard.

## Do not

- Grade the response or invent scoring lenses
- Invent stakeholders so the map looks complete
- Turn gaps into evaluator flags
- Fill Buyer story or public facts (that is External Research)
- Write a seller Slack message or a list of questions (that is a later, separate follow-up)
- Rewrite the proposal from this research

## WORKFLOW

Source: `references/WORKFLOW.md`

# Customer Insight Workflow

Use these workflows as a connected, evidence-preserving system. Run only the stages the request needs, adapt fields to the user's business, and preserve the handoffs whenever a downstream stage is used.

| Order | Skill | Consumes | Produces | Next use |
|---:|---|---|---|---|
| 1 | Customer Brief Setup | Authorised account inputs | `customer-brief.md` + open gaps | External research, research, enrichment |
| 2 | External Research | Target organisation, offering, jurisdiction | `external-source-report.md` | Research, dork building, response enrichment |
| 3 | Customer Brief Research | Brief + evidence gaps + external-source report when present | Updated brief, source log, research themes | Dork building, PDF insight finding |
| 4 | Build Google Dork | Research gaps, organisation aliases, jurisdictions, source log | `public-discovery-queries.md` | External Research or Research validates resulting sources |
| 5 | PDF Insight Finder | Brief, research themes, verified PDFs | Annotated PDF + `pdf-evidence-ledger.md` | Response enrichment |
| 6 | Response Insight Enricher | Buyer question/draft + brief + evidence ledger | `response-insight-pack.md` | Revise the response and close remaining gaps |

## Evidence contract

Every material statement that moves between stages must have a record in the shared evidence ledger:

```markdown
| Claim ID | Claim / exact quote | Source | Locator | Source type | Confidence | Status |
|---|---|---|---|---|---|---|
| C-001 | [exact wording] | [title / URL / user prompt] | [page, section, or quote] | User supplied / Internal approved / PDF primary / Official public / Independent / Illustrative | High / Medium / Low | Provided / Verified / Needs evidence / Illustrative |
```

- `Verified` means the source supports the claim at the stated scope.
- `Provided` means the user or an authorised internal source explicitly supplied the fact; it is not independently verified.
- `Needs evidence` must never become a factual claim in an enriched response.
- `Illustrative` is only for fictional or hypothetical content and must never be presented as verified evidence.
- A Google result is a lead, not a source, until Research records and checks it.
- Retain qualifiers, dates, geographies, sample sizes, and units; do not widen a claim during handoff.

## Revision loop

If a correction reveals a missing account fact, route it to Customer Brief Research. If it needs a public document, route it to Build Google Dork and then back to Research for validation. Re-run Response Insight Enricher only on the changed response.

## Final delivery

Deliver the requested asset plus only the relevant supporting handoffs: a concise customer brief, source/evidence log, annotated PDF, enriched response, and/or prioritised review backlog. Do not expose internal working notes unless requested.
