Custom business software

Custom business software, and when you actually need it.

This page exists to answer one question honestly: is software built specifically for your company the right shape of answer, or is something cheaper and more reversible the right one? Both answers are common, and only one of them involves us.

What it is

Software built for one operation rather than sold to a market.

Custom business software — also called bespoke business software, custom internal tools, or a custom operations platform — is software designed around how a particular company actually works, rather than a product designed around how a category of companies is assumed to work.

Most of what we build are custom operational platforms rather than single-purpose tools: one environment holding the workflows a company runs on, connected to the systems it already pays for, with the logic that is specific to that business built into it. The reason it is one environment rather than a set of tools is that fragmentation is the thing being solved, and a new tool adds to it.

It is not a category anybody should enter casually. It is a serious piece of work with a long life, and the received wisdom that it costs millions and takes years was far more true when everything had to be started from nothing. What has genuinely changed is how much can now be assembled rather than invented — which lowers the cost, and does nothing at all to lower the cost of getting the decision wrong.

What it is not

A website, a mobile app or an online shop.
A configured instance of somebody else's product with your logo on it.
A replacement for the accounting, payroll or e-signature systems that already work.
A pilot, a prototype, or a proof of concept nobody runs the business on.

The decision

Two lists, and the second one matters more.

Anyone who builds software for a living can tell you when building is right. The useful half of this page is the other one — and in our experience it applies more often.

When it is the right answer

The process is how you compete: Your pricing model, approval chain, scheduling constraints or quality process is a reason clients choose you. Nothing on the market implements it, because implementing it properly would mean implementing it for one customer.
The spreadsheets have become infrastructure: Files that several people depend on simultaneously, that no product replaces, and that now sit between systems as the integration layer nobody designed.
You have customised a product past its limits: The bought system has been bent so far that upgrades are frightening, and each new requirement makes the next one harder rather than easier.
The information exists but the answers do not: Everything needed to answer a question is somewhere in the company, and answering it still takes two people and a morning because nothing holds it together.
The rules are stable and worth writing down: How the work runs has settled. It is specific, it is not going to change next quarter, and today it lives in the heads of the people who happen to have been here longest.

When it is the wrong answer

Nobody has decided what the process should be: Software makes a process explicit. If three people do this three ways and no one has chosen between them, building encodes the disagreement and makes it more expensive to resolve. Choose first.
A mature product genuinely fits: For anything a competitor would do identically — accounting, payroll, e-signature, identity — buying means somebody else is obliged to keep it compliant and running for the next decade. That is an excellent trade.
The pain is between systems, not inside one: If the cost is re-typing, reconciling and waiting for handoffs, connecting the systems you already run removes it without replacing anything. Cheaper, faster, and reversible.
The process is still changing shape: If it changed twice last year and will change again, building now fixes a temporary answer in place at exactly the moment flexibility is worth more than structure.
Nobody inside the company will own it: A platform needs someone whose job it is to decide what it should do next. Without that, it is a project that ends rather than infrastructure that lasts, and it will be legacy within three years.

Before you choose

There are three options, not two.

Build versus buy is a good question about applications and a poor one about operations, because most of what a growing company loses is lost between its systems rather than inside any of them.

Buy

Capability that is the same in every company. You are buying somebody else's obligation to maintain it, which is worth far more than the features.

Connect

The space between the systems you already run. Nothing is replaced; the duplicate entry and the reconciliation simply stop. The cheapest of the three, and the one most often skipped.

Build

The logic that is particular to how you earn money. Usually a smaller part of the operation than people expect, and the only part where custom software is clearly the right instrument.

The full framework, with the failure modes

How the work goes

Understanding first. Building second.

We can't tell you whether custom software is right for your company from the outside, and neither can anyone else. What we can do is find out properly, in a way that is useful to you whatever the answer turns out to be.

The four phases in full

It starts with a diagnosis, not a specification: We spend time with the people doing the work and map how it actually moves: who touches what, where it waits, what gets re-entered, which spreadsheet is quietly holding a department together. The output is useful on its own — if it leads you to fix three things yourself and stop there, that is a legitimate result.
Systems that work stay: Your accounting system, payroll, calendars, e-signature and industry software are integrated rather than replaced. Replacing something that works is waste, and the platform has to reflect reality without anyone entering the same thing twice.
You see it before the expensive part: The blueprint — architecture, data model, permissions, and a clickable prototype your leadership can walk through and argue with — comes before anything is built. You are free to take it elsewhere; it is yours.
What is built for you is yours: The systems and code we create specifically for your business are built for you, not rented back to you.

How we think about cost

There are no prices on this page, and there is a reason rather than an evasion. What this work costs depends on what a diagnosis finds: how much needs connecting, how much needs changing, and how much genuinely has to be built. A number quoted before that is a number invented before that.

It is also worth knowing that the software is frequently the cheaper half. Replacing something an operation depends on means agreeing definitions two departments have disagreed on for years, migrating history properly rather than starting empty, and getting people to actually use it. We treat that as part of the work, because a platform people quietly work around has failed regardless of the code.

Tell us what is actually happening.

Describe where things feel fragmented, manual or unnecessarily complicated. We will give you an honest view of what would help — including, when it is the case, that you do not need a platform yet.

Start a conversation