Custom business software

The system your business already runs, written down properly.

Most companies past a certain size are running a process that no product sells: a sequence of approvals, handoffs, exceptions and judgement calls held together by spreadsheets, shared inboxes and two people who remember how it works. That is the ground we survey before we write a line of it into software.

Start with a complimentary 20-minute fit call Start with the blueprint

A custom build is the expensive answer. It is the right answer when the process is genuinely yours and genuinely valuable. The blueprint exists to establish that before you commit, not after.

What this line covers

Line of business applications and the tools around them.

Software written for one organisation and one way of working, rather than configured out of something generic and left fighting the way you actually operate.

Applications that carry a core process end to end, with the states, roles and exceptions that process really has.
Internal tools that replace the spreadsheet everyone is afraid to touch, without replacing the judgement inside it.
Dashboards that pull from several systems and answer one question properly rather than forty questions vaguely.
Workflow systems with approvals, assignment, audit trails and the escalation paths your operations actually use.
Migration of the records and history that have to survive the change.

Signals you are in this line

A spreadsheet has become the system of record and nobody planned it.
New staff take months to learn a process that lives in one person.
The same information is retyped into three places every week.
You have evaluated products and every one of them fits at about seventy percent.

Any one of these is worth a conversation. Three of them usually means the process is real and worth designing around.

The kinds of systems we build

Work the team has taken on in this line.

Described by shape rather than by client, because the interesting part is the structure of the problem.

Operations consoles

Single screens that pull a job, an account or a case together from several underlying systems, so the person handling it stops reconciling tabs and starts making decisions.

Approval and assignment workflows

Multi step processes with roles, queues, escalation and an audit trail that stands up afterwards, built for the exceptions rather than for the happy path.

Reporting that survives scrutiny

Numbers assembled from more than one source, with the definitions written down, so the meeting argues about the business instead of about whose figure is right.

What we would talk you out of

Not every process deserves its own application.

These are the findings that come up most often when the honest answer is something other than a custom build, and we would rather put them in a document you paid for than discover them halfway through a project.

A vertical product covers it

Some industries are well served by mature software written for exactly that industry. If yours is one of them, no bespoke system we could write would be cheaper, better supported or safer.

The process is the problem

Automating a bad workflow makes it faster and harder to change. Where the finding is that the process needs fixing first, the blueprint says that plainly and describes the fix.

One report would do

A worrying number of requests for a new system resolve to a report nobody has built, a permission nobody has set, or a field nobody has added to what you already own.

Inside the blueprint

What the five days settle before any code is priced.

The blueprint covers the same fifteen items whatever the line of work. These are the questions it answers when the work is a custom application.

ItemWhat the blueprint settles for this kind of work

The process as it runs today. Documented from the people doing it, including the workarounds, because the workarounds are where the requirements hide.

Who the users actually are. The roles, their competing incentives, and which of them can make the project fail by quietly not using it.

Build against buy against extend. The market checked properly, your existing systems checked properly, and the reasoning written out either way.

Phase 1 drawn tightly. The smallest release that changes how the work feels, with the exclusions listed beside it so nothing is assumed in.

Data and migration reality. What has to move, what can be left behind, and what that costs, before it becomes a surprise in month three.

A fixed price for the scope. One number against a document you have read and argued with, not a range attached to a wish.

The other three lines

Most projects touch more than one.

Work rarely arrives in a single category. The blueprint is where we decide how much of each one your project actually needs.

Integrations and automation

Making systems talk: APIs, data sync, billing and operations plumbing.

AI and agent systems

Assistants, document and ticket automation, retrieval, agent workflows.

Web and ecommerce platforms

Storefronts, portals and customer facing web applications.

Book the call

Bring the process, not a specification.

Twenty minutes, no charge. Describe how the work moves through your business today and we will tell you whether a blueprint is the right next step or whether you are looking at something we would not sell you.

Start with a complimentary 20-minute fit call Read the blueprint in full