How Much Does Custom Software Development Cost? Six Cost Modules + a Real Quote Sample

This is the question clients ask most and the industry is least willing to answer head-on. This page lays it all out: the cost structure of custom development, man-day rates, three budget tiers, an itemized quote for 180 man-days, and why two vendors can differ by 3×. The ranges reflect typical rates in Suzhou and the Yangtze River Delta, and every project is quoted line by line — before you sign we provide a feature module × man-day quote breakdown, and it's yours to keep even if you don't work with us.

BOTTOM LINE

The Bottom Line: Budget Ranges for Three Types of Systems

If all you want is a mental model of the budget, this table and one range chart are enough. Within a single category, quotes can differ by 5× — so the wide ranges aren't a brush-off, they're the truth.

Project TypeTypical Budget RangeTypical TimelineTypical Examples
Tools & Mini Programs RMB 50,000 – 200,000 4–8 weeks Booking mini programs, repair ticketing systems, inspection and data entry, corporate websites + admin panels
Management Systems RMB 150,000 – 800,000 2–4 months ERP, CRM, WMS, MES, inventory management, SCM, production reporting and quality inspection
Platform & Production-Line Level From RMB 800,000, quoted individually 4+ months Multi-factory collaboration, full-line smart factories, IoT platforms, industrial e-commerce ecosystems
020406080100Initial development cost (RMB 10k; design, development, testing, deployment included)Tools & Mini Programs50–200kMobile apps (with backend)60–200kManagement systems ERP / WMS / MES150–800kProduction-line software (with device integration)250–800kPlatform level (multi-factory / multi-role)From 800k
Quotes within one category can differ by 5×: a single-warehouse WMS with 300 SKUs and a four-warehouse WMS with barcode-driven putaway that writes back to ERP are the same category, yet nowhere near the same project.

Why Are the Ranges So Wide?

Because behind the phrase “a WMS” there might be a single-warehouse in/out/stock system with 300 SKUs, or a multi-entity system spanning four warehouses with barcode-driven putaway, batch traceability, and write-back to ERP. The first can go live in 3 months; the second may not be done in 8.

To tell which end of the range you're on, look at three variables: number of entities (one warehouse, or multiple warehouses and companies), traceability depth (batch / serial number / expiry), and number of integrations (ERP, equipment, third-party platforms). Each variable adds roughly 30%–60% to the man-days.

Illustration of custom development budgets rising with system complexity
Budgets don't grow linearly: every added layer of entities, traceability, or integration multiplies the testing and validation effort.

COST STRUCTURE

The Pricing Formula: Where the Money Actually Goes — Six Areas

Custom development quote = Σ (man-days per feature module) × man-day rate. Man-days aren't spent only on writing code — the chart below shows the man-day distribution of a typical project. Cut any segment and it comes back doubled somewhere else.

12%12%55%10%5%6%Discovery10–15%Process mapping · requirements specUI / interaction design10–15%Prototype review · interface designFront-end & back-end development50–60%Coding · APIs · integrationTesting8–12%Functional & performance · bug fixesDeployment & migration3–6%Environments · data · trial runDocumentation & training3–5%Manuals · training · handover
Man-day distribution of a typical custom project (midpoints of the ranges). Suppliers who quote below the low end almost always cut testing, deployment and migration, and documentation and training — the three things that bite you first after go-live.
Cost ModuleShare of Total Man-Days (Typical)What It CoversWhat Happens If You Cut It
Discovery & requirements analysis10–15%On-site review of business processes; produces the requirements spec, module list, and itemized quoteThe main source of later rework — cutting it is planting a landmine
UI / interaction design10–15%Interaction prototype review, interface design, field and permission mappingInterfaces that work but are painful to use; staff resist and everyone ends up back in Excel
Front-end & back-end development50–60%Feature coding, API development, permissions and approval workflowsThe core — can't be cut, only optimized
Testing8–12%Functional / performance / compatibility testing, bug fixes and regressionIncidents and data errors after go-live; far more expensive than the testing itself
Deployment & data migration3–6%Environment setup, legacy data cleansing and migration, trial runLegacy data loss, or a long dual-track period running both systems
Documentation & training3–5%Deployment docs, user manuals, role-based trainingNobody knows how to use the system once people leave, and maintenance is locked to the vendor

