Skip to content
AdmasJournal
All stories

Practical guides

What it costs to keep an AI-built business app running

Build an honest operating budget for an AI-built business app, including hosting, database, email, usage limits and support, with a reusable cost worksheet.

The first build is a project. Keeping the result useful is an operating responsibility.

Before an agency quotes a monthly maintenance price, it should answer three questions: What must stay running? What grows with use? Who handles the next failure or change? A builder subscription answers only part of that budget.

This guide offers a planning method and an illustrative subtotal using publicly listed prices checked November 18, 2026. It does not report a tested application bill, customer savings, or a recommended stack. The application architecture and its accepted business workflow determine which services belong in the budget.

Start with the work that must keep happening

Describe one complete outcome: a customer submits an inquiry, a reviewer approves the quote, and the customer can return later to find its status. Record the normal route, the exception route, and the people who use each.

Then list what that outcome depends on. It may need a website, server functions, identity, a database, file storage, email, an external API and an operator. A brochure site has a different operating budget from a portal that stores documents and processes payments. A live AI feature adds another usage path.

Count completed jobs as well as visitors. A hundred visitors who browse a page create different work from a hundred operators who upload files, trigger repeated model calls and send notifications. Usage estimates become useful when they describe the workflow.

Keep three budget lines visible

Change work: implementation, development tools, tests and later requested improvements.

Live operation: the services required while customers use the delivered app, even when nobody is changing its code.

Maintenance and support: monitoring, incident handling, dependency updates, access changes and customer assistance.

Some providers combine several services or share an allowance across projects. Trace the bill once, then allocate it using a stated rule. Charging the full shared account minimum to every app overstates the portfolio cost; treating a shared allowance as unlimited understates it.

Read what the builder price actually covers

Admas's public pricing lists Build at $19 monthly with 20,000 shared credits, and its managed application database at a separate $15 per project monthly. Builder model and sandbox work consume the shared wallet; optional application AI uses it after the owner enables that service. A credit represents $0.001 of retail usage. These facts do not establish how much a particular app will consume.

Treat an included credit allowance as capacity inside the chosen plan. Do not add its full retail value to the subscription price a second time. Record extra purchases separately. Ask which live services continue after development stops and verify the actual account and deployment behavior before promising ongoing availability.

Admas owns this publication. The product example explains budget categories; functional acceptance still belongs to the actual project.

Price the intended production architecture

Choose services only after verifying that the exported application can run on them with its required integrations. Portable source alone does not establish that every hosting provider supports its runtime.

For a documented example, Cloudflare Workers has a $5 monthly account minimum on its paid plan. Usage above included allowances can add charges, and storage or other products require their own review. This is an account charge, so state whether the app owns it or shares it. Check that the workload fits before including it in a client quote.

Email also needs a traffic model. Resend's current pricing lists a free allowance of 3,000 emails monthly and 100 daily. A monthly estimate within its allowance can still exceed its daily limit during a launch or notification burst. Paid tiers and optional overage settings change the budget. Provider pricing does not establish that your sending domain, consent, templates or delivery path have been configured.

Put the check date beside every rate. Cloudflare's documentation states that Workers Logs moves to Observability pricing on December 1, 2026. An estimate prepared in November should therefore carry a review before that change when the app uses those logs. A price copied once is not a permanent operating guarantee.

Work an illustrative subtotal without pretending it is the whole bill

Suppose an agency chooses an Admas Build subscription, one managed database and a separate dedicated Workers paid account, after confirming compatibility. The listed lines sum to $39 monthly before taxes: $19 + $15 + $5.

That number is a selected-service subtotal. It omits any unmeasured overage, files, domain renewal, external API, payment fees, backup requirement and labor. If the developer account or hosting account serves several clients, use an allocation instead of automatically passing the full amount to each.

Now add a deliberately hypothetical maintenance allowance: two hours at an assumed internal cost of $40 per hour. That adds $80, taking the selected subtotal to $119. Both labor inputs are assumptions for the example; no work time or market labor rate was measured. Unresolved costs remain unknown. Neither subtotal establishes a profitable client price.

Test the workload that can break the estimate

Before making a fixed offer, collect a small authorized sample of the critical workflow. Record attempts as well as successes: retries and failed operations can still consume services. Measure normal use and plausible bursts, including a larger upload, repeated request, notification batch and exception needing a human.

