Internal operations tools
Job scheduling, stock, quoting, case management, approvals. The systems your team lives in all day, shaped around how they already work rather than the other way round.
01 — Business and domestic software
Software Development
Custom software for the work that off-the-shelf tools cannot do.
The short version
Custom applications for the parts of your business that off-the-shelf software will not fit. Built properly, documented, and handed over in full.
Most businesses reach a point where the spreadsheet, the shared inbox and the three disconnected tools stop holding things together. That is where we come in. We build the software that sits in the middle of how your business actually runs, and we build it so that another developer could pick it up tomorrow.
What this covers
Six things we are asked for most.
Integrations and APIs
Making your accounting package talk to your CRM, your CRM talk to your website, and your website talk to whatever comes next. REST and webhook integrations with retry handling and proper logging.
Legacy rescue and rebuilds
Inherited a system nobody understands? We read it, document it, and either stabilise it or replace it in stages so the business keeps trading throughout.
Data modelling and migration
Getting years of messy records out of the old system and into a structure that will still make sense in five years, with reconciliation reports so you can prove nothing was lost.
Automation
The repetitive work that quietly eats a day a week. Report generation, document assembly, reminder chains, reconciliation. Automated, logged and reversible.
Documentation and handover
Architecture notes, runbooks, environment setup and a walkthrough recording. Written for the next developer, not for us.
What you end up with
Deliverables, not deliverable-shaped promises.
- A working system in production, not a prototype
- Source code in a repository you own, from day one
- Automated tests around the parts that matter
- Written handover so you are never locked to us
Typical stack
- PHP
- Laravel
- WordPress
- TypeScript
- Node.js
- React
- Python
- PostgreSQL
- MySQL
- Redis
- REST & GraphQL APIs
How it starts
A thirty-minute call, then a short paid discovery that produces a written specification and a fixed price. If you walk away after discovery, the specification is yours to take to anyone.
The path
Same five steps, every time.
01
Conversation
Thirty minutes, no charge, no deck. You describe the problem in your own words and we ask the awkward questions. By the end of it we both know whether this is worth taking further.
You get: Outline of the problem, rough budget range, honest yes or no
02
Discovery
A short paid engagement where we sit with the people who will use the thing. We map the current process, find the edge cases that break naive designs, and write it down.
You get: Written specification, wireframes, milestone plan, fixed price for phase one
03
Build
Two-week cycles with something you can click at the end of each one. You see progress continuously, which means course corrections cost days rather than months.
You get: Working software on a staging URL, updated every fortnight
04
Launch
Data migrated and reconciled, team trained, rollback rehearsed, go-live in a planned window. We stay close for the first month while real use finds the last few edges.
You get: Live system, trained team, documentation, thirty days of included support
05
Operate
Monitoring, patching, backups and a monthly written report. Or a clean handover to your own team with everything they need. Both are a good outcome for us.
You get: Retained support, or full handover with documentation
Questions
The ones people actually ask.
Not on the list? Email us — we would rather answer it now than after you have signed something.
We scope first. A short paid discovery gives you a written specification, a milestone plan and a fixed price for phase one. If you decide not to build, the specification is yours to take anywhere. We would rather lose the build than start one on a number neither of us believes.
You do, in full, from the first commit. The repository is created under your organisation where possible, or transferred to you at handover. There are no licence fees back to us and no components you cannot host yourself.
Often. We are comfortable joining an existing team, reviewing someone else's codebase, or taking a defined slice of work while your team carries the rest. We will tell you honestly if we think an extra pair of hands is the wrong answer.
Thirty days of included support while the system settles, then either a retained arrangement or a clean exit with documentation. Both are fine with us.
Customer portals, member areas, booking systems and marketplaces. Accounts, permissions, payments and a front end that does not get in the way.
Start here
Tell us what you are trying to build.
A short conversation is usually enough to tell whether we are the right team for the job. No sales script, no obligation.
We reply within one working day. No sales sequence, no pressure.