Custom software development
Software built around how your business already works.
- Internal tools
- Process automation
- Legacy replacement
- Data migration
What this is for
A way of working that no product on the market matches. A business that has been running a while accumulates a process that is genuinely its own, and forcing it into off-the-shelf software usually means changing the business to suit the tool. Custom software goes the other way. It is the right answer when the process is a real advantage, or simply too particular to bend — and the wrong one where a product would have done the job.
What it covers
- Internal tools
Software for the people inside the business rather than for its customers — the screens that replace a shared spreadsheet, a paper form or a folder of documents.
- Process automation
Steps that currently happen because somebody remembers to do them, made to happen on their own, with a record of each run.
- Legacy replacement
Systems that still work but can no longer be changed, replaced in stages rather than in a single switch-over.
- Data migration
Existing records moved across, cleaned where they need it, and checked against the original rather than assumed to have arrived intact.
What you end up with
- Software shaped to how you already work
Built to the process you described, with its exceptions inside it rather than designed around them.
- The existing data moved across
Migrated and reconciled, with a written record of anything that could not be mapped cleanly.
- Training for the people who use it
For the people doing the work daily, in the language they already use for it.
- Documentation for whoever maintains it
Enough for another developer to pick it up: structure, deployment, and the decisions that are not self-evident from the code.
What we need from you
- To watch the current process once, end to end
Seeing it performed is more accurate than any account of it. The steps people stopped noticing years ago are usually the important ones.
- The data as it stands today
Including its inconsistencies. Cleaning it is part of the work; hiding it is what makes a migration fail late.
- Who is affected by the change
Software that changes how people work needs somebody inside the team who wants it to succeed.
Who works on it
Each part is done by the specialist for it, in the order the work reaches them.
- FirstDesignFlows and screens, agreed before any code is written.
- ThenFront-endInterfaces built to their measurements and checked on real devices.
- ThenBack-endThe logic, the data, and the contracts between them.
- ThenInfrastructurePipelines, hosting, monitoring and on-call.
- LastTestingTesting every release before it reaches a client.
How it runs
- DiscoveryFirst
We work out what you need, what it has to do, and what it will cost.
- Scope written down
- Fixed quote
- Agreed timeline
- DesignBefore the build
You see the site before it is built, on desktop and phone, and approve it before the build starts.
- Designs to approve
- Mobile and desktop
- Final copy
- BuildThe build
The design is built to its measurements, on a link you can open at any point during the build.
- Live preview link
- Progress you can see
- Content loaded
- LaunchHandover
Domain, hosting and email pointed at the new site. Checked on real devices, handed over in your name.
- Live on your domain
- Accounts in your name
- Support after launch
- SupportAfter launch
Updates, fixes and changes for as long as the site is live.
- Updates and fixes
- Monitoring
- A number to message
Questions people ask first
With a conversation about what you actually need, and then a written scope with a price against it. Nothing is built until you have agreed both, and that scope is what the work is measured against for the rest of it.
Also under Build
Get in touch
Every one of these reaches us directly, and is answered by a person.