How much does custom software cost?
Nobody can price it honestly until they've read your systems and your data. What sets the work is the screens, the systems it connects to and the records you move.
Answered in short
4 things that decide this
- 01Nobody can give an honest price for custom software for your business until they have read your systems and your data. Scope written to the screen, the systems it connects to and the records it moves decide the work.
- 02Published cost guides price a project nobody has scoped. TekRevol's June 2026 guide runs from a lean MVP to a complex enterprise platform. Its top figure, which it leaves open-ended, is twenty times its bottom.
- 03Integrations move the price because each system opens up differently. HubSpot bases how many API calls an app can make on the account's subscription. NetSuite bases its concurrent-request limit on the account's service tier.
- 04Hashlogics prices custom software after a free scoping call and a fixed-fee Blueprint. In the Blueprint an engineer reads your systems and fixes a price for each milestone, and its fee is credited in full against the build.
Why published price ranges don't tell you what yours will cost
Search this question and you'll find agency cost guides with dollar ladders. TekRevol's June 2026 guide runs from a lean MVP to a complex enterprise platform. Its top figure, which it leaves open-ended, is twenty times its bottom. The guide is open about why: the exact cost depends mainly on project complexity, the number of integrations, team location and security or compliance requirements.
A range like that prices a project nobody has scoped. It can't know whether your software only reads from QuickBooks or writes invoices back into it, or how clean your old customer records are. Those facts show up only when someone opens your systems, so a number given before that is a guess about someone else's project.
Five things that set the cost of custom software
Scope written to the screen comes first. When you say "a customer portal", that's a wish. A list of every screen, what each one shows and what each button changes is a scope an engineer can price. Many change requests start in the gap between the two.
Systems you need to integrate come next. Each system has its own access rules, and for the three in the table below the limits depend on your plan or tier. Reading and writing back are different jobs. A dashboard that pulls a nightly copy from your CRM needs one connection and a check. Software that writes orders or invoices back needs matching rules, retries and a queue for the records the other system refuses.
Moving old records is easy to leave out of a quote. Horváth surveyed 200 SAP user companies about their move to S/4HANA. CIO reported in March 2025 that the planned budget was exceeded in more than six of every ten migrations. Companies reporting severe quality problems afterwards named underestimated testing and data migration phases among the main reasons, next to expansion of project scope. That's an ERP migration rather than a new build. Still, if your records hold duplicates, blank fields or old formats, each one needs a rule before it moves.
Who can see what in your software changes the build. One admin and one user type is a small permission model. Several client companies on one platform, each walled off from the others with roles inside each, is a much larger one. Audit trails and data-handling rules your industry sets add work in the same place.
Who runs it after launch is the last driver, and it's a standing cost: each connected vendor can change its API on its own schedule. The maintenance question below covers what to set aside.
How three common systems let a builder in
Each row comes from the vendor's own developer pages, read on 31 October 2026. QuickBooks, Salesforce, Xero or whatever you run will have rules of its own, so get your account's limits confirmed before you accept a quote.
HubSpot
From the vendor's own page
For a privately distributed app, the usual setup for a build made for one company, the burst limit applies to each app. The daily limit is shared across all private apps in the same account. That allowance depends on the account's subscription and on whether the API limit increase was bought.
What it means for your build
Your other HubSpot apps draw on the same daily allowance, so the sync design has to count what's already running.
NetSuite
From the vendor's own page
Your account's base limit for concurrent requests depends on its service tier. Each SuiteCloud Plus license raises the base limit for concurrent web services requests by 10. Web services and RESTlet requests count against one combined limit.
What it means for your build
Your software can run only so many requests at once, shared with every other integration on the account. That number depends on your service tier and SuiteCloud Plus licenses, so it belongs in the plan before the price.
Shopify
From the vendor's own page
Bucket size and restore rate vary by API and by plan. Once a store has 500,000 product variants, it can create no more than 10,000 new variants a day on any API. That throttle doesn't apply on Shopify Plus.
What it means for your build
Catalog imports get planned around your plan's limits. A store past 500,000 variants on a plan other than Plus may need a large import spread over several days.
- ScreensEvery screen, field and button written down
- SystemsEach API, its limits, read or write-back
- DataReal records, duplicates and blanks counted
- RulesRoles, tenants, audit and data rules
- RunWho fixes it when a vendor changes an API
Five stations. A quote that skips one of them is pricing a different project from yours.
How a fixed-fee Blueprint turns the drivers into a price
You start with a free scoping call, where a senior engineer looks at the problem with you. Every build then starts with a Blueprint: a fixed-fee plan an engineer writes from your real systems. It covers scope, architecture, risks and a fixed price for each milestone, and its fee is credited in full against the build. If the Blueprint doesn't give you a plan you'd act on, you don't pay for it.
Builds are then fixed-price per milestone, accepted against written criteria rather than billed by the hour. If you're a startup, you know the price of your first version before you commit to it. If you're an enterprise team, your finance office gets a number per milestone it can hold the vendor to. Bring these to the scoping call and your Blueprint starts from your real setup:
- 01Each system your software must touch, and whether it only reads from it or writes back
- 02A sample of the real records you'd move, duplicates and blanks included
- 03Rough sketches of the screens you picture
- 04Your account tiers today, such as your HubSpot subscription or NetSuite service tier
What shaped the scope of TankAware
TankAware is the AI and IoT platform we built for Sutherland Excavating Ltd. It runs petroleum tank and site inspections that used to live in spreadsheets and paper logs. Each client company works in its own secure space under a dedicated subdomain, with five roles from Super Admin to Contractor. IoT tank-level sensors stream real-time data, and contractor payments run through PayPal.
On that build, our hardest design question was keeping each client's data apart while the sensor pipeline and alert models stayed shared. Roles, outside systems and the work of running it all show up in that one build. Those are the questions a Blueprint answers for your software before anyone writes a price.
Some of the systems we have shipped
Related questions
01How much does it cost to hire a custom software development company?+
A custom software development company should price your project from your scope, your systems and your data, not from a rate card. A figure given before anyone reads those is a guess about someone else's project, so we don't publish one. You start with a free scoping call. A fixed-fee Blueprint, credited in full against the build, then fixes a price for each milestone.
02Why do quotes for the same software project differ so much?+
Quotes for the same project differ mainly when each vendor priced a different scope. One priced the screens only, another assumed the integrations would write back, and a third left out moving your old records. Line your quotes up against the five drivers on this page and the gaps start to make sense. TekRevol's guide also names team location as a cost driver, which explains part of the rest.
03Is fixed-price or hourly billing cheaper for custom software?+
Neither billing model is cheaper by default. What matters is who pays when the estimate was wrong. Under hourly billing, you pay for every hour the estimate missed. A fixed price protects you best when someone read your systems before setting it. Our milestone prices come from the Blueprint, and a milestone we estimated badly comes out of our margin.
04How much does custom software cost to maintain each year?+
TekRevol's 2026 guide tells buyers to set aside 15% to 25% of the initial build cost each year as a starting point for maintenance. Each outside system you connect to adds upkeep, because its vendor can change the API on its own schedule. We include the first two months of maintenance in every build. After that you choose written service levels or a trained handover.
05Is it cheaper to buy off-the-shelf software than to build custom?+
Buying is the cheaper route when a packaged tool already fits how your business works. Custom software earns its cost when the job sits between systems the tool doesn't connect, or when your own process is what sets you apart.
Related
- How much does it cost to build an app? →Same question, for mobile and web apps, with published market ranges.
- How much does an AI chatbot cost? →For a chatbot that acts in your systems, the same drivers priced out.
- What does an AI agent project actually cost? →How the drivers change when the software includes an AI agent.
- What does EDI integration cost? →One integration driver, priced out in full.
- AI developer hourly rates →What hourly rates explain about the spread between quotes.
- NetSuite, Epicor and SAP B1 integration →What a real ERP integration involves, step by step.
- Will your automation survive an API change? →Why upkeep keeps going after launch when a vendor changes its API.
- Build vs buy software →The full decision, with a table you can take into a meeting.
- How we work →Free call, fixed-fee Blueprint, fixed-price milestones, then the run.
- Custom software development →What we build, and how we keep it running after launch.
