Founder notes
How to Budget for Custom Software and Monthly Running Costs
Ask for separate build and running-cost estimates, decide where custom work matters, and use three usage scenarios to size the monthly bill.
By Hassan Jamal, Co-founder and Lead Engineer
PublishedAsk for two figures before approving a project: the cost to build it and the cost to run it. Then ask what makes the second figure rise. For a training business that could be more bookings, emails and staff accounts. For an AI app it could also be more document reads, audio minutes or model requests.
Where does custom work earn its place?
A Step Above Medical needed a better way for students to find and book classes and for staff to run them. We looked at which parts existing services could handle and where the team needed software built around their process. That let us focus the build on registration, class management, student emails and certificates. We also talked through the choice between the client owning the hosting bill and running the site under a care plan.
I used that project in my contribution to TechBullion on allocating a software budget. The useful question was where each part of the budget would help the business. See the training website and staff portal.
What should be on the estimate?
| Cost | What to ask for |
|---|---|
| Build | Name the pages, workflows, integrations, migration, testing and training included. |
| Cloud and software | List hosting, database, storage, email and other services with their plan limits and renewal costs. |
| Activity fees | Estimate payments, API calls, documents or audio for normal and busy months. |
| Care and changes | State what monitoring, updates and fixes cover, and how new work is priced. |
For each service, write down who owns the account and who pays the invoice. That matters whether your supplier manages the bill or you pay the provider directly. If a service starts within a free allowance, record the allowance and the price of the next plan. I would check the current provider terms against your usage before putting a figure in a proposal. See an itemized website running-cost example.
How do you plan for an AI app that grows?
Build three examples: the pilot, a typical month and a busy month. Suppose 200 users each submit three documents. That gives you 600 submissions to estimate. If people can ask follow-up questions or listen again, count those separately. For summaries, the length of what goes in and comes out can affect the bill. Decide how long files are kept and whether temporary copies are needed.
Agree who gets the usage alert, when you review the estimate and who can approve an increase. Test the busy-month assumptions against a small pilot once you can see how people actually use the product. It gives you a better estimate to budget against and helps you decide which features to launch first.
If you run a training business, start by listing one class, its registration steps and what staff do after payment. Those are the details we need to price a useful first build. See website and booking options for training businesses.
Common questions
What should a custom software budget include?
How do you estimate an AI app's monthly cost?
Related Articles
Class Registration Software or a Custom Booking System: Which Fits Your Training School?
When class registration software is enough for a training school, when a custom booking system is worth building, and what we built for a phlebotomy school.
Supabase and Vercel: What They Cost as You Grow, and When to Choose Something Else
Supabase and Vercel cost about $45 a month for a small live app and a few hundred for a busy one: where the bills jump and what to move first (November 2026).
Website Redesign Cost in 2026: Scope, Tiers and Buyer Guide
Price a same-platform redesign by UX, templates, design system, content, implementation, testing and rollout, then compare proposals on the same scope.
PandaCodeGen offers website and application development. Recommendations here reflect our delivery approach; the proposal for your project defines its scope. How we use evidence.