Custom software
Softwarethat holds upover the years.
Business software, internal tools, APIs, AI when it helps. Written and run by engineers who know what a bad architecture decision costs three years down the line.
What we build
From scoping to production, with hosting and operations included if you want them.
Custom web applications
Platforms, portals, customer areas. Front end, back end, database, deployment: one team across the whole chain.
Business software & internal tools
The tool your industry doesn't have: the one that replaces twelve spreadsheets, three inboxes and an unspoken agreement between colleagues.
APIs & integrations
Get your tools talking to each other, expose your data cleanly, take back control of data flows nobody understands any more.
AI, when it helps
Semantic search, document extraction, domain assistants. Built in if it saves time, and not for your press release.
What the demo doesn't show
A good demo proves it works today. Here's what keeps it working three years from now.
Automated tests
Unit, integration and end-to-end tests on the critical paths. They run on every change, before every deployment.
CI & code review
A pipeline that rejects anything that breaks, a review for every change. We can set up the same practices in your team: see development process.
Architecture & infrastructure
A design as simple as the need allows. Reproducible deployments, tested backups, hosting on your servers or ours.
Optimisation
We measure before we optimise: slow queries, heavy pages, hosting bills. Then we fix what weighs the most.
Documentation
Architecture decisions with what we ruled out and why, an install guide, API docs. Enough to carry on without us.
Code quality
Readable, typed, reviewed, written for whoever picks it up in three years' time. The repository is in your name from the first commit.
How we run the project
Agile without the theatre: frequent deliveries, and you stay in charge of the priorities.
Scoping
What the tool has to do, for whom, with which data. We write down the scope of the first version, and what can wait for the next.
Reviewing what exists
If a platform is already running, we look at it before building on top: architecture, security, technical debt. See the audit.
Short iterations
Regular deliveries to a test environment. You try things out, you correct course early, and the schedule reflects what we've learned.
Visible progress
A regular check-in, a task board you can look at whenever you like, risks flagged as soon as we see them.
Going to production
Automated deployment, monitoring, rollback when needed. Releasing becomes a non-event.
Training your teams
Once the software is live, we train the people who use it and the people who will maintain it. See training.
Before, during, after
Before
“We already have a system.”
An architecture and security audit, so you know what you've got before building on it.
During
“Every release scares us.”
Tests, CI/CD, code review, agile methods: the same practices, set up in your own team.
After
“Now the team has to use it.”
Tailor-made training on the tool we delivered, for your users and your developers alike.
Describe the tool you're missing.
A few questions to scope the need, then we get back to you. A first 30-minute call, no strings attached.