TL;DR — app development cost in Singapore, up front
- A simple internal tool — one workflow, a handful of screens, one integration — typically lands at SGD 8k–35k depending on who builds it; a Singapore studio quote can reach SGD 60k.
- An MVP web app you can put in front of paying customers runs roughly SGD 25k–120k. A customer-facing mobile app on iOS and Android is usually SGD 40k–200k+.
- Custom back-office software with roles, approvals and three or more integrations starts around SGD 60k and climbs past SGD 300k at the top end.
- Who builds it swings the number as much as what you build. Freelancers and offshore teams quote lowest, a Singapore studio quotes highest, and an AI-assisted build on a well-specified scope sits between the two with studio-grade accountability.
- Our own fixed-scope builds are SGD 20k–80k. We build web apps, internal tools and agent-backed systems. We do not build native mobile apps — more on that below so you are not sold the wrong thing.
How much does it cost to develop an app in Singapore?
Between SGD 8,000 and SGD 300,000. That spread is useless on its own, and most of what ranks for the question is a portfolio page or a job ad, which is not much better. The real answer is that the price is a function of two things — what you are building (an internal tool, an MVP web app, a customer-facing mobile app, or custom back-office software) and who builds it (a freelancer, a Singapore studio, an offshore team, or an AI-assisted build). Cross the two and you get a band you can put in a budget line.
We build apps for a living, so treat this as a friend's read rather than a sales sheet. Every figure below is either our own pricing or indicative of what we see quoted in the Singapore market when clients show us competing proposals. None of it is a survey. All of it excludes 9% GST. The structure mirrors our web design cost guide: one table, then what moves the number.
| Build type | Freelancer | Singapore studio | Offshore team | AI-assisted build |
|---|---|---|---|---|
| Internal tool (one workflow, 3–8 screens, one integration) | SGD 8k–20k | SGD 20k–60k | SGD 8k–30k | SGD 12k–35k |
| MVP web app (auth, payments or billing, 2–3 integrations, admin view) | SGD 10k–35k | SGD 40k–120k | SGD 15k–50k | SGD 20k–60k |
| Customer-facing mobile app (iOS + Android, backend, push, store release) | SGD 15k–50k | SGD 60k–200k+ | SGD 25k–80k | SGD 30k–90k (cross-platform only) |
| Custom back-office software (multi-role, approvals, 3+ integrations, reporting) | Rarely a fit | SGD 80k–300k+ | SGD 40k–150k | SGD 40k–120k |
Two reading notes. First, the freelancer and offshore columns are the price of the code, not the outcome; the gap to the studio column is mostly product thinking, QA, project management and someone accountable when it breaks. Second, the AI-assisted column is where our own builds sit, but it is not our rate card: our fixed-scope builds are SGD 20k–80k inside it, below roughly SGD 20k we will usually point you at a freelancer or a no-code tool, and the SGD 80k–120k top of the column is what other AI-assisted shops quote, not a finyki number. The column only holds when the scope is specified well enough for a model to execute against it.
What we build — and what we don't
Disclosure first, because this post would be dishonest without it. Finyki builds three kinds of software: web apps (customer-facing products in a browser, usually Next.js over Postgres or a headless CMS), internal tools (the dashboards, approval flows and back-office screens that replace a spreadsheet and a Slack channel), and agent-backed systems (apps where an LLM does real work inside the workflow, with evals and human checkpoints). Our AI agents and copilots page lists the shapes we ship most often.
We do not build native iOS or Android apps. If your product needs the camera, Bluetooth, offline-first storage, App Store distribution or a swipe-native feel, you want a mobile studio, and we will say so on the first call rather than sell you a web app dressed up as one. Where we overlap with mobile is the backend: the API, the admin console and the automation behind a mobile product are often the bigger half of the budget, and that half is ours. The mobile ranges in this guide are market observation, not our price list.
App development in Singapore: cost by build type (SGD)
The table gives you the outer edges; this section explains what sits inside each row, because most founders overestimate the row and underestimate the integrations. The "roughly" band under each heading is narrower than the table on purpose: it is where most quotes we see land once you drop the cheapest freelancer cells, while the table keeps the real floor and the studio ceiling. A web app or custom software puts you in rows two and four.
Internal tool — roughly SGD 8k–35k (a Singapore studio will quote up to SGD 60k)
An internal tool replaces something your team does by hand today: a quoting form that writes to the CRM, an approvals screen for purchase orders, a dashboard that joins three systems nobody has joined before. Three to eight screens, one or two roles, a single integration. This is the cheapest kind of app to build and the one with the clearest payback, because you can count the hours it removes, which is why a founder-led Singapore SME gets the most leverage per dollar here. If your need is one workflow, start here and resist the urge to call it a platform.
MVP web app — roughly SGD 25k–120k
The moment a stranger has to sign up, pay you and come back, the cost roughly doubles. An MVP web app needs authentication, a billing or payments flow (Stripe is the Singapore default; some clients need PayNow or a local gateway), an admin view, transactional email, and enough polish that a customer trusts it with a card. Studios in Singapore quote this band anywhere from SGD 40k to SGD 120k. Our own first production builds sit in the SGD 20k–80k fixed-scope range published on our pricing page, and the difference is scope discipline, not magic: we scope to the one thing the product must do on day one.
Mobile app development cost in Singapore — roughly SGD 40k–200k+
This is what most people mean when they say "an app", and it is the most expensive row because there are three products hiding inside it: an iOS app, an Android app and the backend they both talk to. Cross-platform frameworks (React Native, Flutter) collapse the first two into one codebase and bring the floor down to the SGD 40k–60k region for a lean app. Two fully native apps with a custom backend, push notifications, analytics and a store release process push a Singapore studio quote past SGD 100k quickly. Add offline sync, in-app purchases or hardware integration and SGD 200k is not exotic. Budget separately for store accounts and a release cadence, because stores do not let you ship a fix in an afternoon the way the web does. One caveat on that SGD 40k–60k cross-platform floor: it assumes a simple backend or one you already have, which is also why it sits so close to the AI-assisted mobile cell in the table.
Custom software development cost in Singapore — roughly SGD 60k–300k+
Custom software, in the sense most Singapore businesses use the phrase, means this: an operations system with multiple roles, approval chains, audit trails, reporting, and three or more integrations — accounting, CRM, a warehouse or logistics provider, a government portal. The cost is driven by the number of distinct workflows and systems you touch, not by screen count. It is also where "who owns the code" matters most, because this software becomes the spine of the business for five years or more. A SGD 150k system you own outright is often cheaper over that horizon than a SGD 30k build whose author has disappeared.
Freelancer, Singapore studio, offshore team or AI-assisted build?
The build-type bands tell you what it costs to make the thing. The builder bands tell you what you are paying for beyond the code. Hourly rates below are typical of what we see in proposals clients share with us; they are not a rate card.
| Who builds it | Typical blended rate | What you get | Where it goes wrong |
|---|---|---|---|
| Freelancer (SG) | SGD 60–150 / hr | Code, fast, from one person who knows the stack | Single point of failure; no QA or PM; scope creep is your job |
| Singapore studio | SGD 120–250 / hr blended | Product, design, engineering, QA, a PM, and someone to call | Highest sticker; overhead you may not need for a small tool |
| Offshore team | SGD 25–60 / hr | Lowest hourly rate, deep benches | Time-zone drag, spec overhead, variable QA; cheap hours can become many hours |
| AI-assisted build (senior engineer + Claude Code or similar) | Priced fixed-scope, not hourly | Studio accountability at a fraction of the engineering hours | Only cheaper on well-specified scopes; discovery and QA still cost what they cost |
One pattern: offshore and studio quotes often converge by the end, because the spec you must write to make an offshore team productive is the work the studio was charging for. With a product manager and a precise spec, offshore is a real option. With a founder, a deck and an opinion, you are buying the spec whether or not it appears on the invoice.
Fixed scope beats hourly for a first app
We price every first build as a fixed-scope project — you approve one number before a line of code is written, and the price does not move unless the scope does. Hourly billing on a first app transfers the risk of a fuzzy brief entirely onto you. Fixed scope forces both sides to decide what "done" means up front, which is where most app budgets are won or lost.
The five things that move the number
In our experience two app quotes for "the same thing" can differ by three times because they are pricing different things. Five variables explain most of the gap; here they are in the order we check them on a scoping call.
1. Integrations
A standalone app is straightforward. The cost climbs the moment it has to talk to Xero or QuickBooks, HubSpot or Salesforce, a logistics provider's API, a payments gateway, or a government service. Each integration is real engineering plus real testing, and in our experience the ones with poor documentation or no sandbox cost two to three times the ones with good docs. Count them before you ask for a quote, and ask which ones the vendor has built before.
2. Authentication and roles
"Users log in" is cheap. "Admins, managers and staff see different things, managers approve what staff submit, and finance can export everything" is a permissions model, and permissions models are where internal tools quietly become custom software. Every additional role roughly adds a review of every screen. Single sign-on with Google Workspace or Microsoft Entra is table stakes for Singapore SMEs and worth the small premium.
3. Native versus cross-platform versus web
This decision alone can halve or double a mobile budget. A responsive web app costs the least and ships fastest; a cross-platform mobile app costs more and gets you into the stores; two native apps cost the most and are only justified by hardware access, heavy offline use or a performance bar a browser cannot meet. Many Singapore SMEs that ask for "an app" need a web app their staff can pin to a phone's home screen. Ask honestly before you pay for the stores.
4. Compliance and data handling
Any app that stores personal data of Singapore residents sits under the PDPA, and the cost of doing that properly — consent capture, access and correction requests, retention rules, breach logging — is a real line item, not a checkbox. Regulated sectors add audit trails, data residency in a Singapore region and sometimes a security review before go-live. We budget compliance explicitly in every scope because the alternative is retrofitting it after a customer's lawyer asks.
5. Who owns the code
The cheapest-looking quote is sometimes the most expensive because you do not own the result: the code lives in the vendor's repository, the app runs on their accounts, and leaving means rebuilding. Insist on your own GitHub organisation, your own cloud accounts, documented environments, and a handover that your next engineer could pick up cold. We wrote about why this dominates the three-year cost in our AI automation cost guide, and the logic is identical for an app.
How AI-assisted development changes app development cost in Singapore
This is the section most agency pages skip, because it cuts against the hourly model. Claude Code, Cursor and similar tools have changed how much engineering time a well-defined feature takes. In our own builds over the past year, the hours on scaffolding, CRUD screens, integration clients against documented APIs, test suites and migrations have dropped substantially — enough that scopes we would have priced as studio-band work two years ago now sit in the AI-assisted column above. The senior engineer is still there; what changed is how much keyboard time they delegate. Our Claude Code field guide for B2B engineering teams covers the rollout pattern in detail.
"AI tooling makes a precise spec cheaper to build. It does nothing for a vague one. The cost of deciding what the app should do has not moved at all."
Where it compresses cost
- Well-specified features. If a screen can be described in a paragraph with its data model and edge cases, it gets built in a fraction of the time it took in 2023.
- Integrations with good documentation. Stripe, HubSpot, Xero, Google Workspace, most modern SaaS APIs. The client code and the tests come fast.
- Test coverage and refactors. Work teams used to skip because it was expensive is now cheap, so the build is more robust, not just faster.
- Internal tools generally. Admin panels, approval flows and dashboards are pattern-heavy, which is where the compression is largest.
The three places it does not
- Discovery and specification. Deciding which workflow to build, what "done" means, which edge cases matter and which roles exist is human work with the people who do the job today. In our experience this is routinely a third of a first build's cost, and it has not gotten cheaper.
- Undocumented systems and dirty data. A legacy ERP with no API, a CSV export that changes format monthly, a database with three different customer ID conventions. The model cannot read documentation that does not exist, and the hours here are stubborn.
- QA, security and compliance. Auth edge cases, PDPA handling, load testing, a security review — the parts that determine whether the app survives contact with real users. Faster code generation makes this more important, not less.
The honest net effect, in our experience: on a well-scoped internal tool or MVP web app, the saving is roughly the gap between the studio column and the AI-assisted column in the table above, and the quality bar has not dropped — test coverage usually goes up, because it is no longer the thing that gets cut. On a custom back-office system with messy upstream data, the saving is real but smaller, because the expensive part was never the typing.
The costs after launch: hosting, model bills, stores and maintenance
The build is a one-off. The app is not. A budget that stops at launch day is the most common mistake we see on scoping calls; here is the running cost in rough terms.
- Hosting and infrastructure. A small web app or internal tool on Vercel, Cloudflare or a managed Postgres typically runs SGD 30–300 a month in our experience. A customer-facing app with real traffic, background jobs and file storage on GCP or AWS is more often SGD 300–2,000 a month. Check the providers' current pricing pages; these move.
- Model and API bills. If the app has an LLM inside it, you pay the model provider directly. For an internal agent handling a few thousand tasks a month this is usually tens to low hundreds of SGD; a customer-facing feature scales with usage and belongs in your unit economics from day one.
- App store accounts and releases. USD 99 a year for Apple, USD 25 once for Google Play, plus the engineering time for each release cycle and the occasional rejected review.
- Maintenance and improvement. Dependency updates, security patches, small fixes and the backlog of "can it also do this" — budget roughly 10–20% of the build cost per year for upkeep alone, more if you want the app to keep improving. Our operate-and-improve retainers run SGD 5k–20k a month and cover a rolling roadmap rather than just keeping the lights on.
Everything we ship runs in your cloud and model-provider accounts, so the running cost is a line on your invoice from Google or Anthropic, not a markup from us.
How to pay someone to develop an app without getting burned
The question "how much does it cost to pay someone to develop an app" is really two questions: what is the number, and how do I make sure the number is the number. The first half is the table. The second half is process, and it is where Singapore SMEs most often lose money — an agency's portfolio tells you what they shipped, not what it cost or how it went, so the vetting is on you.
- Write the one-page scope yourself first. Who uses it, what they do today, what the app replaces, which systems it touches, what it must not do. If you cannot write this page, you are not ready to get quotes — you are ready for a paid scoping sprint, which is a few days and typically credited against the build.
- Get fixed-scope quotes, not hourly estimates. An hourly estimate is a guess with your name on the risk. A fixed quote forces the vendor to decide what "done" means.
- Ask what you will own. Repository, cloud accounts, domain, store accounts, documentation. If the answer is vague, the price is not the price.
- Ship something in weeks, not months. A first internal tool should be live in two to three weeks; an MVP web app in six to ten. If a vendor's plan has nothing usable before month four, the scope is too big or the vendor is.
- Check whether you need an app at all. A surprising share of "we need an app" requests are a workflow that an automation platform plus a form can handle for a tenth of the cost. Our n8n vs Zapier vs Make comparison is the honest read on when that is enough.
Our own process follows the same rules: a free scoping call, a one-page scope with one fixed number, a build in your stack with a shadow-run against the manual process, and a handover of code, prompts, evals and runbooks. The AI Operations Audit is for teams not yet sure which workflow deserves an app first.