The list that lied

I trusted the count

The first stack I sat with showed a subscriber number that made the channel look like a finished project. Six figures on a good day, if I am allowed to be vague. Sends went out on a schedule. Reports came back with CTR.

What I could not see was arrival. Did this thing actually show up on the phone. How many of those rows were dead. How many had never been reachable in the first place.

I asked. The product did not have a place for that question. You can get used to that. You start arguing from the number you are given.

Then we paid less

We moved. Price, and a bit of hygiene. The new tool at least pruned subscriptions that were obviously gone. The channel started to look like itself. People came back. Clicks were not imaginary. A single well-chosen send could outperform a limp day on social. I still will not put a percentage on that until I can measure it here.

The cheaper product did not explain the leak. It just stopped pretending some of the corpses were alive. That was already an improvement. It was not a ledger.

Why I keep talking about this

If you already send push, the first useful question is not "should we switch composers." It is "how many of these people can actually receive the next one." I do not need a vendor name to ask that. I need an honest reachable count, and I need to know what you do with 410s.

I am building toward that. Some of it is install diagnostics and a test on your own device. Some of the deeper forensics is still product work. I will diagnose a list before I promise a dashboard.

If your current number and your gut disagree, trust the gut long enough to go look. That disagreement is how I ended up here.