Pilot (2–4 weeks)

Scope

• 15–40 micro-nodes on your topics (or use our EPC starter pack).
• Cohort 20–50 people (interns/juniors or mixed).
• Route design: forward-only branching with 2–4 options per step, built-in reinforcement loops.
• Measurement: live KPI dashboard; event-level telemetry for every action.

KPIs we contract on

• Retention/Completion — % who finish the micro-route.
• Post-training Accuracy — decision quality on control micro-cases.
• Orientation Gain — ability to navigate domains/experts/topics.
• Time-to-Productivity — weeks to first independent tasks in the target project.
  (Exact targets agreed in the SOW.)

Deliverables

• Weekly snapshot (KPI trends + content adjustments).
• Final report (KPI results, insights, next-route recommendations).
• Exportables: CSV/XLSX event log, KPI/coverage tables.
• Certificates: QR-verifiable PDFs (KPI, coverage, skills vector summary).

Visual to add: One funnel “Pilot → KPI gates hit → Rollout”.

---

Typical risks — and how we close them

“Too much content, too few resources.”

• Mitigation: ready-to-use node templates (context, 4–6 chat turns, 1 micro-action, feedback); no-code authoring; we co-author priority nodes.

“People won’t finish.”

• Mitigation: Rhythm-Through-Progress™ (visible micro-wins), Focus-by-Micro-Choice™ (2–4 good options often), 3-node reinforcement loops, and Momentum Pulse™ nudges.

“HR won’t trust the certificate.”

• Mitigation: Outcome Traceability & VC™ — full event log → competency vector p(topic) → QR/hash-verifiable certificate; audit-ready evidence.

Visual to add: Three small cards “Content load / Completion / Trust” with the matching mitigation tags.

---

Engagement models

• Paid Pilot (fixed fee) — 2–4 weeks, KPI contract, final report, certificates.
• SaaS license — per-seat or per-module after a successful pilot.
• White-label — your brand, your SSO/LMS integration.
• Co-publishing domain tracks — we package your expertise as reusable domain packs.

---

What we need from you (fast start checklist)

• Topics & outcomes: 5–7 priority topics + 3–5 typical cases.
• Subject experts: 1–2 reviewers for accuracy/sign-off.
• Audience & success definition: roles, cohort size, KPI targets.
• Logistics: access window, comms channel, consent for certificates.
• (Optional) Branding: logo, color palette, certificate signatories.

Visual to add: Checkbox “Pilot Readiness” list.

---

Data, privacy & security (short version)

• PII-light by default; event telemetry stored under anonymized IDs.
• Consent-based certificates (QR/hash) for individuals.
• Exports (CSV/XLSX) for HR/analytics; LRS integration later if needed.

---

Governance & cadence

• Kickoff (60 min): KPI targets + content shortlist.
• Build (days 1–7): 15–40 nodes authored/ingested; route wiring; QA.
• Run (weeks 2–4): cohort live; weekly 30-min reviews.
• Readout (60 min): KPI results, scaling plan, licensing options.

---

Why this pilot pays off

• Route-first learning shows outcome shifts within weeks (not quarters).
• Event-grade evidence de-risks L&D spend and supports HR decisions.
• Reusable micro-nodes cut future content costs across domains (EPC, HSE, Ops, PM, Sales).

---

CTAs

Book a 20-min demo · Request a pilot proposal · Become a Founding Partner