How we work
Our model
Principles first, because they decide what we refuse.
Revops runs a sequenced engagement model. Most clients enter through a paid Diagnostic, and each following engagement is scoped from what the previous one produced.
The conditions that make an engagement work are set out at the bottom of this page. They are stated early so both sides start the conversation from the same place.
Principles
What governs the work
Read before you build
A build is priced once someone has read the engine. Most engagements open with a paid Diagnostic, creditable against what follows, and a documented assessment the client already holds does the same job.
The read is paid because the read is the work
Reading an engine properly takes three weeks of senior time. We price it, and we credit it against whatever the client decides to do next.
Build on what you already own
The default is your existing CRM and stack. If a platform genuinely cannot carry the logic, we show the evidence rather than assert it.
The process before the tool
A tool cannot resolve a disagreement about definitions. We write the logic first, then we configure.
Execution runs on a written process
When Revops operates a motion, it runs on a documented process inside the client CRM, so the activity produces data the rest of the engine can use.
Exit conditions written at the start
Every Operate engagement states how and when the motion transfers back to your team.
One owner per decision
Every rule, field, workflow and metric ships with a named owner. An object nobody owns is a failure with a delay on it.
Evidence over confidence
A stage moves on what the buyer proved. We hold our own recommendations to the same standard, and say when the evidence is thin.
The sequence
How an engagement runs
- 01
Revenue Diagnostic (3 weeks)
Where the engine leaks, and what to fix first.
- 02
Revenue Blueprint (4 to 8 weeks)
The commercial logic, written to be built from.
- 03
Revenue Build (6 to 12 weeks)
The logic, running in your existing stack.
- 04
Revenue Operate (Recurring)
Motions operated to a standard, then transferred.
What makes an engagement work
Six conditions, agreed up front.
Most difficult projects go wrong in the first conversation rather than in delivery. These six points are how we keep that conversation honest, and every one of them is negotiable in form but not in substance.
- 01
The read comes first
Someone reads the engine before anyone prices a build. Usually that is our Diagnostic. A documented assessment the client already holds does the same job, and we will work from it.
- 02
A scope, a date and a boundary
Every engagement states what it covers, when it ends and what it leaves out. The boundary is written on the offer page before anyone signs anything.
- 03
A process before capacity
When we operate a motion, it runs on a written process inside the client CRM. That is what turns operator hours into data the rest of the engine can use.
- 04
Every asset has a commercial role
Content, media and campaigns are designed to produce a signal the system can recognise and act on, which is also how we measure whether they worked.
- 05
The stack stays the client's
We build on the platforms already in place, take no vendor commission, and licences stay in the client's name. It keeps our recommendation worth something.
- 06
A way back
Operate engagements state from the start how and when the motion transfers to the client's own team. The objective is a capability they keep.
Questions