S-07 — Starter Packs for Stakeholders
Scope: What a first deployment buys and starts with — the Day 1 entry in plain language, and how the four starter bundles differ for a non-technical buyer (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back; source: datasets/lookups/lookup.finmon.cohort_billing.v1.json; source: docs/commercialization/playbooks/dictionary.v1.json) Status: as of 2026-11-09 Blueprint sources: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; Playbook Registry — What You Can Run, Who Runs It, What You Get Back; datasets/lookups/lookup.finmon.cohort_billing.v1.json; datasets/lookups/lookup.finmon.revenue_split_profile.v1.json; docs/commercialization/playbooks/dictionary.v1.json
What this means for you
A starter pack is not a replacement system. It plugs into what you already use — WhatsApp, your spreadsheet imports, and mobile money — and returns an AI operations desk that tickets, bills, and proves, without replacing anything (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Day 1 means two desks working together: a maintenance desk that takes a resident's request and proves the fix, and a financial desk that tracks dues and collects cleanly (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). You start with a measured pilot, not a long contract. The first 14 days are onboarding, then a limited live run, and only then a decision to convert (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). No pilot promises a savings number. Success is measured against a baseline you agree up front, and the claims pilot price stays unpublished until that baseline is measured (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back; source: docs/commercialization/playbooks/dictionary.v1.json).
Details
What "Day 1" includes (plain language)
The entry in one sentence is: an AI operations desk that tickets, bills, and proves, without replacing anything (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
- AI Maintenance Desk. A resident sends a WhatsApp or USSD message. The desk classifies the problem (plumbing, electrical, security, facilities), takes the location, urgency, and a photo (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
- Dispatch with approval. The desk proposes the nearest certified vendor. Your manager approves in one tap. The vendor gets the task on mobile (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
- Verification before money moves. The vendor uploads a photo with GPS. An inspector may sign. Only then is the milestone sealed with a proof receipt (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
- Escrow held until proof. The payment stays in community escrow and is released only on proof (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
- AI Financial Desk. A native ledger tracks dues, fines, service charges, and vendor payables per community, with reminders and collection on a schedule, and a monthly statement plus dashboard — no spreadsheet reconciliation (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
- Talk to residents in their language. Every step is narrated in plain English, Swahili, or French with no technical jargon on resident surfaces, for example: "Water leak at Block C, assigned to Juma (certified plumber, 0.8 km), ETA 2h, escrow KES 3,500 locked" (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
- Non-negotiables already on. Tenant separation, role-based permissions, an audit log, presence, emergency break-glass with dual approval, offline tolerance on mobile, and English/Swahili/French narration are part of the starter pack, not add-ons (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
The four starter bundles — how they differ
The billing allowlist names exactly four offer packages a cohort may be pinned to (source: datasets/lookups/lookup.finmon.cohort_billing.v1.json). In plain rows:
| Bundle (offer package) | Who it is for | What is different |
|---|---|---|
Community Starter (offer_package.jamii.starter.v1) | A single estate or housing community buying a first deployment (source: docs/commercialization/playbooks/dictionary.v1.json) | The core Day 1: work orders, light dues, announcements, gate passes, light governance, and an assistant that answers from community documents (source: docs/commercialization/playbooks/dictionary.v1.json). Emergency command, full orchestration, clinical features, and multi-estate federation are explicitly out of this bundle (source: docs/commercialization/playbooks/dictionary.v1.json). |
Estate Safe (offer_package.bundle.estate_safe.v1) | An estate that wants the Community Starter plus community safety as one purchase (source: docs/commercialization/playbooks/dictionary.v1.json) | One bundle = Community Starter plus the ICE Community Guard, covered by one subscription (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). It adds the safety request flow to the same work-order flow; it does not start a second system (source: docs/commercialization/playbooks/dictionary.v1.json). |
Materra AMCOS pilot (offer_package.materra.amcos.pilot.v1) | A farming cooperative (AMCOS) running a field pilot (source: docs/commercialization/playbooks/dictionary.v1.json) | A different job entirely: farmer registry, field forms, certified bag tracking, market prices, and a cooperative organization — not estate maintenance (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Usage is metered per certified bag, and revenue follows the Materra pilot split profile (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). |
Claims Orchestration pilot (offer_package.claims.orchestration.pilot.v1) | An insurer, health scheme, or government desk handling claims (source: docs/commercialization/playbooks/dictionary.v1.json) | An umbrella offer bundling motor-claim handling with provider panels, service-level times, approval bands, intake forms, and lifelong vehicle or building identity (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Motor ships first as a practice pack; medical, home, and government packs remain spec-only until their dependencies land (source: docs/commercialization/playbooks/dictionary.v1.json). Pilot price is unpublished until a baseline is measured, and no savings figure is promised (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). |
Two things stay the same across all four: money movement stays gated until finance keys, a human approver, and the payments ledger are ready, and every pack runs first as a zero-write practice check and cannot declare itself live (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
The pilot commitment (14-day framing)
The pilot is sold as a short, low-risk entry: the first 14 days are white-glove onboarding — tenant set up, WhatsApp number live, historical tickets and dues imported from CSV, staff trained — exiting when one ticket runs end to end in production (report to dispatch to escrow to receipt) (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). After that comes a limited live run on one block or one service category, then a joint value audit before any 12-month commitment (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). The starter-pack pilot fee documented for this entry is a $500–$1,000 commitment, credited in full on conversion (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). No full deployment price or savings figure is stated in these sources. Claims pilot pricing is explicitly unpublished until baseline measurement, and no savings promise is made at sale (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back; source: docs/commercialization/playbooks/dictionary.v1.json).
What your team owns vs what the platform owns
Your team owns: approving dispatches and close-outs in one tap, signing verification, owning the success criteria agreed before the pilot, confirming scope when a request must be refused, and providing the historical CSV and staff time during onboarding (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). The platform owns: intake classification and location extraction, vendor proposal from the certified graph, the ledger and collection schedule, the escrow hold-until-proof rule, proof receipts and audit trail, and multi-language narration (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). The platform never owns: approving its own work. The resolver cannot approve its own close, missing evidence is refused, and the board approves what the AI proposes (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Open items / gaps
- Headless wiring for some bundle components (for example exact notification receipt shape and exact audit-file schema) is UNKNOWN in the cited set — do not treat the plain description as an API contract (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).
- Emergency-call location formatting and trusted timestamping appear only when a public-safety answering point or timestamp-authority customer arrives (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
- Live money movement for Estate Safe, Materra AMCOS, and the claims pilot is gated until finance keys, a human approver, and the payments ledger are ready (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
- Full deployment pricing beyond the pilot commitment above is UNKNOWN in this read set and is not stated here (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: docs/commercialization/playbooks/dictionary.v1.json).