Work About Stack Services Contact
English Nederlands
Software production house

Complex back-end systems, from first conversation to productionMenno
van Hout

I build the systems companies actually run on — back-end platforms, intranets, customer portals and the automation that ties a business together. Architecture, build, deploy and the years of maintenance after it. One engineer who stays with it.

Menno van Hout
0
Years building software
0
Systems & products shipped
0
Own products I run and maintain
What I do

The hard half of the software

Not brochure sites, not another webshop template. The systems underneath — where the data lives, where the processes run and where it has to keep working on a Sunday night.

Back-end systems & platforms
The engine room: data models that survive the second year, APIs other systems depend on, queues, jobs and the monitoring that tells you before your customer does.
Automating companies
Work that is currently a person, a spreadsheet and a lot of copy-pasting. Intake, scheduling, messaging, invoicing and reporting — connected and running by itself.
Intranets & internal tools
The system your staff live in all day. Inventory, inspections, planning, approvals and the reporting the business is actually steered on.
Customer interactions
Everything that reaches your customer: portals, confirmation flows, WhatsApp and SMS, payment links and the one-tap pages that mean nobody has to phone anybody.
Selected work

Systems in production

A SaaS platform I founded, a drain-service company running on software I wrote, an inventory system used daily and a memorial platform that renders video server-side.

How it goes

From a problem to something running

01
Work out what it actually is
Most briefs describe a solution. I want the problem behind it — the process, the people doing it now and what breaks. That conversation usually changes the scope, and it is cheaper to change it there.
02
Architect it to survive
Data model, integrations, failure modes. Where the queues go, what happens when a provider is down, what cannot be allowed to send twice. The decisions that are expensive to reverse get made first.
03
Build and ship it
Back-end, app, front-end and the deployment — all from one person, so nothing gets lost in a hand-off. You see working software early and often, not a demo at the end.
04
Keep it running
Monitoring, health checks and the unglamorous maintenance. Several of these systems have been in daily use for years and I still maintain them. That is the point.
Available for work

Got something complicated?

The projects I do best start with somebody describing a mess. Tell me what you are dealing with and I will tell you honestly whether I am the right person for it.

Start a conversation