RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Doug Is] Build Intake Form with Supabase Submission and Telegram Notification

Develop an intake form for the landing page that includes client-side validation, sends data to an API route, saves it to Supabase `contact_messages` table with metadata, and sends a Telegram notification with lead details upon successful submission.

Original Source

@@afxjzs | 0 pts | 25d ago

## Parent PRD #5 ## What to build Build the intake form, wire it to Supabase for storage, and send a Telegram notification on submission. This can be developed in parallel with the page design (#7). **End-to-end behavior**: A visitor fills out the intake form on the landing page. On submit, the form data is validated client-side, sent to an API route, saved to Supabase `contact_messages` with source/variant metadata, and a Telegram message is sent to Doug with the lead details. The form shows a success state (placeholder for Cal.com embed, built in #8). **Form fields:** - Name (required) - Email (required) - Phone (optional) - One-line description of your idea (required, short text) - How far along are you? (required, select: "Just an idea" / "I've done some research" / "I have paying customers but no product" / "I have a prototype but need it rebuilt") **API route** (`/api/mvp-lead` or extend `/api/contact`): - Validate required fields - Save to Supabase `contact_messages` table

Discussion

Loading comments...