Are indie makers actually bad customers?

About a 7/10. The "time but no money" framing is real for a large chunk of the audience but it's not the whole story. Indie hackers who are post-revenue are actually great customers — they pay, they churn less because they built something themselves and understand value, and they refer. The issue is the pre-revenue cohort drags down the average. If you price and position for where indie builders are going rather than where they are, it changes the math considerably.

both. we sell to indie creators and to agencies/brands. totally different dynamics. indie users will try your product day one, give you honest feedback, tweet about you without asking. but they'll also churn fast if something free or cheaper shows up. they're amazing for learning what to build, terrible for predictable revenue. agency clients take weeks to close but once they're in they stay. they don't have time to switch tools every month. if you're early stage i'd still start with indie users honestly. the feedback speed is worth more than the revenue at that point. just don't fool yourself into thinking that's your long term business. use them to learn, then move upmarket when your product is solid.

I'm just a newbie, reading every comment and learning

I've been on both sides of this. Ran a VC-backed company with hundreds of people - we were enterprise customers spending serious money on tools. Now I'm building solo as an indie maker.

The difference isn't that indie makers are "bad" customers. It's that our buying criteria is completely different. At the startup I'd approve a $500/mo tool because it saved one engineer half a day per week. Now I'll spend hours building something myself to avoid a $20/mo subscription - not because I'm cheap, but because I genuinely enjoy the building part.

The real filter: does your tool solve something I can't reasonably build myself AND that I need right now? If yes, I'll pay instantly. Stripe, Vercel, Fly - shut up and take my money. But "project management for solopreneurs"? I have a text file and it works fine.

The DIY instinct isn't a bug. It's the whole reason we're indie makers in the first place.

Indie makers are not bad customers, they’re just harder to bullshit. They’ll def pay for tools that save time, reduce friction, or help them make money though.

Honestly, as one of the "indies" being talked about — it's mostly true. I run my thing as a side project, so I'll happily pay $5/mo but flinch at $50/mo even when the ROI is obvious. It's not that we're bad customers, it's that we're spending after-tax money from a day job, not a company expense line. Different buyer, different game.

Been on both sides. As a maker I'm a nightmare customer - opinionated, cheap, always asking for discounts. But I close in 5 minutes. No procurement, no legal, no committee. That speed is underrated.

I'd push back on the framing a bit. It's not that indie makers are bad customers -- it's that they're a very specific type of customer, and most tools aren't built for their economics.

Having sold both to indie founders and to small teams, the pattern I've seen is pretty clear:

Where indie makers are great customers:

• Sub-$30/mo tools that save them real, measurable time
• Anything that directly helps them ship faster or acquire users
• They convert fast, give brutally honest feedback, and become evangelists if the product is good

Where they're bad customers:

• Anything that feels like a "nice to have" vs "need to have"
• Tools priced for teams (even $50/mo hits different when it's your grocery money)
• Products that require a learning curve -- they don't have time to learn your tool, they have a product to build

The DIY instinct is real, but I think it's actually a signal worth paying attention to. If an indie maker says "I could just build this myself," what they're really saying is that the value proposition isn't specific enough. Nobody builds their own Stripe. Nobody builds their own analytics. They DIY when the tool feels 70% useful but not 100% essential.

The question I'd ask: what's the specific, measurable outcome your product delivers? If you can put a dollar amount or time savings on it, indie makers will pay. If the value is abstract ("better workflows", "improved productivity"), they'll bounce.

The "time but no money" framing misses the real question, which is: does your product sit inside the workflow or outside it? Indie makers will pay 20 bucks/mo all day for something wired into their daily process. They will never pay the same for something they open once a week. When a founder says "I'll just build it myself" that tells you your product feels adjacent to their work, not embedded in it. The Reddit commenter is describing a positioning failure, not a customer segment failure.

"Time but no money" is a useful heuristic but it misses a real segment: indie makers who are already paying customers for professional tools.

The pattern I've seen from running paid acquisition campaigns targeting bootstrapped founders: they're one of the highest-conversion audiences in the $15-50/month bracket. They evaluate fast, trial quickly, and if the value is clear in week one, they convert without needing a sales call.

Where they drop off is above ~$79/month and anything that takes more than 10 minutes to understand. The attention cost is real — they're wearing 5 hats. But that's a UX and positioning problem, not a customer quality problem.

The "bad customers" conclusion usually comes from founders who built for enterprises, tried to sell down-market without adjusting their funnel, and got burned. The acquisition playbook for indie makers is different: community-led first (IH, Product Hunt, specific subreddits), paid amplification second. Cost-per-acquisition is actually lower than most B2B audiences because the audience is concentrated on a few platforms — high signal, low waste.

One useful reframe: indie makers are the first-mover segment for most successful B2B tools. Not the biggest revenue — the proof of concept that makes closing bigger customers easier later. That's a different ROI calculation entirely.

True part: Many indie hackers are bootstrapped, so budgets are tight.

False part: They're not "not great customers." They're selective customers.

Indie hackers will pay for something if:

It solves a real problem they have
It saves them time or money
They understand the ROI
It's priced fairly

They won't pay for:

Hype
Features they don't need
Vaporware
Overpriced solutions

Honestly, it depends entirely on what you're selling and at what price point.

I've been on both sides — as an indie maker buying tools and building for others. Here's what I've noticed:

Indie makers are fantastic customers for anything under ~$30/mo that saves them real time. They'll pay quickly, give you honest feedback, and tell their friends. They're also incredibly forgiving of rough edges if the core value is there.

Where they're "bad" customers is for enterprise-y tools priced at $200+/mo. At that point, a solo founder will 100% try to build it themselves or find a free alternative. That's not because they're cheap — it's because their economics genuinely don't support it yet.

The other thing people miss: indie makers churn fast but they also come back fast. Someone cancels because their project didn't work out, then resubscribes 3 months later with a new idea. Lifetime value is more interesting than monthly retention if you zoom out.

The Reddit commenter was half right. It's not that indies have no money — it's that they have very specific money for very specific pain points. If your tool directly makes or saves them money, they'll pay. If it's a nice-to-have, they'll DIY.

I'd say the real question isn't "are indie makers bad customers" but "is your pricing aligned with what a solo founder's economics can support?"