Co-pilot buyer activation × nurture

No-Reply Nurture Calendar

A 90-day DEFONEOS no-reply calendar for public-sector buyer threads: four useful touches, one proof object per touch, clean CRM evidence, explicit stop conditions, and no spam behaviour.

90dmax window

4touch cap

7cadence gates

0spam scripts

Use now: open this page immediately after a buyer reply or a validation request. Classify the signal, choose the smallest proof object, keep the owner gate clear, and log the action in the DEFONEOS CRM.

Why a nurture calendar exists

Silence after a first contact is normal in UK public-sector buying. The sovereign move is not to chase harder. It is to keep the record clean, send only useful updates, and stop when the buyer gives no route.

Maximum four follow-ups over 90 days unless the buyer engages.
Every touch must contain a useful public object or a specific close-out question.
No fear language, no invented urgency, no false scarcity.
No bulk campaign. Each touch is tied to one buyer record and one public-service problem.

90-day no-reply calendar

Window	Action	Object	Condition
Day 0	Send the promised artefact only. No added sales copy.	Meeting promise link or evidence-room bundle.	Buyer asked for it.
Day 1	If no acknowledgement, send a one-line correction opportunity.	Did I capture your constraint correctly?	Positive meeting only.
Day 7	Send one useful public object tied to their remit.	Risk register, route map, or governance crosswalk.	No guilt language.
Day 14	Send a route-confirmation close-out.	Should I close this or route it to a colleague?	No more than one cc.
Day 30	Send a substantive update only if something changed.	New evidence room, updated SoW, live demo improvement.	Must be real new value.
Day 60	Send a procurement-calendar note if relevant.	Upcoming DASA, DIANA, CCS or G-Cloud timing.	Public source only.
Day 90	Archive politely unless the buyer engaged.	Closing the loop. Happy to reopen if useful.	Stop pursuit.

Useful-update library

Only send one of these if it genuinely fits the buyer remit.

Buyer remit	Useful update	Why it is safe
AI assurance	JSP 936 control-map update and evidence-room shelf.	Governance evidence, no operational data.
Procurement	DSP, DASA, G-Cloud or procurement-vehicle route page.	Public route guidance, owner must verify current link.
Technical owner	Technical validation agenda and byte-verified public artefact.	No classified system details.
Budget owner	90-day SoW, pricing card and risk register.	Draft commercial model, not a quote unless owner approves.
Civil resilience	999 integration and public-source demo boundary.	No personal surveillance.
Prime partner	Work-package framing and supplier-on-ramp bundle.	No exclusivity or endorsement claim.

No-reply templates

Day 7 useful update
I am keeping this light. One public artefact may be useful for [buyer problem]: [single link]. If this is not in your remit, I will stop here unless you point me to the better route.

Day 14 close-out
I do not want to add noise. Should I close this record, or is there a better owner for UK-sovereign AI assurance pilots? Either answer is fine.

Day 30 substantive update
A material update since the last note: [one concrete update]. It may help your [remit] because [one sentence]. If not useful, no reply needed and I will keep the record dormant.

Day 90 archive
Closing the loop on this thread. DEFONEOS remains available as a public-source, sovereign-by-design assurance pilot route, but I will not keep chasing without a live route.

Calendar governance

The calendar is an evidence trail. It shows restraint, relevance and respect for the buyer inbox.

Rule	Reason	CRM evidence
Four touches max	Avoid spam and preserve trust.	touch_count field.
One proof object	Avoid dumping the estate.	proof_object_sent field.
One ask	Make response easy.	next_action field.
No weekend sends	Respect public-sector cadence.	scheduled_at field.
Archive at 90 days	Stop stale pursuit.	state DORMANT.
Manual owner send	External comms remain human-gated.	owner_sent true or false.

Weekly nurture review

Every Friday at 16:00 BST, run this review before the next week starts.

Sort CRM by next_action_date and state not CLOSED.
Remove any buyer with RED no-fit or explicit no-contact.
Check whether the proposed object is genuinely new since the last touch.
Verify every link returns HTTP 200 from the Vercel alias.
Update signal score decay for 14, 30, 60 and 90-day silence.
Prepare drafts only. Nick presses send.

Do-not-send list

These messages damage trust and are forbidden in the DEFONEOS lane.

Just checking in.
Bumping this to the top of your inbox.
As mentioned by MOD or NATO.
We are DAIC certified or AUKUS partnered.
This is urgent for national security.
Can I have 30 minutes of your time without a specific agenda.
Any message containing sensitive operational data or personal surveillance framing.

