Skip to content

Custom software built around how you actually work

Every growing business hits the same wall: the spreadsheet that runs everything is now too important to trust and too messy to fix. We replace it with something built for how your business actually works.

  • Hours saved
  • Fewer mistakes
  • Grows with you

The problem

Everything runs on one spreadsheet and only Dave properly understands it.
Operations manager

The spreadsheet worked when there were five of you. Now it has forty tabs, three people editing it at once, and a formula nobody dares touch. The risk isn't that it's inefficient — it's that it's a single point of failure holding your business together, and it's held together by one person's memory.

What you get

Everything that's included.

Not a list of intentions. These are the things that exist at the end, and they're all in the price.

  • A clear map of how the work flows today, before we change anything
  • Software built around your process, not a template you bend to fit
  • Your existing data brought across and checked, not left behind
  • Roles and permissions, so people see what they should
  • Training for your team, and written instructions they can keep
  • Runs on accounts in your name — you're never locked in
  • Documented and readable, so any developer can pick it up later
  • 30 days of support after go-live, included

How it runs

What happens, and when.

  1. Weeks 1–2

    Understand the work

    We sit with the people doing the job and map what actually happens — including the bits nobody wrote down. You get a fixed scope and price from this.

  2. Weeks 3–4

    Design the system

    How the data is structured and how the screens flow, agreed before building. Getting this wrong is what makes projects overrun.

  3. Weeks 5–10

    Build, in the open

    A working version you can log into from the first fortnight, with a demo every week. You use it as it grows.

  4. Weeks 11–12

    Move across and train

    Your real data comes over, your team gets trained, and we run alongside the old way until you're confident enough to switch it off.

Is this you?

We'd rather tell you now than in month two.

This is for you if

  • A core part of your business runs on spreadsheets or paper
  • Your team re-types the same information into several systems
  • Off-the-shelf software almost fits, but not quite
  • You can give us access to the people who do the work daily

It's probably not if

  • You want it finished in a fortnight — this is months, not weeks
  • Existing software already does the job and you'd be rebuilding it
  • Nobody internally can decide how the process should work
  • You want the price before we understand the problem

By industry

What this looks like in your sector.

The approach is the same everywhere. What changes is which problems come up first and what matters most.

How we price it

You'll know the number before you commit.

We charge for the first stage — understanding the work — separately and cheaply, because nobody can honestly price custom software before they know what it has to do. At the end of it you get a fixed price for the build, and you're free to take that scope elsewhere if you'd rather.

We don't publish prices because the honest answer depends on what you need, and a number on a page would either be meaningless or wrong. What we will do is give you a real one quickly — usually within a day or two of understanding the job.

Common questions

The things people ask before they commit.

How is this different from buying off-the-shelf software?

Off-the-shelf is cheaper and faster when it fits. We'll tell you honestly if it does — we've talked people out of custom builds before. Custom is worth it when your process is genuinely different, when you're paying for ten tools to do one job, or when the workaround costs more in staff time than the software would.

How long does custom software take?

Around three months for a first version that replaces the thing you're struggling with. It's deliberately not one big launch — you'll be using parts of it well before the end.

What happens to the data we already have?

It comes with you. Bringing existing data across and checking it's correct is part of the work, not an extra. We usually run the old and new side by side for a while so nobody has to trust it blindly.

What if we need changes later?

You will, and that's normal — a business that stops changing is in trouble. It's built so changes are straightforward, and it's documented so any competent developer can make them. You're not tied to us.

Who owns the software?

You do, completely. It runs on accounts in your name, and the work is yours to take anywhere. We don't hold anything hostage.

What if it doesn't work out?

The first stage is deliberately small and separately priced so you can stop after it with a clear scope in hand and very little spent. That's the point of splitting it.

Will our team actually use it?

That's mostly decided by whether they were involved in designing it. We talk to the people doing the job, not just the person paying, because software that ignores the day-to-day reality gets quietly abandoned.

Often needed alongside

Next step

Tell the chooms what needs building

Send the problem, not a spec. You'll hear back within 24 hours with a straight answer on what it takes, what it costs, and whether we're even the right chooms for it.