Bespoke operational software
When the product nearly fits, but your business still has to bend around it.
I build the custom software a business runs on when off-the-shelf products, spreadsheets and manual handovers cannot handle the actual workflow.
Problem diagnosis
The gap is usually specific, awkward and valuable.
- A product covers most of the workflow, but the important exceptions still happen by hand.
- Three tools each hold part of the process and people stitch them together with spreadsheets and memory.
- The business has a way of working that is sensible, but no product represents it cleanly.
That gap becomes duplicated admin, delayed work, avoidable mistakes, reporting nobody trusts and a dependency on the few people who know the workaround.
Responsibility
The work is not a menu of services. It is responsibility for the build.
I diagnose the process, decide what should be built, build it, test it, document it and hand it over. Integrations, automation and reporting are parts of that work only when they serve the owned system.
What I would build
The first useful version would be concrete.
- 01
A model of the work
The people, records, states, approvals and exceptions are named before the interface is designed.
- 02
A small first operating version
The first build focuses on the part of the process where fit matters most, so the business gets a working system rather than a grand promise.
- 03
Interfaces for the people doing the work
Screens are organised around roles and decisions, not around database tables or software categories.
- 04
Connections where they reduce manual work
Existing systems can stay where they are the right source of truth, with custom software filling the gap between them.
- 05
Documentation and handover
The system is left with setup notes, dependencies, access rules and operating instructions.
Fit filter
Probably right, probably not.
Probably right when…
- The process is operational, repeated and commercially important.
- Off-the-shelf software forces workarounds that now cost time, money or confidence.
- Someone authorised can define what working would mean.
Probably not me when…
- You need a brochure website, SEO, PPC, CRO or ecommerce experimentation.
- You want a pair of hands on a backlog someone else has already designed.
- The work needs a contractual SLA or production on-call from me.
First step
Start with diagnosis, not a big commitment.
The first step is a diagnostic conversation about the process, the failed product fit, and the smallest useful thing to build first.
£150 per hour plus VAT where applicable. Two hours minimum for new clients. No retainer, no minimum term, no lock-in. You own everything I build.
Useful things to send before a call
- Screenshots or recordings of the current workflow
- Examples of awkward cases products do not handle
- The reports or outputs the business relies on
- The systems, people and approvals involved
Objections
Questions this page should answer before you email.
Is this just custom software development?
The build is custom software, but the offer is narrower: operational software the business runs on because a product cannot do the job properly.
Could a product still be the better answer?
Yes. If a product can handle the real workflow safely, I would rather you use it than pay me to rebuild it.
Can this start small?
It should. The first useful version should reduce a real operational problem without pretending to replace everything at once.
Next step
If this looks like your problem, send me the awkward bits.
The useful first email is short: what is breaking, what product or process cannot handle it, and what working would need to mean.