Compare the sample with provider usage records. Reconcile the units before projecting a month. A request, CPU millisecond, stored gigabyte, email and completed business job are different measures. Extrapolation remains an estimate until a real period of use is reconciled.

For the sample period, record the application version, provider plan, measurements, failures and exclusions. Do not describe a budget worksheet as an actual load test. If a test would spend money or touch production data, obtain the project's required approval first.

Agree what happens when usage or support increases

A maintenance agreement should say what is covered, who receives alerts, when support is available, how usage is reviewed, and what requires approval. Record the owner of each service and renewal. Include the route for suspending optional work or changing limits when a budget is exhausted.

An alert and a hard stop serve different purposes. Confirm which controls each provider actually supports. A notification does not itself cap a bill; a cap may stop part of the workflow. Explain that consequence to the buyer before it happens.

Track support time against the assumed allowance. A client who needs frequent correction may create a valuable product-improvement question, but the support cost still belongs in the economics. Recurring value comes from the workflow continuing to help the business and the team continuing to operate it effectively.

Copy this operating brief

Keep [one business job] available for [named users]. List each required service, owner, renewal, base charge, included capacity, overage unit and verified limit. Separate change work from live operation and maintenance. Measure [normal use] and [burst] during [authorized sample]. State every unknown, review date, support responsibility and approval threshold. Deliver an itemized budget and acceptance record before presenting a recurring client price.

Bring that brief to an Admas project or another development process. Request the dependency inventory and verification evidence for the actual software. Then reconcile the first operating period and the next useful change. Those observations provide a stronger basis for a continuing service than a plan price alone.

Copyable cost worksheet

Fill this before using a total in a client quote. Unknown values stay unknown; an explicit zero requires evidence that the cost is absent or included elsewhere.

For each cost line below, copy and complete this record:

  • Cost line: [name]
  • Plan and dated source: [plan; source URL; check date]
  • Scope: [account or project; allocation rule]
  • Monthly base or allocation: [amount or unknown]
  • Included capacity: [unit and allowance]
  • Forecast: [quantity; normal use and burst]
  • Overage rule: [price per unit; minimum and rounding]
  • Owner and review: [person; next review date]

Repeat for these cost lines:

  • Builder and change work
  • Production compute
  • Database
  • Files and transfer
  • Application AI/API
  • Transactional email
  • Domain and certificates
  • Logs, monitoring, backups
  • Payment processing, if used
  • Support and maintenance labor
  • Taxes and other mandatory charges

For a simple linear allowance: usage cost = max(0, forecast quantity minus included quantity) × price per unit. Convert billing units first. Use the provider's actual tier, rounding, minimum and shared-account rules wherever this simple formula does not apply.

Monthly operating estimate = allocated fixed charges + forecast usage charges + maintenance hours × internal hourly cost + other applicable charges. Annual renewals may be divided by 12 for planning, while the cash payment still occurs on its actual due date. Implementation and later feature projects have their own scope and price.

  • Selected service subtotal: 19 + 15 + 5 = $39. Public listed lines; hypothetical selection.
  • Maintenance allowance: 2 × 40 = $80. Explicit assumptions.
  • Partial combined estimate: 39 + 80 = $119. Incomplete estimate; other lines unresolved.

Evidence record: sample dates [ ]; completed jobs [ ]; attempts [ ]; billed/observed units [ ]; allocated versus incremental costs [ ]; exceptions [ ]; invoice reconciliation [ ]; remaining unknowns [ ].

Method and evidence

Original proposed budgeting method. Public rate examples were rechecked November 18, 2026 against Admas public pricing, Cloudflare Workers documentation and Resend pricing. The $39 selected-service subtotal and $119 partial estimate use explicitly assumed labor. No actual application workload, customer savings, profit or hosting compatibility was tested. Prices and service limits may change; unresolved costs remain unknown.

Put the idea to work

Bring your next useful problem.

Describe a workflow, inspect the result, and keep improving it in Admas.

Start a project

Keep exploring.

All stories

A useful read, once a week

Get the Field Notes.

One investigation, a practical takeaway, and an idea worth testing. Free. Leave whenever you like.

Confirm your address before receiving editions. Privacy notice.