Customer Onboarding — Evidence First, Access Second

Onboarding principle

A new buyer should experience DEFONEOS as controlled, auditable, and bounded from minute one. The onboarding path starts with evidence and scope, not with unbounded platform access.

• First 10 minutes: confirm buyer route, public evidence, and owner gate.
• First 24 hours: send evidence room, pricing card, and validation agenda.
• First 7 days: scope a 90-day pilot or close the thread honestly.
• First 30 days: produce control map, public-source demo, and risk register.
• First 90 days: deliver go/no-go report and procurement route.

Onboarding stages

This replaces vague “your sandbox is live” language with a real controlled path.

First-10-minute checklist

Use this after a high-intent buyer action.

• Open CRM and create or update the buyer record.
• Classify source: demo, pricing, investor, partner, procurement, or checkout.
• Check whether the buyer is public-sector, prime, SME, academic, regulator, or investor.
• Send the correct public link bundle only.
• Schedule a validation slot or stop if the signal is low-quality.
• Do not claim operational access, security clearance, or certification.

Sandbox provisioning truth

The old onboarding page implied automatic sandbox provisioning. This page makes the truthful route explicit.

Command examples

Commands below are illustrative until a buyer-specific sandbox exists. Do not present them as live credentials.

# Public-source pilot preparation
python -m defoneos.verify --evidence-room public --red-lines strict
python -m defoneos.scope --template 90-day-pilot --buyer public-service
python -m defoneos.audit --frameworks jsp936,nist-ai-rmf,iso42001,uk-gdpr

# Private sandbox commands require owner-gated provisioning.
# Never paste real API keys into public pages or email.

Welcome email template

Send this only after owner verification.

Subject: DEFONEOS onboarding — evidence, scope, and next step

Thank you for the DEFONEOS request. I have verified the public route and set up the next step as a bounded validation, not an open-ended platform rollout.

Your public evidence links:
- Evidence room: /defoneos-mod-evidence-room-index
- Pricing: /defoneos-mod-pricing-card-onepager
- 90-day pilot SoW: /defoneos-mod-meeting-notes-to-sow

Before any sandbox or private workspace is provisioned, we will confirm data boundary, scope, commercial route, and accountable owner.

Regards,
Nicholas Templeman

30-day onboarding cadence

The onboarding cadence turns a high-intent buyer into a governed pilot without assuming that all infrastructure is already accredited.

Access-control model

Access follows the least-privilege route. Public pages are open. Private workspaces are created only after scope, payment or contract path, and data boundary are verified.

• Public visitor: can read public pages and evidence-room artefacts.
• Prospect: can receive tailored public links and validation agenda.
• Pilot buyer: can access a private workspace only after owner gate.
• Prime or consortium partner: receives partner-safe artefacts without exclusivity.
• Regulator or standards body: receives governance and assurance artefacts, not sales pressure.
• Investor: receives investor pack only after identity plausibility check.

Onboarding failure modes

These are the common places onboarding goes wrong. The page names them so the operator can prevent them.

First technical validation agenda

This is the agenda for the first call after onboarding.

0-3 min   Confirm buyer problem and success condition.
3-8 min   Show evidence-room map and red-line register.
8-13 min  Walk through public-source demo route and data boundary.
13-17 min Show pricing card and 90-day SoW skeleton.
17-20 min Agree next step: stop, route, technical deep dive, or pilot scope.

Evidence artefacts created during onboarding

Each buyer journey should leave a small, auditable trail. That trail is the operating system: not a spreadsheet of vague promises, but named artefacts with owners and review dates.

Data-boundary pledge

This pledge is the clearest way to explain onboarding to a cautious public-sector buyer.

• Public pages contain only public, illustrative, or owner-approved content.
• Private buyer data does not enter public Vercel pages.
• Classified, sensitive, or operationally protected data is out of scope for public demos.
• Every AI-assisted output remains advisory during pilot unless a separate assurance path changes that status.
• Every pilot has a named human accountable owner.
• Every red-line request stops automation and routes to Nick.
• Every external claim is bounded by evidence, sample size, and honesty status.

Procurement route primer

Onboarding should quickly identify the likely route so the buyer is not left with “interesting, but impossible to buy”.

12-framework crosswalk

The mapping below is a design and evidence discipline, not a claim of third-party certification.

Honesty register

Explicit bounds for this page.

• This page is public onboarding or thank-you material, not legal advice or official government endorsement.
• No AUKUS, NATO, DAIC, DASA, Dstl, MOD, or Cyber Essentials certification is claimed unless separately evidenced.
• No kinetic-targeting, kill-order, find-fix-finish, personal-surveillance, face-recognition, or phone-location pattern is included.
• DEFONEOS-SEAL is not issued here and requires BFT quorum plus owner gate.
• Public links only. Buyer-specific sensitive data must not be pasted into this page.
• Generated 2026-07-11T08:07:40Z. File slug defoneos-onboarding.