The business transformation method

Your business guides every stage.

Six stages, concrete deliverables and your teams involved throughout.

Your operational knowledge becomes a shared foundation for designing, verifying and improving software. AI accelerates delivery; your objectives and your teams guide the decisions.

Explore the method

The method

From understanding to measured outcomes

I immerse myself in your business, the problems you need to solve and the optimisation you are looking for. Twenty years across sales, hospitality, logistics, airport operations, credit-card back-office operations, pricing and business intelligence help me connect the human, operational, commercial and technical dimensions quickly.

The highest-return opportunities are often overlooked because they live closest to execution: in tasks repeated every day by frontline teams. A few minutes saved, one error prevented or one better-supported decision then compound at scale.

  1. Understand real work

    Documents, recorded interviews and usage recordings agreed with participants become structured observations, including JSON, linked to their sources. We make exceptions explicit, establish current lead times, volumes and errors, then identify the data to move and migration constraints.

    What you receive
    Process map, measurable objectives, source evidence and initial migration inventory.
    With your teams
    Teams demonstrate everyday work; business leaders define the outcomes they need.

  2. Build living specifications

    The planned application will question domain experts to fill gaps and surface contradictions. Every exchange will enrich the project record; requirement changes will need validation before becoming authoritative. A shared glossary and Q&A area will make decisions and documented progress accessible.

    What you receive
    Versioned specifications, glossary, approved decisions and open questions.
    With your teams
    Domain experts explain exceptions and validate rules; business leaders resolve priorities.

  3. Prototype with users

    Users try key workflows in a prototype. Their feedback tests assumptions, refines interfaces and updates specifications. We agree on the scope to build and the acceptance criteria.

    What you receive
    Validated prototype, agreed build scope and shared acceptance criteria.
    With your teams
    Future users test concrete situations and identify friction or missing steps.

  4. Build and prepare migration

    I lead architecture, code and testing with AI agents. Anonymised data preserves useful relationships and edge cases needed for verification. We refine mappings between old and new data, cleansing, migration rehearsals and the rollback plan.

    What you receive
    Tested software and a rehearsed migration approach, with checks and rollback.
    With your teams
    Data owners verify mappings and the quality of migrated data.

  5. Verify against real operations

    Depending on what the existing system supports, we replay captured operations or compare both systems in parallel, without duplicating external actions such as messages or payments. Each difference is investigated: a defect to fix or an approved business change. Domain experts validate expected outputs and behaviour.

    What you receive
    Comparison results, explained differences and business acceptance before wider access.
    With your teams
    Domain experts review differences and confirm acceptable behaviour changes.

  6. Deploy, adopt, improve

    An initial group uses the system and reports friction. We refine screens and workflows, support teams and prepare a progressive transition. Lead times, errors and usage are compared with the baseline; lessons feed into documentation and future improvements.

    What you receive
    Adoption feedback, measured outcomes and prioritised improvements.
    With your teams
    Pilot users shape everyday usage; business leaders track outcomes and decide when to expand.

Feedback can revisit any earlier stage. Documentation follows decisions, prototypes and real usage throughout the project.

I lead business discovery, architecture, development with AI agents, testing, migration and deployment. Your domain experts validate rules and results; your users shape how the software works in practice.

Planned capability · application not yet available

A workspace that asks your experts the right questions

The principle: the application will interview you to clarify how the business works. Project sources and decisions will inform targeted questions and richer specifications. This workspace is part of the proposed approach; it remains to be built.

Clarify the rules

Targeted questions, contradictions to resolve and changes submitted to domain experts for validation.

Share a common language

A shared glossary of business terms, definitions and exceptions, enriched through each exchange.

Understand progress

Q&A grounded in documented project status: decisions made, open issues and pending approvals.

Confidential programme · €80M-turnover business

A confidential ERP programme, one simple question: what must be true before we build?

For a confidential €80M-turnover business, the work begins by exposing exceptions, tacit rules and decisions that determine the architecture. The public outcome is not a screenshot: it is a method for reducing risk before production.

In progress: architecture and user-prototype validation.

The agent is not the architecture.

Agents accelerate implementation when constraints, decisions and verification already exist. Human judgement remains accountable for business trade-offs, security and quality.

Teardown my process ↘