Systems · Custom systems

When the off-the-shelf thing does not fit.

Some work does not match any product on the market. A custom system is the smallest piece of software that removes the bottleneck — and nothing more.

Start a project

What it is

Custom does not mean large. Most of the systems worth building are small: an internal tool that replaces a fragile spreadsheet, a portal that lets clients see their own status, a calculator that ends a daily argument about pricing.

We start by trying to talk you out of it. If an existing tool fits, use the existing tool. Custom is worth it when the fit is genuinely wrong and the cost of the workaround is paid every week.

How it works

  1. 01

    Describe the bottleneck

    What takes too long, breaks too often, or depends on one person.

  2. 02

    Check for an existing answer

    If something off-the-shelf fits, we say so.

  3. 03

    Build the smallest version

    The part that removes the pain, in use quickly rather than perfect slowly.

  4. 04

    Grow it only if used

    Features get added because people asked, not because they were planned.

What you get

  • Scoped to the bottleneck — Not a platform. A tool.
  • Yours — No per-seat licence on your own process.
  • Documented — Handover is part of the build.
  • Static where possible — Fewer moving parts, fewer failures.
  • Integrates — Talks to the tools you already run.
  • Honest scope — If it is not worth building, we will tell you.

Who it is for

  • A spreadsheet that has become load-bearing and now frightens everyone.
  • Client-facing status that is currently delivered by phone call.
  • Internal calculations where two people get two different answers.

Questions

How small is too small?
Rarely too small. Small tools that remove a weekly bottleneck are usually the best value work we do.
Do we own it?
Yes. It is your system, documented, with no per-seat licence on your own process.
What if an existing product would do?
Then we will point you at it. Building something you did not need is not a good outcome for either of us.
How do you price it?
Per scope, after the bottleneck is defined — not from a table before anyone understands the problem.