Get written client approval for ongoing usage responsibility separately from the build fee. The approval should identify who monitors activity, who funds it and what happens when usage exceeds the agreed operating scope—not predict an unsupported monthly bill.
Explain the activities behind the balance
Lovable describes one credit balance spanning building and chatting, hosting its app and built-in backend, and deployed-app AI features. It also states that usage limits and alerts are managed in workspace settings.
This means a client should not treat credits purely as a count of development prompts. Building the app and operating it are distinct activities even when they draw on one balance. The source does not establish a universal cost for a visitor, message or month of hosting.
Write an operating-cost responsibility addendum
As editorial practice, attach a short operational note to the project acceptance record. Include:
- Build scope and the boundary of the agreed build fee.
- Expected hosted-app activity, described without a price promise.
- Deployed AI features approved for use.
- Party funding ongoing usage and named budget approver.
- Person reviewing usage, limits and alerts.
- Review frequency and evidence to be retained.
- Change-approval process for new activity.
- Response owner when the agreed scope is exceeded.
For an Indian client budgeting in INR, record the client’s spending ceiling as an internal approval amount. Do not present that ceiling as a provider quotation or a guaranteed amount of service.
This is an operational worksheet, not legal drafting advice.
Bound a hypothetical launch
Suppose a fictional Ahmedabad agency delivers an internal app for 15 staff members. The client approves a two-week pilot involving 100 synthetic requests and one specified deployed AI feature.
The addendum names the client’s operations manager as usage approver and the agency as reviewer during the pilot. It records hosting, backend and AI activity as categories requiring observation. No monthly bill is forecast from the 100-request input.
Evaluate the pilot by comparing observed activity with its approved scope, documenting usage evidence and identifying which assumptions remain uncertain. Public launch is a separate approval because a staff pilot does not establish public demand.
Pause expansion, not accountability
Stop launch expansion if nobody accepts ongoing funding responsibility or if the client thinks the build fee necessarily includes indefinite usage. Next, resolve the addendum and agree how the team will respond to alerts or scope changes. Do not assume an alert guarantees a spending outcome.
If supplementary access is considered, review the AI tools catalog, checking access format and saved terms before buying. Marketplace account, code or token offers are not proof of official subscription equivalence.
Sources and scope
Source material checked 29 October 2026; features/policies may change. Lovable credits and usage establishes the shared activity balance and workspace management of limits and alerts. The addendum, pilot boundary and approval gate are editorial advice, not pricing or contractual guarantees.