Man-day rate reference (typical ranges in Suzhou and the Yangtze River Delta)

LevelMan-Day RateTypical Project Role
Junior engineerRMB 800 – 1,200 / man-dayPage development, simple APIs, data cleanup and entry
Mid-level engineerRMB 1,200 – 2,000 / man-dayCore business modules, database design, third-party integrations
Senior engineer / architectRMB 2,000 – 3,500 / man-dayArchitecture design, performance and concurrency, devices and industrial protocols, hard problems

Quotes well below the low end usually leave out rows two, four, and six of the table above — design, testing, and documentation. What these three share: the client can't spot it at the acceptance meeting, but will feel every bit of it three months after go-live.

WORKED EXAMPLE

What a Real Itemized Quote Looks Like: Single-Warehouse WMS + WeCom Approvals

Put the formula on paper and you get the table below. Project background: an electronics assembly plant in Suzhou, one warehouse with about 1,800 SKUs, needing barcode receiving, putaway and picking, batch traceability, two-way sync with an existing ERP, and material-requisition approvals inside WeCom.

01DiscoveryObserve processes on siteCapture real pain points02Module breakdownFeature listScope and exclusions03Man-day estimateEstimated by moduleBy role and discipline04Rate settingBy levelBy technical difficulty05Itemized quoteEvery line checkableAttached to the contract
A quote isn't pulled out of thin air; it comes from these five steps. Any scope change sends you back to step 3 to recalculate man-days and issue a written estimate — implementation starts only after the client confirms.
ModuleKey ContentMan-DaysRate (RMB)Subtotal (RMB)
Requirements & prototypeOn-site discovery, process mapping, requirements spec, clickable prototype181,50027,000
Master dataMaterials, bin locations, batches, suppliers, coding rules241,40033,600
Receiving, putaway & pickingReceiving, putaway, transfers, stocktaking, outbound, picking, verification, shipping581,40081,200
Barcode & PDALabel templates, printing, PDA scanning UI adaptation161,30020,800
ERP integrationTwo-way sync of materials and inventory, write-back of in/out documents, exception reconciliation221,60035,200
Reports & dashboardsInventory turnover, slow-moving stock, movement details, warehouse staff performance121,40016,800
Testing & migrationFunctional and concurrency testing, opening-inventory import and reconciliation, trial run181,20021,600
Deployment, training & docsEnvironment deployment, user manual, two training sessions with screen recording121,20014,400
Subtotal—180—250,600
Project management & warranty8% of the subtotal, includes 12-month warranty and response SLA——20,048
TotalAbout 11 weeks (including trial run)180—270,648

This table is the contract attachment. If any line looks expensive, we can discuss it on its own; if you want to cut a line, you can see the impact immediately — cut the 18 man-days of Testing & migration and you save RMB 21,600, at the cost of counting the opening inventory yourselves and owning any data errors after go-live.

Why don't we quote per page? Page count doesn't track effort: a list page with an approval flow may be 0.5 man-days, while a barcode outbound page with batch validation and concurrency locks may be 3. Quote per page and the client inevitably overpays for simple pages, underpays for complex ones, and then gets asked for more money mid-project.

BUDGET TIERS

Three Budget Tiers: Which One First Depends on What You Need to Validate

These aren't packaged price lists but three common project scopes. The same system can start at Starter and expand to Standard in phase two — it's the same codebase on our side, with no rewrite.

TIER 01

Starter · Phase-One Validation

RMB 50,000–150,000 / 4–8 weeks

Best for: teams with one clear pain point who want to prove the value before investing further.

  • One core workflow (e.g., in/out/stock, repairs, orders)
  • 10–15 pages, 1–2 user roles
  • Basic reports and exports
  • One release + training
  • 6-month warranty

Typical: repair / inspection mini programs, single-warehouse inventory, quotes and order management

Get an estimate at this tier →
TIER 02 · Most popular

Standard · Full Business Loop

RMB 150,000–400,000 / 2–4 months

Best for: teams whose processes are already clear, replacing Excel or legacy systems, and needing integration with existing systems.

  • 3–5 business modules, end-to-end document flow
  • Role permissions, approval workflows, audit logs
  • Integration with existing ERP / accounting software
  • Dashboards and historical data migration
  • 12-month warranty + response SLA

