How we work

From the first conversation to a system in operation.

How an engagement runs, what drives the price, and where to start, whether you have one stubborn process or several across departments.

Engineered for operation, not just demonstration.

A demonstration only has to work once. A business system has to keep working on a busy Monday, with bad data, a missing person and a supplier whose system is down. This is the method we use to get there.

  1. Discovery

    Agree what the problem is, and what "working" will mean, before anything is built.

    • Understand the business problem.
    • Map the existing workflows, including the exceptions.
    • Identify the stakeholders and who signs off.
    • Document the requirements.
    • Identify dependencies and constraints.
    • Define measurable acceptance criteria.
  2. Architecture

    Decide how it will be built, and how it will fail safely, on paper first.

    • Select technologies that fit the problem and the client's existing systems.
    • Define integrations and data flows.
    • Establish access-control requirements.
    • Identify security and privacy considerations.
    • Define error handling and escalation to people.
    • Plan monitoring and recovery.
  3. Pilot

    Prove it on a bounded scope with real work before it touches everything.

    • Implement a bounded scope.
    • Test normal and exceptional scenarios.
    • Validate the business rules with the people who use them.
    • Measure performance against the agreed criteria.
    • Gather stakeholder feedback.
    • Document outstanding issues.
  4. Deployment

    Release on purpose, with the checks and documents written down.

    • Follow an agreed release process.
    • Verify configuration.
    • Validate every integration in the live environment.
    • Document operating procedures.
    • Train the people who will use it.
    • Obtain formal acceptance.
  5. Support

    Agree who looks after it, and what happens when something goes wrong.

    • Define support responsibilities.
    • Establish incident escalation.
    • Document backup and recovery arrangements.
    • Agree maintenance responsibilities.
    • Define monitoring and reporting.
    • Document termination and handover arrangements.

This is how we run engagements. Not every project needs every stage at full depth, and work that stops at a tested prototype has not been through deployment and support. Service levels, response times, recovery objectives and support hours are not promised here. They are defined for each project in its contract.

How a project moves

Eight steps from an initial discussion to an operational system. You see a written scope and price before any build starts.

  1. DiscoveryA conversation, then a closer look at how the work moves today.
  2. ScopeWhat is in, what is out, and what "done" means.
  3. Proposal and pricingA written proposal with phases, assumptions and price.
  4. ArchitectureThe design, the data flows and the failure modes, agreed before the build.
  5. ImplementationBuilt in increments you can see and test.
  6. Testing and acceptanceChecked against the acceptance criteria, with you.
  7. DeploymentReleased through the agreed process, with documentation.
  8. Support and handoverSupport as contracted, and a clean handover if you take it in-house.

What drives the price

There is no price list, because two projects with the same name can differ tenfold in effort. Every engagement is priced from its scope, in writing, before work starts.

Requirements
How many processes, roles and rules the system has to handle.
Integrations
How many systems it connects to, and how well documented they are.
Complexity
Exceptions, approvals and edge cases, which take more work than the normal path.
Risk
How sensitive the data is and what a failure would cost, which sets how much testing and control it needs.
Support
The support hours, response commitments and maintenance you need after go-live.

Where to start

The right first step depends on how clear the problem is and how much is at stake. We will say so if a smaller step makes more sense.

Starting pointSuitsYou get
Paid discoveryWhen the problem is clear but the solution is not.Mapped workflows, requirements, a proposed architecture and a costed plan you can take to any builder.
Bounded pilotWhen you want proof before committing to more.One process running with real users, measured against criteria agreed up front.
Phased implementationFor multi-department or multi-system work.Delivered in phases, each with its own scope, acceptance criteria and price.

Request a confidential technical briefing

For qualified projects, we can discuss implementation architecture, testing methodology, delivery controls and relevant technical evidence, within the limits of applicable confidentiality obligations.

Evidence is not available for every project, and some of it can only be described, not shown. A briefing request is a request, not a booked meeting: we reply to arrange a time.

You can ask for

  • An architecture discussion
  • A technical demonstration
  • An implementation-readiness discussion
  • An enterprise automation assessment
Request a briefing

Have one specific problem?

Not every project is a programme. Tell us what keeps landing on a person, and we will say honestly whether a system is the answer.