This page is for IT, security, procurement and legal teams reviewing a Rev-Lens engagement. The short version is one line: customer-owned infrastructure, Rev-Lens-delivered intelligence. Everything built for you is yours. Our methods stay ours.
Who owns what
| Item | Owned by | What that means |
|---|---|---|
| Cloud infrastructure | You | The data lake, storage and cloud services sit in your own account. |
| Your data | You | Read from the sources you name, into a governed copy in your account. Never pooled, never used to train models. |
| Model and API usage | You | Your model accounts and your token consumption, billed to you at your rates. No markup. |
| Agents built for you | You | Including their configuration, workflows and business logic. Yours to maintain and extend. |
| Findings and reports | You | Every finding, with the evidence behind it. |
| Rev-Lens methods and toolkit | Rev-Lens | Pre-existing methods and reusable, non-confidential components. Where they are embedded in your agents, the statement of work licenses them to you. |
How access works
- Scoped. Access only to the sources you name, for the period in scope.
- In your account. One governed copy built inside your own cloud account, not ours.
- Your model. Analysis runs on the model you already license.
- Never pooled, never trained on. Your data is not combined with any other customer's and is not used to train models.
- In writing first. The specifics go in writing, and are reviewed by your team, before any access is granted.
What it costs you to run
The engagement is a fixed fee set by scope: the questions, the sources and the number of agents. It is not set by company size or seat count. Separately, you pay your own cloud storage and model usage, as you do today. Rev-Lens does not resell infrastructure or mark up compute.
One thing to check early. Many chat subscriptions to a model do not include API access. We confirm on the first call that your license covers it, and how it is billed.
What goes in the statement of work
- The questions in scope, and the number of sources, integrations and agents
- Data access prerequisites, and who on your side grants them
- The security model and each party's responsibilities
- Acceptance criteria for the findings delivered by week five
- The handover and training delivered in weeks 6 to 8
- Ownership of what is built for you, and the license for any Rev-Lens components inside it
- The difference between a delivered finding and a measured revenue outcome, which depends on what your team does with it
After the engagement
By week eight your team runs the agents itself. Anything after that is optional and month to month, with no long-term contract.
Questions we get asked
-
Does any of our data leave our cloud account?
No. The governed copy is built inside your own cloud account and analyzed there with your licensed model. Nothing is copied to Rev-Lens systems, pooled with another customer's data or used to train models.
-
Who pays for cloud storage and model usage?
You do, on your own accounts, as you do today. Rev-Lens doesn't resell infrastructure or mark up compute. We check on the first call that your model license includes API access, because many chat subscriptions don't.
-
Can we keep running the agents without Rev-Lens?
Yes. Everything built for you, including the agents, configurations and business logic, is yours to run, change and extend. Weeks 6 to 8 are spent training your team to do exactly that.
-
What does Rev-Lens keep?
Its pre-existing methods and toolkit, and generalized improvements to them that contain none of your data or confidential information. Where a Rev-Lens component sits inside an agent built for you, the statement of work gives you the license you need to keep running it.
-
What do we commit to after week eight?
Nothing. Ongoing help is optional and month to month: either regular reads and tuning, or new agents and sources.
About Rev-Lens. Rev-Lens is a founder-delivered go-to-market intelligence practice. In an eight-week engagement it joins a company's CRM, recorded calls, email, internal chat and intent data at the opportunity level, inside the company's own infrastructure, and returns win-rate findings by week five, each with a denominator, the evidence behind it and a named owner. The company keeps the joined dataset and the agents, and its team is trained to run them.
Keep reading: The Model Layer, on why GTM data is moving inside the walls, or the page for RevOps leaders.