Web applications
Customer-facing products and portals with authentication, permissions, billing and the operational tooling to actually run them.
Web and software development
Web apps and software you actually own.
We build web applications, SaaS platforms, internal tools and custom software - engineered to be maintained by someone other than us.
There is a version of custom software that costs less up front and far more later: no tests, no documentation, one person who understands it, and a codebase nobody else will touch. It looks identical to good software on the day it is delivered. The difference shows up in month eight, when a change that should take a day takes three weeks.
We build the other version. Typed, tested, documented, deployed through a pipeline, with the architecture decisions written down and the reasoning kept. It is not slower to build in any meaningful sense, and it is the difference between an asset and a liability on your books.
What we build
SaaS platforms
Multi-tenant products with subscription billing, usage metering, admin tooling and the isolation model decided before it is expensive to change.
Dashboards and reporting
Internal analytics and operations dashboards built on a reconciled data model rather than six teams querying six versions of the truth.
Internal tools
The admin panels, review queues and back-office software that operations teams live in all day and that off-the-shelf tools never quite fit.
E-commerce and marketplaces
Storefronts, checkout, multi-vendor flows and payment integration, connected to your existing inventory and fulfilment systems.
Legacy modernisation
Replacing or wrapping ageing systems incrementally, with parallel running and reconciliation, rather than a big-bang rewrite that stalls.
How we build software that outlives us
- 01
Decide what not to build
The cheapest feature is the one we talk you out of. We scope to the smallest thing that proves the product works, then expand from evidence.
- 02
Architecture written down
Data model, boundaries and the decisions behind them documented at the start, so the next engineer inherits reasoning rather than archaeology.
- 03
Build with tests and pipelines
Typed code, automated tests and CI/CD from the first week. Deployment is boring by design, because boring deployment is what lets you ship weekly.
- 04
Handover that holds
Documentation, runbooks and a walkthrough with your team. The measure of success is that your developers can extend it without calling us.
Who we build this for
SaaS founders
First production version of a product, built to be extended rather than rewritten after the seed round.
Operations teams
Internal tools replacing the spreadsheet-and-email process that runs a critical part of the business.
Enterprises
Customer portals and internal platforms integrated with existing ERP and identity systems.
Marketplaces
Multi-sided platforms with vendor onboarding, payments and dispute handling.
Data-heavy businesses
Reporting platforms built on a single reconciled model that finance and operations both trust.
Teams with legacy systems
Incremental modernisation with parallel running, so nothing breaks during the transition.
The stack we standardise on
Frontend
- React and Next.js
- TypeScript
- Design systems
- Accessibility
Backend
- Node and Python
- PostgreSQL
- REST and GraphQL
- Background jobs
Infrastructure
- AWS, Azure and GCP
- Terraform
- Kubernetes and containers
- CI/CD
Quality
- Automated tests
- Type safety
- Observability
- Documentation
Trusted to ship AI across the world's operational industries
ManufacturingLogisticsEnergyHealthcareFinanceSmart CitiesAgricultureRetailAerospaceTelecomMiningPublic SectorManufacturingLogisticsEnergyHealthcareFinanceSmart CitiesAgricultureRetailAerospaceTelecomMiningPublic Sector
Questions we get asked about web development
What does custom software cost?
It depends on scope and integration count, not on a per-page rate. An internal tool replacing one manual process is a small engagement. A multi-tenant SaaS platform with billing and admin tooling is a much larger one. We price in phases after scoping, so you can stop between phases rather than commit to everything up front.
Do we own the code and infrastructure?
Yes, entirely. Repositories, infrastructure as code, documentation and cloud accounts are yours. There is no licence, no hosting markup and nothing preventing another team from taking over.
Will our own developers be able to maintain it?
That is the point. Typed code, automated tests, written architecture decisions and runbooks, plus a handover walkthrough. If your team cannot extend it without us, we did the job badly.
Can you work with our existing codebase?
Yes. We audit it first and give you a straight assessment of what is worth keeping, what needs replacing and what it will cost either way, before proposing work.
How do you handle ongoing support?
Optionally. Some clients take full handover and never need us again, which is a fine outcome. Others keep us on a support retainer for changes and on-call. Both are available and neither is required to keep your software running.
Related capabilities
Let's build
Have an idea? We'll ship it.
Tell us the problem. We'll come back with an architecture, a timeline and a team ready to build it in production.