What changes the cost of a custom dashboard or web app
My dashboards and internal tools start from $900 and usually take 3–7 weeks. Product MVPs start from $2,500 over 6–14 weeks. Where your project lands depends mostly on six things: roles, data sources, real-time needs, reporting, data migration and design.
1. How many kinds of users there are
Every role, such as owner, staff, customer or parent, needs its own permissions, screens and tests. The school system I built has four portals, for students, teachers, parents and admins, sharing one login system. That is a very different budget from a single admin panel.
2. How many systems it connects to
Each integration, whether payments, WhatsApp, email, accounting or an existing database, adds setup, error handling and testing. Some APIs, like WhatsApp Business, also bring approval steps and rate limits. The donation platform I built needed a message queue just to pace campaigns within those limits.
3. Whether it needs to update in real time
A dashboard that refreshes when you reload it is simpler than one that pushes changes to every screen instantly, like a kitchen display. Real time is worth it when people act on the update within seconds; otherwise, skip it.
4. How much reporting you need
One summary screen is quick. Filterable reports by product, category and date range, with exports and charts, take longer, but they are often the reason the project exists. Decide which three numbers you check every week and start there.
5. Whether existing data has to move in
Importing years of spreadsheets means cleaning duplicates, mismatched names and missing fields. A clean start with only current records is much cheaper. A one-time import script is a reasonable middle ground.
6. How custom the design needs to be
Internal tools rarely need a bespoke visual identity; a clean, consistent interface is enough. Customer-facing products usually do need more design work, because the interface is part of what you are selling.
How to cut cost without cutting value
- Build the one workflow that saves the most time first, and plan the rest as release two
- Start with one or two roles and add the others once the core works
- Use exports before building complex in-app reports
- Choose reload-based updates unless people genuinely act within seconds
- Import only current records at launch
Written by a developer who builds these systems. Where a guide describes a project, the details come from delivered work in the portfolio; results that would need client data to verify are not claimed.
Want this applied to your business?
A free 20-minute call. You leave with a clear next step and a fixed quote if a build makes sense.
