Case studies
None published yet, and this is the standard each one will meet.
A case study goes on this page when three things exist: the client has agreed in writing to how they are named, the success criteria are the ones signed before the build, and the result has been measured. Not before.
What every case study here will contain.
The process, as mapped
The map of the process as it actually ran before the engagement, including the steps that were in no documentation.
The success criteria, agreed before the build
Metric, baseline, target and measurement method — the document both sides signed before anything was built, reproduced as it was signed.
What was built, and what it integrates with
The automation itself and the systems it runs against: ERP, CRM, accounting, commerce. Named, so you can judge whether it resembles your estate.
The measured result, against the criteria
The measurement taken after the agreed window, set against the target. Where a target was missed, the case study says so and says why.
The client's name and their written permission
Named, with permission on file for the attribution used. Where a client permits the sector only, the sector is named and the client is not.
Why there are none yet.
The company is new and the first engagements are under way. A published result needs two things that take time: the written permission of the client, and a measurement window after go-live long enough for the number to mean anything. Neither is worth shortening.
What you can check instead.
Three things are verifiable today. The record of the two founders — named people, stated certifications, profiles you can open. The method — the full sequence from process map to measured result, written out. And a conversation with the two people who would do the work.
Be the first documented engagement.
The first case study on this page will be someone's. Written criteria before the build, a measurement after go-live — and whether you are named stays your decision.