TL;DR: A cluster of indie developers ship apps with no behavioral analytics at all — no view of what users do, no funnels, no retention curves — and discover it only when they need the data and it isn't there. The heavy suites feel like too much to integrate, and their pricing can collapse on the first paid step. Across 42 threads in PainHunt (a small but consistent signal), the gap is a genuinely lightweight, privacy-respecting analytics SDK for small apps — not another enterprise platform.
The evidence
PainHunt holds 42 posts on product-analytics pain scoring 10 or higher out of 15, average score 11.3/15, average commercial-intent score 7.0/10, and 34 of them are from the last six months. This is a small sample — worth saying plainly up front rather than dressing it up — spread across Reddit (12), Medium (8), WeWorkRemotely (6), Mastodon (6) and a BlueSky and HackerNews tail. Treat it as a real-but-narrow signal, not a mass market.
Two clusters recur.
No instrumentation at all. Indie developers, often with several small apps, describe having no visibility into user behavior, no funnel data to see where people drop, and no retention curves to measure churn. The only remaining signal is the support inbox — and, as one puts it, almost nobody writes in to complain. Someone facing an App Store Connect deadline notes there's no way to backfill the data they never collected. The problem isn't a bad tool; it's that instrumentation felt like too much effort to set up, so it never happened.
Pricing that punishes the upgrade. The second cluster is people who did adopt a suite and hit the wall. The vivid version: a free tier of 20M events/month dropping to 10K on the first paid step — a 2000x reduction described as a trap-door rather than an upgrade path. For a small app with modest revenue, that math ends the relationship.
The commercial signal is narrow but coherent: small developers who will pay a little for something that is genuinely light to add and doesn't punish them for growing.
Why now
Solo and small-team app development kept growing. More people ship several small apps each, and the per-app instrumentation cost — integration time, SDK weight, privacy review — is exactly what a solo dev defers. The "I have no data" moment arrives repeatedly across a portfolio.
Privacy expectations rose. App-store and OS privacy rules make heavyweight, telemetry-hungry SDKs a liability. A lightweight, privacy-respecting option is more attractive now than when analytics meant "phone everything home."
Event-based pricing became the norm — and the trap. As suites moved to metered event pricing, the free-to-paid cliff got steeper, which is what turns a happy free user into a churned one at the worst moment.
The wedge
The crowded build is "a product analytics platform." The threads point at a narrow segment.
- Minimal-integration SDK for small apps. The whole pitch is low effort to add — funnels and retention with a few lines, privacy-respecting by default. The product is the absence of an integration project, which is the exact reason indie devs skip analytics today.
- Transparent, gradual pricing. Increase event limits when someone upgrades rather than dropping them; make the paid step a step, not a cliff. Positioning explicitly against the trap-door is sharper than a feature list.
- A defined, modest buyer. Indie and small-team developers with several small apps — a narrow segment with a concrete pain and modest but real willingness to pay. Don't pitch it as an enterprise platform; pitch it as the analytics you'll actually bother to add.
Risks and honest caveats
- The sample is small (42). This is the most important caveat: treat it as a narrow, validate-before-you-build signal, not proof of a large market. The next step is talking to indie devs, not writing code.
- The category is crowded and mature. Mixpanel, Amplitude, PostHog and open-source options are entrenched. Entering means being demonstrably lighter and fairer on price for the small-app segment, not merely present.
- Willingness to pay is modest. At 7.0/10 and an indie buyer, the revenue per customer is small; the business only works at volume or with a very low cost to serve.
- "Lightweight" and "useful" pull apart. The less you instrument, the less you can show; the honest product finds the few metrics (activation, retention) that matter and resists becoming another heavy suite.
How to validate this further
Read the underlying threads in the Pain Point Browser, and pressure-test the indie-segment wedge with the Idea Validator. Related reading: conversational product analytics and silent churn early warning.