A file on a reporter who never agreed to it and does not know it exists: record where each line came from, fix the jurisdiction before the send, then let a named partner sign.
A reporter enters the file, and the source of each line in it is written down beside it.
02
A record is enriched from a third party, and the notice that record owes is scheduled, not deferred.
Reason
03
A story is matched to a reporter, and the lines in the file that selected them are named in the match.
04
A draft is written, and its subject line is tested before a news offer turns into an advertisement.
05
A recipient resolves to a country and a subscriber type, because one market says opt-in and the next does not.
Decide
06
Something of value is offered, and the offer and who was told of it are logged before the pitch goes.
07
An item goes out for a foreign principal, and the forty-eight-hour filing clock starts with it.
Out
08
A reporter goes quiet, and the silence is recorded as unreadable rather than scored as a result.
09
Execute send or write actions only inside the approval boundaries agreed at implementation.
→Product statement
Matching, drafting and logging belong to the agent. Release belongs to a named partner, who signs for what went out and to whom.
Example workflow
One pitch, file to release
AgentHuman
1Reporter file assembledBylines, beat, outlet, stated preferences, prior contact and where each line came from
2Recipient fixed and classifiedThe country, the subscriber type, the corporate form and the day that classification was set
3Match and draft raised togetherThe lines that selected the reporter, the draft, the subject line and any offer inside it
4Controls appliedNotice checks, jurisdiction checks, subject-line classification and disclosure checks
No human action required
Stages 1 to 4 run unaided, and nothing leaves the building at any of them — the agent is drafting, and the partner lane opens at the release gate.
5DecisionSplits at the release gate
Ordinary trade pitch
Goes to the named partner to release.
Anything for a foreign principal
Adds a counsel read first.
Partner review
The pitch is held with the file lines that selected the reporter, the classification and the offer log.
Send · Append source · Hold for partner review
Released — by the named partner▼
6Outbound and filing records updatedOnly where send access and the records policy permit it
7Outcome evaluatedNotice currency, classification accuracy, partner corrections and what review found
Corrections
Each partner correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Releasing a pitch to a named reporter.
Deciding an item is not informational materials.
Judging whether a mandate sits outside FARA.
Signing the six-monthly statement under oath.
Automation boundaryAgent acts unaided
✓Write down the origin of each line in the file.
✓Schedule the notice a new record owes before it is enriched again.
✓Fix the country and the subscriber type before the draft is raised.
✓Log the item, the channel and the named recipient.
Nothing reaches a reporter except by a named partner, inside the agreed boundaries.
Judging whether an offer needs disclosing.
Telling counsel the outbound log is complete.
Choosing which reporters a mandate may approach.
Changes to the file, the send list or the classification.
Example output
One reporter file, annotated
This serves a press office that may have to account for a named contact years after the pitch went out; below is one record exactly as the agent leaves it.
Reporter file · single contactIllustrative example
Selection
Recorded as
Outlet
Evidence of record
Confidence
Held for
Technology desk, named correspondent
Matched on three filed lines
Provenance, per line
Published byline, 3 August 2026
Held unsent
The named partner, by name
As receivedBuilt from published bylines and one vendor record, and it claims nothing the reporter has not printed.
What the file holdsPublished bylinesVendor recordPrior contact log
Why no send hereApproaching a named reporter is a judgement a named partner makes.
ActionReleaseAppend sourceSend to counsel review
What the score decidesWhere the client is a foreign principal the draft gets a counsel read before release.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Each pitch draftedFrom the file lines that selected the reporter
03Evidence
Where each line is put to work
The agent does not vouch for a reporter file, only for where each line came from, when it was taken, and which of those lines selected the recipient.
01Approved path
A file on a named reporter
Move the country, the subscriber type or the question of whether a partnership counts as corporate, and the same message changes footing, with nobody having lied.
02Human review
What was searched for, and not found
No data-protection authority in the sources searched was found to have ruled on a PR or media contact file as such, while a control query on those same sources returned live data-broker enforcement, so the surface works and what is missing is a carve-out rather than the risk.
04Build an evidence trail
The pitch, the file that selected the reporter and the person who sent it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Published journalismBylines · outlet mastheads Beat, desk and coverage filed lately
Contact vendorsMedia CRM · list vendors Names, addresses and provenance
Your own contact historySent mail · embargo records Approaches made and any replies received
Agent
Pitch matching and outbound records
Reads the file Raises the match and the draft Holds for the partner
Filing and registry sourcesRegistry filings · public notices Mandates carried for a principal
An outlet-level correction figure can read clean while foreign-principal mandates carry most of the disclosure rework. Nestack reports the correction rate by mandate class, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Foreign-principal mandates
10.8%
3.7×
Review
Multi-market send lists
7.7%
2.6×
Review
Vendor-enriched records
4.8%
1.6×
Watch
Established named contacts
2.4%
0.8×
Normal
Bar: correction-rate lift vs. established-contact baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an unsourced file costs
The loop shuts when the reporter contacted from a file never disclosed is a standing case. That suite is what the next send list is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on foreign-principal mandates.
02Diagnose
The pitch that reached a reporter whose record nobody could source is worked backwards until one cause is left standing.
03Improve
Every send goes out numbered, with the files that selected it attached.
04Verify
Nothing sends while one touched disclosure case is still red.
05Learn
The case stays on, and the matching rules are redrawn beside it.
Learn → DetectThe return edge. The next send list is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, matching and drafting, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Journalist-file and automation-boundary definition.
02Published, vendor and internal sources.
03Contact-to-recipient and disclosure-coverage mapping.
04Contact-file ingestion.
05File, recipient and outlet binding.
06Disclosure scoring and review routing.
07Partner release workflow.
08Media-CRM integration.
09Disclosure and selection cases.
10Guardrails and outbound controls.
11Send-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne mandate, one cycleProductionProduction outbound workflowAdvancedMultiple mandates / markets
Introduced at Pilot
Pitch drafting to your house rules✓✓✓
Named partner release✓✓✓
Contact-file baseline✓✓✓
Introduced at Production
Reporting by outlet class—✓✓
Partner review workflow in your systems—✓✓
Approved outbound sends—✓✓
Database-and-sender integration—✓✓
Introduced at Advanced
Multi-market classification——✓
Cross-mandate pitch packs——✓
Large contact files——✓
Multi-market outbound controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, contact volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your live mandates and the reporters each one names→File capture and provenance versioningWeek 1
02Representative published, vendor and internal sources→Source binding, match logic and the contact-file baselineWeek 2
03Your outbound calendar and the partners it names→File mapping, provenance binding and the automation boundaryWeek 1
04Access to the APIs, feeds or exports behind them→Published, vendor and internal source assessment, then integration setupWeek 2
05Files you would not want disclosed→Selection cases and the evaluation roundWeek 4
06What no pitch may offer→Disclosure scoring, review routing, guardrails and release controlsWeek 3
07A named partner who releases the pitch→Release to the named partner, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Widths here follow cost rather than the grid, which is why the fifth week shows one band under another.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1File discovery, provenance versioning and the automation boundaryW2Source integration and the contact-file baselineW3Match logic, drafting rules and release controlsW4Evaluation suite, selection cases and failure-mode testingW5Media-CRM integration, pilot sends and targeted correctionsW6One outbound cycle run under the media-relations lead, then Agent Care handover
Reading the bandEach bar spans only the weeks its own work is named for, and week five is shared by design.
At the end of W6Once the send record validates, Agent Care assumes the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · PR AI agent
Build a pitch matching agent around the reporter file your last send never wrote down.
Show us one send list you reuse each quarter and the file behind the last name on it. If nobody can say where those lines came from, or which of them chose the recipient, then the pitch is being trusted rather than defended. A file nobody can source comes back as a finding.
