Enigmatix Global
Methodology · Enigmatix GlobalBook a 30-min call →

Five phases.
Named artefacts.
Nothing hidden.

Every Enigmatix engagement runs through the same five phases — Discover, Design, Build, Run, Evolve — with written deliverables you can inspect at each one. This page is the method, in public.

Selected clients · 2010 – today
Power to LiveRBM GlobalDragonflySquiblerMOOSainsbury'sMPCX-LinkPower to LiveRBM GlobalDragonflySquiblerMOOSainsbury'sMPCX-LinkPower to LiveRBM GlobalDragonflySquiblerMOOSainsbury'sMPCX-Link
The five phases

What actually
happens, in order.

Each phase ends with written artefacts your team can read, not a verbal hand-off. If the work is worth doing, it is worth documenting.

  1. /01

    Discover

    2–4 weeks

    We understand the product, the people and the constraints before we pitch an architecture. Discovery ends with a written scope the sponsor can fund and the engineering lead can execute.

    Goals

    • Pin down the business outcome the engagement has to move.
    • Map the existing estate — systems, teams, vendor contracts, data flows.
    • Identify the top 3 risks and what would kill the project in month 3.
    • Agree a budget shape, not a fixed number — realistic cost with named tradeoffs.

    Named artefacts

    • Discovery brief (what we will build, why, and for whom)
    • Risk register with named owners and mitigations
    • Reference architecture and integration map
    • Team shape, engagement model and ramp plan
    • Indicative timeline with milestone checkpoints
  2. /02

    Design

    2–6 weeks

    Design is where we commit to the shape of the thing. We prototype the risky parts, lock the architecture, and produce UX that engineering can build without guessing.

    Goals

    • Prototype the two or three journeys that decide whether the product works.
    • Settle the architecture and tech stack with tradeoffs on record.
    • Produce design-system-level UI, not just screens.
    • Agree the non-functionals — SLOs, privacy, compliance, audit needs.

    Named artefacts

    • Working clickable prototype of the critical flows
    • Architecture decision log (ADRs) with alternatives considered
    • Design system tokens, components and Figma library
    • API contract and data model drafts
    • Non-functional spec — SLOs, RPO/RTO, compliance posture
  3. /03

    Build

    3–9 months

    Build is where the team ships, continuously. We work in two-week cadences, release behind feature flags, and keep a visible burn-down against the milestones agreed in Discover.

    Goals

    • Ship production-grade increments every sprint — no demo-only throwaway.
    • Keep the production system shippable at the end of every working day.
    • Maintain a visible product, delivery and quality dashboard for sponsors.
    • Rotate knowledge so no module has a single point of failure in the team.

    Named artefacts

    • Production deployments on a measurable release cadence
    • Automated test suite with coverage targets per module
    • CI/CD pipelines, environment parity and rollback drills
    • Sprint reviews, demo recordings and written changelogs
    • Operational runbook drafted alongside the first production release
  4. /04

    Run

    Continuous

    Run is operations: keep the service healthy, inside SLO, and out of incident. Most of our engagements include Run from day one so the team that built it also pays the pager.

    Goals

    • Meet service-level objectives agreed in Design.
    • Respond to incidents inside agreed response and resolution times.
    • Protect cost, security and data integrity against drift.
    • Keep documentation, runbooks and on-call rotations current.

    Named artefacts

    • Live SLO dashboard with error-budget burn tracking
    • Incident post-mortems with action items and owners
    • Quarterly security and cost reviews
    • Runbooks maintained alongside the code, not in a separate wiki
    • On-call rotation with written escalation paths
  5. /05

    Evolve

    Quarterly

    Software that ships is software that changes. Evolve is the quarterly loop that funds what is working, retires what is not, and keeps the engagement aligned to the business.

    Goals

    • Review outcome metrics against the Discover brief every quarter.
    • Retire unused surface area — features, services, vendors.
    • Re-scope the roadmap with evidence from production, not opinion.
    • Agree a new budget shape for the next quarter with named tradeoffs.

    Named artefacts

    • Quarterly outcome review vs the original business brief
    • Updated risk register, architecture log and roadmap
    • Tech-debt register with payback plan for the next quarter
    • Written renewal or resize recommendation from the delivery lead
Principles behind the method

Four rules that
shape every phase.

The phases are the what. These four rules are the why. Break one and the engagement drifts — quietly, then all at once.

/01

Written down or it didn't happen.

Every decision that would be painful to reverse gets an ADR. Every milestone closes with a written artefact. We favour boring documents over heroic memory.

/02

The team that builds it runs it.

Engineering owns production from the first release. On-call sits with the people closest to the code, not a separate ops tier.

/03

Re-scope on evidence, not opinion.

Quarterly reviews compare outcomes against the Discover brief. Roadmaps shift when production data says they should, not when a stakeholder asks loudly.

/04

Exit is part of entry.

Your code, cloud and docs live in your accounts from day one. A wind-down is a day-long handover, not a quarter-long extraction.

Trusted by our clients

What partners
tell us.

Most clients renew for a second engagement. The ones who don't usually hire someone from our team to run the project in-house.

We are a mental health charity and not tech minded. We needed to improve our patient registration system but wanted a company that we can relate to. Hassan took the time to meet with me and patiently went through our process to find a personalised solution for us. Hassan's team did a great job streamlining our process and connected our registration system to our patient management software. Whenever we have a glitch, they resolve this quickly. Cloudini provides a personal and efficient service and we have adopted them to be our IT provider.
Tien Kuei, CEO at Power to Live Foundation
Tien Kuei
CEO · Power to Live Foundation
I am writing to wholeheartedly recommend Cloudini as a premier bespoke software development agency. Our journey with them has been nothing short of exemplary, far exceeding our initial expectations. While many agencies can develop based on strict specifications, Cloudini demonstrated an incredible commitment to our project that was truly unparalleled.
Robert McPherson, Managing Director at RBM Global Ltd
Robert McPherson
Managing Director · RBM Global Ltd
Dragonfly has been working with the team at Cloudini for several years now on building out our web-based platform and APIs. One of their strengths is quickly building out a multi-disciplinary team to work on the development and delivery of features with different technical requirements. Their support has allowed us to accelerate our development work without building an internal team. They have also worked seamlessly with other third parties both during the acquisition of Dragonfly and development of our mobile app. Cloudini has been instrumental in bringing our ideas to life and providing guidance to help us make the best technical decisions. I would recommend getting in touch with them if you're looking for support.
Rebecca Palser, COO at Dragonfly
Rebecca Palser
COO · Dragonfly
Methodology · Frequently asked

How engagements actually run.

  • A typical product engagement runs 4–12 months from Discover to first production release, then continues in Run and Evolve. Discovery takes 2–4 weeks, Design 2–6 weeks, and Build 3–9 months depending on scope. Simple integrations can finish in 6–10 weeks. Regulated or multi-system programmes can run 12+ months with staged releases.

Still wondering something?Book a 30-min call
Start here

Let's build
from here.

Thirty minutes with an actual engineer. No sales, no drip campaign. If we're the wrong fit we'll tell you and point you somewhere better.

Book a 30-min callinfo@enigmatixglobal.com
Response
Within one working day
Minimum
Two-week discovery