business

Verdict

Submitted 5/23/2026, 6:24:02 PM · Completed 5/23/2026, 6:33:01 PM

6.5
pivot
The idea

I got tired of vague bucket lists, so I built a more realistic version

Show original source text →
I’m building an app called Before. It’s basically a realistic bucket list planner. I always found normal bucket list apps kind of useless because they just store dreams. They don’t tell you whether something is actually realistic. For example, if someone wants to do Japan, Europe, a marathon, Northern Lights, and scuba diving, the real question is not “add this to a list.” The real questions are: Can I afford it? How long will it take? What should I do first? What becomes harder with age? What needs fitness prep? What should wait? What tradeoff am I making? So the app takes basic context like age, income/savings capacity, city/country, vacation days, travel style, life stage, and optional fitness readiness, then creates a roadmap. Each goal gets a reality score, cost estimate, timeline, best timing, preparation steps, and tradeoff warning. Example: “Japan Trip — Stretch — realistic in 14–18 months.” “Marathon — Needs fitness prep.” “Europe — Not realistic yet unless you delay Japan.” I’m testing the beta now. Looking for brutal feedback: \- Is this useful or overthinking? \- Would you enter this kind of information? \- Should this focus only on travel first? \- Would you pay for this if the roadmap was actually good? I can share TestFlight with anyone interested.
TRIZ inventive level: 3/5· Principles: parameter changes, separation
Synthesis verdict
**Pivot**. The idea of a realistic bucket list planner has merit, addressing a genuine pain point in the market. However, the execution and monetization strategy require refinement to justify payment and outperform free alternatives. The app's success hinges on the accuracy and robustness of its roadmap generation algorithm, which is a challenging task. The target audience is identifiable, but data input friction and the complexity of the 'reality score' algorithm are significant risks. A travel-first focus is correct, but the competitive landscape is brutal, and the willingness-to-pay signal is weak at the general bucket list level.

Strengths

  • Addresses a real planning pain point
  • Unique value proposition with realistic cost estimates and timelines
  • Identifiable target audience with disposable income
  • Potential for affiliate commissions on bookings or premium human coaching

Weaknesses

  • High complexity in developing a robust roadmap generation algorithm
  • Data input friction and potential user distrust of automated estimates
  • Severe competitive landscape with free alternatives
  • Regulatory compliance risks with financial data handling
  • Potential for high churn rates due to over-complexity

Best angle

Focus on travel planning and integrate booking-commerce features to increase monetization potential and justify payment.

Panel verdicts

Viability

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

7.0

The app's success hinges on the accuracy and robustness of its roadmap generation algorithm.

Building a basic version of the Before app within 4-12 weeks is feasible for a solo or 2-person team. The core functionality involves taking user input (age, income, location, etc.) and generating a roadmap with reality scores, cost estimates, and preparation steps. This requires developing a simple UI, a backend to process user data, and an algorithm to generate the roadmap. However, creating a robust and accurate algorithm that considers various factors and tradeoffs will be challenging and may require significant development time. The team will need to simplify or prioritize certain features to meet the tight deadline. The beta test is a good step, but the quality of the roadmap and the accuracy of the estimates will be crucial in determining the app's usefulness and user willingness to pay.

Competition

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

7.0

A realistic, context‑aware roadmap turns vague wishes into actionable, financially and physically viable plans, a gap currently unfilled by existing bucket‑list or travel tools.

Existing bucket‑list apps (e.g., Bucket List, Notion templates) only store aspirations without evaluating feasibility, while travel planners (TripIt, Roadtrippers, Wanderlog) focus on itinerary logistics but ignore personal financial, temporal, and physical constraints. A few niche tools (Mint, YNAB) handle budgeting, and fitness apps (Couch to 5K) address preparation, but none combine these dimensions into a single, personalized roadmap. By ingesting age, income, vacation days, fitness readiness, and life stage, Before can generate realistic cost estimates, timelines, and trade‑off warnings, filling a clear gap. The differentiation is real because it moves from static listing to dynamic, data‑driven planning, which is difficult to replicate without robust cost databases, AI modeling, and continuous user‑context updates. Durability hinges on maintaining accurate, up‑to‑date pricing and health‑related data, as well as keeping the onboarding burden low; if the app can automate much of the input (e.g., via calendar or bank‑link integration) and provide clear, actionable steps, the value proposition will stay relevant. However, the market is crowded, and users may resist detailed profiling, so the venture must prove the roadmap's accuracy and ease of use to avoid being dismissed as over‑engineered.

