Web applications and SaaS platforms
The product your customers log into, from the first release to the version that pays the bills.
Digitalize / Web development
Web platforms and internal tools, built to last.
Customer-facing platforms, admin tools and APIs, built so the next engineer can pick them up. Mostly React and Next.js in front, Node.js and Postgres behind.
What we build
Where we usually start.
Internal tools and admin panels
The screens your team uses all day, built around the work rather than around a template.
APIs and integrations
Clean APIs and connections to the software you already pay for, so data is entered once.
Speed and reliability
Monitoring, backups, security updates and the slow pages fixed, for systems that are already live.
Learn more
How we measure it
A baseline before, the same numbers after.
For a system that already exists, we measure it before we change anything. After each release we report the same numbers.
- 01Page load time
- 02Errors per week
- 03Manual steps per task
- 04Time to ship a change
How it runs
Four steps, the same on every project.
- 01
Map the work
We sit with the people who do the work today and map the process as it actually runs.
- 02
Measure the baseline
Time, errors and cost for the task as it is now, written down before we build anything.
- 03
Build in small releases
Working software early, reviewed with you as it develops.
- 04
Report the same numbers
After launch we measure the same things again, so the result is a number, not an opinion.
From the blog
Guides on this.
Building software · 14 Aug 2026 · 7 min read
Monitoring and Alerts for a Small SaaS
You do not need an observability stack. You need about six alerts that catch the failures that cost you money, and the discipline to keep the rest quiet.
Building software · 13 Aug 2026 · 8 min read
Retrofitting Multi-Tenancy Into a Single-Tenant App
Your app assumes one company per account and a customer just asked for teams. Here is how to add tenancy to a live product without a rewrite or a data leak.
Building software · 12 Aug 2026 · 6 min read
Feature Flags for Teams of One to Five
Use a small, disciplined set of feature flags to separate deployment from release without creating a second configuration system nobody understands.
Questions
What buyers usually ask.
Mostly React and Next.js in front, Node.js and Postgres behind. We use what fits the job and what your team can maintain after we hand over.