How much does custom software development cost, to build and to run?

Why do custom software quotes vary so much?

Two quotes for the same idea can sit far apart, and both can be honest. Keyhole Software says team makeup, technology choices and how changes are handled can move a project’s cost 30 to 50% either way. Here is what moves it:

• The systems it connects to: each link to accounting, email, a phone system or an older database has to be built, tested and kept working when the other side changes.
• Screens and user roles: a tool one office uses is smaller than one where staff, managers, clients and partners each see their own screens and data.
• Records from the old tools: moving years of records out of spreadsheets or an old system takes cleaning and checking before anyone can trust them.
• AI steps inside the workflow: a step where a model reads an email or a PDF needs testing on real examples and a way for a person to catch what it gets wrong, and the model’s usage is billed on top. Main & Machine names model usage and third-party subscriptions as costs outside its fees.
• Compliance review: single sign-on, audit trails and a security review all add work, and Keyhole Software’s guide gives its healthcare and fintech examples a higher floor than its logistics one.
• Who writes the code: BD Emerson’s guide sets its own US planning rate well above the rates it quotes for teams in Latin America, Europe and Asia, so the same build is priced very differently depending on where the team sits and how senior it is.

When a quote leaves one of these out, ask how it will be handled, because the work behind it doesn’t go away.

What does custom web application development cost?

A web application is software your team opens in a browser, with its own logins, screens and database: a quoting tool, a client portal, a scheduling board. A marketing site with no logins or database of its own is a website instead, with its own ranges on website design cost. Custom web application development pricing follows the same market ranges as other custom software, from RaftLabs, Keyhole Software, Codestringers, BD Emerson and the ERP guides listed below: the established local band is $24,000 to $100,000, the multi-location or regional band $45,000 to $150,000, and the national band $150,000 to $600,000.

Where a project lands inside its range comes down to scope. Keyhole Software’s lower tier is a basic feature set on one platform with limited integrations and a simple interface. Its middle tier adds support for more than one platform, custom workflows and third-party integrations. Who uses it matters too: BD Emerson prices a customer-facing web or mobile app above an internal tool built for one department, in a range that runs past the top of the national band.

Codestringers’ worked example puts half of a build’s cost in engineering, with discovery, design, testing, and integration and deployment making up the rest. That split is a useful check on any proposal: if one shows almost nothing for discovery or testing, ask why before you sign.

What we would build is on the custom web application development page, and client portals and internal tools covers the software your clients and staff log in to.

What does custom software cost to keep running?

The build is the bigger number, but the monthly cost lasts as long as the system does. BD Emerson and Keyhole Software put maintenance at 15 to 25% of the build cost a year, and Codestringers gives 15 to 20%. In monthly terms, the market’s upkeep ranges are:

• Established local business: $300 to $2,080 a month.
• Multi-location or regional: $560 to $3,130 a month.
• National: $1,880 to $12,500 a month.

These monthly figures are 15% and 25% of each level’s build range, spread over twelve months. Most of the guides give upkeep as a yearly percentage; RaftLabs gives its running costs by the month. BD Emerson’s share covers defects, patches, dependency upgrades, small enhancements and infrastructure. Hosting is usually a separate line: BD Emerson, Keyhole Software, Space-O and RaftLabs each list it apart from upkeep. Model usage for any AI step is a cost of its own.

Once a system we build is live, it runs on a monthly plan, and the proposal after your call prices that plan alongside the build.

How do you work out workflow automation cost savings?

Start with one repeating task. Count the hours a week your team spends on it, multiply by the fully loaded cost of an hour of that time (pay plus taxes and benefits), then multiply by 52. That is what the manual version costs a year. Ten hours a week is 520 hours a year before any rate is applied.

Then set it against the cost of the system: the build, plus a year of upkeep. Three outcomes are worth knowing:

• The manual work costs well above the build and a year of upkeep: the case is strong. After the first year, the saving each year is the manual cost less the upkeep.
• The two are close: look at what else changes, such as errors caught, faster replies or the hours the team gets back for other work, before deciding.
• The manual work costs less than a year of upkeep alone: it won’t pay back. Leave it as it is, or fix the process first.

Workflow automation cost savings are an estimate until the system runs, so measure the hours before you start and you will have a number to check against afterwards. If the sum comes out small, that is an answer too, and it cost nothing to find.

The cost calculator on the AI automation page runs the first half of this sum. The guide to what to automate first and the operations audit worksheet help you pick the task.

What does an n8n automation agency charge?

n8n, Zapier and Make connect the tools a business already has: a form comes in, a record is created, a message goes out. Agencies that build on them usually charge a setup fee, then a monthly fee to run and adjust the workflows. Most of the price pages we read pair the monthly plan with a setup or build fee; ProsperSpark folds setup into its monthly plan.

Builts.ai and BetOnAI both name n8n alongside Make and Zapier where they set out their prices. For an established local business, the market’s figures look like this:

• Setup: $1,500 to $5,000 (Sam Automates, whose entry plan includes n8n integration, and Builts.ai).
• Monthly: $500 to $2,000 (ProsperSpark, BetOnAI, Main & Machine and Sam Automates).
• Tool subscriptions: the automation tool’s own plan, paid on top of both (Builts.ai).

Where a workflow sits decides what it costs. A workflow that follows fixed rules belongs in these tools. A step that has to read an email or a PDF and decide what it says needs a model, which makes it AI automation, with its market prices on AI consulting cost. A workflow that needs its own screens, users and database has outgrown the tools and becomes a custom build, priced like the ranges above.

Rules-only workflows are our Zapier, Make and n8n work, and the guide to Zapier vs Make vs n8n vs custom compares the four.

Why does a system we build cost what it does?

A system we build is made for one business, in its own repository. We don’t sell an off-the-shelf product or a software licence. Because the system isn’t shared with anyone else, its cost is the work of building it, and then of running it. The systems we build, set out in full on custom software development, include:

• The records the team works from: a CRM, quoting, scheduling, inventory, and billing and payouts.
• Paperwork and access: e-sign forms, and portals for clients or affiliates.
• AI steps inside the workflow: reading emailed orders into the system, a dispatch assistant, or sorting new leads.
• Larger systems: we build custom ERPs and other systems of record too; see the custom ERP and custom CRM pages.

We build a system once, then keep it running each month after launch. After the 15-minute call, you get a scoped proposal with what we would build and the price of building and running it, and no work begins until you approve it.

Sometimes the honest answer is not to build. When an off-the-shelf tool does the job, we tell you to buy it. The build vs buy software guide and custom CRM vs off-the-shelf walk through that call.

Where do these figures come from?

The build ranges come from guides published by firms that sell custom development, so read them as the sellers’ own estimates. We found no independent survey of what businesses paid. Space-O and CMARIX publish the same prices for small and mid-sized ERP builds, so they count as one piece of evidence here. BD Emerson’s figures run through the stabilization period after launch and cover builds in regulated industries, and they sit at the high end. Each level’s range is drawn from the published figures of the publishers named beside it. The automation figures come from agencies’ price pages and published guides.

Every source here is read again each April and October. For the same three levels across every service, see pricing.

To find out which level you sit at, what would move the cost of your system, and whether building is the right call at all, book a 15-minute call.