Feature spec
Goal: Send a clear invoice after finishing a job.
- Add a client, line items, a due date, and payment instructions.
- Preview the total before exporting a PDF.
- Keep an editable draft if export fails.
App Overview
Bills Must Be Paid
Bills Must Be Paid is an active incremental game about paying your bills by smashing piggy banks.
$5.99
OVERALL US RANK
#17
Paid · all categories
REVENUE (Est)
$506K/mo
$299K - $714K
RATING
★ 5.0
31 ratings · Top 5%
Evidence scope: #17 is the current overall US Paid chart position. Category-chart positions shown in discovery are a separate scope. Revenue is a directional model estimate, not verified earnings.
Build your own version
Build Kit
Make this idea yours
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Add to a Remix
Combine features and design from your favorite apps.
Your first Build Kit is free with a verified email.
Generating… usually about a minute.
Make it yours Optional
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
What's included
A product spec, phased build plan, differentiation notes, and screen references.
- START_HERE
- AGENTS
- EVIDENCE
- SPEC
- BUILD_PLAN
- DIFFERENTIATION
- skills/
- screens/
Preview a sample Build Kit No email needed
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Screen plan
Invoice editor: Client at the top, editable line items in the middle, total and preview action at the bottom.
States: Empty draft, validation errors beside each field, exporting, and a retry action that preserves the draft.
Differentiate and validate
Hypothesis: Contractors need faster repeat invoices more than more templates.
First experiment: Test duplicating a previous job with five contractors. Watch where they hesitate before expanding the feature set.
The full kit adds a phased build plan, evidence notes, tool prompts, and implementation guidance. It is a plan for your coding agent, not a finished app.
Usage: Mechanics are fair game; never reuse the original name, branding, assets, or verbatim copy.
JavaScript is required to complete mailbox verification.
Free quick prompt For a smaller starting point
Quick prompt
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
// RORK SYSTEM PROMPT
Loading build analysis and prompts…
JavaScript is required to complete mailbox verification. Return to this prompt preview.
Continue in Rork >
Affiliate link: CloneChart may earn a commission at no extra cost
App evidence
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
Screenshots
< Scroll to see more >
App Store description
Bills Must Be Paid is an active incremental game about paying your bills by smashing piggy banks. Smash Piggy Banks Smashing costs stamina. When your hand is getting tired the run is over. Pay your bills Bills show up. If you ignore them, bankruptcy will be your destiny. Pay them off to unlock perks that help you pay back your bills even faster. Paying bills also gives you legacy points which you can spend on rings and bracelets to upgrade your hand after declaring bankruptcy. Different piggy types New types to discover. Some run away, some are too lazy to move, and others carry all the black money you never had :P... Random loot Piggies spawn random loot You never know which one is holding the most, or do you? Upgrades A skill tree with multiple paths. Improve your grip strength, get addicted to caffeine, hit the gym, pump up your wrist, get more lucky, unlock abilities like rock rain, electrify your hammer, and more. Different Hammers Unlock different types of hammer. Some have higher crit chance and smaller radius, while others are super fast with big radius and less damage. Choose the one that better fits your own playstyle. Collect rare coins
Written user reviews are not shown here. Check current App Store reviews >
Opportunities
AI-GENERATED OPPORTUNITY HYPOTHESES
These are generated suggestions, not verified review quotations. Check current App Store reviews and speak with users before treating a possible gap as a requirement.
Build scope
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Define the first version
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Set boundaries
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Check the hard parts
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
SUGGESTED BUILD STACK
BUILD KIT DIFFICULTY
Not assessed in a Build Kit yet.
A reliable timeline needs an agreed scope and a technical check. Ask your agent to estimate the phases in BUILD_PLAN.md after that review.
