Apps are not websites with more buttons
The previous guides covered AI-built websites. This one is about the heavier case: an application, auth, database, payments, background jobs, built with AI tools (Lovable, v0, Bolt, Cursor) by a founder or a non-specialist. These tools are genuinely extraordinary at shipping the first working version. The question this page answers: what does month two to month twenty-four look like?
The four ongoing responsibilities
- Dependencies age. A generated app pulls dozens of packages. Advisories arrive; versions drift; upgrades break things. Somebody must read, test and merge, monthly.
- Data grows and must be protected. Backups with tested restores, storage monitoring, and a privacy posture matching what the app collects. A database nobody has restored from backup is a rumor of a backup.
- Deployments and environments. Every change needs a path to production that cannot take the app down: staging, checks, rollback. Builder platforms give some of this; self-hosted gives more control and more responsibility.
- The app's actual logic. New requirements, bug fixes, edge cases users find. AI regenerates features well; understanding an existing generated codebase under pressure is a different skill.
The three ownership models, honestly
- Self-maintain: viable if you are technical and the app is small. The moment the app pays salaries, your engineering time has a price and your attention has a limit.
- Original tool/platform: builder subscriptions cover hosting and some ops, not your custom logic, not your data, and lock-in grows with usage.
- A developer relationship: monthly or per-milestone, someone who understands the codebase, watches dependencies, protects the data and ships changes. This is the care-plan model applied to apps, and it is the only model where someone else's calendar absorbs your 3 AM.
The first-month stabilization, honestly itemized
- Dependency audit and upgrade to current safe versions.
- Backup automation with one real restore test.
- Environment separation: development, staging, production, with secrets out of the codebase.
- Error monitoring and uptime alerts wired to a human.
- Basic security pass: auth review, input validation, rate limits, admin surface lockdown.
- Documentation: what exists, where, how to deploy, how to restore.
Band in INR: ₹45,000 – ₹2,26,000 depending on app size, then ongoing care. Compare with one data-loss incident or one week of downtime, see also the hidden-costs guide for the economics.
The honest test before you hire anyone
Ask the candidate: how would you restore this app if the database vanished tonight, and how would you know an upgrade broke payments without a customer telling you? The right maintainer answers both in minutes. Start there.