Skip to content

One part at a time. Nothing switched off until the new part works.

Replacing the software a business runs on sounds risky because it usually is. This is how we take the risk out of it, stage by stage, and what we'll ask of you along the way.

0minute first call, with the people who'd build it
0system map, scope and fixed price per stage
0 wksto the first part in daily useTypical
0%of the code, data and IP handed over
  1. Within a business day

    01You tell us what you run

    A short note is enough: what the business does, which tools you pay for, and where the hours go. A specialist who has read it replies.

    From you
    Ten minutes and a rough list of your tools.
    You walk away with
    A reply from a person, and a time to talk.
  2. Thirty minutes

    02Discovery call

    We go through a normal week in your business: where work comes in, who touches it, which systems it passes through and where it gets copied by hand.

    From you
    Whoever knows how the place actually runs. Often that's not the owner.
    You walk away with
    A straight answer on whether custom software makes sense for you, even if it's no.
  3. Before anything is built

    03The system map

    A plan of the system: every part, what it replaces, what it connects to, and the order we'd build it in. Each stage has a scope, a timeline and a fixed price.

    From you
    Exports or screenshots of the tools you use now, and an hour or two with the people who use them.
    You walk away with
    The map itself. It's yours to keep whether or not you build with us.
  4. A few weeks

    04The first part goes live

    We start with the part costing you the most hours. Your team uses it on real work while the old tools keep running alongside it, so nothing stops if something needs changing.

    From you
    An hour a week from someone in operations, and a few staff willing to try it early.
    You walk away with
    Working software in daily use, with your history moved across from the old tool.
  5. Part by part

    05Move across and switch off

    Each new part replaces another tool. Once the team has stopped opening the old one, you cancel that subscription. The system grows only as fast as each part proves itself.

    From you
    Decisions on what comes next, informed by what the last part changed.
    You walk away with
    Fewer logins, fewer subscriptions, one record of every job, customer and dollar.
  6. From day one

    06You own it

    The code lives in your repository and runs in your cloud account. It's documented so another developer could pick it up. We keep improving it with you for as long as it's useful.

    From you
    Nothing more than you'd give any long-term supplier.
    You walk away with
    The software, its source code and your data, as a business asset.

Ten weeks from the brief to handover.

What the move looks like. Tools go as parts arrive.

Nothing is switched off until the part replacing it has been in daily use. The old stack shrinks month by month instead of in one risky weekend.

02468StartMonth 3Month 6Month 9Month 12Tools still runningParts of your system live
Month 2 · First part liveMonth 3 · Two subscriptions cancelledMonth 10 · Fifth part liveIllustrative shape. Accounting and payroll usually stay.

What owners worry about. And what we do about it.

“We switch off the old system and the new one isn't ready.”

Nothing gets switched off until your team has stopped using it. The old and new run side by side first.

“The team won't use it.”

It's shaped by the people who do the work, and they test each part on real jobs before it replaces anything.

“The cost keeps growing.”

Every stage is scoped and priced before it starts. You decide whether to start the next one.

“We end up locked in to Hypex.”

The code, the data and the cloud account are in your name, and the system is documented for whoever works on it next.

“We lose years of history.”

Customers, jobs and documents come across from your current tools as part of each stage, checked against the originals.

“It won't be as secure as a big product.”

It runs in your own cloud account, with sign-ins and permissions by role. How it is run and governed is set out in one place.Security and governance

Ways to engage. Pick the one that fits how you buy.

A staged build

After a discovery call we produce a system map. Each stage in it has a scope, a timeline and a fixed price, and you decide stage by stage whether to go ahead.

A dedicated team

Engineers embedded in your existing workflow, sized up or down as the roadmap shifts, with direct access to the people writing the code.

Dedicated team

After launch

You own the code and it runs in your own cloud account. Most clients keep working with us to extend it, and it is documented so any capable developer could take it on.

Security and governance

Questions owners ask us

How long does it take to build custom software for a business?

The first working part is usually in use within weeks. A full system replacing several tools is built part by part over months, with each part in daily use before the next starts.

Do we have to stop using our current software?

No. The new system runs alongside your current tools until your team has moved across. Subscriptions are cancelled one at a time, once nobody needs them.

How is a custom software project priced?

After a discovery call we produce a system map. Each stage in it has a scope, a timeline and a fixed price, and you decide stage by stage whether to go ahead.

What happens after launch?

You own the code and it runs in your own cloud account. Most clients keep working with us to extend it, but it's documented so any capable developer could take it on.

Start with the call.

Thirty minutes on how your business runs today. You'll know by the end whether this is worth doing.