Skip to content

How we work

A clear scope, a fixed price, then ongoing support

Three stages, each with a defined output and a defined commercial model. You always know what you are paying for and what comes next.

  1. 01Short and low-commitment

    Discovery

    We meet the people who do the work, map the process as it really runs and look at the systems involved. You leave with a written scope: what the system will do, what it will not, where a person approves, and how success is measured.

    What you get

    • Process map
    • Written scope and limits
    • Fixed price for the build
    • Estimate of monthly running costs
  2. 02Fixed price, paid by milestone

    Fixed-scope build

    We build what the scope describes for the price agreed. You see working software in short iterations, tested against real examples from your business, and nothing goes live until it passes the checks we agreed.

    What you get

    • Working system with integrations
    • Tests built from your own cases
    • Gradual rollout
    • Documentation and team training
  3. 03Monthly, cancel with notice

    Support retainer

    After launch we monitor the system, fix issues, and update it as your policies, prices and software change. The retainer also covers small improvements, so the system keeps pace with the business.

    What you get

    • Monitoring and issue fixes
    • Updates when your process changes
    • Monthly performance summary
    • Agreed response times

Why this way

Small first, then grow

We would rather launch one narrow system that works than promise a platform. A first project is scoped to prove value quickly; the next one builds on what you learned.

FAQ

Commercial questions

What does it cost?

It depends on how many systems are involved, how risky the actions are and how varied the inputs are. After discovery you get a fixed price for the build and an estimate of running costs, in writing, before you commit to anything further.

Who owns the code?

You do. On final payment the code, configuration and documentation are yours, and you are free to run or extend them with any team.

What if our needs change during the build?

Small changes are absorbed. Larger ones are written up as a change with its own price and time, so the original scope and budget stay clear.

Do we have to take the retainer?

No. We recommend it for systems that customers or finance depend on, but you can also take a handover and run it yourselves.

Will you sign an NDA?

Yes. We are happy to work under an NDA and within the access rules you set.

Have a process that should run itself?

Tell us what your team spends too much time on. We will come back with a clear view of what can be automated and how we would build it.