Implementation
Go live on the way you already sell.
We set PROOF up around the way your team already sells, then walk every role through it on your own deals before anyone has to rely on it.
Where a launch actually stands
Go-live stops being a matter of opinion.
Every control either has evidence behind it or is visibly open with a name against it. Eighteen of twenty-one, and you can see the three.
Configuration readiness18 of 21 controls evidenced
Demonstration status · no invented time-to-value claimLaunch whenDefinitions agreeJourneys passRecovery is provenand ownership is clear
After the subscription is agreed
What we configure before anyone logs in.
Everything on this page happens once you're a customer. PROOF is set up from your stages, your forecast categories, your targets and your rules about who may change what. It's not a generic template with your logo on it.
What we need from you
Four things, and none of them is a project team.
If setting PROOF up needs more than this, the setup is wrong, and we will say so rather than book more of your time.
Somebody who can decide how the team sells
Usually a CRO, a RevOps lead, or the partner who already does this work with you.
Read access to the CRM, and an hour of whoever administers it
Nothing is written back until you have approved what may be written and by whom.
Including the one everybody skips
We configure what your team actually does, not what the process document says they do.
One you won, one you lost, one still live
The live one matters most. It is how you find out whether the setup holds before anyone depends on it.
The launch gate
Nobody logs in until four things are true.
A launch date that arrives before these do is how software ends up unused six weeks later.
Your definitions agree.
Your stages, forecast categories and targets mean the same thing in PROOF as they do in your QBR. If two regions define Commit differently, you find that out now rather than in week six.
Every role walks a real deal.
A Seller, a Manager and a Revenue Leader each go end to end on one of your own deals. Not a demonstration. Yours.
Getting your data back out is proven.
We show you how your evidence comes back out, and how PROOF behaves when a source stops responding, before you depend on either.
Every part has an owner.
Each stage, mapping and permission is owned by someone named on your side. Nothing is left for whoever notices it first.
A scoped launch plan
Clear responsibilities from the first working session.
We assess your Sales DNA, CRM mappings, data availability, access requirements and desired workflows. Together, we agree the milestones, owners and acceptance criteria for launch.
We publish timing only after that assessment, when the sequence can be supported by evidence rather than a generic promise.
Before any of that, most teams need to get us past security.
The answers your reviewer will ask for are already written down.
Prepare the launch