Custom Software
For Established Businesses.
Established businesses often reach a point where several products each hold part of the process and staff bridge the gaps by hand. We build the missing system around the real workflow, with the integrations and controls needed for company use.
Map the work
Agree the scope
Build the system
You get software built around how your team works.
Bespoke
FOR ONE BUSINESS, YOURS
One workflow
PROVED BEFORE EXPANSION
Yours
CODE, DATA, IP, NO LOCK-IN
Test the case for custom software
Standard products can cover much of a business process. Custom software is worth considering when an important gap remains expensive or difficult to manage.
A focused first release lets staff test that gap before the business funds a wider build. We compare its cost with improving the systems already in place.
The proposal records what the first phase will do, the dependencies and how the business will judge the result.
COSTS TO WATCH
- Large budget before anything's live
- Months before anyone touches it
- Spec frozen early, hard to change later
- Discovery without a defined output
- Code you can't open without the agency
HOW WE SCOPE IT
- First phase priced before it starts
- A scoped first release, often measured in weeks
- Changes assessed against scope and budget
- Defined phases and commercial terms
- Your repo, your data, your call
When standard tools no longer fit
Most established businesses are not underspending on software. They are paying for several products that each cover part of a process, while staff manage the gaps and duplicate the data.
Start by tracing one process across its systems. The repeated entry, missing checks and waiting time show whether a new integration or application would help.
The review uses your workflow and costs to assess the case for a build.
The SaaS doesn't fit your workflow.
A required approval, calculation or data field may fall outside the product's supported workflow. Staff then maintain it separately.
Connections need manual intervention.
Imports, failed syncs or unsupported fields can require repeated fixes. We compare repairing the existing integration with replacing it.
One person holds it all together.
They built the spreadsheet, they know the macros, they trained the VA. If they leave, you lose the operating manual with them.
Admin grows with each customer.
Repeated entry and checking can add work with every order. Measuring that effort helps establish whether automation is worth building.
The data is everywhere and nowhere.
Customers in HubSpot, jobs in Trello, invoices in Xero, files in Google Drive. You can't answer "how are we doing this month" without three people and a meeting.
The work custom software should replace
The strongest cases have a costly manual gap, an accountable department and enough repeated work to measure the change.
Internal tools
The platform your staff run the business in. Jobs, customers, stock, scheduling, invoicing. Replaces the sheet, the whiteboard, the three SaaS subscriptions.
Customer portals
Where your clients log in to see their account, book the job, upload the file, sign the thing. Cuts repeat inbox traffic when customers use it.
Integrations
Stripe, Xero, HubSpot, Companies House, your supplier's REST API and the one warehouse system that still wants SFTP. We make them talk, properly, with retries and an audit trail.
AI-native features
Document extraction, triage agents, drafting, classification, search that understands what you meant. Connected to the relevant records and review steps.
MVPs and v1 products
A new product you want to put in front of customers quickly. A narrow first release can often be built in weeks once the user, workflow, integrations and acceptance criteria are agreed.
How we take it into live use
Each phase has an agreed decision, scope, dependencies and commercial proposal. The first phase gives users something concrete to test before more budget is approved.
Large all-at-once builds expose expensive mistakes late. Testable phases let users and system owners challenge assumptions before the business approves more scope.
BOOK A SCOPING CALLScope and price
A working call, a written scope, a fixed price for phase one. You see exactly what we'd build, what's in, what's out, and what the next phase looks like. If we're not the right fit, we'll tell you in the call.
Model the work
We map the entities, the workflows, the user roles, the rules. You see the data model and the screens before we write production code. Cheap to argue about now, expensive once it's built.
Launch phase one
A working version your team uses in production. We migrate the data, train the people who'll use it, and run it alongside what you've got until the new thing's earned its place.
Iterate
New fields, new views, new integrations as you find them. Small releases, no big-bang rewrites. When the software's settled, we either hand it to your in-house team or stay on a light retainer. Your choice.
A maintainable technical stack
We use supported frameworks and document the data model, setup and operating procedures so another engineering team can take over.
Laravel, PHP, PostgreSQL
A documented framework and relational database for business workflows, with tests and maintenance included in the operating plan.
Livewire, Blade, Tailwind
We choose the interface approach against the interactions required and the team's ability to maintain it.
OpenRouter, Claude, Gemini
We assess models against the task, privacy requirements and cost. Changes to a model or provider are tested before release.
In your account
Hosting ownership, location, access and support are agreed before the build. We can work with your infrastructure or provide managed hosting.
Our public work covers whole operating systems
AM2PM, Leo Associates, Crystal, Digbeth Events and Olton Bedrooms all use custom software built around their own work, connected to the products they already relied on.
When this is worth discussing
We work best when there is a real operating problem, enough volume to measure and people from the affected teams who can make decisions.
Usually a good fit
- An established UK business, usually with annual revenue above £10m
- A repeated process with a known cost, delay, error rate or capacity problem
- A senior sponsor and a day-to-day owner who understand the work
- Access to the relevant staff, systems, sample records and security requirements
We may point you elsewhere
- A standard product already covers the process well
- The requirement is a one-off small build with no wider operating case
- There is no owner or access to the people and data needed to test the result
- The plan relies on AI making high-impact decisions with nobody responsible for review
Questions before connecting the systems
How much does it cost?
Priced per phase, fixed before we start. Scoping is its own short phase so you see the build number before anything's committed. Anything bigger we keep on the same per-phase footing.
How long until we see something?
We agree the data model and key workflows before building a controlled first release. Delivery continues in defined phases so users can test assumptions before the business approves more scope.
Why is bespoke suddenly cheaper than it was?
AI tools can reduce time spent on routine implementation. The total cost still depends on business rules, integrations, data migration and testing, so we price the actual scope.
Who owns the code?
The agreement assigns the bespoke source, data, product IP and deployment credentials to you. Third-party services and open-source components remain subject to their own licences. The repository can live in your Git account from day one.
Can't we just use Lovable, Bolt or Replit ourselves?
Those tools can help create working software. Before real users, payments or sensitive data are involved, the implementation needs review of access controls, secret handling, validation, monitoring and recovery. Our production review can assess an existing build.
What about GDPR, security, compliance?
Default. UK or EU hosting where the data needs it, role-based access from day one, audit logs on the things that matter, encryption in transit and at rest, sensible password and session policies. If you've got a regulator or assessment to satisfy, such as FCA rules, ICO guidance, NHS DTAC or SRA requirements, tell us early and we'll build to it.
What if we already have something half-built?
Send it. We'll look at it honestly. Sometimes the right answer is keep it and extend, sometimes it's start again from the data model. We'll tell you which, on the call, before you've spent anything.
Do we need an internal software team or CTO?
You do not need an internal software team. We need access to the people who own the process, its data and the security requirements. We turn their working rules into a scope that business and technical reviewers can challenge before build approval.
Talk to us about the software you need
Tell us which process has outgrown the current products, who owns it and what it costs to keep working around the gaps. We will define the first phase, its dependencies and whether custom software is justified.