Enterprise systems
Work
For 14 years I've designed the SAP systems that global businesses run on: order-to-cash, billing, trade compliance, and the migrations between them. This is the work, and the thinking behind it.
01 — Industries
Four industries
- High-tech
- Telecom
- Chemical
- Energy
02 — Capabilities
What I architect
S/4HANA, BRIM, GTS, SD, LE, MDG and BIS, across the full order-to-cash flow.
-
S/4HANA
Core ERP on SAP S/4HANA
-
BRIM
Billing and Revenue Innovation Management
-
GTS
Global Trade Services: trade compliance
-
Order-to-cash
SD and LE: from order to delivery to invoice
-
Integration
How SAP talks to everything around it
-
Migration
ECC to S/4HANA
03 — How I work
How I work
Three principles that shape every system I design.
-
01 · Principle
Determinism
Predictable systems beat smart ones. I'd rather have a boring system that works every time than a clever one that fails unpredictably.
-
02 · Pattern
SLA Isolation
Compliance never blocks commerce. Critical paths stay fast; everything else queues.
-
03 · Design
Async First
Scale without coupling. Every system I design assumes the other end might be slow, down, or lying.
These aren't abstract principles — they're the result of years spent building enterprise systems where downtime means lost revenue and compliance failures mean regulatory action. I apply them daily across SAP landscapes, cloud-native architectures, and AI integrations. The patterns stay the same whether I'm designing a real-time order pipeline or wiring up an autonomous agent system: deterministic defaults, async boundaries, and strict SLA isolation between what must be fast and what can wait.