Client Data Dependency
When the proof of your work lives inside the client's systems, write the data into the agreement as a term of the engagement. Build nothing to collect it.
By James Schramko · Updated September 2026
AI System for CRM Prospecting covers your own prospect records, kept in tools you already run. This playbook covers the other side: the client's data, and what to do when your delivery depends on it.
You sell a change in a number. More revenue, a better conversion rate, stronger retention, fewer hours in the owner's week. It applies to a coach who promises a lift in the client's revenue, a consultant paid partly on results, and an agency whose report has to show what its work produced. Whatever you deliver, the proof lands in systems you do not own: their CRM, their phone system, their accounting file, their booking calendar. At some point someone will ask whether it worked, and only their systems can answer it.
The instinct at that moment is to build. A form, a shared sheet, a tracking layer, a dashboard you control, so the number is there whenever you need it. Every version of that instinct puts you in charge of plumbing that belongs to the client. I have watched a one-number question turn into a build project, and the build was never in the fee.
Make The Data A Term Of The Engagement
Reporting is a term of every serious contract. A franchisee sends sales figures to the franchisor. A borrower sends accounts to the bank. Nobody in those arrangements builds a system to extract the numbers from the other party, because the numbers arrive under the agreement.
Do the same thing. Owner-supplied data goes into your agreement beside the fee, the term and the deliverables. Name the two or three numbers that prove the work, the system each one comes from, who sends them, how often, in what form, and from when. Ask for the same figures for the months before you started, because without them you have a number and no comparison. In plain words: the client supplies the named figures from the named system monthly, by the fifth of the month, and includes the three months before the start date. Your lawyer can word it properly. You decide what goes in it.
Every revenue share deal I have done pays me a percentage of the partner's net revenue. The visibility is written into the contract: access to their sales system or a monthly report from it, plus the right to audit. Some of those deals have paid me monthly for more than a decade, and the numbers have come from the partner's side every single month. The full structure is in Revenue Share Deals.
One more rule: owner-supplied, never participant self-report. If the people in your program are the owner's staff rather than the owner, the numbers come from the owner. Self-report gets rounded in whichever direction pleases the room, and it gets forgotten in any busy week. The owner already holds the real figures in the CRM and the accounts, and has every reason to want them accurate. I take revenue rather than profit in those partner deals for the same reason. Profit can be adjusted through expenses. Revenue sits closer to the source and is harder to bend. Take the number closest to the source.
Pull From What They Already Run
You need a feed from their data, never a copy of it. Their CRM already knows how many opportunities closed, their accounting file has revenue by month, and their phone system logs what happened on it. Ask for the report those systems already produce, on a schedule, in whatever format they already export. A one-page PDF on the first of the month is enough for the read you need to do.
The best feed is the report the owner already reads to run the business. A report built for you gets skipped the first busy month. The one they look at every Monday keeps arriving, and it carries the same definition of the number every time. A consistent definition beats a precise one you only get once. Two or three figures, defined the same way, from the same system, on the same day each month. Fewer numbers means fewer conversations about numbers.
Where The Client Has Nothing
Some businesses run on memory and a bank feed. When there is nothing to pull from, recommend one light tool, on the client's account, at the client's cost. You recommend and they run it.
Whose account it sits on decides who owns the problem. A tool on your account ties their history to your engagement. When it ends, either they lose the record or you keep maintaining a system for a company that has stopped paying. On their account it is their asset. It stays when you go, the vendor answers their support questions, and the password problem at four on a Friday afternoon is theirs to solve.
The Demo Test
One question filters every tool recommendation: would I recommend this exact tool to a client who currently has no system at all? If yes, it earns its place. If no, the tool is for your convenience rather than their result, and your convenience is their cost.
A shared spreadsheet the owner updates monthly passes, and so does a simple CRM on their account. A connector that pipes their data into a dashboard you built fails, because the only person who needs it is you.
You Are The Insight Layer
Your job is the read on top of the numbers: what moved, why it moved, and what to do next. The moment you own the plumbing you own its failures. An export breaks, a field gets renamed, someone leaves and takes the login with them, and the next three client conversations are about the pipe. Nobody hired you for the pipe. Every one of those problems is a loop you are holding for a business that should be holding it. Hand it back.
When I was at Mercedes-Benz, head office benchmarked every dealer and showed us our stats against dealers of the same type. The numbers came out of our own dealership. The comparison came from them, and the comparison was the part we could not have produced ourselves. That is the layer you are paid for.
How A Term Becomes A Platform
Ask an AI how to see whether your program moved a client's numbers and read what comes back. A tool to collect the data, a second tool to store it, a connector between them, a dashboard on top, and a project plan in phases. The question was how to see one number. The answer is a platform, and it arrives with enough confidence that building it feels like diligence.
Scope drifts in one direction. It starts as "I need to see one number" and ends as "I am building a system". Somewhere in between, a project has formed where a sentence in the agreement was all that was needed. The tell is the count. When the answer to a visibility question contains more than one tool, you asked the wrong question or accepted the wrong answer. Go back and ask the useful one: who already has this number, and what would it take for them to send it to me every month?
When The Numbers Stop Arriving
They will, at some point. Treat it the way you treat a late invoice: one plain reminder, then a conversation. The conversation is about the engagement itself, because without the numbers neither of you can see whether the work is working. That is the owner's problem as much as yours, and a term in the agreement is what keeps that conversation short.
The Self-Diagnostic
Run these against your current clients, one at a time.
Which number would prove your work for this client, and which of their systems holds it today. Is that number written into the agreement, with a baseline from before you started. Who sends it, and when did it last arrive. How many tools do you own between their system and your read, and whose account are they on.
If you own even one of those tools, you are running a data department the client did not order.
Quick Reference
- Owner-supplied data is a term of the engagement. Write it into the agreement beside the fee, with the numbers, the source system, the sender, the schedule and the baseline.
- Owner numbers, never participant self-report. The owner holds the real figures and wants them accurate.
- Pull from what they already run: their CRM, their phone system, their accounting. A feed from their data, never a copy of it.
- Where they have nothing, recommend one light tool on their account at their cost. You recommend, they run.
- The demo test: would I recommend this to a client with no system at all? If no, it is for your convenience.
- You are the insight layer. Own the plumbing and you own its failures, and every conversation becomes about the pipe.
- A visibility question that comes back with more than one tool has drifted. A sentence in the agreement was the answer.
Getting the two or three numbers that prove your work into the agreement before the next client starts is the kind of pass I run with founders inside Mentor.