Custom software development cost in 2026: ranges, rates and how to estimate

Published October 7, 2026

Custom software development cost in 2026 runs from about $20,000 to $90,000 for a small-business system (an internal tool, a customer portal, a CRM built around your own process) and $90,000 to $250,000 for a mid-size platform, going by Rorixtech's October 2026 tiers, which are one vendor's figures. Survey data lands in the same place: in GoodFirms' September 2026 survey of 100-plus development companies, 65.7% of projects fell between $30,000 and $100,000. Wide bands. The spread inside them is what matters to you. One developer saw two quotes for the same booking app, $9,000 and $74,000, from one page of description, and both could have been honest. The hourly rate, the scope the vendor assumed and the work they left out each move the number by a multiple. So the sections below put a source on every range, show how to build a software development cost estimate from your own brief, and work one small-business example through at seven different rates. Our own rate is in there too: $8,000 a month for a senior engineer, about $50 an hour, arithmetic included.

How much does custom software development cost in 2026?

Three kinds of number get printed as "the cost of custom software", and they measure different things. A vendor tier is what one shop charges, a survey band is what many shops say they charge, and directory data is what reviewed clients paid. Here they are side by side, labeled.

Two rows need a note. Clutch's average ($132,480) sits far above its typical project ($10,000 to $49,999) because a handful of large projects drag the mean up; Fullstack Labs calls it "a right-skewed distribution" (October 14, 2026). If you're a small business, use the typical band and ignore the average. NextGen's tiers start at $40,000 because the page says they assume a US-based team billed at a blended $140 to $220 an hour. Halve the rate and you halve the tier.

What small businesses report paying

Published ranges come from sellers. These came from buyers, in their own words and with dates.

• A music school had an agency build a system that has since "become the main tool our entire business uses": $7,000, which the owner says was less than a year of the subscriptions it replaced (r/CRM, December 2025).
• An operations lead specified and tested a custom CRM in 12 weeks for AU$36,000, penetration test included, using AI tools plus an offshore team of four (r/CRM, August 2026). "Does not include my salary or sleepless nights."
• A non-technical founder shipped a scheduling product for HVAC contractors in 12 weeks for $58,000 against a $65,000 cap (r/SideProject, June 2026).
• Two rebuilds of aging applications, reviewed on Clutch: about $140,000 for a 15-year-old portal over nine months (January 2025) and about $285,000 for 35-year-old software at a chemical manufacturer over seven months (February 2025).

So "custom software for a small or mid-size business" has cost real buyers anywhere from $7,000 to $285,000. Here's why.

Why do two quotes for the same software differ so much?

Five things explain most of the gap, and you can ask about every one of them.

1. The hourly rate comes first. $25 an hour and $250 an hour both exist in 2026 (the rate table below has both). Same 400 hours, $10,000 or $100,000.
2. Then the scope each vendor assumed. A founder who sent one brief to seven shops got "two offshore studios came back same-day with no questions, $9k and $11k. priced what they assumed I meant, not what I actually needed" (June 2026). When a quote arrives with no questions attached, it was priced for a different product from yours.
3. Who does the work matters more than who sells it. A senior engineer on the sales call and a junior one in the repository (the folder that holds your code) is a common pattern, and it shows up later as rework. Ask for names.
4. A low quote is often a partial one. Design, testing, project management, deployment, importing your spreadsheets, documentation and a warranty period are each a line that one quote includes and another leaves out.
5. Whether anyone did discovery before pricing. Acquaint Software, a vendor, says "A project quoted at $60,000 without discovery commonly runs to $90,000 to $100,000 by the time it ships". That's one vendor's claim, and it matches what paying clients say further down.

Two quotes can also be the same price in different clothes. A startup team on r/SaaS had "One agency quoted us 80k fixed for the whole MVP. Another wants to do hourly at 150/hr and estimated 400-500 hours" (October 2025). If the estimate holds, the hourly route lands at $60,000 to $75,000; if it doesn't, there's no ceiling. The fixed $80,000 has the overrun risk priced in, until the first change order. Neither is cheaper until you know how firm the scope is.

What do software developers charge per hour in 2026?

Rate tables on cost pages contradict each other because they sample different pools of sellers. Here is the 2026 data with the pool named on every row.

Now the contradictions. Clutch's $50 to $99 for the United States is the average band of US firms listed in its directory, which leans toward small shops that sell to small businesses. Keyhole's $125 to $250+ is the senior tier in a US firm's own table. Second Talent reckons agencies "quote 1.5 to 2.5 times the individual rate, or $165 to $275 an hour", and cites a federal contract ceiling with a median of $136.56 for a developer. All three can be right at once, because they describe different sellers. Western Europe is the sharpest case: Accelerance surveys outsourcing firms that sell abroad and gets $64 to $76 for seniors, while Keyhole's table describes local Western European firms at $150 to $165. When a vendor shows you a regional table, ask which pool it came from.

