Operational systems architect
I turn complex operations into systems that scale.
Architecture-first ERP & Business Central — strategy through delivery, from one pair of hands.
Architecture before chaos.
Five layers, one pair of hands.
Most projects need three of these at once. I cover the whole stack, so nothing gets lost between specialists.
Architecture before the fix.
I don't start at the symptom. First see the whole system, then design the structure, then build it — strategy to shipped, from one pair of hands. The stack below is the mental model behind every engagement.
Business Central sits in the middle as the system of record — everything below feeds it, everything above leverages it.
Shown, not told.
Proof is how I think
No logo wall, no invented numbers. The diagrams on this page and the field notes below are the evidence — how I map a system before I touch it. And this site is my own work end to end: brand, design and build.
Current, not legacy
The stack I recommend is the stack I run: Business Central as the system of record, Claude-based agents and automation layered on the ERP core. Working methods from this year — not habits maintained from ten years ago.
Latest from the notebook.
What I'm building and learning, in the open.
Start a project
Let's turn your operations into a system that scales.
Tell me where things are breaking — I'll bring the architecture.