FeatureAudit: User-Reported vs. Internally-Tracked Feature Usage Gap Finder

The Problem

A persistent pain documented in r/indiehackers product threads is that founders build feature usage dashboards from event tracking, but those dashboards only capture what engineers remembered to instrument — leaving a graveyard of features that users mention in support tickets and churn interviews but that show zero usage in analytics because the tracking event was never fired. FeatureAudit cross-references support ticket text, cancellation survey responses, and NPS verbatims against the product's instrumented event list to surface 'dark features' — capabilities users talk about but that analytics cannot see — so founders know where their tracking has blind spots before making cut-or-double-down decisions.

Target Audience

Solo SaaS founders and small product teams who use Mixpanel, PostHog, or Amplitude alongside Intercom or Zendesk support

Monetization Angle

$29/mo for up to 500 support tickets/month analyzed; $79/mo for unlimited with Slack alerts when a dark feature is detected

Recommended Tech Stack

Why Now

PostHog's rapid adoption among indie SaaS founders means more teams have partial event tracking in place but no tooling to audit its completeness — the gap between 'we have analytics' and 'we trust our analytics' is now acute.

MVP Scope

A one-time CSV upload tool: paste your Mixpanel event list and upload a Zendesk ticket export; the LLM returns a ranked list of feature names mentioned in tickets that don't appear in the event schema.

AI Angle

LLM canonicalizes messy user language ('the export thing', 'that button on the left') into normalized feature names that can be fuzzy-matched against the instrumented event taxonomy.

Primary Risk

Integration depth required (support tool + analytics tool) creates a high setup friction that may kill activation before users see the first insight.

Validation Checklist

• Post a 'How do you know if your feature analytics have blind spots?' thread on r/indiehackers and measure how many founders describe the exact gap
• Build a free manual version: accept a CSV of support tickets and a plain-text event list, run the LLM analysis, and email the report within 24 hours to validate demand before building integrations
• Reach out to 15 PostHog community members who have posted about analytics gaps in PostHog's Slack and offer free audits
• Track whether beta users actually change their instrumentation after seeing the report — if nobody adds missing events, the insight isn't actionable enough to monetize

Who Would Pay For This

Likely buyers are people already trying to solve this problem with manual workarounds. Start with Solo SaaS founders and small product teams who use Mixpanel, PostHog, or Amplitude alongside Intercom or Zendesk support and validate urgency before adding secondary features.

First 10 Users

Find the first 10 users by searching for recent complaints around "SaaS product analytics" in Multiple Sources, developer communities, GitHub issues, and niche Slack or Discord groups. Offer a concierge version first: manually solve the workflow for a few users, then automate only the repeated steps.

Idea Playbooks

This opportunity also appears in curated IdeaGenius playbooks for builders comparing adjacent markets.

More Developer Search Paths

Why This Idea Has Legs

• Sourced from real discussions and complaints across Reddit and social media
• Cross-checked against recurring demand signals in the IdeaGenius archive
• Difficulty rated Medium — buildable by a solo developer or small team
• Clear monetization path from day one

Generate Your Full Project Spec

Get a complete blueprint for building this app — tech stack, database schema, API endpoints, go-to-market plan, and more. Generated by AI in seconds. Download as Markdown.