Multi-tenant platforms
One codebase serving many customers, with data kept apart, roles and settings per account.
Custom software development for teams that have outgrown spreadsheets and off-the-shelf tools
We build the web platforms, internal tools and integrations your business runs on, and we write them to be maintained by the next engineer, not just shipped by us.
What is custom software development?
Custom software development means building an application around your own process and data, instead of bending your process to fit a product someone else designed. It costs more up front than a subscription, so it pays off when the process is core to your business, when off-the-shelf tools need constant workarounds, or when you need to own the system and the data.
- First release
- 6–10 weeks
- Discovery
- 1–2 weeks, fixed price
- Runs in
- Your cloud account
- Stack
- Rails or Node, React, PostgreSQL
What we build
Internal tools and admin panels
The back office your team uses every day: search, bulk actions, exports and permissions by role.
Payments and billing
Card gateways, bank APIs, wallets, fees and refunds, with records that hold up when finance checks them.
Integrations between systems
APIs, webhooks and scheduled syncs with partners, government systems, devices and the tools you already pay for.
Reports and exports
Reports and CSV or Excel exports that run in the background, so they keep working as your data grows.
Work on an existing codebase
Upgrades, performance fixes and data migrations on a system that’s too important to rewrite.
How a custom software project runs
Every build follows the same five steps. Hand-over is the one most projects treat as an afterthought, and the reason the next engineer has to start from zero.
Discover
We sit with the people doing the work and map the process, the data and the systems it touches.
Design
Data model, screens and integrations agreed in writing, with a fixed quote for the build.
Build
Releases every week to a live test environment, so you see working software early.
Launch
Monitoring, backups, access controls and a runbook go in before the first real user.
Hand over
Documentation, tests and a walkthrough for whoever runs it next, your team or us.
Included in every build
- Automated testsCovering the business rules, run on every change before it ships.
- Your accounts, your codeRepository, cloud and third-party accounts are yours from the first commit.
- Monitoring and error trackingErrors, slow pages and failed background jobs alert someone before a customer notices.
- API documentationEvery endpoint documented, so partners and future apps can build on it.
- Runbook and handoverWritten for the engineer who maintains it after us.
Custom software our engineers have shipped
Student information system for universities
3.5 years, 160+ tickets delivered
Smart-locker cloud platform
A fifth of all commits in 8 months
Security-awareness training platform
18 months, a quarter of all backend commits
Meal-kit fulfilment exports
1,000 shipments per batch job
Custom software development FAQ
When does custom software make more sense than another SaaS tool?
When the process is core to how you make money, when you’re paying for several tools and still working around them, or when you need to own the data. If an off-the-shelf product does most of the job, we’ll tell you to buy it.
Can you take over an existing codebase?
Yes. Most of our engineers’ experience is on large, long-lived codebases other teams started. We begin with a short audit of how it’s deployed, what’s tested and where it breaks, then fix the riskiest parts first.
Which technologies do you use?
Mostly TypeScript, React and Next.js on the front end, Ruby on Rails or Node on the back end, and PostgreSQL. If you already have a stack, we’ll usually build on it rather than add another one.
Who owns the code?
You do. The repository, the cloud accounts and everything in them are yours from the first commit.
What happens after launch?
We can stay on to fix, tune and extend it, or hand it to your team with documentation written for the next engineer. Either way, monitoring and a runbook are in place before launch.