Don’t Reinvent the Wheel, Question the Price Tag Instead

Sometimes the vibe is already there. The real work is deciding whether it fits.

Lately, I’ve been enjoying how often people are asking a simple question:

“Should I really be paying this much for that?”

Not in a cynical way.
Not in a burn-it-all-down way.
Just with curiosity.

That shift matters.

We see it clearly in the vibeCoding discussions. People aren’t trying to replace everything with AI. They’re questioning why they’re paying for certain things in the first place. The conversations aren’t about hype, rather they’re about trade-offs, ownership and whether the setup actually fits the work being done.

Instead of asking “What tool should I buy?”

More people are asking “What problem am I really solving and what’s the simplest way to support it?”

For a long time in tech, the default move was to assume the price was justified because the logo was big, the pitch was polished and everyone else was doing it. So we accepted the cost and moved on.

What’s changing now is that people are slowing down and looking more closely at what they actually need.

And when you do that, you realise something important:

A lot of functionality isn’t that special.

Email sending.
APIs.
Queues.
Auth.
Search.
Dashboards.
Agents.
Workflows.

These are well-understood building blocks.

So the real question becomes:

Am I paying for capability I actually use, or for comfort, branding and assumed safety?

This is where open source, or building something yourself, enters the conversation.

Not as a silver bullet.
Not because it’s free.
But because it gives you options.

Often, someone has already done the early thinking. They’ve felt the need, shaped the idea and built something solid. Open source can let you benefit from that work instead of paying to reinvent it or locking yourself into a single vendor’s roadmap.

Sometimes the vibe is already there. You just need to decide whether it fits your situation.

Open source can mean:

• You can see what’s really going on
• You can change parts over time
• You’re not tied to one roadmap
• You pay for usage and support, not just branding

And sometimes, building it yourself makes sense too.

Not because it’s clever. But because the thing you need is small, clear and contained.

Building can be the right move when:

• The requirement is narrow
• You want understanding, not just configuration
• The cost of ownership is clear
• You’re comfortable maintaining it

That doesn’t mean everyone should build everything.

Sometimes paying more is the right call:

• When you need strong support
• When compliance matters
• When speed matters more than flexibility
• When fewer decisions is the goal

The point isn’t buy vs build vs open source.

The point is choosing on purpose.

What excites me isn’t people abandoning platforms. It’s people thinking in systems, not price lists.

Have you ever, found an open-source tool where the hard thinking was already done?