The global picture is lower than any US table. Techreviewer's January-to-February 2026 survey of 127 providers put the largest band at $30 to $49 an hour (37.8%), with fewer than one in ten billing $100 or more; a quarter of the respondents were in India. GoodFirms has 56.3% of surveyed companies at $20 to $50, and Clutch says most firms it lists charge $24 to $49. Accelerance reports that rates "dipped by single-digit percentages in all major outsourcing regions" this year.

For comparison with hiring: the median US software developer earned $135,980 in May 2025 (Bureau of Labor Statistics), and benefits are 30% of employer cost (BLS, June 2026), so a salaried developer costs about $93 an hour on a 2,080-hour year before recruiting, equipment or management (our arithmetic). Second Talent's fully loaded in-house figures run $75 to $190 an hour by seniority.

Deepsel's rate, with the arithmetic

Few vendors print their own rate on a cost page. Ours: one dedicated senior engineer is $8,000 a month full-time or $4,000 a month half-day. At 160 working hours a month that's $50 an hour, and the half-day option is the same rate for about 80 hours. The engineers work from Hanoi, Vietnam, under a Delaware corporation. Their working day overlaps US hours. That's how the rate lands inside Accelerance's Southeast Asia senior band with a US contract and US-jurisdiction IP terms attached. The $15,000 a month fractional CTO retainer adds technical leadership on top of the build team, and our fractional CTO cost guide prices that market on its own.

What drives the price up or down?

Hours are the cost, so the question is what adds hours. In rough order of how often they surprise a first-time buyer:

• Integrations are the usual first surprise. Ardura prices common ones (payments, email, analytics) at $1,000 to $5,000 each (April 2026); SFAI Labs says "Each integration point adds $5,000-$15,000" (February 2026). Both are vendor figures, and the gap between them is real: sending an email through an API is a day, a two-way sync with your accounting system is weeks.
• Payments and subscriptions cost more than they look. $8,000 to $30,000 on Appinventiv's table, and Blackthorn Vision puts billing alone at $20,000 to $50,000 by the time proration, tax and failed payments are handled. If all you need is to take a card, a hosted checkout keeps it at the low end.
• Compliance can double the bill. HIPAA, SOC 2 or GDPR requirements add 30% to 100% in SFAI Labs' figures, through audit trails, access controls and testing.
• Serving several customer companies from one system is a different product. Each organization needs its own data, users, roles and settings, and uxcontinuum calls that "an architecture decision, and it is expensive to bolt on later" (September 2026). That's the line between an internal tool and a SaaS product, and our SaaS development cost guide covers the extra.
• Each user role is its own set of screens and rules. Owner, office staff, delivery driver, customer: four kinds of user means four of everything that touches permissions.
• Data migration is a project of its own. Moving years of records out of spreadsheets or an old system brings surprises nobody scoped, and our page on legacy software modernization goes into them.
• Custom-designed screens cost more than a component library, and for an internal tool the library is usually the right call.
• Scope growth is the one line you control. GoodFirms' survey puts the cost of scope creep at 10% to 25%.

How do you estimate software development cost?

A software development cost estimate is a range with its assumptions written down. One number with no assumptions is a guess, rounded to look like data. Atomic Object's nine estimating techniques (decomposition, team estimates, prior data, concrete experiments, range estimates and separating assumptions from risks, among them) are the best short read on the craft. Here's the version we run with clients. Seven steps, and you can do them on your own brief in an afternoon.

1. Write the scope as things people do. One line per action: "the office manager creates a rental contract with a return date", "a driver sees today's deliveries on a phone". Twenty to forty lines covers most small systems. If you can't write the line, nobody can price it.
2. Group the lines into features and give each a low and a high in hours. Two numbers, never one. When the high is more than three times the low, the feature isn't understood yet: split it, or spend a day on a throwaway experiment (Atomic Object's "concrete experiments").
3. Add the work that isn't a feature. Design, testing, deployment, documentation, project management and meetings. In the example below that's about 30% of all hours, which matches what we see on real projects. Quotes that skip this line are the ones that grow later.
4. Multiply by the rate of the people who will write the code. Write the rate down next to the total. Six hundred hours at $50 and at $200 are different products, and the rate table above tells you which pool a number came from.
5. Add the costs that aren't hours. Hosting, third-party services, licenses, app-store accounts, a domain. For an internal tool these are tens of dollars a month; for a payments product they're a budget line.
6. Hold contingency outside the quote. Scope creep eats the 10% to 25% GoodFirms measured, and even happy clients spend their buffer (a Clutch reviewer who spent about $250,000 is quoted further down: he used all of his). Keep 15% to 25% that the vendor never sees; the rest of the controls are in our guide to cost management in software outsourcing.
7. State the uncertainty band, then narrow it with discovery. Before requirements exist, software estimates can be wrong by a factor of four either way, and a two-to-six-week discovery brings that to about plus or minus 25%; Fora Soft's write-up of the "cone of uncertainty" puts it as ±400% to ±25% (July 2026). So a pre-discovery "$40,000" means $10,000 to $160,000. Discovery is priced accordingly: $1,500 to $4,000 and one to two weeks for an internal tool or integration on Acquaint Software's table, $5,000 to $15,000 in two to three weeks for a small-business scope at Fora Soft, and $2,500 to $40,000 across the published prices one engineer compiled on dev.to (October 2026). Deepsel's version is the $3,000 fixed one-week sprint, described below.

