The short answer
Custom software projects reviewed on Clutch typically cost $10,000 to $49,999, and the average is $132,480 over about 13 months, per Clutch's pricing data updated September 2026. Simple internal tools sit at the low end. Builds that must integrate a POS, ERP or payment gateway run into six figures. Scope and integrations move the price more than any hourly rate.
What Do Projects Actually Cost by Size?
Clutch's pricing data, last updated September 21, 2026, is the most useful public benchmark. Custom software projects reviewed there typically cost $10,000 to $49,999, and most firms charge $25 to $49 an hour. By country, the US band is $50 to $99 an hour, Canada and Australia run $100 to $149, and India, the Philippines, Ukraine, Spain and Mexico sit at $25 to $49. The ranges below for larger builds are our own planning figures from the projects we scope, not a published survey.
The average across Clutch-reviewed projects is $132,480 with a timeline of about 13 months, and the average monthly cost is $10,209. That average is a more honest planning anchor than any vendor's starting-at price.
| Project shape | Typical 2026 range | Timeline |
|---|---|---|
| Simple internal tool or MVP | $10,000 to $50,000, the typical Clutch project | 2 to 4 months |
| Mid-size business application | $50,000 to $250,000, our planning range | 4 to 9 months |
| Custom ERP or multi-system platform | $150,000 to $500,000 plus | 6 to 18 months |
| Ongoing operation and extension | 15% to 25% of build cost annually, a common rule of thumb | Continuous |
What Moves the Price Most?
Four levers dominate the quote. Scope is first and always: every screen, role, and report is engineering hours. Integrations are second; each system the software must talk to, POS, accounting, payment processing, adds connective work that is invisible in mockups. Team location is third: Clutch's published bands run from $25 an hour at the low end to $100 to $149 in the highest-priced countries, and the cheap end frequently costs more by the second rewrite. Compliance is fourth: payments, lending, and health data carry security and audit requirements that price in from day one.
The honest lever nobody sells: cutting scope to the workflow that actually earns money. Version one of a system that nails the five daily workflows beats a two-year everything build that ships stale.
Why does scope drive cost more than hourly rate?
Scope drives cost more than rate because hours scale with surface area, not with who is billing them. Every screen, role, permission and report is a thing to design, build, test and then maintain. A team at $75 an hour building forty screens costs more than a team at $150 an hour building twelve.
This is why comparing two quotes by their hourly figure is the most common way buyers get burned. Normalise both to the same screen and integration count first, and the cheaper rate often turns out to be the more expensive project.
How much do integrations add to a software budget?
Each system the software must talk to (POS, accounting, payroll, a processor's gateway) carries its own authentication, data mapping, error handling and sandbox testing. In the worked example below, two integrations account for $20,000 of a $120,000 build, or about 17%.
Integrations are also where timelines slip, because the third party controls the sandbox, the rate limits and the review queue. Budget calendar time for their responsiveness, not just engineering hours for yours.
What Drives the Price of a Small-Business Build?
For a merchant or small operator, the quote is set less by the app itself than by what it has to connect to and what rules it has to follow. Four items account for most of the difference between a $30,000 tool and a $150,000 platform.
Use the table as a scoping checklist: every row marked yes adds design, build and test hours to the estimate, and should appear as its own line item in a credible quote.
| Cost driver | Why it adds cost | What to ask the builder |
|---|---|---|
| POS integration | Each POS exposes a different API, sandbox and approval process; orders, items and refunds must map cleanly | Which POS versions are supported, and who handles API changes after launch |
| ERP or accounting sync | Two-way sync needs conflict rules, retries and reconciliation reports so the books match | Is sync one-way or two-way, and how are mismatches surfaced |
| Card payments | PCI DSS applies to any business that stores, processes or transmits cardholder data, including through a third party | Does card data ever touch our servers, or is it tokenized by the processor |
| Data migration | Old spreadsheets and legacy systems need cleaning, mapping and a tested cutover | Is migration priced separately, and how many trial runs are included |
| Roles and permissions | Each role multiplies screens and test cases, and audit logs add more | How many roles are in scope, and is an audit trail included |
Does custom software that takes card payments need PCI compliance?
Yes. The PCI Security Standards Council states that PCI DSS applies to any entity that stores, processes or transmits cardholder data, whether it does so directly or through a third-party service provider. The cheapest compliant design hands card entry to the processor's hosted fields or terminal so card numbers never reach your servers, which shrinks the scope you have to validate.
Ask the builder to show where card data flows on a diagram before pricing. If raw card numbers pass through the custom system, the security and audit work rises sharply and should be priced as its own line.
Is hiring an in-house developer cheaper than a firm?
Usually not for a single project. The BLS reports a median annual wage of $135,980 for software developers in May 2025. Benefits add more: in private industry, wages are 70.0 percent of employer compensation costs and benefits the other 30.0 percent, per the BLS June 2026 compensation release. Applying that ratio, one median developer costs roughly $194,000 a year before recruiting, equipment and software.
That is more than the $120,000 worked example below, and one developer rarely covers design, testing and infrastructure alone. In-house earns its cost when there is a steady multi-year roadmap, not a single defined build.
What Does a Worked Example Look Like?
A merchant operation wants an order and inventory system tied to its POS and accounting. Call it 12 screens, 3 roles, 2 integrations, and reporting.
At a blended $100 an hour, just above Clutch's $50 to $99 US band: design and architecture 150 hours, $15,000. Core build 700 hours, $70,000. Integrations 200 hours, $20,000. Testing and launch 150 hours, $15,000. Total near $120,000 across roughly six months, close to the Clutch average cost of $132,480 though on a shorter timeline than its 13 months.
Run the same numbers at an offshore $40 rate and the sticker falls by 60%, to about $48,000, but budget review cycles and rework honestly before believing the arithmetic.
When Is Off-the-Shelf the Right Answer?
Most businesses should not build. If an established product covers 80% of the need at $50 to $300 per user per month, the subscription wins on speed, support, and upgrades, and the honest advice from a builder is to buy it. Custom earns its cost when the workflow IS the business advantage, when per-user licensing across a large team dwarfs a build, or when the off-the-shelf product forces the operation to work the tool's way at real operational cost. A build is a strategic asset, and assets deserve a real business case, not a vendor pitch.
When should you buy software instead of building it?
Buy when an established product covers roughly 80% of the requirement, because the remaining 20% is almost never worth six figures and a year. Subscription software also absorbs security patching, uptime and upgrades that a custom system makes your problem permanently.
Build when the workflow is the edge: when the way the business runs is the thing competitors cannot copy, when per-seat pricing becomes punitive at scale, or when no product on the market models the operation at all.
How Do You Scope a Build Without Getting Burned?
The checklist that separates good engagements from horror stories.
- Write the five workflows the software must nail before talking to any builder
- Demand a discovery phase with a fixed-price outcome: architecture, backlog, estimate
- Insist on staged delivery with working software at each stage, not a single far-off launch
- Get source code ownership and deployment access in the contract
- Budget 15% to 25% a year to run and extend it, not just the build
- Check who maintains it in year two before signing who builds it in year one
How to Read a Development Quote
A quote you cannot audit is a number, not a plan. A credible proposal itemizes design, build, integrations, and testing separately, states whether the price is fixed or time and materials, names the team and their location, and ties payments to shipped milestones rather than calendar dates.
The comparison discipline: normalize every quote to scope. A $60,000 bid and a $140,000 bid for the same request are usually not pricing the same software; one of them has quietly cut screens, integrations, or testing. Make each bidder map their price to the same feature list before comparing digits.
- Line items for design, build, integrations, and testing
- Fixed price or time and materials, stated plainly
- Named team, location, and who owns the code at the end
- Payments tied to shipped milestones
What should a credible software quote itemise?
A credible proposal separates design and architecture, core build, integrations, and testing and launch into distinct line items with hours against each. It states plainly whether the price is fixed or time-and-materials, names what is explicitly out of scope, and says who owns the code and the repository at the end.
A single number with no breakdown is not a plan, and it cannot be audited against a competing bid. If a vendor will not itemise, that is the finding.
The Build vs Buy Arithmetic
Before any custom quote, price the subscription alternative honestly. Run the arithmetic: established software at an illustrative $150 per user per month for 20 users is $36,000 a year. A $120,000 custom build amortized over five years is $24,000 a year plus the 15 to 25 percent annual operation cost from the table above, so roughly $42,000 to $54,000 all in.
On those numbers the subscription wins unless the custom system does something the product cannot: encode a workflow that is the business's actual edge, remove per user pricing at scale, or integrate systems no vendor connects. That is the honest test, and it is the one a builder who wants your long term trust will run with you before taking the project.
If the arithmetic lands on building, the scoping questions above are the ones worth asking any vendor, including ours. Batch Group's software development division builds custom ERPs, internal tools and integrations for merchant operations, and quotes them itemised the way this article describes.
Commonly Asked Questions
Why do custom software quotes vary so wildly?
Because scope interpretation and team rates both swing widely. Clutch's published rates run from $25 an hour to $100 to $149 depending on country, and two vendors can read the same one-page brief as a 400-hour or 1,500-hour project. A written discovery phase collapses the variance.
What does custom software cost per month after launch?
A common rule of thumb is to budget 15% to 25% of the build cost annually for hosting, maintenance, and extension. A $120,000 build should plan roughly $18,000 to $30,000 a year to stay healthy and keep evolving.
Is an MVP worth it, or should we build the full system?
Start with the version that runs your money workflows end to end. A working core in production teaches more about the real requirements than any specification, and it starts paying back while the rest is built.
Does Batch Group build software for outside clients?
Yes. Batch Group Software Development builds custom ERPs, CRMs, mobile apps, and web applications for merchants, enterprise clients, and its own Sub ISOs, with teams that stay on to run what they ship.
Is it cheaper to hire a developer than to hire a software firm?
For a single defined project, rarely. The BLS median wage for software developers was $135,980 in May 2025, and benefits make up 30 percent of private-industry compensation costs, so one developer costs roughly $194,000 a year fully loaded. A firm brings design, testing and infrastructure for a fixed scope.
Does custom software that takes card payments need PCI compliance?
Yes. PCI DSS applies to any business that stores, processes or transmits cardholder data, even through a third-party provider. Using the processor's hosted payment fields or terminals keeps card numbers off your servers and narrows what you must validate.
Sources
- Clutch: Software Development Pricing Data (updated September 21, 2026)
- U.S. Bureau of Labor Statistics: Software Developers, Occupational Outlook Handbook (modified August 27, 2026)
- U.S. Bureau of Labor Statistics: Employer Costs for Employee Compensation, June 2026
- PCI Security Standards Council: Does PCI DSS apply to merchants who outsource all payment processing?
Keep reading