Nurture queue worksheet

The nurture queue is a low-noise operating list. Each buyer has a next useful object, a stop date and a reason for receiving the next note. If the reason is weak, the note is not sent.

Field	Purpose	Example
buyer_id	Stable record key without unnecessary personal data.	dstl-ai-assurance-2026-07
last_touch	Prevents accidental over-contact.	2026-07-14 09:10 BST
next_useful_object	Forces the message to carry value.	Technical validation agenda or procurement route map.
reason_to_send	Explains why the buyer should care now.	New evidence-room map or public call deadline.
stop_condition	Defines when pursuit ends.	No reply after Day 90, explicit no-fit, or no named route.
owner_gate	Marks whether Nick must verify or send.	Yes for all external comms.

Monthly useful-object plan

The calendar below gives the owner a non-spam reason to stay visible only when there is real substance.

Month	Useful object	Use only when	Stop if
July	Evidence room, pricing card, 90-day SoW.	The buyer had a first conversation or asked for proof.	No authority or no remit.
August	Technical validation agenda and acceptance criteria builder.	The buyer asked how the pilot would work.	They require classified data before a route exists.
September	Procurement route map and public call calendar.	The buyer asked how to buy or route internally.	Procurement restriction blocks the route.
October	Governance update and red-line register.	The buyer has an assurance function or risk concern.	They asked for no further updates.
November	Close-out summary with one reopening condition.	There has been no engagement for 90 days.	Any explicit no-contact request exists.

Operator note

This additional operator note exists to make the page self-contained when opened without the rest of the DEFONEOS pack: if the owner cannot explain the next action in one sentence, the correct move is to pause, classify the buyer state again, and send nothing until the proof object is clear.

12-framework crosswalk

Use this crosswalk when the buyer asks whether the operating artefact can become assurance evidence. It keeps the page honest: designed controls are named as designed, live proof is named as live, and owner-gated claims remain gated.

Framework	How this page maps
EU AI Act	Human oversight, transparency, risk management, logging, technical documentation and post-market monitoring vocabulary.
GDPR	Data minimisation, lawful basis, purpose limitation, retention boundary, access logging and contact-note minimisation.
JSP 936	UK defence AI assurance framing, safety case discipline, human responsibility, evidence pack, review gate and escalation path.
JSP 440	Protective security discipline for information handling, marking, distribution and no-sensitive-data public-pilot boundary.
NIST AI RMF	Govern, Map, Measure and Manage actions tied to buyer signals, evidence quality, risk owners and response cadence.
ISO 42001	Management-system responsibilities, review cadence, audit trail, competence, roles and continuous improvement loop.
NIST PQC	Migration-aware crypto language, no promise of final PQC certification, signature and ledger route designed for future algorithm agility.
NATO STANAG	Interoperability mindset, common vocabulary, coalition-safe evidence, no national endorsement claim.
AUKUS Pillar II	Design-compatible dual-use AI assurance language, no partnership claim without signed letter.
OSCAL	Control evidence can be exported into a machine-readable SSP later; this page is the human operating sheet.
Five Eyes ITAR §734.7	Public-domain and open-source evidence boundary; no controlled technical data, no classified material.
C2PA 2.0	Future media provenance route for screenshots, demos and proof bundles; public page links remain the low-friction evidence trail.

Honesty register

The register below is deliberately explicit so the artefact stays usable in a UK-sovereign procurement conversation without overclaiming.

This page is an owner-executable operating artefact, not legal advice, not government endorsement, and not a submitted procurement response.
AUKUS-compatible means design compatibility only. No AUKUS partnership, DAIC certification, NATO endorsement, DASA award, or MOD approval is claimed.
DEFONEOS-SEAL is not issued here. Any credential requires the 33-agent BFT council quorum plus owner-gated authority.
No kinetic-targeting, strike-package, find-fix-finish, kill-order, face-recognition, phone-location, or individual-tracking pattern is included.
Buyer names and public bodies are routing examples from public procurement context. Nick must verify current named contacts before sending.
All external communications remain owner-gated. JEEVES may draft, verify, package and log, but Nick presses send.
SIGIL anchor is local until the SOV3 ledger response is attached to the tick record.
Generated 2026-07-11T10:19:10Z. File slug: defoneos-mod-no-reply-nurture-calendar.