And one more of Atomic Object's points, with credit, because it's the one that catches buyers: false significance. A quote of $47,350 is no more accurate than "$40,000 to $55,000". The extra digits came out of a spreadsheet, and the spreadsheet knew nothing its author didn't.

A worked example: estimating a small-business internal tool

Now the method on a real-shaped brief. An equipment rental company with 12 office and yard staff runs on spreadsheets and a shared calendar. It wants one system for customers and the units they rent, recurring rental contracts with return dates and renewal reminders, delivery scheduling with driver assignment, invoice export to QuickBooks Online, text and email reminders, and a dashboard for the owner. Three kinds of user: owner, office, driver. A web app that works on a phone, rather than a native mobile app. The hour bands below come from past builds rather than a template. They're still pre-discovery figures, so treat them as the wide band.

Now the same 480 to 770 hours at the rates from the table above, which is the whole reason two honest quotes can be $50,000 apart.

Read the table from the buyer's side. A $25,000 quote and a $75,000 quote for this brief both sit inside the US directory band; the cheaper one is probably a smaller shop, fewer hours, or less included. At $150,000 you're looking at a US firm at its own rate with everything in. And $12,000 from an Indian agency is plausible on hours and rate. The questions then are who manages it, which our guide to outsourcing for startups and small businesses takes on, and what year two costs, which the after-launch section covers. None of the quotes is wrong until you've seen its hours.

Calendar time: 480 to 770 hours is three to five months for one full-time engineer, or roughly half that with two working in parallel, which is how we'd staff it after the first month. Add the running costs from the after-launch section below and you have the whole number.

Fixed price, hourly or a monthly team: which should you choose?

Most vendors offer more than one. In GoodFirms' 2026 survey, 81% offer time and materials, 66% fixed price, 59% a dedicated team and 47% milestone-based pricing. Buyers lean the other way from vendors: they want a fixed number, then flinch at it. The r/SaaS team with the $80,000 and $150-an-hour quotes put it plainly: "The fixed price quotes are giving me anxiety because they're big numbers upfront", while the hourly one "obviously ... could go over". Another founder, comparing seven proposals, called an uncapped hourly freelancer "fine if you've managed dev projects, terrifying if you haven't".

Fixed price moves the estimating risk to the vendor, who prices it in and then defends the scope. Week three is where it goes wrong: something real turns up, and the answer is "out of scope" plus a change order. It suits a discovery phase or a first module, where the scope is small and known. A whole system, rarely.

Hourly, or time and materials (you pay for the hours worked, at an agreed rate) is honest about uncertainty, and it's the cheapest model when the team is good and the scope keeps moving. The catch is that you can't see padding. One commenter "watched two friends get destroyed on hourly because they couldn't tell when a shop was padding". So it needs a cap, demos you can click through, and the right to stop.

A dedicated engineer or team by the month is hourly with a predictable invoice. It fits when the work continues past the first release, which for a system the business runs on is nearly always. What kills it is drift. A retainer with no roadmap buys presence rather than progress.

We'd mix them, and it's the shape buyers who did well describe: a small fixed first step with a defined deliverable, paid on acceptance, then month-to-month with a 30-day stop clause, a working demo every two weeks and the code in your own accounts from the first commit. That's how Deepsel is priced. It's also what we'd tell you to ask any vendor for, and our guide to choosing a software development company has the rest of the questions.

What does custom software cost after launch?

The build is the first bill. Year two is the one buyers forget, and the one that sours relationships: a commenter on r/CRM has "seen companies spend $15K on custom development then get hit with $3K+ annually just for security updates and bug fixes" (December 2025). That's 20% a year, right inside the vendor rule of thumb. Budget for four things.

