Why this matters
You walk into a first expansion conversation at a Tier 1 account. Your brief says the customer reduced labour cost by one and a half percent since go-live.
You say it in the room. The VP of Operations looks at you and says: that was our estimate, we never published it, and our finance team disagreed with it. The rest of the meeting is about whether you are careful.
Nothing in your brief was invented. Every number was in a real document. And the brief is still the reason the meeting went badly.
Everything this lesson uses came in the practice pack from the course page; if you have not downloaded it, do that first.
What you will be able to do
- Structure an account brief so internal certainty comes before external inference.
- Put a source line on every claim, and an "unknown" section that is allowed to be long.
- Run a repeatable fabrication hunt, and fix the brief rather than the output.
Internal facts first, on purpose
Fixed sections, in this order:
1. What we already know from our own data (usually half the brief)
2. Opportunity history and outcomes
3. Relationship map, from contacts and activities
4. Product usage and support signals, if we are already in the account
5. External context, every claim with a source
6. Why now: the hypothesis, labelled as a hypothesis
7. Unknown: what could not be established
The ordering is the point. A seller reads top to bottom and stops when time runs out, so the most certain material goes first. It is usually also the most useful: here, section 4 tells you Wexley Care Group runs at 92% seat utilisation with the payroll sync module switched off, a better reason to call than anything on a website.
Section 6 is labelled a hypothesis, in the output, in that word. Section 7 is not a failure state. A brief with a long unknown section and six sourced facts beats one with twenty confident sentences, and the second kind is what you get by default.
One source line per claim
Every claim says where it came from:
Claim: Expansion opportunity open at 74,000 EUR for payroll sync and extended
compliance reporting.
Source: opportunities.csv, OPP-007532, stage Proposal, close_date 2026-09-20.
Claim: The payroll sync module is not switched on.
Source: product_usage.csv, ACC-02830, 2026-07, feature_payroll_sync = FALSE.
Claim: Their payroll platform is on an old release with an upgrade planned for
the fourth quarter, and their IT director will not integrate twice.
Source: notes/qbr/business-review-wexley-care.md, "What stands between us and
74,000 EUR". Reported by the customer on the QBR call, not verified by us.
Notice the third one: sourced, and still not a fact about the world, only a fact about what somebody said on a call. The source line says so. That distinction is the whole of the break below.
The fabrication hunt
Run this on every research output until it stops finding things. About four minutes per brief.
- No source line, no claim: delete it, do not investigate it. The fastest step, and it removes most of the problem. Checking whether an unsourced claim happens to be true rewards the behaviour you are trying to remove.
- Verify five sampled claims at source by hand. Open the file, find the record, read the value.
- Search for the tells. Precise numbers with no source. Recent events with no date. Named people in named roles. Tooling claims ("they use X"). Any sentence that would be embarrassing if wrong.
- Change the brief, not the output, then re-run. Make that class of claim require a source or be out of scope. Fix only the output and the same class returns next week, in a brief you have less time to check.
Step 4 is the one people skip, and the only one that compounds.
Try this now: run the research brief
Save this brief as 20-briefs/account-research.brief.md; a seed to start from is at
templates/M7/account-research.brief.md in your practice pack.
OUTCOME
Produce an account research brief for ACC-02830 that a seller can act on before
an expansion conversation.
INPUTS
10-data/accounts.csv, contacts.csv, opportunities.csv, activities.csv,
product_usage.csv, support_tickets.csv
10-data/notes/ (call notes and QBR documents)
PERMITTED SOURCES: the files above only. Web research: not enabled.
OUTPUT SHAPE
30-output/demand/account-briefs/ACC-02830.md
Sections in this order: what we already know | opportunity history |
relationship map | usage and support | external context | why now (hypothesis) |
unknown.
Every claim is followed by a "Source:" line naming the file and the record id or
the document section.
CONSTRAINTS
Do not use general knowledge about this company, its industry or its people.
A claim with no source is not written as prose: it goes in the unknown section
as a question.
Where a source marks a figure as customer-reported, unaudited or unverified,
carry that marking into the output in those words. Do not paraphrase it away.
Anything that reads as an event ("recently", "just announced") must carry a date
or be dropped.
DEFINITION OF DONE
Every paragraph in sections 1 to 5 has at least one source line.
The unknown section is not empty.
The why-now section is labelled "Hypothesis" in the output.
EXCEPTIONS RULE
Any claim you cannot source goes to the unknown section as a question naming who
could answer it. Do not delete it silently and do not assert it.
What you should see, in section 4 and the unknown section, in this shape:
## Usage and support
Seat utilisation 92.4% in 2026-07 (3,008 active of 3,254 licensed), flat trend,
adoption score 86.
Source: product_usage.csv, ACC-02830, 2026-07.
Forecasting module in use. Payroll sync module not in use.
Source: product_usage.csv, ACC-02830, 2026-07, feature_forecasting = TRUE,
feature_payroll_sync = FALSE.
Nine support tickets on record, one currently open, four escalated beyond first
line.
Source: support_tickets.csv, filtered on ACC-02830.
## Unknown
- Whether the four escalations were the same root cause. The ticket categories
are recorded but no linkage field exists. The support agent named on them
could answer this.
- Who signs a 74,000 EUR expansion. Two contacts are recorded with persona
Economic Buyer (CON-008577, CON-008609) and the QBR names one of them as the
budget owner. Which of the two holds this budget is not established.
Source for the ambiguity: contacts.csv and
notes/qbr/business-review-wexley-care.md.
That last unknown is the brief working as intended: two records say Economic Buyer, the QBR names one person, and the honest output is a question, not a guess. An unguarded brief picks one, and the seller addresses the wrong person.
When this goes wrong
Break it
Run the same brief against ACC-03128 (Lyndhurst Retail Group Inc) without the constraint line
that carries unverified markings through. Web research is still off: this failure is entirely
internal.
The tell
The brief comes back reading, in confident prose:
Lyndhurst has 192 corporate properties live with approximately 84 hourly staff each. Labour cost is down 1.5% since go-live, and schedule publication has moved from a Thursday scramble to a Monday routine.
Now open the source, the QBR note at data/notes/qbr/business-review-lyndhurst-retail.md in your
practice pack, section "What the customer
reported":
Figures below belong to the customer and were presented by Liesbeth. Talvera has not audited any of them and they must not be quoted externally without written permission.
The underlying call note, data/notes/call-notes/lyndhurst-retail-franchise-workshop.txt, independently
says the same:
Their numbers, which are theirs and not ours, and which we should not repeat outside without asking.
Two documents, by two different people, both flagged these figures. The brief stripped both markings and kept the numbers.
Nothing was fabricated. Every figure is real and correctly transcribed. What was removed was the sentence saying whose figures they are and what may be done with them. The claim now reads as something Talvera measured, and the next place it appears is a slide.
Next to the source, the laundering is obvious. Alone, as a seller reads it at 8:50am, it is invisible. That is why this failure survives review by the person who wrote the brief.
A second instance in the same dataset has a different shape.
data/notes/call-notes/call-selby-supply.txt records a champion's estimate that depot supervisors spend
two to three hours a week each rebuilding rotas across 18 depots. The rep who wrote it added: "His
number, not ours. I have never validated it and I should." An unguarded brief produces "depot
supervisors lose two to three hours a week to manual rota building", and now Talvera is asserting
it.
The guard
Three rules in the brief, and a fourth habit:
Every claim carries a source line. Already in the brief.
Anything the source marks as unverified, unaudited, customer-reported or not to be quoted stays marked in the output, in those words. Not paraphrased, not footnoted, not dropped because it interrupts the sentence.
Anything with no source goes to the unknown section as a question, never into prose.
Re-run and confirm the sentence survives with its marker attached. A guard you have not watched fire is not a guard. The corrected output reads:
The customer reported, on the QBR call and unaudited by Talvera, labour cost down 1.5% since go-live across 192 corporate properties. Source: notes/qbr/business-review-lyndhurst-retail.md, "What the customer reported", which states the figures belong to the customer, have not been audited by Talvera, and must not be quoted externally without written permission.
Then write one sentence, by hand, on what would have happened if the first version had reached a pricing conversation. Keep it. It is why you will not remove the guard when it makes a brief less punchy.
Worth knowing: the call notes here are messy in form but agree with the CSV rows, with one
deliberate exception, documented in answer-keys/PLANTED-ISSUES.md in your pack, which you open
only after attempting the lab, under note-crm-contradiction: opportunity
OPP-007372 on account ACC-02826, where a note states an amount, a close date and a stakeholder
role the CRM rows disagree with, and claims the record has been updated when it has not.
Laundering (this lesson) is a marked claim losing its marking; a source-marking rule catches it.
Contradiction is two sources disagreeing about a fact; you catch it by reconciling sources and
refusing to pick, the deal-card corroboration work in Module 6.
What you keep
20-briefs/account-research.brief.md, with the permitted-sources block, the source-line rule, the unverified-marking rule and the unknown-section rule.30-output/demand/account-briefs/<account-id>.md, at least one.- A
50-runs/RUN-LOG.mdentry recording the fabrication hunt: claims checked, claims removed, claims moved to unknown, and the brief change you made as a result.
Check yourself
- A brief contains: "They are investing heavily in workforce technology this year." What is wrong, and what are the two acceptable outcomes for that sentence?
- Your source is a QBR document that flags a figure as customer-reported. Your seller says the marking makes the brief read weakly. What do you say, and what do you offer instead?
- A fabrication hunt finds three unsourced claims of the same kind. Name the two changes you make, and which one comes first.
- Your unknown section has eleven items and your sourced facts number six. Working or failing? What would tell you?
Where this goes next
L7.4 builds the list these briefs feed: suppression, a reconciliation that proves nothing was dropped, and the review gate between a draft and a prospect.