Define the first release
List the users, complete tasks and exceptions that must work at launch. Share sample records and existing reports.
Cost guide
What affects the cost of a custom web application in Malaysia?
UNO's custom web application projects start from RM30,000. A useful budget discussion begins with the work people must complete, rather than the number of pages on a sitemap. The quotation needs to cover the rules and connections behind each screen.
Request a project quotationWhat belongs in your quotation?
For an approval system, that includes who can submit a request, who may approve it, what happens when it is returned and how the decision is reported. A second department with different rules can add work even when the screens look similar. An integration adds mapping, access checks and failure handling as well as the visible feature.
| Scope item | What to bring to the discussion |
|---|---|
| Users and permissions | Roles, departments and restricted records |
| Workflows | A real example from submission to completion |
| Integrations | System names, current documentation and vendor contact |
| Migration | Sample files, record volume and known data issues |
| Reports | Existing examples and definitions of the totals |
| Running costs | Hosting, external services, maintenance and support needs |
Compare proposals against the same first-release scope. Ask what is included in testing, deployment, training and handover, and which dependencies can affect the schedule. A fixed headline price is difficult to assess without those details.
Prepare a comparable project brief
Use the same assumptions when discussing scope with development teams.
Identify dependencies
List connected systems, vendor access, data migration and the people responsible for approvals.
Agree acceptance and operation
Include testing, training, handover, account ownership and ongoing costs in the proposal.
Web application budgeting questions
Is RM30,000 a fixed price for every web application?
RM30,000 is UNO's advertised starting point for custom web application projects. The quotation follows a review of user roles, workflows, integrations, reports and migration. A platform covering several departments is a different scope from one approval workflow, even when some screens look similar.
Why can web applications with similar screen counts have different costs?
A web application's cost depends on the rules and connections behind each screen as well as the interface. Different approval limits, restricted records, exception routes and reporting definitions add implementation and testing work. Share a complete workflow and sample records so these differences appear in the quotation.
What should we compare alongside the web application build price?
Compare web application proposals against the same first-release scope, including testing, deployment, training and handover. Identify hosting, external services, maintenance and support costs separately, and agree who manages the accounts. A headline price alone does not show which responsibilities remain with your team.