When Revenue Grows, Remember Who Still Holds the Switch

The best moment in a small business can be the moment when nobody wants to ask an unpleasant question. Traffic is steady, orders are growing, payments work, and every week looks better than the last. As long as the chain keeps running, growth feels like an owned capability.

A saved essay contains a line worth shrinking into a business diagram: some profit models exist only inside somebody else’s permission. Every external node on that diagram is a switch held by someone else.

External nodes are still switches

An independent product may depend on app-store approval, cloud APIs, search distribution, advertising accounts, and payment channels. They provide enormous efficiency, and each follows its own rules. The problem is not using platforms. The problem is leaving users, data, distribution, delivery, and payment under the same permission.

Imagine a business earning 100 a month, with 90 coming through one platform. The revenue report looks healthy, but it does not reveal how much customer access remains after an account review, API change, or settlement suspension. The 100/90 example is a stress test, not data from a real business.

Revenue answers, “How much comes in now?” Dependency answers, “Who can allow it to keep coming?” They are different questions.

Remove one dependency at a time

An earlier article reviewed how Apollo, an eight-year product, was cut off by an API policy change. The next useful step is to test dependencies before the switch is turned off.

Remove the traffic source: can existing users still be reached? Remove the payment channel: is there another way to collect and reconcile money? Remove the API: can core data be exported completely? Remove the platform account: do users know where to find the product?

This does not mean every small project should rebuild all infrastructure. That may cost more than the risk it removes. The stress test identifies which dependencies are acceptable and which would take revenue directly to zero.

Track owned capability separately

I would keep platform-generated revenue and retained capability in separate columns. The first can be large. The second should not be blank.

When the revenue curve rises, draw the reverse flow as well: close one external node and trace where users, data, delivery, and money can still go. Growth deserves celebration, but the location of the switch tells you how much of that curve is truly yours.

Source: It Is Not That Money Cannot Beat Power; It Miscalculated Time.