★ Internal tool · cost estimate
How Much Does It Cost to Build an Internal Tool?
Internal tools pay for themselves in saved hours, so the useful number is the payback period. The build is usually smaller than a customer product: no marketing site, simpler design, fewer edge cases.
- Runs in your browser
- No signup
Your estimate: $12,900–$28,300.
Want a second opinion? Send it to me and I'll tell you which features I'd cut to ship weeks sooner.
What people forget to budget for
Source systems
Internal tools sit on top of existing databases and APIs. Access, data quality and rate limits set the pace.
Permissions
Ops tools often touch sensitive data, so role-based access and audit logs are worth including.
Adoption
If the tool is slower than the spreadsheet it replaces, people will keep the spreadsheet.
How the estimate works
Each feature has a range of hours for a senior engineer building production-quality software. Those hours scale with the number of platforms, then the estimate adds what every real project needs on top of writing features.
hours = (build + 20% QA + PM overhead) × 1.15 contingency
cost = hours × hourly rate
weeks = hours ÷ productive hours per week
Ranges, not single numbers, because the honest answer depends on details nobody knows yet: how clean the third-party APIs are, how many design rounds you want, how often scope moves. If someone quotes a single number without asking those questions, the range is hiding in their change requests.
Building for web and mobile is not twice the work with React Native: the backend, business logic and much of the UI code are shared. That is why the platform factor for web plus mobile is about 1.5, not 2.
Worked example
Take an internal tool MVP with 5 features (sign-up & login, teams, roles & workspaces, search & filters, dashboards & charts, third-party integrations (×2)), built by a senior freelancer at $60/hour:
| Line | Hours |
|---|---|
| Feature build (incl. setup and design) | 144–316 |
| QA, project management, contingency | 71–156 |
| Total | 215–472 |
That comes to $12,900–$28,300 over roughly 7–16 weeks. Deferring teams, roles & workspaces alone would save about $4,310.
Hours by feature
The ranges the estimator uses, before platform factor and overhead. The features founders most often underestimate are payments, permissions and admin tooling: none of them are visible in a demo, and all of them are needed the week after launch.
| Feature | Covers | Hours |
|---|---|---|
| Sign-up & login | Email + Google/GitHub OAuth, password reset, sessions | 16–32 |
| Teams, roles & workspaces | Invites, permissions, multi-tenant data isolation | 32–64 |
| Search & filters | Full-text search, facets, sorting, pagination | 16–40 |
| Dashboards & charts | User-facing analytics, aggregates, exports | 24–56 |
| Third-party integrations (×2) | e.g. Slack, Google Calendar, HubSpot, Zapier | 24–60 |
Questions founders actually ask
Low-code builder or custom code?
How do I justify the cost?
Can an internal tool include AI?
How accurate is this estimate?
Why is this higher than the agency quotes I've seen?
Do AI coding tools make an MVP cheaper?
Estimate by product type
- Cost to build a B2B SaaS
- Cost to build a marketplace
- Cost to build an AI chatbot
- Cost to build an AI agent
- Cost to build a mobile app
- Cost to build a fintech app
- Cost to build an e-commerce store
- Cost to build a booking app
- Cost to build a CRM
- Cost to build a learning platform
- Cost to build a social / community app
Or start from scratch with the full MVP cost estimator.
More from the workbench
Fine print
Tools: on the house.
Engineer: by the hour.
Building it isn't free either, but it can be faster than you think. Send me the breakdown and I'll tell you what I'd ship first.
I'm Himanshu, an AI and full-stack engineer. I build MVPs, AI agents and the growth plumbing around them for early-stage startups.