How to Scope a Custom Software Project Without Overpaying
What drives the cost of custom software in Malaysia, how to write a brief vendors can quote fairly, and the contract terms that protect you.
Two vendors quote the same brief. One says RM 15,000, the other RM 120,000. Both may be honest — they are simply pricing different projects, because the brief left the important questions open.
Most overruns in custom software start at scoping, not in development. Here is how to scope a build so quotes are comparable and the project stays on budget.
What actually drives cost
Features are the visible part of a quote. These are the parts that move the number more:
- Integrations. Every system the software must read from or write to — accounting, CRM, e-invoicing, WhatsApp, a hospital system — adds design, testing and edge cases. Legacy systems without an API cost the most.
- Roles and permissions. Two user types is simple. Eight roles with different approvals and data visibility is a different project.
- Data migration. Moving years of spreadsheets into a clean database often takes longer than building the screens.
- Edge cases. The 10% of orders that are unusual — partial deliveries, credit notes, manual overrides — often take half the effort.
- Non-functional requirements. Uptime, audit logs, data residency, response times and security reviews.
- AI components. Model usage costs, evaluation on your real data, and human-review workflows.
If a quote is far below the others, check which of these it quietly left out.
Write a brief that can be quoted fairly
A good brief describes the process, not the screens. Include:
- The process today, step by step, with who does what and in which tool.
- Volumes. Orders per day, users, documents per month.
- Systems involved, with names and whether they have an API.
- The outcome you are paying for, as a number: hours saved per week, time to quote, error rate.
- What is out of scope — as important as what is in.
- Constraints: PDPA, data location, security reviews, go-live dates tied to real events.
If you cannot fill in points 1, 2 and 4, you are not ready for a build quote. You are ready for an audit — a short paid engagement that maps the process and quantifies the leak, so the build can be scoped properly. That is how our AI Opportunity Audit works, and why its fee is credited toward the build.
Contract terms that protect you
- Fixed price per milestone, each milestone ending in working software you can test — not a document.
- Payment tied to delivery. We use 40% at kickoff, 40% at a working milestone, 20% at go-live.
- You own the code and data. Hosted on your accounts wherever possible, with admin access for your team.
- KPI agreed before kickoff, with a baseline measured in advance.
- Stabilisation window. At least 30 days after go-live where defects are fixed without new change requests.
- Documentation and handover training as named deliverables, not assumptions.
Plan for year two
Software has running costs: hosting, model usage for AI features, monitoring, and changes as your business evolves. Ask every vendor for an estimate of annual running costs and what a maintenance retainer includes. A cheap build with an expensive or undefined maintenance path is not cheap.
Finally, plan who in your company will own the system. The strongest projects we see have an internal owner who was trained during the build — sometimes through a course like Build with AI — and can handle small changes without calling a vendor.
Summary
Scope the process, not the screens. Put a number on the outcome. Compare quotes on integrations, roles, data and edge cases rather than feature lists. And insist on milestones, ownership and handover. If you would like a second opinion on a brief or a quote, send it to us — we will tell you what it is missing.