Typical: ERP inventory + production reporting, WMS, CRM + order collaboration

Get an estimate at this tier →
TIER 03

Platform · Multi-Entity and Production Lines

From RMB 400,000 / 4+ months

Best for: multi-factory / multi-warehouse / multi-brand operations, or projects that need production-line data collection and public APIs.

  • Multi-entity, multi-company, multilingual
  • Device data collection (OPC UA / Modbus)
  • Open APIs and single sign-on
  • Performance, backup, and disaster recovery
  • On-site implementation and phased delivery

Typical: group-wide multi-factory collaboration, full-line smart factory, industrial e-commerce platforms

See our smart factory solution →

The price gap between tiers is driven mainly not by feature count but by three variables: number of entities, traceability depth, and number of integrations. Nailing down these three before discussing budget is more useful than listing a hundred requirements.

WHY 3×

Why Can Two Quotes Differ by 3×? Compare Line by Line, Not Totals

For the same requirements, quotes of RMB 120,000 and RMB 360,000 usually differ in these five places — not in “who's more greedy.” Line both quotes up against the table below and the source of the gap is obvious.

Source of DifferenceWhat the Low Bidder DoesAfter Go-LiveHow to Spot It Before Signing
Requirements understandingSkips discovery, pulls a lump sum out of a verbal description“This isn't included” keeps coming up mid-development, and change orders exceed the gapAsk: which page of the requirements doc does the quote map to? Is anything outside the scope written down?
Staff levelUses mainly junior staff to keep rates lowSlow progress, poor architecture; the rebuild in two years costs more than what you savedAsk: who architects this project? Can I meet them?
Testing & deploymentQuote excludes independent testing and data migrationGo-live incidents, legacy data loss, or long dual-track operationCheck whether the line items include “testing” and “migration”
System integration“Integration is billed separately”Integration with ERP / production lines / WeChat becomes the hidden bulk of the costList every system to be integrated and write them into scope
Warranty & SLANo clear warranty period or response timeEvery post-launch change means new negotiations and waiting in lineDoes the contract state the warranty period, response time, and exclusions?

ROUTES

In-House, Low-Code, or Custom Development: Three Questions to Pick Your Route

The criterion is total cost of ownership (development + operations + the labor cost of bending your processes), not the initial development fee. Answer the three questions below in order and the route basically picks itself.

① Can an off-the-shelf product / low-code cover 80%+ of your processes?Look at the gaps: are approvals, pricing, or traceability industry-specific?YesBuy off-the-shelf / low-codeTens of thousands a year + internal configuration effortNo② Is the system a core competitive advantage, and can you sustain a 3+ person tech team long term?Long view: 3-year payroll vs. one-time development feeYesBuild in-housePayroll from hundreds of thousands a year, ongoingNo③ Can the requirements be split into an 8–12 week phase that ships independently?Look at the boundary: can phase one ship on its own and deliver value?YesCustom outsourcing (phased)One-time development + annual maintenance, source code deliveredNoStandardize processes and clarify requirements firstTurn uncontrollable requirements into acceptance-ready scope, then return to question ②
The criterion is total cost of ownership (development + operations + the labor cost of bending your processes), not the initial development fee. When all three questions lead to custom outsourcing, the scope is clear and the risk is controlled — that's when comparing prices actually means something.
RouteWhen It FitsCost StructureMain Risks
Standard SaaS / low-code Processes are fairly standard, budget is limited, requirements change often Tens of thousands a year + internal configuration effort Core processes can't be changed; deep customization is limited by the platform; data is locked to the platform
In-house development team The system itself is the core competitive advantage and you plan to fund a 3+ person tech team long term Payroll from hundreds of thousands a year, ongoing Hard to hire, key-developer turnover risk, low R&D management efficiency in non-tech companies
Custom outsourcing Processes are industry-specific, need integration with production lines / equipment / private data, and you don't want a large in-house team One-time development fee + annual maintenance Picking the wrong vendor leads to rework and disputes — mitigate with phased acceptance

HIDDEN COSTS

Six Costs That Get Left Out — Put Them in Your First Budget Draft

These aren't in the development contract, but they will happen. Knowing them in advance keeps you from ending up with “a finished system that can't go live.”

