Rev-Lens is a small practice led by Todd Abbott, a former CRO. For 60 days we work inside your RevOps team, on your own CRM, recorded calls, email and Slack, to find where and why you win and lose. We build it on the AI license you already pay for and train your team to run it. At day 60 you keep all of it, and you decide whether you want more help.
What it is, and what it isn't
- A fixed-scope engagement with a start, a check point and an end.
- Led by the person who scopes your questions and presents the answers.
- Built inside your infrastructure, on your model license. No platform license from us, no platform change.
- Not a subscription, a dashboard or a seat-based tool.
The 60 days
The clock starts once access is in place. Security reviews and approvals sit on your side, so we don't let them eat into the work; most of the setup is ours.
| When | What happens | What you see | What you decide |
|---|---|---|---|
| Week 1 | Agree three questions and the sources that can answer them. Access granted to those sources only. | Written scope and data terms | The questions |
| Day 30 | Calls, email, threads and CRM history joined to the same deals, inside your infrastructure. | Whether your data can answer the questions, with the first candidate findings | Go or no-go |
| Day 50 | Findings checked against the deals you won, each traced to its source records. | A prioritized set of findings, each with a count, the evidence, a recommended action and a named owner | Which actions to take, and who owns them |
| Day 60 | Handover and training. Your RevOps team reruns a finding without us. | The runbook and everything built | Whether you want more help |
The day 30 check
At day 30 we show you whether the engagement can deliver what was agreed. We check three things:
- Access is complete for the sources you named.
- Enough of your deals are matched across those sources to count patterns, not anecdotes.
- Candidate findings are passing the four tests: a denominator, evidence, a comparison with the deals you won, and an owner.
If they aren't, we stop there and tell you why. You keep whatever was built.
What gets built, and what your team keeps
- The data. A joined, governed copy of your GTM history in your own warehouse, matched to opportunities.
- The agents. Tuned to your questions, running on your model license, documented so your team can run and change them without us.
- The findings. Each with its count, the source records behind it, a recommended action and a named owner. Reported at the level of deals and patterns, not individual reps.
- The runbook. How to rerun the analysis each quarter.
Everything built for you stays with you either way. The detail for IT, security and legal is in who owns what.
What it needs from your side
- A sponsor, usually the CRO: agrees the questions, attends the day 30 check and the day 50 readout, owns the actions.
- One RevOps or data contact: grants access to the sources named, and takes part in the handover and training. We agree the training hours at kickoff.
- An hour from each leader whose question is in scope.
- IT and security: review the access model and the written terms before anything is connected.
- No rep time.
The fee
A fixed fee for the 60 days, set by the questions and sources in scope, not by company size or seats, and agreed in writing before any access is granted. Your own cloud storage and model usage stay on your accounts, as they are today; we check on the first call that your model license includes API access.
How it ends
At day 60 you decide. You can stop and keep everything. You can keep us on month to month for regular reads and tuning. Or you can add new questions and sources. There is no long-term contract.