Jijibora Competitive Positioning — Buyer's Language
Scope: What buyers in this category ask for (from the market/customer doc), which asks Jijibora already meets, which it does not, and the structural differentiators a buyer should notice. Competitor features are framed as market category capabilities — no fabricated vendor claims. Status: as of 2026-11-09 Blueprint sources: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md; docs/jijibora-gtm/04_AI_DRIVEN_INTERFACE_AND_ORCHESTRATION.md; docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md; Architecture — Design Thesis and Planes (Developer Concept Doc); Claims Plane — Processing Claims, Guarded Transitions, and Declarative Packs
What this means for you
Read this as the call you must win with a builder, not as sales copy. Your buyers pay for proof and for relief from WhatsApp chaos — your build must give them a receipt they can recompute and a ticket board that already exists in their channel.
Details (features/interfaces)
1. What buyers in this category ask for
The market thesis is narrow by design: small, self-governing communities that already have a legal entity, a budget, and 50–5,000 households that must self-organise because the city does not. Four archetypes, four buying centres: master-planned developments (100–5,000 units), retirement/independent living (50–1,000), golf/lifestyle/resort (50–500), bedroom/commuter (200–5,000). (Source: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §1.)
The buyer map and jobs to be done (ranked by willingness to pay) drive every pitch:
| # | Job asked for | Buyer / blocker | What the buyer is really asking | Source |
|---|---|---|---|---|
| 1 | "Stop the WhatsApp flood / ticket black hole" | Champion (property/community manager) — blocked by time + training | One ticket board that lives in WhatsApp/USSD, with classification, location, assignment, ETA, receipt | docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §§2, 4 |
| 2 | "Collect dues without chasing" | Treasurer/finance — blocked by spreadsheet reconciliation | Ledger + period close + M-Pesa/Stripe reminders, receipts | docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §§2, 4 |
| 3 | "Prove the money was spent right" | Economic buyer (board, developer MD, county CFO) + donor/regulator — blocked by disbursement fraud | Escrow that only releases against verified work, with an auditor-recomputable receipt | docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §§2, 4 |
| 4 | "Know before the pump fails / the road floods" | Security/ops — blocked by existing CAM/guard contracts, phone trees | Predictive/reactive orchestration: pre-cool, shelter-open, generator-start via standing orders | docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §§2, 4 |
| 5 | "Vote without a 3-hour AGM" | Board — blocked by disengagement | Digital proposals, quorums, elections that are recorded decisions | docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §4 |
| 6 | "Answer the auditor / donor in one click" | Treasurer + donor/regulator — blocked by reconciliation | One-click evidence export that survives external audit | docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §§2, 4 |
Segment tiers set the price/bandwidth contract: Community Starter (50–500 households, $99–$349/mo, manager+treasurer, light regulation), Community Pro (500–2,000, $499–$1,800/mo, board+finance, HOA bylaws), District/SEZ (2,000+, $3,500–$25,000/mo, C-suite + county procurement, heavy regulation), Care & Compliance (retirement + health, $750–$3,500/mo + health add-on, heavy PHI regulation). (Source: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §3.)
2. Which of those we already meet
| Buyer ask | Met today | Evidence |
|---|---|---|
| Ticket black hole → tracked, assigned, receipts | Yes — claim desk + community starter pack over WhatsApp/SMS/email | lookup.jijibora.community.starter.v1.json declares ticket/due/announcement/visitor_pass types, channels whatsapp/sms/email, actions dispatch/complete; Akili takes tickets, classifies, assigns, ETA + receipt. (Source: datasets/lookups/lookup.jijibora.community.starter.v1.json; docs/jijibora-gtm/04_AI_DRIVEN_INTERFACE_AND_ORCHESTRATION.md §2.) |
| Prove spend → escrow + PoCE | Yes — PoCE verification layer + guarded finalisation + evidence export | Verification machine: declared path spec → per-request session → append-only stage steps → hash-chained receipt pinned to spec id/version, chain head, root hash. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) §4.) |
| One ID per thing (kill the five-language problem) | Yes — unified claims + truth fabric dual-map | Canonical claim as universal fact primitive typed by CNS; graph linked with agreeing typing. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) §§2–3.) |
| Buildings react (phone tree → seconds) | Yes (declaratively) — standing orders + geo/compliance gates + solver | so.flood.shelter, so.heat.precool, so.blackout.generator, so.occupancy.night_setback seeded as lookups; Kestra standing_order_arm; solver 3–5 sec chain + checker + MUS repair. (Source: datasets/lookups/lookup.jijibora.property.standing_orders.v1.json; docs/jijibora-gtm/04_AI_DRIVEN_INTERFACE_AND_ORCHESTRATION.md §3.) |
| Fair local sourcing | Yes — sourcing mesh as composed pattern | lookup.jijibora.community.sourcing.v1.json (requirement/offer/binding; solve/bind/complete) + solver bridge with outbox anchor. (Source: datasets/lookups/lookup.jijibora.community.sourcing.v1.json; Data Fabric — Message Bus and Engine Interfaces (Developer Concept Doc) §5.) |
| Channel-first (no new app on Day 1) | Yes — headless REST/GraphQL/WebSocket/WhatsApp/USSD consumers | Logic lives in headless engines; surfaces are optional consumers. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) §0.) |
| Headless ERP / WhatsApp plug-in (not $10M rip-and-replace) | Yes (by architecture) — capability catalogue + Camel gateway | Integration plane is stateless translation only (no authority); capability catalogue resolves CNS-typed capability → route, fail-closed. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) §6; Data Fabric — Message Bus and Engine Interfaces (Developer Concept Doc) §6.) |
3. Which of those we do NOT yet meet (thin coverage — explicit)
| Buyer ask | Gap status | What is missing |
|---|---|---|
| Live billing / settlement from the claims plane | Not claimed. VAS + panel eligibility answer only; monetisation ceremony is separate. | No live billing or live settlement from this plane. (Source: Claims Plane — Processing Claims, Guarded Transitions, and Declarative Packs Open items.) |
| Panel coverage for government / community lines | Thin. Seeded panel roles cover insurance lines only; government + community have no panel mesh. | Motor (broker/adjuster/garage/reinsurer), property (adjuster/garage/reinsurer), medical (adjuster/reinsurer) only. (Source: Claims Plane — Processing Claims, Guarded Transitions, and Declarative Packs §4.) |
| Multi-signer ceremonies beyond code | Thin. Quorum open refuses below-threshold or when quorum plane unavailable; resolution is zero-write. | Live gate unmet on quorum/panel/SLA timeout reads. (Source: Claims Plane — Processing Claims, Guarded Transitions, and Declarative Packs §§2, 5.) |
| Customer-held seal / certification / signing root | Not enforced. | Described as future; today root is platform-recomputable. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) Gaps and honesty limits.) |
| Ceiling digest in receipt; approved-digest recomputation | Not yet. | Ceiling digest not yet carried in PoCE receipt; seeder recomputation pending. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) Gaps and honesty limits.) |
| Autonomous AI (dispatch / escrow release) and care-AI clinical advice | Never (by doctrine). | AI proposes; named humans decide. Care-AI clinical advice gated by BAA; autonomous dispatch/escrow-release deferred forever. (Source: docs/jijibora-gtm/04_AI_DRIVEN_INTERFACE_AND_ORCHESTRATION.md §§1, 5.) |
| US federal/defense, EU filing, US PHI custody | Out of market. | No FedRAMP High / FIPS crypto; EU operator files (Jijibora supplies pack); US covered-entity PHI is consultation-only (no BAA). (Source: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §6.) |
| External-gate integrations (identity/content/sanctions/quota/customs) | All unwired by design. | Verdict router answers REFUSE until real endpoints land. (Source: Apache Camel Compliance Gateway (compliance-camel, :8181) §6.) |
| Compliance gateway targets for EU CBAM / TRA TANCIS / TRACES NT | Echo placeholders. | Route YAMLs currently POST to httpbin.org/post; portal URLs are prose, not literal routed URLs. (Source: Apache Camel Compliance Gateway (compliance-camel, :8181) §6.) |
4. Structural differentiators — market category capabilities
The market doc names four competitor classes. Below maps each class to the category capability buyers expect, and the Jijibora structural difference. No invented vendor claims.
| Competitor class (as named in market doc) | Market category capability buyers expect | Jijibora structural difference |
|---|---|---|
| Legacy HOA software (AppFolio, Buildium, QuickBooks + spreadsheets) | Ticketing, ledger, owner comms | Inheritance + orchestration, not just records. Rules compose, ceilings enforce (a ward can tighten but never loosen), buildings react via standing orders. (Source: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §5; docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md §2.) |
| Smart-city suites (Itron, Black & Veatch) | Sensor/command integration at city scale | Community-scale + headless. Not a $10M rip-and-replace; plugs into WhatsApp/ERP via capability catalogue and stateless Camel gateway. (Source: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §5; Architecture — Design Thesis and Planes (Developer Concept Doc) §6.) |
| GRC vendors (Vanta, Drata, ServiceNow GRC) | Evidence collection for SOC 2 / audit | Runtime refusal, not evidence collection. Jijibora refuses a widening child at compose time and logs federation decisions. (Source: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §5.) |
| DIY WhatsApp + Excel (incumbent) | Fast coordination | Proof. Every governed action is a hash-chained receipt an auditor can recompute without trusting Jijibora. (Source: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §5.) |
Three differentiators you should notice:
- Provable receipts instead of screenshots. The receipt is hash-chained, pinned to
path-spec id + version + chain head + root hash, bound to exactly one result. Any verifier can recompute it. This is the audit product, not a marketing claim — Vanta-class categories collect evidence; a PoCE receipt is the evidence. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) §4; docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §2.) - Configuration as vertical, not code as vertical. A new community type is a pack declaration (claim types, panel/threshold/SLA values, scenario + lookup bindings, event subjects) over the same guarded transition, quorum, evidence, and external-assertion sequence. The runner never branches on claim type. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) §9; Claims Plane — Processing Claims, Guarded Transitions, and Declarative Packs Facts.)
- Soft-honest audits, and the spine underneath. Soft apply validates references, returns
live_gate_met: false, zero writes, and fails closed on missing values; readiness probes real dependencies, metrics are computed from real rows, and the event spine (canonical envelope → transactional outbox → relay → subscribed consumer → consumed receipt) guarantees that "done" means durable before it means published. (Source: Claims Plane — Processing Claims, Guarded Transitions, and Declarative Packs §§2, 6; Data Fabric — Message Bus and Engine Interfaces (Developer Concept Doc) §2.)
Moat sentence (verbatim from market doc, do not paraphrase when quoting to buyers): "AppFolio stores your tickets. Jijibora makes your rules executable, your escrow provable, and your buildings reactive — and it does it headlessly, in the channel your residents already use." (Source: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §5.)
Open items / gaps
- Orchestration facade remains proposed ergonomics over existing engines rather than shipped code. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) Gaps.)
- Six-stage promotion lifecycle (draft → live → retired) has dual control documented but no single running workflow for every fragment. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) Gaps.)
- Break-glass elevation does not yet open proof or file corrective action. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) Gaps.)
- Enterprise messaging, commercial operations, notarisation, trade, lifecycle mesh, and parts of external engines remain gaps beyond Done boundary. (Source: Architecture — Design Thesis and Planes (Developer Concept Doc) Gaps.)
- All competitor positioning above uses the market doc's class labels only; no feature-level vendor claims are made. (Source: docs/jijibora-gtm/01_MARKET_AND_CUSTOMER.md §5.)