Building relationships with customers through support didn't turn out as hoped
An indie developer of a paid podcast app describes how personally answering every support email, hoping to build loyalty and rapport, mostly led to frustration on both sides. Commenters argue over whether the real problem is the developer’s dismissive tone and unwillingness to prioritize user requests, or the inherent limits of time, money, and one-person “side project” support. The thread broadens into a debate on subscription fatigue, whether good support truly differentiates consumer apps, and how much ongoing care users can reasonably expect for low-priced software.
Support approach and user rapport
- Many commenters felt the described support style was inherently antagonistic: elaborate, polite explanations of “no” (no bugfix, no feature, no pricing change) predictably worsen user sentiment.
- Several argued that telling users “we won’t change anything” or “this is low priority” might be honest but is guaranteed to feel dismissive and disrespectful.
- Others defended the constraints: solo/side‑project, limited time, can’t chase every edge-case bug or implement every feature; some criticism was seen as over‑harsh or naïve about tradeoffs.
- Broad agreement that trying to build “relationships” through support, especially around frustrations (bugs, pricing), rarely works; the real way to build loyalty is by improving the product.
Bug reports, telemetry, and process
- Disagreement on unreproducible bugs: some say there is always time if you value users; others say this is unrealistic at scale.
- Several suggested better logging/telemetry and in‑app feedback to reduce reliance on manual reports; others cautioned that deep telemetry conflicts with privacy norms.
- A recurring theme: if bug reports feel like a waste, that may indicate weak diagnostics and QA, not “bad users.”
Subscriptions vs one‑time pricing
- Large subthread on pricing: many are fatigued by subscriptions for self‑contained apps and want one‑time or per‑version licenses, sometimes with optional upgrades.
- Arguments against subscriptions:
- Users often don’t care about continuous new features; they just want the existing version to keep working.
- Bugfixes are seen as part of what was already paid for.
- One‑time pricing plus future paid upgrades can be sustainable, just a different risk profile.
- Arguments for subscriptions:
- Ongoing costs exist even for “finished” apps (platform fees, hardware, support, maintenance).
- One‑time sales are a gamble; recurring revenue better matches reality of continued work.
- Critics of subscriptions often ignore what’s required to run a stable business.
B2B vs B2C support dynamics
- B2B SaaS operators reported much more positive support experiences: customers better understand complexity and cost, and personal support can be a true differentiator.
- For consumer apps, support is often a cost center with low marginal return; highly vocal users can dominate time without corresponding revenue.
General takeaways from the thread
- Common wisdom: support should be fast, professional, bounded, and mainly a way to gather signal, not to win affection.
- Several saw the article as a useful honest post‑mortem; others felt it rediscovered well‑known lessons and underplayed arrogance in dismissing user feedback.