The riskiest mistake is ranking vendors by the single bottom-line number. What matters is scope clarity, whether admin is included, and how acceptance / source code are written.
Scenario logic
- Internal tools: auth, lists, notifications — more controllable.
- Membership / stores: points and redemption need admin — retail membership app case.
- Content or commerce: payments and state machines raise QA cost.
See custom app development; for a lighter China channel read mini program pricing.
Line items every quote should show
- Scope and acceptance criteria
- Platforms: iOS / Android / cross-platform
- Admin / back office included or not
- Third-party integrations
- Design, QA, store release
- Source and docs — source code ownership
- Milestones, payment, change rules — requirement change control, custom software contract tips
- Warranty or software maintenance services
What “cheap” often costs
- Verbal scope that collapses at acceptance
- No admin — ops becomes code changes
- No source/docs — lock-in
- No owner after launch
How to compare vendors
- Send every vendor the same checklist
- Normalize lines: design / client / admin / integrations / QA / ops
- Confirm demo milestones are acceptance-ready
- Confirm IP and handover clauses
FAQ
Must we go dual native?
Not always. Hardware-heavy → native; dual-store budget control → cross-platform.
No UI kit yet?
Quote prototype + design + build, or lock scope with a prototype first.
How long should a quote stay valid?
Weeks if scope is stable; otherwise clarify before locking price.
Takeaway
Compare acceptables deliveries, not the lowest total. Share industry, platforms, and core flows for a structured range.
contact for software projects