How we work

From the first conversation to delivery review, we define the business problem, agree on ownership, and track the measures that matter.

Two colleagues reviewing a plan in a sunlit meeting room.

Discovery and scope

Tell us what has changed, what is getting stuck, and which decisions or deadlines matter most. We clarify the stakeholders, the data or systems we need, and whether to start with a diagnostic, a project, or fractional support.

Days 1–30 in a 100-day engagement

In an illustrative 100-day engagement, the first month is for interviews, process mapping, and a baseline. For an order-to-delivery problem, that could mean tracing sample orders across sales, warehouse, dispatch, and collections to see where delays begin.

Days 31–60 in a 100-day engagement

Agree on priorities, owners, success measures, and dependencies. We identify which changes the team can test quickly and which require a budget decision, a vendor, or more reliable data.

Days 61–100 in a 100-day engagement

Put selected improvements into use, review what is changing, and coach the people responsible for the new process. Transfer the operating notes and scorecard to the people who will maintain them.

Ways to engage

Choose a scoped diagnostic for a prioritized set of findings, a project for an agreed implementation milestone, or fractional support for ongoing leadership and follow-through. The 100-day sequence is an example. Scope and timing are agreed for each engagement.

Proposals, invoices, and changes

A proposal identifies deliverables, timing, client responsibilities, and price. It also explains how to approve additional work and when invoices are due. Raise scheduling, payment, or scope questions before the affected work starts.

Discuss an engagement