General
Share and discuss tech, products, business, startups, or product recommendations
Start new thread

Would you pay for a product you could easily rebuild yourself?

by•

As developers, it’s easy to fall into the “I could just code this in a weekend” mindset.

But I’ve realized time, maintenance, and support often cost way more than the price of the tool.

Still, sometimes I just can’t justify paying for something I know I could make.

Where do you draw the line what makes you buy instead of build?

299 views

Add a comment

Replies

Best

I can make amazing Pizza at home.

But, 99% of the time, I'd order it from Dominos. Why? Convenience.

That's how the software works as well.

 Great analogy! :)

 for real great analogy.

I think this problem got even bigger with AI - it’s easier than ever to build things quickly.

But I’ve learned not to jump on every "I can make this myself" idea.

Before I build, I ask myself:

- How much of this tool do I actually need?

- How long would it take to make something good enough for my use case?

- Are there solid open-source options already?

If I only need a small part of the product, or I think I can add something unique (or need deep customization), that’s when I’ll build. Otherwise, I will buy.

 100% agreed! Especially with vibe coding, a lot of builders get into the mindset of building it on their own. But the real problem is not building it, it's putting it on production and then scaling. And that is literally the point where most AI projects stall right now.

 that's a good point. I have been in this trap as well of "i can make this myself".

I'll keep your questions in mind as well

Agree 100%.

I think this purely depends on the mindset and possibilities of individuals. I am that person who (if knows how) will build it itself.

 hm, I see, so is not about the time you're consuming of building it?

 If I will be using the tool repetitively, it will pay off. So I am taking it long-term.

yea definitely

Not at all because it's all about convenience because even if I can build it but I don't if I can trade my time against the money.

 true, true

Nope, if it in not my core business I would not because it is waste of time and effort

 Understandable

If it’s not a core part of my product or something I’d genuinely enjoy building, I’ll pay and save my time. Convenience is worth a lot. Energy’s better used where it actually moves the needle.

I usually draw the line at time-to-value.
If building something will slow my team down or distract us from core goals, I’d rather pay for it.
But when the feature is central to our product or something we need deep control over, that’s when we build.

As a dev ,I would say the build the things if it is used for the main purpose and see the vision whether it is worth building the product.
Before? Yes Now? Absolutely not Because behind every "I can code this, I can make this" is ways someone crying for rest. I'd rather just pay for it and make life easier for me 😊😊

I am starting to think that I have probably been b@nned, because I never get a reply to my comments, even if I am the first to drop one. Others get replies to their comments, and I don't.

If it saves me time and mental energy, I’ll pay. Even if I could build it, I’d rather focus on what moves my own product forward.

12
Next
Last