Three numbers, tracked on every engagement, not just the ones that went well, and shown to you directly rather than filed away.
How often we land on the date we committed to at kickoff, measured against the original signed timeline, not a revised one.
How closely final cost tracks the original statement of work, and what specifically drove any gap when there is one.
How much support demand shows up in the first 90 days after cutover, a fair proxy for how ready the team actually was.
Yes, on a call. A metrics page that only shows wins isn't measuring anything, so we'd rather walk through a miss and what changed afterward.
Against the go-live date committed to at kickoff. If scope changes mid-project, that's tracked and disclosed separately, not folded quietly into a revised baseline.
No. An aggregate number is easy to make look good and hard to verify. We'd rather show you the actual tracking for engagements comparable to yours.
Any inbound request in the first 90 days post-cutover, including basic how-to questions. A high count is often a training or data-readiness signal, not just a software issue.
Yes. Bring it up on the first call. If a partner won't discuss their own delivery track record before you commit, that's worth noting.
Ask us for these numbers directly on a call, including the engagements that did not go perfectly.
With someone who has run this before.
Four minutes, no email required.