• Upkeep runs 10% to 25% of the build each year by the vendor rules of thumb, 10% to 20% (Fullstack Labs, citing GoodFirms) or 15% to 25% (Blackthorn Vision), and it covers dependency updates, security patches, bugs and small changes. On a $35,000 build that's $3,500 to $8,750 a year. Ask every vendor whether it's a retainer, hourly or per request, and what the response time is, before you sign.
• Hosting and services are tens of dollars a month for an internal tool at 2026 list prices (Render: $7 a month for a web service and $19 for a managed Postgres database; Supabase Pro from $25), more with SMS volume, file storage or an AI feature.
• Expect the build itself to run over. The best academic data (Flyvbjerg and Budzier, 1,471 IT projects) found an average cost overrun of 27%, with one project in six running 200% over; those were mostly large public-sector projects, so take the shape rather than the number. McKinsey and Oxford put large IT projects (over $15 million) at 45% over budget on average. Small projects built in two-week increments don't behave like that, which is the strongest argument for starting with one module.
• The handover has a price too. Documentation, admin access and a second person who knows the system. If a vendor's price leaves them out, add them back before you compare it with anyone else's.

He was a satisfied client. So was the founder who wrote that "The project turned out to be more complex than initially expected, which meant the final cost was higher than the original estimate" (Clutch, August 2025). Overrun is normal. The question for a vendor is how early they tell you, and whether the increments are small enough that you can stop.

What does Deepsel charge for custom software?

A former corporate buyer of $50,000 to $100,000 a year in services wrote that "nothing aggravated me more than 'lets setup a call to discuss pricing'. No, give me a range." Agreed. Three prices, all public on our services page, and none of them changes after the call.

• The sprint is $3,000 fixed and takes one week. A full audit of product, code and architecture; critical bugs and security holes fixed and shipped; a plain-English scorecard and roadmap, yours to act on with Deepsel or anyone. If you have a prototype, an AI-built app or a system that already runs, start here. You end up with a written roadmap to put next to the quotes you're holding, for about what the vendors above charge for discovery alone.
• One senior engineer is $4,000 a month half-day or $8,000 full-time, with a demo every two weeks and a daily window that overlaps US hours. The worked example above is three to five months of this.
• A fractional CTO plus the build team is $15,000 a month, for founders with nobody technical in charge. Our fractional CTO cost guide prices that against the market.

What's inside the number: the people on the discovery call are the people who write the code, every two weeks ends in a version you can open, and the documentation arrives with the code rather than after it. The rate works because the team sits in Hanoi and the company in Delaware (the arithmetic is in the rate section above). This team replaced the front end of the Swiss federal government's central login while it stayed live, built a nightclub booking marketplace with deposits and payments, and shipped its own AI coding assistant in 2023, before agent tools existed.

Terms, as published:

• Month-to-month, 30 days' notice, no termination fees.
• First 30 days: full money-back guarantee.
• IP yours from the first commit under a US-jurisdiction agreement; repos and servers in your own accounts.
• Any engineer replaced within 7 days if not a fit.
• Happiness Index: you score us every month on delivery, accepted work and incidents. A month under 50 is refunded.

Some readers should buy something else. When a packaged tool does the job, we'll say so on the call, and you should buy it; the music-school owner's $7,000 was well spent because no packaged CRM fitted, and most businesses aren't that unusual. Engineers in the room in a US city, or a regulated enterprise program with a dozen stakeholders, put you in the $150-to-$250 column, so budget for it. A startup building a first product rather than a business tool is better served by MVP development and the MVP development cost guide (and AI MVP development if the product itself uses AI). If something is already built and stuck, read software project rescue. And if you'd rather compare shops first, we keep a list of small software development companies that build for startups, ourselves included.

How do you tell which quote to trust?

Seven questions for the quotes already in your inbox, in the order that saves the most time.

1. Ask for the hours by feature and the rate behind the total. A vendor who built the estimate has it on a sheet already; one who can't produce it picked the number.
2. Ask who writes the code, by name, and where they sit, then whether those same people were on the scoping call.
3. Find out what's excluded. Design, testing, project management, deployment, data import, documentation, warranty: price each exclusion and add it back before you compare anything.
4. Count the questions the vendor asked you. Zero means they priced their own assumptions. The founder with seven proposals concluded that "the proposal IS the test. how a shop scopes you is how they'll build for you."
5. Put every quote on the same scope and the same hour count, then look at the rate. Now the $9,000 and the $74,000 are comparable, and usually one of them is a different product.
6. Read the terms before the price. Payment on demo, repository and accounts in your name from the first week, exit terms, who owns the code (the longer list is in our guide to risk management in software outsourcing). A startup lawyer's rule from r/startups: "you learn a lot from a developer based on what they are willing to put in a contract."
7. Prefer the vendor who told you what to cut. The one that agreed with everything priced everything.

Custom software development cost: frequently asked questions

If you're pricing a system for your business, or holding quotes that don't agree, book a free 30-minute call with Tim. Bring the quotes. You'll leave with a read on the scope and the numbers whether or not we work together, and if something is already built, the $3,000 one-week sprint turns it into a written roadmap.