1 · Legacy Data Cleansing and Migration

Legacy systems hold duplicate material codes for one part, same-name-different-item records, and duplicated customers. That data must be cleansed before migration. Data governance typically runs 5%–15% of total investment and is the most underestimated item.

2 · Metered Third-Party Services

SMS, e-waybills, maps, OCR, and e-signatures are billed per call; some ERP vendors also charge for API access. On high-volume projects, tens of thousands of RMB a year is common.

3 · Servers, Storage, and Backup

Cloud servers, object storage, database backups, SSL certificates, disaster recovery. Small and mid-size systems run thousands to tens of thousands of RMB a year; on-premise adds server and data-center costs.

4 · Licenses and Certifications

Mini-program verification fees, payment merchant accounts and processing rates, and industry-specific business licenses or cybersecurity classified-protection assessments (Level 2 typically starts at tens of thousands of RMB).

5 · Your Own Internal Labor

The time your business owners and key users spend confirming requirements, preparing data, and testing and accepting the system often costs more than the development fee. Budget at least one person at 30% of their time for 3 months.

6 · Supporting Policies After Go-Live

Performance reviews, document standards, stocktaking rules, permission approvals. Systems only amplify management; they don't replace it — without supporting policies, even a great system degrades into an electronic ledger.

COST CONTROL

Five Ways to Bring the Budget Down

Saving money isn't about cutting features — it's about cutting the scope right and ordering the work right. These five are our standard advice to clients; on average they save 20%–30%.

  1. Phase it: in phase one, build only the one workflow that delivers value on its own. Get “order → shipment → reconciliation” running first, then extend to production and cost accounting. Projects that try to do everything at once are the most likely to overrun and stall.
  2. Reuse: don't rewrite what a standard open-source ERP module already does. Odoo / ERPNext purchasing, inventory, and finance modules are mature enough; spend your money on the industry-specific 20%.
  3. Set boundaries: put “maybe later” into phase two, not the phase-one quote. The cleaner the phase-one scope, the closer the quote is to reality and the fewer mid-project changes.
  4. Cleanse data first: standardize material and customer codes before you go live. Do it internally and it costs next to nothing; hand it to the implementation vendor and it becomes tens of thousands of RMB in cleansing hours.
  5. Integrate on demand: not every connection needs to be real-time. End-of-day batch sync cuts integration effort by more than 30% and is usually plenty for reconciliation.

COMMITMENT

Jiding's Four Pricing Commitments

  • An itemized quote before you sign: feature module × man-days × rate, every line checkable. Even if you don't sign with us, take this breakdown and compare it with any team.
  • Payment in milestone installments: requirements sign-off, prototype review, phase demo, go-live acceptance. No payment for the next phase until the current one passes acceptance.
  • Complete delivery of source code and documentation: on acceptance, the copyright belongs to the client. No platform lock-in — you can migrate on your own or switch maintenance teams.
  • Warranty period and response times written into the contract: clear SLAs for post-launch bug fixes, with no vague “annual service fee.”

Why is project management a separate line? Because it's real work: progress tracking, risk alerts, version and release management, and coordination with several of your departments. Bury it in the man-day rates and you can neither see it nor negotiate it down; list it separately and you can question it and trim it — and we can show exactly what it buys.

FAQ

Frequently Asked Questions

Compared to low-cost outsourcing teams, what makes your services more expensive?

The main focus lies in requirement confirmation and process management: preparing a requirement specification and itemized quotation before signing the contract, developing only after prototype review, conducting phased demonstrations and acceptance checks, independent testing, and data migration. The cost of skipping these steps for low-cost teams is usually doubled in the middle of the project in the form of rework and disputes.

How long does it take for a management system to go online?

Single module tools or mini-programs take 4–8 weeks; management systems such as ERP, WMS, MES, and CRM usually take 2–4 months; for projects involving production line equipment integration, an additional 2–6 weeks are needed for on-site debugging. Dividing the scope into modules that can be independently launched in 8–12 weeks per phase is the most manageable pace - this is also the phasing approach we usually recommend.

Want to know which tier your project falls into?One call is enough to find out

Tell us your number of entities, traceability depth, and the systems you need to integrate, and within 48 hours we'll send an itemized quote breakdown.