I Paid 5 Cents for Company Data. Apollo Charges $780 a Year for the Same Thing.

Yesterday I paid a nickel for something that would've cost me $65 a month to access. Not because I found a discount code. Because I used a micropayment protocol that let me pay per API call instead of buying a subscription I'd use twice.

The service was Apollo.io — an excellent B2B data enrichment platform. Their smallest plan gives you 1,300 requests per month. I needed twelve. That's like buying a 1,300-song album when you only wanted one track.

So I routed around it. Found an API endpoint that accepted micropayments. Five cents for the enrichment data. Another nickel to cross-check it against a competitor's dataset. Ten cents total. Two sources. Verified data. Done.

The math isn't the interesting part. The fault line underneath the math is.

The Album Strategy Worked Until It Didn't

In 2003, record labels had a beautiful business model. You wanted three songs? Buy the $15 album. The other eleven tracks were strategic filler — enough to justify the price, not good enough that you'd have bought them individually.

Then Apple launched iTunes at $0.99 per song. The labels fought it. They were right to fight it — unbundling destroyed their economics overnight. By 2010, album sales had dropped 55%. Today the album exists mostly as a Spotify organizing principle, not a pricing strategy.

SaaS subscriptions are the album.

Every enterprise software vendor that charges you monthly for something you use occasionally is playing the same game the record labels played. Bloomberg at $24,000 a year when you check commodities prices twice a quarter. Salesforce at $300 per seat when half your team logs in monthly. Thomson Reuters when you need case law four times a year, not four times a day.

The pricing survives because there's no alternative. You can't pay Bloomberg $8 for an afternoon. You can't rent a Salesforce seat for Tuesday. The "Professional Plan" isn't professional — it's the only door into the building.

I've Watched This Movie Before

I was working in financial services when electronic trading unbundled the NYSE. Floor traders charged fixed commissions whether you bought ten shares or ten thousand. Then Charles Schwab started charging per transaction. Then Robinhood made it free. The commissions didn't fade gracefully — they collapsed.

I watched media companies insist people would keep paying for newspaper bundles when they only read three sections. They were wrong. Readers unbundled to Substack and podcasts.

Nobody gets fired the day the railroad arrives. The company just slowly realizes the economics changed while they were defending the old model.

The SaaS vendors aren't stupid. They know most customers use a fraction of what they're paying for. That's not a bug. It's the business model. Spotify survives because most subscribers don't listen to $11 worth of music per month — they subsidize the power users. SaaS works the same way. Your underutilization funds someone else's overuse.

But that only works if there's no way to pay for exactly what you need.

What Actually Happened Yesterday

Here's what I did, technically: I hit an API endpoint that returned a 402 HTTP status code. That's the "Payment Required" code from the 1990s that nobody ever implemented because micropayments didn't work on the internet. Credit card fees were 30 cents plus 3%. You couldn't charge a nickel — the transaction cost more than the product.

Stablecoins fixed that. I paid in USDC on Base (a blockchain optimized for cheap transactions). The payment cost a fraction of a cent to process. The API verified payment and returned data. The whole interaction took four seconds.

Am I suggesting your finance team start buying API calls with cryptocurrency? No. I'm suggesting that someone at a startup is building the version of this your finance team will use in 2028. The same way Spotify wasn't Napster, but Napster proved the model worked.

This is early and weird. I'm a nerd who enjoys paying stablecoin-powered API endpoints because I like seeing where the friction used to be. Your CFO is not doing this on Monday. But the economic logic is sound: why pay $780 a year for something you use $1.20 worth of?

The Uncomfortable Questions for Your Stack

Walk through your SaaS subscriptions. Not the ones you use daily — those earn their cost. Look at the ones you use seasonally. The research databases you check quarterly. The analytics platforms you open twice a month. The collaboration tools that half your team forgot existed.

Now ask:

• What percentage of the subscription do you actually use? If it's under 20%, you're not buying software. You're paying rent on the possibility you might need it.

• Could you reconstruct this workflow with pay-per-use tools? Not today, necessarily. But in three years when someone builds the iTunes version?

• What happens when your competitor figures this out first? They're running the same analysis on the same cost structure. Except they're a startup that never signed the enterprise agreements you're mid-contract on.

I'm not predicting Bloomberg dies next year. But I am saying their $24,000 terminal fee assumes nobody will offer you the same data for $8 on Tuesday afternoon. That assumption has an expiration date.

The album didn't die because iTunes was better. It died because once someone proved you could charge per song, customers stopped pretending they wanted the whole album.

What to Do Monday Morning

If you're in finance, procurement, or operations, here's the specific question worth asking:

"Which of our SaaS tools could we replace with pay-per-use alternatives if they existed?"

Not to cancel everything and switch to crypto APIs. But to map where you're vulnerable when someone inevitably builds the à la carte version. Because the startups aren't asking whether to unbundle your software stack. They're asking which piece to unbundle first.

If you're building software, the question is harder: Is your pricing model defensible because you deliver concentrated value, or because customers have no alternative? One of those survives micropayments. The other doesn't.

The railroad is here. Not for everyone, not yet. But the economic logic is sound, the infrastructure is working, and someone is building the version that your team will use in three years.

What's the SaaS subscription on your desk that you use 2% of and pay 100% for?

That's the album.

---

Want to talk through what this means for your finance stack? I work with teams navigating technology disruption in financial services — the practical questions, not the hype. Reach out here.