Cheap Tools Cost More At Your Stage

The cheapest ingestion tool at 10 engineers is often the most expensive one by 40.

I’ve seen the pattern enough to call it. A team picks the open-source connector, or the vendor with the free tier, or a set of Python scripts, because the paid option looked like a luxury.

It holds up for a year. Then the sources multiply. A schema changes upstream and the scripts fail silently for a week. The free tier caps at a row count you pass in March. The open-source connector hasn’t had a maintainer since last spring.

Now someone on your team is the maintainer. That’s part of a salary, plus incident response and the migration you’ll do anyway.

Cheap is right sometimes. Three sources that barely change? A script is fine. I’d write it myself.

The test I use: who fixes this at 2am, and are they paid for it? If the honest answer is “one of our engineers, on top of the work they were hired for”, the paid tool usually costs less.

The reverse happens too: teams buy an enterprise tier years before anyone uses a single enterprise feature.

What’s the cheap tool in your stack that’s quietly become someone’s part-time job?