Readiness review
Find out which track fits your project before anyone quotes a price.
Why a readiness review comes first
Rather than call a project “not ready”, a Principal Architect checks it against six objective engineering criteria, the Definition of Ready, in a free 48-hour readiness review.
The result decides how the work starts. A scope-ready project receives a binding proposal, an idea without a specification goes through the Blueprint Studio first, and a live system that needs rescue or integration gets a diagnostic before anyone fixes a price.
Check your project
Answer one question per dimension, then one on any live system. The check suggests a track and carries your answers into the request form, so the review starts from them.
| Readiness dimension | Ready for Track A | Points to Track B |
|---|---|---|
| Functional scope and user journeys | User roles, workflows, business rules and edge cases are documented in a requirements document or an RFP. | A high-level goal only, such as a custom CRM, a citizen portal or a super-app, without screen-level flows. |
| Technology stack and hosting | The target cloud or on-premises environment, the database architecture and the runtime stack are selected and validated. | Still deciding between cloud and on-premises, building and buying (Odoo or SAP against custom), or which language model to use. |
| Integration boundaries | Every third-party API, ERP module (SAP, Oracle), bank rail (ISO 20022) and POS endpoint is inventoried. | Legacy systems exist, but their APIs, data schemas or middleware needs have not been audited. |
| Data and AI readiness | Data sources, schemas, volumes and access-control rules are mapped. | Unstructured documents or siloed databases need a data quality, lineage and AI-readiness audit first. |
| Security and regulatory requirements | The mandates that apply (ZATCA, PINT-AE, EU AI Act, DORA, PDPL, post-quantum cryptography) and the data-residency rules are specified. | Cross-border data residency, encryption standards or national compliance clearance are still unclear. |
| Acceptance and SLA criteria | Acceptance testing gates, concurrency targets (transactions per second and latency) and uptime SLAs are defined. | No measurable definition of done, target concurrency or post-launch operational ownership yet. |
Ready for Track A
- Functional scope and user journeys
- User roles, workflows, business rules and edge cases are documented in a requirements document or an RFP.
- Technology stack and hosting
- The target cloud or on-premises environment, the database architecture and the runtime stack are selected and validated.
- Integration boundaries
- Every third-party API, ERP module (SAP, Oracle), bank rail (ISO 20022) and POS endpoint is inventoried.
- Data and AI readiness
- Data sources, schemas, volumes and access-control rules are mapped.
- Security and regulatory requirements
- The mandates that apply (ZATCA, PINT-AE, EU AI Act, DORA, PDPL, post-quantum cryptography) and the data-residency rules are specified.
- Acceptance and SLA criteria
- Acceptance testing gates, concurrency targets (transactions per second and latency) and uptime SLAs are defined.
Points to Track B
- Functional scope and user journeys
- A high-level goal only, such as a custom CRM, a citizen portal or a super-app, without screen-level flows.
- Technology stack and hosting
- Still deciding between cloud and on-premises, building and buying (Odoo or SAP against custom), or which language model to use.
- Integration boundaries
- Legacy systems exist, but their APIs, data schemas or middleware needs have not been audited.
- Data and AI readiness
- Unstructured documents or siloed databases need a data quality, lineage and AI-readiness audit first.
- Security and regulatory requirements
- Cross-border data residency, encryption standards or national compliance clearance are still unclear.
- Acceptance and SLA criteria
- No measurable definition of done, target concurrency or post-launch operational ownership yet.
Questions and answers
Is the self-check's suggestion binding?
No. It is a starting point for the conversation. A Principal Architect confirms the track in the free 48-hour readiness review, after going through your documents with you.
What does the readiness review cost?
Nothing. The review, like the free 30-minute online pre-consulting session before it, is free. A fee applies only to a Blueprint Studio or diagnostic engagement: fixed, and quoted in the proposal.
What counts as a live system?
A system already in use that is failing, undocumented or needs integration: for example, a platform a previous vendor left half-finished, or an ERP that must connect to e-invoicing or ISO 20022 payment messages.
What should we prepare for the review?
Whatever you have: an RFP or a specification, architecture diagrams, the list of systems to integrate, the regulations that apply and any acceptance criteria. Gaps are not a problem; they point to the right track.
Start with a conversation, not a contract.
Tell us what you need to build, connect or secure. An architect goes through it with you, then recommends where to start.
What happens next
Agreeing a time
Our team emails you to agree a time for the session.
Pre-consulting session
A free 30-minute online pre-consulting session: we go through your goals, systems and constraints.
Readiness review
In a free 48-hour readiness review, a Principal Architect checks your project against the 6-point Definition of Ready and recommends the track that fits.
Choosing the track
Scope-ready projects receive a binding proposal within 3–5 business days. Concept-stage projects start in the Blueprint Studio. A live system that is failing, undocumented or needs integration starts with a diagnostic of 1–2 weeks. The Blueprint Studio and the diagnostic each have a fixed fee, quoted in the proposal.