I have yet to meet a growing company that can tell me, with confidence, how many things it sold last month.
Not a struggling company. A growing one, with real revenue and competent people. Ask for last month’s number and you do not get a number. You get two, and someone explaining the difference between them.
I have been rebuilding that plumbing for twenty-five years. Analytics, tag manager, event schema, a test-and-learn layer on top. Re-tag, re-implement, stand up a warehouse, hire someone whose entire job is the discrepancy. It gets closer. It has never once closed. And I have yet to encounter a growing company that is not struggling with some version of this, which after enough companies stops being an implementation problem and starts being something else.
The polite word for it is a discrepancy. A variance. Something to be reconciled down to an acceptable tolerance and then lived with. That word is too kind. What you have is a hole where a fact should be.
When two systems disagree and neither one is authoritative, you do not have a number with an error bar on it. You have a menu. Marketing quotes analytics, which is higher, because it counts attributed conversions. Finance quotes the processor, which is lower, because it counts money that actually moved. Both are reading a real system correctly. Nobody is lying. And the figure that lands in the board deck is whichever one the person building the deck pulled.
Decisions come off that figure. Which channel gets more budget next quarter. Whether the quarter was good. What the company believes about itself.
So the thing you cannot do is not “reconcile two reports.” It is state a fact about your own business without first naming which vendor you asked.
Why it never closes — You rented both ledgers.
Analytics is not measuring your business. It is measuring its own model of your business, built for its purposes, with its definitions of a session, a conversion, an attributed sale. The payment processor has a different model, built for different purposes, with a different definition of the same event. Both are internally consistent. Neither is authoritative. Neither will move its definitions to match the other.
You are the only party in the arrangement who needs those two systems to agree. You are also the only party with no ability to make it happen.
That is what tenancy costs, and the bill never arrives as a bill.
The machine on the desk
The first computer I used was an Apple IIc. It sat on a desk in our house. I typed BASIC into it, line numbers and all, and when I switched it off nothing about it changed. No account. No subscription. Nobody had to approve anything. It was a machine, it was ours, and that was the entire arrangement.
I have not had that arrangement since.
This is not a hardware complaint. The bill of sale on the laptop I am writing this on says it is mine. But the operating system updates on someone else’s schedule, the files sync to someone else’s building, the tools renew annually or they stop opening, and the part now doing the actual thinking is an API call to a company free to change its mind. Somewhere in there, ownership stopped being about the box. What I own is a login.
Most of the argument goes the other way, and I want to concede it first
Renting is usually right. I am not going to tell a twelve-person company to run its own mail server, and I would talk them out of it if they tried. Card receipts belong at Square. The books belong in QuickBooks. Payroll belongs with someone whose entire job is payroll and the penalties for getting it wrong.
That data is a record of what already happened. It is replaceable, it is reconstructable, and paying someone else to hold it is a good trade nearly every time.
So the line is not “own everything.” Nobody sane is arguing that.
The line is that renting the record is fine right up until you are renting two of them, at which point you have quietly outsourced the ability to know what is true.
What lives one layer up
Ask any owner what actually makes their business work and you will not get a list of their data. You will get judgment. Which customer is difficult and why. Which job always runs over. What broke last time with that supplier. Which quote they would take at a discount and which they would walk away from. Twenty years of that, living in one person’s head.
Put an operating layer on top of the transactions and that judgment starts accreting somewhere outside that person’s head for the first time. Which is enormously valuable, and is exactly the thing you would never want held by a landlord — because a landlord’s improvements are on the landlord’s roadmap. When the rented layer holds your operating logic, changing how your business behaves stops being a decision you make and becomes a feature request you file.
I have a recent, measured version of that: we sent keyed legal documents to a hosted model and a third came back refused, on a policy decision inside one vendor that arrived in our product as behavior we had not shipped. The write-up, including the correction after a second provider returned zero refusals, is here: What's in a Name? Everything — to one model, and nothing to the other.
Different surface, same arrangement. Somebody else’s definitions, running inside your business, changing when they decide.
A return, not a novelty
What I am building now is an appliance. It sits on a shelf in the back of a business, on their network, in their building, and it works. The model runs on it. The judgment accretes on it. If we disappeared tomorrow it would still be sitting there, still working, and it would still be theirs.
People call that a strange idea, and I understand why — for twenty years the arrow has pointed one way. But it is not a new idea. It is the arrangement I had when I was ten, with a far better machine inside it.
We used to own our computers. We rented them out one layer at a time, mostly for good reasons, and mostly without noticing when we crossed from renting the filing cabinet to renting the thinking.
A business should be able to say what it sold last month and mean it.