Prompt Details
Model
Chat - (gpt-5.6)
Token size
2,386
Example input
[Describe the product, feature, or product idea]: AI personal finance planner that creates personalized monthly spending and saving plans
[Describe the target users, customer segment, market or buyer]: Young working professionals aged 22-35
[Describe the problem, pain point or unmet need]: Users struggle to understand where their money goes and how much they can safely spend or save each month
[Revenue, growth, retention, acquisition, efficiency, market entry, etc.]: Increase paid subscriptions and monthly retention
[Budget, team size, timeline, technology, market, compliance, resources or other limitations]: 4-person team, 10-week timeline, limited development budget, privacy-sensitive financial data
Example output
PHASE 1 - PRODUCT CONTEXT RECONSTRUCTION
π― Product Objective
Help users understand their monthly finances and make practical spending and saving decisions.
π Facts
- Product is currently a prototype.
- Target users are young working professionals.
- The core problem involves financial planning complexity.
- Business goal is paid subscription growth and retention.
- Team has limited time and budget.
- Financial information creates elevated privacy and trust requirements.
π Assumptions
- Users will trust an AI system with financial information.
- Users will connect or manually provide enough data for useful recommendations.
- Personalized recommendations are more valuable than generic financial education.
- Users will pay for ongoing financial planning.
- Users will regularly return to the product.
β οΈ Critical Unknowns
- What financial decisions cause the most stress?
- Will users actually follow AI recommendations?
- Is automatic account data necessary for value?
- How frequently will users use the product?
- What subscription price feels justified?
- What level of privacy and transparency do users expect?
π§ Product Decision
Do not immediately build bank integrations or a large financial dashboard.
First validate whether users find the personalized planning experience valuable using manually entered or imported data.
---
π₯ PHASE 2 - CUSTOMER & USER ANALYSIS
Primary User
Young professionals managing their own income and expenses.
Buyer
The same individual using the product.
π― Jobs-to-be-Done
"When I receive my monthly income, I want to know how much I can spend, save, and allocate toward my goals so I can make financial decisions confidently."
π₯ Pain Points
- Unclear spending patterns
- Difficulty creating realistic budgets
- Irregular expenses
- Saving inconsistently
- Too many financial categories
- Lack of personalized guidance
- Difficulty staying accountable
π Desired Outcomes
Users want to:
- Understand their financial position
- Control unnecessary spending
- Save consistently
- Plan for upcoming expenses
- Reach personal financial goals
- Feel more confident about monthly decisions
π Current Alternatives
- Spreadsheets
- Notes apps
- Banking apps
- Budgeting applications
- Manual calculations
- Generic financial advice
π Most Important Problem
Users struggle to turn raw income and expense information into simple, actionable monthly decisions.
The product should therefore focus on decision assistance, not simply expense tracking.
---
π₯ PHASE 3 - PROBLEM VALIDATION
Factor| Assessment
Problem Severity| Medium
Frequency| High
Urgency| Medium
Existing Alternatives| High
Willingness to Pay| Unknown
Business Relevance| High
Evidence Strength| Medium
π§ͺ Validation Question
The key question is:
Will users repeatedly use personalized financial planning enough to justify paying for it?
A budgeting tool may be useful but still fail commercially if users only open it once or twice.
π¨ Major Risk
The product could become another dashboard that users enjoy initially but stop using after the first month.
Therefore, retention should be treated as a core product hypothesis from day one.
---
π PHASE 4 - VALUE PROPOSITION DESIGN
Core Value Proposition
Turn your income, expenses, and financial goals into a simple monthly action plan.
Primary Customer Benefit
Instead of forcing users to interpret financial data themselves, the product tells them:
- What they can safely spend
- What they should save
- Which upcoming expenses matter
- Whether they are on track toward their goals
π― Differentiation
Avoid positioning it as:
"An AI budgeting app."
That is too generic.
A stronger positioning is:
"Your monthly money decision planner."
Why Customers Should Care
Users don't necessarily want more financial data.
They want clear decisions from their financial data.
---
π§ PHASE 5 - PRODUCT STRATEGY
π Product Vision
Make everyday personal financial planning simple enough that users can confidently make better monthly money decisions.
π― Product Mission
Transform financial information into personalized, understandable actions.
Strategic Objectives
1. Create a fast onboarding experience.
2. Generate useful personalized plans.
3. Build recurring monthly engagement.
4. Establish trust through transparency.
5. Convert active users into subscribers.
Core Use Case
Monthly financial planning.
Product Principles
- Simplicity over complexity
- Explain recommendations
- User control over automation
- Privacy by design
- Actionable insights over excessive charts
β What the Product Should NOT Do Initially
Do not attempt to become:
- A full investment platform
- A lending marketplace
- An insurance marketplace
- A tax filing platform
- A cryptocurrency platform
- A banking replacement
These directions would significantly increase complexity and regulatory considerations.
---
π§© PHASE 6 - FEATURE & REQUIREMENT ARCHITECTURE
π’ MUST-HAVE FEATURES
1. Financial Profile Setup
User problem: The system needs basic financial context.
User value: Recommendations become personalized.
Business value: Creates the foundation for the core experience.
Complexity: Low.
Risk: Users may abandon onboarding.
Success condition: Users complete setup quickly.
---
2. Monthly Plan Generator
User problem: Users don't know how to allocate their income.
User value: Converts information into a concrete plan.
Business value: This is the primary product value.
Complexity: Medium.
Risk: Recommendations may feel unrealistic.
Success condition: Users understand and consider the plan useful.
---
3. Financial Goal Planner
User problem: Users struggle to connect daily spending with longer-term goals.
User value: Creates motivation and direction.
Business value: Supports recurring engagement.
Complexity: Medium.
---
4. Monthly Progress Review
User problem: Users need feedback on whether they followed their plan.
User value: Encourages continued usage.
Business value: Potential retention driver.
Complexity: Medium.
---
π‘ IMPORTANT FEATURES
- Spending-category analysis
- Upcoming expense planning
- Personalized reminders
- Recommendation explanations
- Monthly progress visualization
π΅ FUTURE OPPORTUNITIES
- Account synchronization
- Household planning
- Advanced financial forecasting
- Multi-currency support
- Personalized financial education
π΄ FEATURES TO REJECT FOR NOW
- Investment trading
- Loans
- Credit products
- Cryptocurrency trading
- Complex tax automation
These features are outside the core product problem.
---
βοΈ PHASE 7 - FEATURE PRIORITIZATION
Framework: Impact vs Effort
This is appropriate because the team has only 10 weeks and needs to protect MVP scope.
Feature| Customer Impact| Effort| Decision
Financial profile| High| Low| π’ Build
Monthly plan generator| Very High| Medium| π’ Build
Goal planner| High| Medium| π’ Build
Monthly review| High| Medium| π’ Build
Spending analysis| Medium| Medium| π‘ Build if capacity allows
Bank synchronization| High| High| π΅ Later
Household planning| Medium| High| π΅ Later
Investment features| Low strategic fit| Very High| π΄ Reject
Tax automation| Low strategic fit| Very High| π΄ Reject
π Priority Principle
Build the smallest system that proves:
Input financial information β receive useful plan β take action β return next month.
---
π PHASE 8 - MVP DEFINITION
MVP Objective
Determine whether personalized monthly financial plans create enough value to drive repeated usage.
Essential User Journey
1. User creates financial profile.
2. User enters income and recurring expenses.
3. User adds one or more financial goals.
4. Product generates monthly allocation plan.
5. User reviews recommendations.
6. User adjusts the plan.
7. User tracks progress.
8. Product provides monthly review.
β MVP Exclusions
- Automatic bank connections
- Investment management
- Complex financial forecasting
- Financial marketplace
- Advanced social features
π― MVP Success Criteria
Potential validation targets:
- High onboarding completion
- Strong percentage of users who generate their first plan
- Users returning for a second monthly planning cycle
- Positive usefulness ratings
- Evidence that users follow or adjust recommendations
- Early willingness to pay
The exact thresholds should be determined through testing rather than invented as guaranteed benchmarks.
---
π PHASE 9 - PRODUCT REQUIREMENTS
Feature: Monthly Plan Generator
π€ User Story
As a working professional, I want to receive a personalized monthly financial plan so that I know how to allocate my income toward spending, saving, and goals.
Functional Requirements
1. User enters monthly income.
2. User enters recurring expenses.
3. User provides variable spending information.
4. User defines financial goals.
5. System calculates available allocation.
6. AI generates an understandable recommendation.
7. System explains the major recommendations.
8. User can modify allocations.
9. System updates the plan based on changes.
10. User can save the final plan.
β
Acceptance Criteria
- User cannot generate a plan without required financial information.
- The plan clearly displays major allocations.
- Recommendations include understandable explanations.
- User can modify suggested allocations.
- Updated allocations are reflected immediately.
- Saved plans remain available for future review.
β οΈ Edge Cases
- Income is missing
- Expenses exceed income
- User enters unrealistic values
- User has irregular income
- User has no financial goal
- User changes income after creating a plan
π Analytics Events
- "profile_created"
- "plan_generation_started"
- "plan_generated"
- "plan_edited"
- "plan_saved"
- "goal_created"
- "monthly_review_completed"
- "subscription_started"
Definition of Done
Feature is designed, implemented, tested, instrumented, reviewed for privacy considerations, and validated with target users.
---
π PHASE 10 - KPI & METRICS FRAMEWORK
β North Star Metric
Monthly Active Users who complete a financial planning cycle.
This is stronger than simply measuring app opens because it represents meaningful product value.
Primary KPI
Percentage of users completing a second monthly planning cycle.
This tests whether the product creates recurring value.
Activation Metrics
- Profile completion
- First plan generated
- First goal created
- First plan saved
Engagement Metrics
- Monthly planning sessions
- Plan modifications
- Goal updates
- Progress reviews
Retention Metrics
- Second-month planning rate
- Third-month planning rate
- Monthly active planning users
Conversion Metrics
- Free-to-paid conversion
- Trial-to-paid conversion
Revenue Metrics
- Monthly recurring revenue
- Average revenue per subscriber
- Subscriber retention
Quality Metrics
- Recommendation usefulness rating
- Recommendation edit rate
- Error reports
- Support requests
π¦ Guardrail Metrics
- Privacy complaints
- Incorrect recommendation reports
- User trust score
- Account deletion rate
Key Decision
If engagement is high but users don't return monthly, improve the recurring planning loop before adding more features.
---
π§ͺ PHASE 11 - VALIDATION & EXPERIMENTATION
Experiment 1 - Prototype Usability Test
Hypothesis
Users can understand and act on a personalized financial plan without extensive explanation.
Method
Show the prototype to target users and ask them to create and interpret a monthly plan.
Success Criteria
Users can independently understand:
- How much they can allocate
- What they should save
- How their goals affect the plan
Failure Criteria
Users are confused about recommendations or cannot explain why the plan was generated.
Decision
Improve the planning experience before increasing functionality.
---
π§ͺ Experiment 2 - Concierge MVP
Hypothesis
Personalized planning itself creates enough value to drive repeat usage.
Method
For a small group of users, generate personalized plans with significant human assistance behind the scenes.
Measure
- User satisfaction
- Plan usefulness
- Follow-through
- Repeat usage
- Willingness to pay
Decision
If users repeatedly use the service and value the outcome, automate the highest-value parts.
---
π° Experiment 3 - Pricing Test
Hypothesis
Users will pay for ongoing personalized financial planning.
Method
Test multiple subscription propositions with qualified users.
Measure
- Conversion
- Trial completion
- Subscription activation
- Cancellation feedback
Important
Do not assume that high usage automatically means willingness to pay.
---
πΊοΈ PHASE 12 - PRODUCT ROADMAP
π’ NOW - Weeks 1-4
- Financial profile
- Monthly plan generation
- Goal creation
- Basic plan editing
- Core analytics
- Prototype validation
π‘ NEXT - Weeks 5-7
- Monthly review
- Better recommendation explanations
- Progress tracking
- Improved onboarding
- Pricing validation
π΅ LATER - Weeks 8-10+
Only pursue based on validation:
- Account synchronization
- Advanced forecasting
- Household planning
- More personalization
π¨ Roadmap Rule
Do not automatically use the entire 10-week period for feature development.
Reserve capacity for:
Testing β Learning β Iterating.
---
π€ PHASE 13 - CROSS-FUNCTIONAL EXECUTION PLAN
π§ Product
- Define hypotheses
- Conduct interviews
- Prioritize experiments
- Analyze product behavior
π» Engineering
- Build planning engine
- Build profile system
- Implement analytics
- Maintain secure data handling
π¨ Design
- Simplify onboarding
- Design financial-plan experience
- Make recommendations understandable
- Reduce cognitive load
π Data
- Define event taxonomy
- Build retention analysis
- Track planning-cycle completion
π£ Marketing
- Focus on financial clarity
- Avoid exaggerated financial promises
- Test positioning and acquisition messaging
π€ Customer Success
- Collect user feedback
- Identify trust issues
- Understand cancellation reasons
---
π PHASE 14 - LAUNCH & GO-TO-MARKET PLAN
Launch Objective
Acquire an initial group of users and determine whether the product creates recurring financial-planning behavior.
π― Target Audience
Young professionals who:
- Have regular income
- Want better financial organization
- Already attempt budgeting
- Find traditional budgeting tools complicated
Positioning
"Know exactly what your money should do this month."
Launch Channels
- Content marketing
- Personal finance communities
- Short-form educational content
- Referral programs
- Product-led acquisition
Beta Strategy
Start with a small beta group rather than a large public launch.
Beta Goals
- Identify onboarding friction
- Measure plan usefulness
- Measure repeat usage
- Discover trust concerns
- Test pricing
Launch Metrics
Focus on:
- Activation
- First plan completion
- Second-month return
- Plan usefulness
- Paid conversion
---
π PHASE 15 - POST-LAUNCH OPTIMIZATION
If onboarding completion is low
Simplify financial-data collection.
If users generate plans but don't follow them
Improve recommendations and make plans more actionable.
If users use the product once but don't return
Strengthen the monthly review and goal-progress loop.
If retention is strong but conversion is weak
Test pricing, packaging, and perceived ROI.
If users don't trust recommendations
Increase transparency and explain how recommendations were produced.
If users repeatedly request the same feature
Evaluate whether it strengthens the core monthly planning workflow before building it.
---
π PHASE 16 - FINAL PRODUCT MANAGEMENT DECISION REPORT
1. π― Executive Product Summary
The concept addresses a real and frequent problem: people have financial information but struggle to convert it into practical monthly decisions.
Recommendation: GO WITH A NARROW MVP.
---
2. π₯ Target Customer
Young working professionals who want simpler and more actionable financial planning.
---
3. π₯ Core Problem
Users struggle to translate income, expenses, and goals into a realistic monthly action plan.
---
4. π Value Proposition
Convert personal financial information into a simple, personalized monthly plan.
---
5. π§ Product Strategy
Win through:
Simplicity + Personalization + Actionability + Trust
rather than trying to become a complete financial-services platform.
---
6. π§© Feature Architecture
Core loop:
Financial Profile β Personalized Plan β User Adjustment β Progress β Monthly Review
---
7. βοΈ Prioritization Matrix
Highest priority:
1. Financial profile
2. Monthly plan generator
3. Goal planner
4. Plan editing
5. Monthly review
6. Basic analytics
---
8. π MVP Definition
The MVP should prove that users can receive a personalized plan and return to use it during subsequent monthly cycles.
---
9. π Product Requirements
The most important implementation requirement is a transparent and editable planning experience where users understand why recommendations are being made.
---
10. π KPI Framework
The most important metric should not be:
"How many people opened the app?"
It should be:
"How many users complete meaningful financial-planning cycles repeatedly?"
---
11. π§ͺ Validation Experiments
Prioritize:
- Prototype testing
- Concierge MVP
- Pricing validation
- Monthly retention testing
---
12. πΊοΈ Product Roadmap
NOW: Core planning experience.
NEXT: Retention and usability improvements.
LATER: Integrations and advanced personalization.
---
13. π€ Execution Plan
Keep the team focused on validating the core user behavior rather than expanding functionality.
---
14. π Launch Strategy
Start with a focused beta, gather behavioral evidence, improve the product, and then scale acquisition.
---
15. π Growth & Optimization Plan
Growth should come from:
Useful first experience β recurring monthly value β retention β referrals β paid conversion.
---
16. β οΈ Product Risks & Final Recommendation
Biggest Risks
- Users may not trust AI with financial information.
- Users may not return regularly.
- Recommendations may feel too generic.
- Users may prefer free alternatives.
- Financial-data privacy can become a major adoption barrier.
π FINAL DECISION
GO, but validate retention before scaling development.
The strongest product opportunity is not to build another budgeting dashboard.
It is to become the user's simple monthly financial decision layer.
The critical question to answer before significant expansion is:
"After using the product once, do users come back next month because it genuinely helps them make better financial decisions?"
If the answer is yes, invest in personalization, integrations and deeper planning capabilities.
If the answer is no, do not solve the retention problem by simply adding more features. Find out why users don't need to return.π This sample is intentionally built around a different product, customer problem, business model, feature architecture, and validation strategy so it can test whether your master prompt handles a new product scenario properly.
By purchasing this prompt, you agree to our terms of service
GPT-5.6
Product teams often struggle to turn ideas into validated, prioritized, and executable product plans. π
π― Validate product opportunities
π₯ Define users & pain points
π§© Design the right product scope
π Prioritize features objectively
πΊοΈ Build an actionable roadmap
π Plan launch & growth
π Define KPIs and success metrics
Turn your product idea into a clear product strategy and execution plan. π
...more
Added over 1 month ago
