03 · Custom software
Software built around you
Custom applications and business tools shaped around real workflows and long-term goals.
Typical timeline: 4 weeks for a first working tool
Typical for a well-scoped first release, agreed in week one. Larger scopes are planned in phases.
What it is
Custom software is built around one business and the way it works: a customer portal, a SaaS platform, an internal tool that replaces a tangle of spreadsheets, an integration that stops people copying data between systems.
Who it’s for
- Companies whose operations depend on spreadsheets and copy-paste.
- Founders turning a validated idea into a product customers pay for.
- Teams with a process that no product on the market handles well.
Typical scope
We start by mapping the workflow as it really runs today, with the people who run it. Then we build the smallest piece that removes the most friction, put it into use, and grow it from there — with the data model planned for the next versions, so growth never means starting again.
How we work
How the project runs
01Week 01
Discover
Understand the business, clarify objectives, identify users and agree on scope.
You receiveA written scope and plan, agreed together.
02Week 02
Design
Shape the experience and settle what will be built before development begins.
You receiveDesigns you can click through, and the technical plan.
03Weeks 03–04
Build
Develop, test, refine and prepare the solution for launch.
You receiveTested software, live on accounts in your name.
04Ongoing
Run
Agreed maintenance, support and improvements after launch.
You receiveUpdates and improvements, or a documented handover.
Four weeks is our standard for a well-scoped project, agreed together in week one — not a promise for every project. Larger work is planned in phases, and ongoing support follows the engagement we agree.
Quality, shown
The technical standard
What every project includes, whichever service you choose.
See how this site measures up| Commitment | Standard |
|---|---|
| Code review | Code review on every change before it’s merged |
| Automated tests | Unit and end-to-end tests, with a DevSecOps pipeline, scope agreed per project |
| Accessibility | Designed and tested against WCAG 2.2 AA |
| Performance | Performance budgets targeting “good” Core Web Vitals, tested on mid-range Android |
| Security | Security review based on the OWASP Top 10 before launch |
| Updates | A written update every week |
| Ownership | Repository and accounts set up in your name; you own the code as set out in your contract |
| Handover | Documentation, architecture notes and a handover walkthrough (recorded on request) |
Custom software
Frequently asked questions
When does custom software make sense over an off-the-shelf tool?
When an existing product covers your needs, use it — we’ll tell you so. Custom software makes sense when your process is what sets you apart, when tools don’t talk to each other, or when the workaround costs more each month than building the right thing.
Can you build a full SaaS platform?
Yes — accounts, teams, billing, an admin back office. We start with the smallest version a customer would pay for, ship it, and grow the platform in planned phases from what people actually use.
Can you work with our existing systems?
That’s most of the job. We map what you have — databases, exports, APIs, spreadsheets — and connect to it rather than asking you to replace everything at once.
Who owns the code and the data?
You do, from day one. The repository, the cloud accounts and the data are in your name; we work inside them.