Risk

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

4.0

Before's viability hinges on balancing complexity with user simplicity while navigating financial data regulatory pitfalls.

The concept of Before, a realistic bucket list planner, addresses a legitimate frustration with traditional bucket list apps by incorporating practicality through 'reality scores,' cost estimates, and tailored roadmaps. However, several specific failure modes could demise the venture within 6-12 months: 1. **Regulatory Compliance with Financial Data Handling (Likelihood: 8/10, Impact: 9/10)**: Collecting and processing users' income, savings, and financial capabilities may trigger stringent financial data protection regulations (e.g., GDPR, CCPA). Non-compliance could lead to severe fines. 2. **Churn Due to Over-Complexity (Likelihood: 9/10, Impact: 8/10)**: The depth of required user input (age, income, vacation days, fitness readiness, etc.) might overwhelm potential users seeking a simple, inspirational experience, leading to high churn rates. 3. **No-Budget Customer Base for Premium Features (Likelihood: 7/10, Impact: 8/10)**: If the target demographic (likely younger adults or those with variable incomes) cannot afford premium features (assuming a freemium model), revenue projections may not materialize. **Mitigation Strategies**: Simplify onboarding, ensure transparent financial data handling practices, and offer a basic free version with clear value propositions for upgrades.

Market

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

6.0

The idea captures a real planning pain point but must prove it can outperform free AI tools and justify payment through either superior personalization depth or booking-commerce integration, not just better organization.

The core insight - moving bucket lists from fantasy to actionable planning - is genuinely valuable. The unmet need is real: millions use notes apps, spreadsheets, or abandoned bucket list apps precisely because existing tools lack this reality layer. The target audience is identifiable: 25-40 year olds with disposable income but limited time, experiencing decision fatigue about life experiences. This group already pays for Notion templates, travel planners, and financial wellness apps. However, critical risks emerge. First, data input friction is severe: accurate cost estimates require enormous backend data (Japan trip costs vary 3x by travel style), and users may distrust or ignore automated estimates. Second, the 'reality score' algorithm is deceptively complex - marathon feasibility depends on injury history, local race availability, and training time, not just 'fitness readiness.' Third, the competitive landscape is brutal: free alternatives include ChatGPT (which handles this conversational planning already), travel agents, financial advisors, and simple spreadsheets. The willingness-to-pay signal is weak at the general bucket list level but stronger for specific verticals. Travel-first focus is correct - it's the highest-spend, most emotionally charged category with established booking monetization. The subscription model ($5-15/month) faces churn once users complete their initial roadmap. Better monetization might be affiliate commissions on bookings, premium human coaching, or white-label for financial advisors. The beta phase is essential for validating whether users complete profiles and return after receiving 'depressing' reality scores. Pivot potential exists toward employer benefits (experience planning as wellness perk) or retirement planning (pre-retirement experience acceleration). The founder's instinct to question whether this is overthinking is warranted - execution must be significantly better than free alternatives to justify existence.

Monetization

mistralai/mistral-nemotron(fallback #1)

7.0

Success hinges on delivering highly accurate, actionable roadmaps that users perceive as worth paying for.

The idea addresses a clear pain point - helping users prioritize and plan realistic life goals - with a unique value proposition. The monetization potential is strong if executed well. Pricing could follow a freemium model with a one-time purchase or subscription for advanced features (e.g., $4.99/month or $29.99/year). Conversion could leverage a free trial or limited free roadmap generation, with upsells for detailed planning tools. Unit economics should focus on low customer acquisition costs (CAC) via organic growth (e.g., word-of-mouth, SEO) and high lifetime value (LTV) from engaged users. Margins should be healthy given the digital nature of the product, but cost-to-serve could rise with personalized support or AI-driven recommendations. The key challenge is ensuring the roadmap accuracy and user trust in the recommendations to justify payment.

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