About
Operational modeling isn't a side offering — it's the only thing we do.
This is a single-person practice. There’s no sales team, no account managers — when you reach out, you’re talking to the person who builds the models.
The case studies on this site are representative analyses designed to demonstrate methodology and the kinds of questions these techniques can answer.
Background
I build optimization and simulation systems for manufacturing scheduling and operational decision-making, using constraint programming, discrete-event simulation, and related methods.
Before Margaux Systems, I worked as a backend engineer building production-grade Python systems — FastAPI services, event-driven architectures with RabbitMQ, and distributed data systems. That engineering background shapes my approach: models are structured and reproducible, designed to support real decisions rather than act as one-off analyses or spreadsheets.
Why a single-person practice
Most operations consulting firms scale by adding junior staff and standardizing deliverables. That works for process mapping and ERP implementation. It breaks down when the goal is to model specific operational constraints — because every operation has its own constraints, trade-offs, and failure modes.
By staying small, every engagement gets direct attention from someone who builds the models himself. The trade-off is capacity: engagements are scoped tightly and taken one at a time. The upside is consistency: what you read in the proposal is what gets built.
What this means for you
When you reach out, you’ll get a direct response — not an automated sequence or a business development layer. If modeling can help your decision, I’ll tell you how and scope it. If it can’t, I’ll tell you that too.