Battle-test applied AI in your own operations before you ship it to a customer.
Customer Zero is the enterprise operating discipline of deploying applied intelligence, governed data platforms, and agent workflows directly into live core operations before external market rollout. Internal teams act as the first, most demanding customer — the test surface that exposes every organisational failure mode a model cannot reach.
Why internal-first
Most enterprise GenAI programs report zero measurable return. The failure is rarely the model — it is the organisational system around the model. Incentives decide adoption before capability does. People embrace what makes them look capable, hide what makes them feel replaceable, and rarely volunteer the saving that costs their own team.
Synthetic test environments do not surface this. They surface whether the model produces the right tokens. The harder question — whether the workflow around the model produces the right outcome, on real data, with real permissions, for real accountability — only an internal production deployment can answer.
The three stages
Each stage produces an artefact the next stage consumes, and each is auditable in isolation.
01 / Integrate
Foundational Data Governance
Connect systems of record, isolate credentials in Google Secret Manager, and select verified business entities. The artefact is a catalogue of source instances, each with a credential pointer and an active-subscription grant, never a plaintext secret.
02 / Distribute
Internal Production Stress-Testing
Scope active instance access, enforce append-only audit trails, and run real team workflows in live operations against the governed platform. The artefact is a stress-tested grant envelope — what the audit log shows worked in practice, not what a design doc said would work.
03 / Serve
Enterprise Market Rollout
Connect AI clients (Claude, ChatGPT, Gemini Enterprise) to the governed Snowflake MCP endpoint with zero data leakage. The artefact is a customer deliverable: a per-instance, per-client grant envelope that customers can audit, rotate, and revoke without coordinating with the vendor.
How the framework becomes the platform
Customer Zero the methodology is what IKMJ (Ikigai & Majime Pty Ltd) applies to its own operations and to client engagements. Customer Zero the platform is the productised version: the same catalogue, the same instance-scoped grants, the same append-only audit trail, exposed through a governed Snowflake Model Context Protocol (MCP) endpoint that any supported AI client can query.
Stages 01–02 produce the platform's internal operational substrate (IKMJ's own instance catalogue, its own grant envelopes, its own audit log). Stage 03 is the customer-facing surface: the MCP endpoint plus the per-tenant controls the customer's own operators use to grant, scope, rotate, and revoke.
The platform and the methodology are deliberately the same thing. A customer buying Stage 03 is buying the same controls IKMJ uses internally; a customer buying Stage 01 understands the controls because they are the ones they would have implemented anyway.
Who runs it
Customer Zero is built and operated by IKMJ (Ikigai & Majime Pty Ltd), an active Australian private company The framework writeup, including the team behind it, lives on the parent site.