Service
Custom Software
Most businesses reach this point the same way: a spreadsheet became load bearing, and now four people maintain it by hand. The work is to replace that process without pretending the rest of the business will change to suit it.
Request thisProject or day rate
- Fixed scope per milestone, or day rate
- Three weeks to six months
- Documented code, your infrastructure, your data
- A process no off-the-shelf tool fits
Deliverables
What You Actually Receive
Named up front, so there is something to hold the work against when it is finished.
The Process, Mapped First
What actually happens today, including the exceptions people handle manually. The exceptions are usually where the real requirements are.
A Working Slice, Early
One complete path through the system in front of real users within weeks, rather than a full specification signed off in advance and discovered to be wrong at the end.
Integrations That Survive
Payment, logistics, ERP and CRM connections built to fail loudly and retry, because the systems on the other end will go down.
Operable Software
Logging, backups, error reporting and a runbook. Software nobody can operate is not finished.
In detail
How The Work Runs
What This Covers
Internal tools that replace a spreadsheet or a manual process. Dashboards that put the numbers a business already has in one place. Client portals. Data import and export between systems that were never designed to speak to each other. Occasionally a desktop application, where the work genuinely needs to happen on a machine rather than in a browser.
The common thread is that no product on the market fits the process closely enough, and bending the business to fit a product would cost more than building the thing.
Built Around The Existing Business
The systems already running the business (the accounting package, the ERP, the warehouse, the payment provider) are constraints, not obstacles. Software that requires everything around it to change does not get adopted, whatever its merits.
Where an existing system is genuinely the problem, that gets said. But it gets said with the migration cost attached, not as an aside.
Scope And Money
Work is quoted per milestone, each one small enough to be estimated honestly and useful on its own. A typical shape:
| # | Milestone | Ends with |
|---|---|---|
| 01 | Process mapping | A written description of what happens today, exceptions included |
| 02 | Thin slice | One complete path working, in front of real users |
| 03 | Core build | The everyday cases, in production |
| 04 | Integrations | The connections to whatever else the business runs |
| 05 | Handover | Runbook, backups, monitoring, and the code in your repository |
If a milestone turns out to be wrong once it meets reality, it is re-quoted before the next one starts, not absorbed quietly and billed later.
You can stop after any milestone with working software and the code in your hands. That is the point of cutting them this way.
Other services
The Rest Of It
Most engagements start with one of these and turn into another. That is fine. The scope gets re-agreed, not absorbed.
Site Audit
Performance, security, GDPR and accessibility, checked against the live site. Written report in five working days, with the fixes ranked by what they are worth.
Accessibility & EAA Compliance
The European Accessibility Act has applied to new online services since June 2025, and 2026 is the first full year national authorities supervise against it. An audit against EN 301 549, then the fixes, in priority order.
Website Engineering
Marketing sites, stores, content platforms and everything between. Built on WordPress or WooCommerce where that genuinely fits, built from scratch where it does not.
Rescue & Recovery
Hacked site, failed update, broken migration, or a developer who stopped answering. I take it, stabilise it, and tell you plainly what happened.
Care Plans
Updates, monitoring, backups, security and small fixes. The same person every month, reachable directly.