Your enterprise. Your evidence.
Begin with a bounded outcome. Capture capabilities, workflows, roles, applications, data, policies and measures using stable IDs and an evidence register.
Get the blank profile kit ↓DISCOVERY STUDIO · PROPOSED PRODUCT
Give your enterprise a shared context.
Bring structured enterprise knowledge and approved resources together. Shape a reviewed contextual model that connects business strategy, people, systems, evidence and authority.
Start today with the profile kit. Download eight blank CSV templates for a human-led discovery engagement. The connected, AI-assisted Studio described below is a proposed roadmap, not an operational software service.
A reviewed contextual model.
A proposed future Studio would combine approved source material with structured records, keeping provenance, disagreements and unknowns visible for human review.
Explore the fictional model →Readiness into strategy.
Use accepted context to examine constraints, responsible AI readiness and delivery options. Retain differentiating capabilities and use the existing stack where it fits.
Explore the health check →From enterprise profile to an accountable strategy
- 01Agree outcome & boundary
- 02Profile the enterprise
- 03Approve resources
- 04Extract with provenance
- 05Review semantic context
- 06Assess readiness
- 07Prioritise strategy
Structured records provide explicit identifiers and relationships. Approved policies, architecture documents and interview records add context that a spreadsheet cannot express alone. In the proposed design, bounded AI assistance would suggest entities, relationships, questions and summaries with source references. Named owners would resolve conflicts and accept the resulting CAE contextual and semantic model before it informs a readiness profile or transition plan. CAE is our proposed architectural framework; this is not an industry certification.
The intended result is a reusable view of meaning, dependencies and decision rights, alongside a prioritised strategy for separately authorised delivery. Lower future transformation effort is a hypothesis to measure against a baseline, not a guaranteed saving.
Download the enterprise profile kit
The files contain column headers only. They collect no information and connect to no system. Work within your organisation’s approved environment; agree the handling basis before sharing completed files. Start with the completion and reference instructions.
| Blank template | What it connects |
|---|---|
| Capabilities CSV | Business capability, parent capability, owner and differentiating role. |
| Processes CSV | Workflows to capabilities, applications, inputs, outputs and policies. |
| Roles CSV | Responsibility, approval scope and delegation by role. |
| Applications CSV | Legacy and modern systems, ownership, lifecycle and interfaces. |
| Data CSV | Information ownership, classification, purpose and system of record. |
| Policies CSV | Versioned requirements, applicability and approval roles. |
| KPIs CSV | Definitions, baseline, target, measurement period and evidence status. |
| Evidence CSV | Approved source references, provenance, classification and review status. |
Use stable IDs across files: owners reference the roles table; source references point to the evidence register; process relationships join capabilities, applications, data and policy records. A reference identifies evidence, not permission to retrieve it. Empty, disputed and unknown values remain visible. Completing these templates does not produce an automated score or certify readiness.
Bounded agents. Explicit controls. Human decisions.
| Proposed responsibility | Appropriate boundary |
|---|---|
| Intake assistant | Ask scoped questions and draft a profile; people confirm material facts. |
| Evidence analyst | Summarise permitted resources and cite sources; retrieved text remains untrusted data. |
| Context modeller | Suggest entities and relationships; domain owners accept meaning and resolve disputes. |
| Readiness and strategy assistant | Surface gaps and compare options against accepted context; a sponsor approves priorities and investment. |
| Deterministic validation | Enforce schema, unique IDs, reference integrity, source access, tenant boundaries and configured limits. These cannot rely on a model’s judgement. |
| Permission and execution gate | Check caller identity, scope and approvals before any connector or action. A model cannot grant itself authority. |
| Usage and commercial controls | Attribute operations to the engagement; enforce agreed limits and record measured usage. Pricing follows an agreed scope, never an AI-generated approval. |
A practical first software increment
The proposed first MVP is an authenticated, isolated engagement workspace with validated CSV intake, an approved evidence register, bounded extraction, a review queue and versioned export. Success would require verified cross-file integrity, source-linked claims, useful review and recovery, and a measurable time-to-reviewed-context baseline. Further connectors and execution agents follow separate design and authorisation.
None of that software workflow is implemented in this release. There is no upload, customer sign-in, tenant workspace, source connector, AI extraction, automated pricing or saved assessment. Downloads and fictional visualisations are available; discovery services, deliverables, availability, duration and pricing are to be agreed. See the capability status and sources and limitations.
Bring one business question. We can discuss an enterprise profile, the evidence you already hold and a sensible first discovery boundary. Discuss your discovery scope →
YOUR ENTERPRISE. YOUR NEXT CHAPTER.
Turn complexity into
a clear next move.
Bring a business question. We can discuss a discovery scope and the decisions it should support.
Start a discovery conversation