// service 02 — custom software
Software that fits where off-the-shelf doesn’t.
Excel files floating around in email. Customers calling for a status update. A process only Liesbeth still knows. We build tools that remove that kind of friction — without you waiting months on a delivery.
// project types
What we typically work on.
Customer portals
A dedicated space where your customers self-serve: pull documents, submit requests, or check the status of their project.
Internal dashboards
One screen that brings together sales, inventory, work orders or margins — no more piecing it together from six systems.
Booking & scheduling
Reservations, appointments or capacity planning, linked to your calendar and invoicing.
Workflow automation
Repetitive work that’s done manually today — quotes, confirmations, reports — handled automatically.
Integrations
Existing systems (Teamleader, Yuki, Shopify, ...) wired together so data isn’t retyped anymore.
Data & reporting
Insight into what really happens: numbers per day, week, month — automatically in your inbox or dashboard.
// approach
Start small. Ship fast. Iterate.
Write a hefty spec document and see something only six months later? That’s not how we work. We aim for a working first version within three weeks — then build it out iteratively based on what you actually need.
Discovery
A day around the table: current workings mapped, friction named, scope of version 1 defined.
Prototype
Clickable version within a week. You see the tool working before a single line of production code is written.
Building in sprints
Two weeks ahead. Weekly demo, you steer based on what already works — not on what’s in a document.
Live & maintenance
After launch we stay available for extensions, small changes, or a next phase.
// principles
Our technical rules.
Software that still holds up well in five years takes choices you make today.
No vendor lock-in
We build on open standards and common frameworks. You can always continue with another team.
Your data, your account
Hosting, database, repository — everything is registered to your name. We get access, not ownership.
Boring tech, in the right places
We prefer proven tools over the hippest one from last month. Stable, predictable, widely supported.
Tests where they matter
Not all code needs tests — critical flows do. We write them where downtime would really hurt.
Documentation as a commitment
How it works, how it’s deployed, and how you can change small things yourself — in writing.
// let’s talk
A process that could be better?
A 20-minute call usually gives a first sense of what’s feasible — and roughly what it would cost.