Chapter seven
The invisible costs were carried by the customer.
Every interaction could become something to capture. Every user could become a record.
Tracking software was installed. Scripts were added. Links followed people across the web. Customer databases recorded behavior. Email tools watched opens and clicks. Automated systems tested which message brought a person back. Dashboards measured how long someone stayed and whether they returned.
Most of this remained invisible to the person using the product. The customer saw an interface. Underneath it were integrations, monitors, third parties, and pipes carrying information away from the surface of the tool. The business called this insight. The customer rarely had enough information to call it anything.
Measurement can improve a product, but invisible measurement changes the relationship. The founder begins to know the customer through the record created by the machine rather than through the reason the customer arrived.
The customer also paid with confusion. More systems meant more notices, more links, more chances to land on the wrong page, and more uncertainty about who held the relationship. A person who simply wanted to use the tool could be asked to understand the internal structure of companies that had inserted themselves between the need and the answer.
The hidden layer
What the user saw was not what the business recorded.
The user clicked. A script recorded the click. The record was stored. A dashboard counted it. Another system compared it with the last click. A campaign used the comparison to decide what the next person should see. One ordinary action became part of a machine the customer could not inspect.
The problem was not that every record was harmful. A secure entitlement record can prove that a customer paid and should have access. A device record can protect a one-device subscription and allow the owner to replace an old phone. A first-value signal can stop a setup reminder from bothering someone who already finished the task.
The difference is purpose. A record should exist because it protects access, improves support, or helps the product do the job the customer chose. It should not exist simply because modern software can collect it. The boundary should be understandable even when the plumbing is complex.
The old route made the relationship visible. The new system has to work harder to keep invisible machinery honest.
The hidden layer
Convenience did not erase the need for consent.
A system can make collection effortless for the business and invisible to the customer. That is exactly when the boundary matters most. The fact that a script can record an action does not answer whether the action should become part of a permanent customer profile.
Circle needed a simpler rule. Keep the records required to protect payment, entitlement, device access, support, and the customer's own work. Explain those records honestly. Do not turn every useful moment into permission for another sales system to follow the person somewhere else.
The old customer saw the seller at the door and could close it. The modern customer deserves an equally clear boundary, even when the software underneath is more complicated than anything the old route imagined.
The same rule applied to follow-up. A customer who bought one tool had not automatically asked to hear about every other tool. Setup help could be part of the transaction. Cross-selling was another relationship and needed another choice. Respect meant allowing the useful moment to stand on its own without immediately turning gratitude into a new campaign.