business

Verdict

Submitted 5/19/2026, 5:53:51 PM · Completed 5/19/2026, 6:13:26 PM

5.5
pivot
The idea

First time building with AI; I made a tool to stop giving my roommate the same post-date debrief

Show original source text →
My roommate goes on dates. I stay home, she gets back & then we always have the same discussion: "he's good but ..." "what do you think about xyz" Every. Single. Time. "Is it a red flag or he just needs work?" I realized I wanted to make a spreadsheet so I could at least track her shifting ratings based on whether the guy's jawline was doing something that week. Then I realized maybe I could finally jump into the ai wagon & finally learn how to do vibe coding before I get fired because I keep using gpt 5 like a caveman. **Anyway, after a few trials, I came up with "Rate My Situationship":** it lets you build a custom criteria board (dealbreakers, what matters, nice-to-haves), rate someone 1–10 on each, and get a score + tier + AI verdict with more honesty than I was willing to offer. The more extreme on the rating, the better it works *And yeah, this is just a fancy spreadsheet with a weighted average formula.* 🔗 [https://rate-my-situationship.vercel.app/](https://rate-my-situationship.vercel.app/) Not a technical guy, Claude made these reco for the Stack\*\*:\*\* \- Next.js 16 / React 19 \- Claude (Anthropic) for the AI verdict \- Supabase for storing results \- deployed on Vercel. First time I've touched AI APIs: the hardest part was getting the prompts to be funny without tipping into mean or being too generic. Still improving on that. Looking for feedback on the flow, the UX, and whether the verdict output actually lands. I guess my success metric is: would you share the results to your friend? Be as harsh as the app lol Thank you!
TRIZ inventive level: 3/5· Principles: parameter changes, self-service
Synthesis verdict
**Pivot**: The idea of 'Rate My Situationship' has a clear and relatable pain point, but the current implementation and monetization strategy are misaligned with user willingness to pay. The application's core functionality is relatively simple, and the quality of the AI verdict output is crucial to its success. However, the concept treats the debriefing ritual as a solo tool when the magic is social, and people don't want an AI to replace their friend. The 'share to friend' metric is actually a shareability play, not a utility play, which means competing with memes and TikTok. To improve, the developer should focus on refining the AI prompts, enhancing the UX, and exploring alternative monetization strategies such as charging for premium verdicts or social badges.

Strengths

  • The application's core functionality is relatively simple and feasible to build
  • The use of Next.js, React, Supabase, and Vercel is a reasonable tech stack for a web application
  • The integration with Claude AI API is accomplished, and the developer has iterated on prompt engineering
  • The concept taps into a relatable, shareable pain point with a playful, low-friction tool
  • The custom criteria + AI verdict combo is novel and aligns with the viral potential of self-assessment quizzes

Weaknesses

  • The concept treats the debriefing ritual as a solo tool when the magic is social
  • The 'share to friend' metric is actually a shareability play, not a utility play, which means competing with memes and TikTok
  • The application has no retention mechanism, guaranteeing rapid user churn within 6 months
  • The regulatory risks are low, but platform dependence on Anthropic's Claude for AI verdicts introduces a significant single-point failure risk
  • The target audience's budget isn't a concern since it's free, but the real killer is the transient user interest

Best angle

Lean into the 'shareable roast' format, make it explicitly multiplayer/roommate-synced, or pivot to content/entertainment to increase shareability and retention.

Panel verdicts

Competition

nvidia/nemotron-3-nano-omni-30b-a3b-reasoning

6.0

The app's real edge is turning subjective relationship chatter into a shareable, weighted score, but that advantage is easily duplicated, limiting durability.

The concept tackles a clear, relatable pain point - friends endlessly debating the same vague judgments about dates - and offers a structured way to capture those opinions through a customizable, weighted scoring board. This adds a layer of objectivity that a plain spreadsheet lacks, and the AI‑generated verdict attempts to inject humor and perceived honesty, which could increase shareability. However, the core differentiation is thin: the app is essentially a weighted‑average spreadsheet with a prompt‑engineered AI overlay, both of which can be replicated with minimal effort. Competitors such as generic rating tools (e.g., Google Forms/Sheets templates), niche dating‑feedback platforms like "The Grade" or "Happn" (which already provide rating‑style feedback), and even community‑driven rating bots on Discord or Telegram serve the same need without requiring a dedicated UI. Because the technical moat is low - Next.js, React, Supabase are off‑the‑shelf technologies - and the AI verdict relies on prompt engineering that can be copied or improved by anyone, the differentiation is neither unique nor durable. Market demand exists for quick, shareable rating experiences, but the niche is small and the value proposition quickly erodes as users discover that the AI output is generic and the underlying calculations are trivial. Consequently, while the idea is clever and may attract early adopters for its novelty, its long‑term defensibility and scalability are weak, justifying a moderate‑low score.

