Where custom beats bought
Off-the-shelf software is built for the average of its market. When your process is genuinely your own — and for many businesses the process is the competitive advantage — the average is a poor fit.
The usual signal is a business running its core process in a spreadsheet because the software they bought does not model how they actually work.
What we typically build
- Job and project tracking shaped around your actual stages
- Quoting tools with your pricing rules built in
- Scheduling that understands your constraints
- Reporting that produces the numbers your business actually uses
- Approval workflows matching your real authority levels
The economics
| Bought software | Custom tool | |
|---|---|---|
| Initial cost | Low | £6,000–£25,000 |
| Per user cost | Ongoing, forever | None |
| Fit to your process | Approximate | Exact |
| Change when you change | Wait for the vendor | Whenever you need |
| Maintenance | Included | 15–25% annually |
At twenty users on a per-seat product, a custom tool frequently pays for itself within two to three years, and that comparison ignores the process fit entirely.
Build the smallest useful version
The most common mistake in internal tools is building everything anyone mentioned. The version that gets used is usually a fraction of the specification.
Build what the process actually requires today, put it in front of the people who do the job, and extend from what they tell you.
It must be genuinely faster
An internal tool competes with a spreadsheet that people already know. If it takes more clicks than what it replaces, it will not be adopted regardless of its other merits.
Speed of use is the primary design constraint, ahead of features and well ahead of appearance.