The data model
How the ledger, business graph, policy engine, and agents relate, and why the ordering matters. Without this, a partner cannot scope integration work accurately.
Partners
Certification exists for partners doing genuine co-delivery, not as a gate on referrals and not as a badge. Our own research says certification measures the wrong thing, so this page explains what ours actually covers and what it does not.
Tell us what you would co-deliver. Certification only makes sense for some arrangements.
Partners
Each is a capability we can assess and that materially affects delivery. Nothing here is a quiz on feature names.
How the ledger, business graph, policy engine, and agents relate, and why the ordering matters. Without this, a partner cannot scope integration work accurately.
Actors, scopes, thresholds, and the fixed ceiling on agent authority. This is the part partners most often get wrong when configuring for a client.
What a tie-out checks, why one clean month proves nothing, and how to run a parallel period properly.
Running a data diagnostic and interpreting the findings — duplicate rates, unbalanced periods, dimension coverage — without over-claiming what they mean.
Deriving requirements from transactions rather than interviews, and writing exclusions down. This is the largest single predictor of whether an engagement lands.
Our own research on implementation failure found that the software being genuinely incapable was the primary cause in about 4% of stalled projects — the rarest cause and the most commonly blamed. Requirements, data quality, and decision authority accounted for roughly three quarters.
Certification tests product knowledge. It does not test whether a firm can settle requirements, examine data honestly, or tell a client something they do not want to hear. Those are the things that decide outcomes, and they are difficult to assess in a certification.
So a certified partner is a partner who understands the system. It is not our warranty that they will deliver well, and we do not present it as one. If you are a buyer choosing a partner, our guidance on what to ask is more useful than any badge.
We certify partners who are actually co-delivering, which is a small number. A long certified list makes a channel look substantial and tells a buyer very little, because the variance within any large certified population exceeds the difference between certified and not.
You do not need certification to refer a client. Referral terms are identical either way, and a gate on referrals exists to make a programme look serious rather than to improve outcomes.
Presenting certification as an endorsement of delivery quality by us. Configuring a client past the agent authority ceiling or attempting to work around the policy engine. Failing to disclose a referral fee to a client. Or repeatedly scoping engagements that turn out to have been sold on requirements nobody derived from data.
We would tell you first and give you a chance to address it. We would also tell the affected client, which is the part worth knowing in advance.
Do not weight our certification heavily when choosing who to work with. Ask the partner how many deployments they completed last year for companies your size, who specifically will be assigned, and for two references whose projects overran. Those three questions predict outcomes considerably better than any badge, including ours.
Questions
Which is the thing that goes wrong least often. We run it anyway, and we would rather say what it does not cover.