Web applications
Multi-user products with authentication, roles, billing and the unglamorous state management that makes them dependable.
Services / Software Development
Custom software, built to be maintained
Most business software is bought, bent into shape and endured. We build the thing that actually fits, then type it, test it and document it well enough that the next developer can pick it up.
Scope
What we build
If your operation runs on a spreadsheet nobody is allowed to touch, or a tool that does 60% of what you need, that's the gap we fill.
Internal tools
Dashboards, admin panels and workflow tools that replace manual process and give your team one place to work.
APIs & integrations
Well-documented services, and the connective work of making systems that were never designed to talk to each other cooperate.
SaaS platforms
Subscription products from first version to production: multi-tenancy, plans, entitlements and the operational tooling around them.
Data & reporting
Pipelines and reporting layers that turn scattered records into numbers a leadership team can act on with confidence.
Legacy modernisation
Incremental migration of systems that still work but cost too much to change, replaced piece by piece, without a big-bang cutover.
Our approach
Boring technology, carefully applied
We choose tools for how well they'll be understood in three years, not for how new they are. Novelty is a cost you pay at 2am.
Types end to end
TypeScript from the database schema to the interface. A whole category of bug simply stops being possible.
Tested where it counts
Full coverage is a vanity metric. We test the logic that would cost you money or trust if it broke, and we test it properly.
Observable by default
Structured logging, error tracking and alerting from day one, so problems are found by monitoring rather than by customers.
Documented decisions
Architecture notes record why a choice was made, not just what was built. That context is what makes handover work.
- Typed, reviewed codebase in your own repository
- Automated test suite and CI pipeline
- Staging and production environments with one-click rollback
- Error tracking, structured logging and uptime alerting
- Architecture documentation and runbooks
- Handover sessions with your team, recorded
Questions
Things people ask before starting
If your question isn't here, send it over. A straight answer costs nothing.
We have an idea but no specification. Can you still help?
That's the normal starting point. We run a short discovery phase that turns the idea into a scoped, prioritised plan, and you own that document whether or not you build it with us.
Can you work alongside our in-house developers?
Yes. We're comfortable joining an existing team, working to its conventions, and reviewing code rather than owning all of it.
What technologies do you use?
Usually TypeScript, React and Next.js on the front end, Node.js and PostgreSQL behind it, deployed to managed infrastructure. We'll adapt to an existing stack where it makes sense to.
What happens after launch?
Every project includes a support window. After that, most clients move to a monthly retainer for feature work, updates and monitoring, but it's optional and you're not locked in.
How do you handle security and data protection?
Least-privilege access, encrypted data at rest and in transit, dependency scanning in CI, and a documented backup and restore procedure that we actually test.
Start a project
Let's build something worth keeping
Tell us what you're working on, and we'll tell you honestly whether we're the right people for it. We reply within two working days.