business

Verdict

Submitted 5/27/2026, 3:46:34 PM · Completed 5/27/2026, 4:27:04 PM

5.5
pivot
The idea

Built a Chrome extension as a final year engineering student — 56 installs, 3 active users, launched on Product Hunt today. Roast it.

Show original source text →
Not a CS student. Final year Electrical Engineering. Kept losing track of everything discussed in Google Meet calls — classes, group projects, internship syncs. Spent 20 mins after every call trying to reconstruct what was said. Got tired of it and built [MeetSnap](https://aman01-hdl.github.io/MeetSnap?utm_source=reddit&utm_medium=post&utm_campaign=ph_launch&utm_content=sideproject). It runs silently in the background during your Meet call, captures the live captions, and converts them into structured Minutes of the Meeting + action items. One click. No copy-paste, and sends a well structured google doc directly in your gmail. **Where I'm at:** * 56 installs since launch * 3 active users (yes I know, brutal honesty) * Launched on Product Hunt today if anyone wants to support a solo indie build **What I genuinely want feedback on:** * Is the onboarding confusing? (I suspect yes) * Does the MoM output format actually feel useful or is it too generic? * Anything that made you uninstall or not even try it? I'm not a developer by training — built this entirely with AI assistance. So if something feels rough, it probably is. Tell me what to fix. Chrome Web Store link + PH link in comments.
TRIZ inventive level: 3/5· Principles: parameter changes, mechanical interaction
Synthesis verdict
**Pivot**: MeetSnap has a viable concept with a clear pain point, but its current execution is marred by onboarding issues and unclear monetization. With refinement, it could be successful.

Strengths

  • Captures a real, emotionally resonant pain point for students and professionals in virtual meetings
  • Early traction with 56 installs despite near-zero marketing
  • Unique value proposition in structured output and one-click Gmail integration

Weaknesses

  • Poor onboarding leading to high drop-off (53 out of 56 installs)
  • Unclear pricing and monetization strategy
  • Regulatory and platform risks due to dependence on Google Meet's caption API

Best angle

Refine onboarding, test pricing tiers, and differentiate the output format to overcome commoditized competition and prove demand beyond early adopters.

Panel verdicts

Viability

meta/llama-4-maverick-17b-128e-instruct

7.0

The main challenge lies not in the technical feasibility of the idea, but in refining the user experience and onboarding process to improve user retention and satisfaction.

The idea of automating meeting minutes and action items is valuable, and the creator has successfully built a functional Chrome extension, MeetSnap, despite not being a CS student. The tool's core functionality - capturing live captions and converting them into structured minutes - is technically feasible with AI assistance. However, the low number of active users (3) compared to installs (56) suggests potential issues with onboarding or user retention. The creator's request for feedback on onboarding, output format, and user experience indicates a willingness to iterate and improve. The fact that the creator is not a developer by training and relied on AI assistance may have resulted in some rough edges, but this also demonstrates the feasibility of building such a tool with modern development tools. Overall, the idea is viable, and with refinement, it could be more successful.

Monetization

mistralai/mistral-medium-3.5-128b

6.0

Define a pricing tier and fix onboarding to prove demand beyond early adopters.

MeetSnap addresses a clear pain point (time wasted reconstructing meeting notes) with a concrete solution (automated MoM + action items). The value proposition is strong for students, freelancers, or small teams, but the current traction (56 installs, 3 active users) signals friction. Pricing is undefined—critical for monetization. A freemium model (e.g., $5/month for unlimited MoMs, free for 5/month) could work, but the conversion path is unclear. The onboarding likely fails to demonstrate immediate value; users may not trust a background app capturing captions. The MoM format’s utility hinges on customization—generic templates may feel impersonal. Unit economics are favorable (low cost-to-serve via automation), but margins depend on scaling beyond niche users. Key gaps: no pricing, weak onboarding, and unproven demand beyond early adopters.

Competition

no model

This agent failed to return a verdict (executor exception: 'NoneType' object has no attribute 'strip'). The synthesis ran with the remaining agents.

Risk

nvidia/llama-3.3-nemotron-super-49b-v1

2.0

MeetSnap's survival hinges on resolving API policy compliance and simplifying onboarding before Google Meet API changes or regulatory actions force shutdown.

MeetSnap faces imminent demise due to regulatory, platform, and customer acquisition challenges. **Regulation (8/10 severity)**: Google's strict API policies might revoke access if MeetSnap's silent capture of captions violates terms, especially without explicit user consent for each call. **Platform Risk (9/10)**: Dependence on Google Meet's caption API means any changes (e.g., removing captions for free accounts) could break MeetSnap. **Churn & No-Budget Customers (7/10)**: With only 3 active users from 56 installs, the onboarding process is likely too complex for non-technical users, and the value proposition might not justify paid conversion for students/interns with limited budgets.

Market

moonshotai/kimi-k2.6(fallback #1)

7.0

The idea captures a real, emotionally resonant pain point with early traction, but its survival depends on whether the structured output is uniquely valuable enough to overcome commoditized competition and whether the onboarding friction can be reduced from a 53/56 drop-off to a viable funnel.

Strong niche demand signal from a validated pain point (meeting chaos, ADHD-adjacent workflow friction) in a high-value B2B adjacency. The 56 installs with near-zero marketing and brutal onboarding suggests genuine pull. Target audience is precise: final-year STEM students, junior PMs, and async-first remote workers who live in Google Meet/Zoom and currently use Notion/Obsidian/Todoist but lack real-time capture. Unmet need is acute—post-meeting reconstruction is a known time sink. However, the current execution risks being a feature not a product: MoM generation is increasingly commoditized (Otter, Fireflies, Zoom AI, Google’s own Duet). The defensibility and willingness-to-pay hinge on whether the 'structured output + one-click Gmail doc' is meaningfully better than copy-pasting Otter summaries, or if the silent background capture and format specificity create a 10x workflow for a subsegment. The 'built with AI assistance' shows in potential rough edges, but also demonstrates modern build velocity. The 3 active users is concerning—it suggests either onboarding failure (likely given the 'confusing' self-assessment) or that the value prop doesn't land post-install. For market size: the TAM for meeting productivity is large ($B+), but the SAM for Chrome-extension-based, student/indie-built, Gmail-integrated tools is small and trust-sensitive. Willingness to pay exists for professionals billing hourly or managing client calls; students have low willingness-to-pay but high virality potential if it becomes a 'study group hack.' Recommendation: double down on the specific output format that differentiates from generic AI summaries, test pricing with a 'pro' tier for teams, and fix onboarding immediately—if 53 of 56 installs churned, the funnel is broken not the idea. Score reflects high potential but unproven retention and monetization path.

Synthesized by meta/llama-4-maverick-17b-128e-instruct (fallback #1) · 5.0s