The short answer
A scoping call is the one conversation that turns an idea into a fixed quote. In about an hour we map five things: who uses the app and their roles, the must-have flows for launch, the systems you need to integrate, any compliance requirements, and your target timeline. From that, we place your project in one of our published tiers — Starter/MVP from SGD 20,000, Business from SGD 38,000, or Enterprise from SGD 90,000 — and follow up with a quote we hold to.
We run this call before quoting, not after, because a real number needs a real scope. Guessing at a price without knowing your roles, flows and integrations would only produce a number we'd have to walk back later.
| What we map | Why it matters |
|---|---|
| Users and roles | One customer journey is Starter territory; staff, admin and multiple permission levels grow the build into Business scope. |
| Must-have flows for launch | The short list of journeys that make version one worth releasing; money-movement flows are flagged early. |
| Integrations | Each existing system (POS, ERP, identity, messaging) adds scoping, build and test effort. |
| Compliance | Requirements such as Singapore PDPA are scoped as an explicit line item, never buried in the base price. |
| Target timeline | Scope is mapped to a realistic window and confirmed in the follow-up quote. |
Who uses the app — users and roles
The first thing we map is people. One customer journey — download, sign up, use — is usually Starter territory. The moment you add staff screens, an admin dashboard, or several permission levels, the build grows into Business scope, because each role needs its own screens, rules and testing.
- End users. Who they are and the single most important thing they come to the app to do.
- Staff and operators. Anyone who fulfils, manages or moderates what end users create.
- Admins. Whether you need a web dashboard behind the app — effectively a second product surface.
Must-have flows for launch
Next we separate what has to ship at launch from what can wait. We push for a short, honest list of must-have flows — the handful of journeys that make version one worth releasing. Everything else becomes a later phase. Anything involving money movement — payments, bookings, checkout — gets flagged early, because those flows need integration work, edge-case handling and testing that a content screen never touches.
Integrations and compliance
Then we list the systems your app must talk to — a POS, an ERP, an identity provider, a messaging service. Every existing system adds scoping, build and test effort, so we name them on the call rather than discovering them mid-build.
Compliance is scoped in the same breath. If your app handles personal or financial data, requirements such as Singapore's PDPA may apply. When they do, we scope and quote that work as an explicit line item — never buried in the base price — so you can see exactly what it costs.
Timeline and how the number comes back
We finish by mapping scope to a realistic window. Most Starter builds ship in 8–12 weeks, Business apps in 12–20 weeks, and Enterprise platforms are scoped per project. Throughout, one project manager owns your project end to end, and every build runs the same six steps: Discover, Design, Build, Test, Launch, Support. Because it's iOS and Android from one codebase, you get one release cycle — QA on real devices, then submission to the App Store and Google Play.
| Tier | Price (from, SGD) | Timeline |
|---|---|---|
| Starter/MVP | 20,000 | 8–12 weeks |
| Business | 38,000 | 12–20 weeks |
| Enterprise | 90,000 | Scoped per project |
Namtech's published starting points. Your scope on the call determines which tier applies; the fixed quote follows.
How to prepare — and what happens next
You don't need a spec. Come with a rough idea of who uses the app, the two or three flows that matter most, any systems it must connect to, and your target launch window. Even partial answers let us scope accurately; the gaps are exactly what the call is for.
After the call we send a fixed quote tied to the tier your scope lands in. Billing is milestone-based — a deposit to begin, then payments tied to agreed deliverables, with no full payment upfront. If scope changes mid-project, we re-quote that change explicitly rather than absorbing it into surprise invoices. Beyond launch, plan for maintenance and support from 15% of build cost per year (monitoring, OS-version updates, security patches, minor improvements and priority support); hosting, third-party service fees and app-store accounts are billed at cost.
Ready to scope your app?
Bring your idea to one call and leave with a clear scope and a fixed quote. See where you'd land on our pricing tiers, then get in touch to book a scoping call — Namtech is a Singapore mobile app studio working with clients worldwide.