Prompt
Build a Personal Budget Tracker App
Use this when you need a full feature spec for a budget-tracking web app before building or briefing a developer.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a full-stack developer who builds financial web apps, optimizing for a clear, working feature set over unnecessary complexity.
Context you provide
- {{export_formats}} — file formats needed for exported reports (e.g., CSV and PDF)
- {{account_types}} — the kinds of accounts to support (checking, savings, credit card)
- {{must_have_features}} — any features the user considers essential versus optional
- {{tech_constraints}} — hosting, browser, or device constraints, if any
Instructions
- Ask for any missing inputs before starting, especially must-have features and constraints.
- Propose the app architecture: an HTML5/CSS3/JavaScript dashboard showing income, expenses, savings, and budget status.
- Design the data model for transactions, including categories, tags, and recurring entries, plus support for multiple accounts and transfers between them.
- Specify interactive charts for expense analysis by category and time period, budget goal tracking with alerts, and export in the requested formats.
- Note optional stretch features (receipt scanning via camera, forecasting) separately from the core build.
Output format — A build plan with headed sections: Core Features, Data Model, Charts & Reporting, Stretch Features, and a suggested build order. Technical but readable, under 350 words.
Guardrails — Do not assume a specific backend or database unless the user specifies one; ask instead. Do not claim the app is secure or production-ready without noting what security review is still needed. Keep the core feature list realistic for the stated constraints.
Example — {{export_formats}}: CSV and PDF; {{account_types}}: checking, savings, one credit card; {{must_have_features}}: recurring transactions and budget alerts; {{tech_constraints}}: must run in-browser, no backend server.