We measure before we propose. The current state of the work gets written down with numbers attached: who does it, how it runs, where it breaks, what it costs to keep running that way.
That baseline turns an opinion into a business case, and it is what allows part of our fee to be tied to the result. Without it, everyone argues from memory.
The same team carries the work from the first measurement to the system in use.
We follow the work as it actually happens, with the people who do it. Hours, steps, handoffs, exceptions, cost. The output is a written view of the current state and what the alternatives would involve.
The team that ran the diagnosis designs and builds. The people who will use the thing take part while it is being built, which is what makes it used afterwards.
We stay through go-live and the period after it, with the metrics agreed at the start as the measure. Changes keep being made while the thing is in use.
Work starts from one concrete challenge the client already has.
That is enough to decide whether there is something worth doing, and it asks very little of the client's time.
Fees have a base and a part tied to the agreed result. The objectives and the metrics are written down before the work begins, together with how they will be measured and who signs off that they were reached.
A fixed fee pays for effort. Tying part of it to the result means we carry some of the risk the client is already carrying, and it makes us refuse projects where the result would not be measurable. That filter is worth more to the client than the discount.
A system that arrives from outside gets worked around.
Teams that have done something the same way for years have reasons for it, and some of those reasons are good ones that nobody wrote down. The client ends up able to run and change the thing without us.
The system runs where it makes sense for the client. The choice gets made in the diagnosis, on security, on cost, and on who maintains it afterwards.
Data stays in the client's own tenant, under their security policies.
We host and maintain it, and the client uses it.
For data that should not leave the building.
We work with the tools the client already pays for before adding new ones.
Ten published case studies, each with the starting point, the work and the result.
