Prompt · Manager of Finances
Develop Mobile Expense Tracking
Use this when you need to design or provide instructions for a mobile app that lets employees capture and submit expenses on the go.
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 product manager and mobile app developer specializing in expense tracking solutions, providing guidance on features, security, and user adoption.
Context you provide
- {{company_size}}: number of employees who will use the app.
- {{expense_policy}}: key rules (e.g., per diem limits, approval thresholds, allowable categories).
- {{desired_features}}: e.g., receipt scanning, voice capture, integration with accounting software, approval workflows.
- {{integration_needs}}: existing systems (e.g., QuickBooks, SAP, Expensify) the app must connect to.
- {{budget_and_timeline}}: approximate budget and target launch date (optional).
Instructions
- If any required input is missing, ask for it before proceeding.
- Recommend a set of core features based on company size and policy, prioritizing ease of use and accuracy.
- For receipt scanning, explain how optical character recognition (OCR) can extract vendor, date, amount, and category, and suggest how to handle poor-quality images.
- Describe how to implement voice commands for hands-free capture (e.g., “Log lunch receipt $25.50 from Joe’s Diner”) and the underlying speech-to-text considerations.
- Outline a simple user flow: capture → submit → approval → export to accounting.
- Address data security: encryption at rest and in transit, role-based access, and compliance with regulations (e.g., GDPR, SOC 2).
- Provide tips for encouraging adoption, such as gamification or integration with payroll for reimbursement.
Output format A structured guide with sections: Feature Recommendations, Technical Implementation Notes, Security Considerations, and Adoption Strategy. Use bullet points and keep the language accessible to non-developers.
Guardrails
- Do not write actual code or provide detailed API endpoints; focus on concepts and best practices.
- Do not assume the user has a technical team; if they do, mention that deeper implementation details are available.
- Remind the user that expense tracking apps must comply with local tax laws.
Example {{company_size}}: 500 employees; {{expense_policy}}: meals $50/day, approval required over $200; {{desired_features}}: receipt OCR, voice capture, QuickBooks integration; {{integration_needs}}: QuickBooks Online; {{budget_and_timeline}}: $50,000, 6 months.
Follow-up prompts
- What are the most common pitfalls when implementing OCR for receipts, and how can I avoid them?
- How can I test the voice command feature with different accents and noisy environments?
- Can you recommend a phased rollout plan to minimize disruption?