Viability

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

8.0

The application's core functionality is relatively simple, but the quality of the AI verdict output is crucial to its success.

The idea is feasible for a solo or 2-person team to build in 4-12 weeks. The core functionality is a weighted average formula, which is straightforward to implement. The use of Next.js, React, Supabase, and Vercel is a reasonable tech stack for a web application. The integration with Claude AI API is the most complex part, but the developer has already accomplished this with some effort. The main challenge was crafting suitable prompts, which is a task that requires iteration and refinement. The existing prototype demonstrates that the concept can be built. However, the success of the application depends on the quality of the AI verdict output and the overall user experience. The developer's success metric, 'would you share the results to your friend,' is a good indicator of the application's potential. To improve, the developer should focus on refining the AI prompts and enhancing the UX.

Monetization

mistralai/mistral-medium-3.5-128b

7.0

Monetize the shareability - charge for premium verdicts or social badges, not the core tool.

The idea taps into a relatable, shareable pain point (dating ambiguity) with a playful, low-friction tool. The custom criteria + AI verdict combo is novel and aligns with the viral potential of self-assessment quizzes. Monetization is unclear - currently a free, ad-free toy. Pricing could include: (1) $2.99 one-time for premium templates (e.g., 'Red Flag Detector'), (2) $4.99/month for unlimited AI verdicts + shareable 'tier badges' (e.g., 'Certified Situationship'), or (3) affiliate links to dating apps/books. Unit economics: Cost-to-serve is minimal (Supabase free tier + Claude API ~$0.01/verdict). Conversion path: Free tier with 3 verdicts/month → paywall. Gross margin ~90% if priced as SaaS. Risks: Low retention (one-and-done use case), competition from free spreadsheets or TikTok quizzes. UX is solid but needs a 'share results' CTA to drive virality.

Risk

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

2.0

Transient novelty with no retention mechanism guarantees rapid user churn within 6 months.

The concept's novelty wears off quickly, leaving a shallow, non-essential tool. Users may share results once for entertainment, but the lack of actionable insights or meaningful engagement loops will lead to rapid churn. Regulatory risks are low, but platform dependence on Anthropic's Claude for AI verdicts introduces a significant single-point failure risk if their API terms change or costs increase substantially. The target audience's budget isn't a concern since it's free, but the real killer is the transient user interest.

Market

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

4.0

The value is in the shared friend conversation, not the scoring - people want to gossip together, not get an AI verdict alone.

The core problem is real but the solution is misaligned with willingness to pay. The 'debrief with roommate' ritual is genuine and widespread among women 22-35, but the app treats it as a solo tool when the magic is social. People don't want an AI to replace their friend - they want content to share WITH their friend. The 'share to friend' metric is actually a shareability play, not a utility play, which means you're competing with memes and TikTok, not spreadsheets. The audience is large (millions of women in situationships) but the product as built serves the wrong moment: pre-debrief solo rumination instead of the actual social ritual. The 'honesty' framing also risks feeling robotic or mean at exactly the wrong time. Monetization path is unclear - no one pays for this, ads would kill the intimacy, and the data isn't defensibly valuable. The vibe-coding origin shows: it's a technically competent wrapper around a weighted average with a Claude prompt, which means zero defensibility. Competitors exist (relationship apps, Co-Star's social features, even shared Google Docs) and do the social part better. What could work: lean into the 'shareable roast' format, make it explicitly multiplayer/roommate-synced, or pivot to content/entertainment (TikTok filter, not standalone app). As built, it's a fun weekend project that solves a real ritual poorly by removing the human from it. The stack is overbuilt for what it is, and 'learning vibe coding' is not a business strategy. Harsh truth: your roommate is the product, not the spreadsheet.

Synthesized by meta/llama-3.3-70b-instruct · 32.2s