Service · Updated August 26, 2026

Understand the business, design, implement

That's the whole job, in that order. An assessment without implementation is a report that sits in a drawer. Implementation without an assessment builds what was asked for, which is almost never what's needed.

Why all three together

An assessment without implementation is a report that sits in a drawer. Implementation without an assessment builds what the client asked for, which is almost never what the client needs.

The same people do all three stages, and they're the same people who pick up the phone afterward. There's no sales team that promises and no technical team that later explains why it couldn't be done.

What happens in each stage

• Understand. We talk to the people who run the business day to day, not just the people who manage it. The expensive problems are almost always known to someone who was never in the meeting.
• Design. On top of the systems you already have. The constraint isn't technical: your operation can't stop while we work.
• Implement. In production, one piece at a time. Every improvement has its number, and if the number doesn't show up, the improvement isn't counted as done.

What turns up along the way

When you bring together data that was never in one place, you find things nobody was looking for. It's the part of the work you can't promise up front, and it's usually the most valuable: money that was leaking out through a path nobody watched, because seeing it meant matching two systems that had never been matched.

How long it lasts

The work doesn't end with a delivery. With the client running in production today, we're three months in, and the engagement has continued because each stage earned the next one.