How Long Does It Take to Build a Web or Mobile App?

"How long will it take?" is the first question in almost every discovery call, and the honest answer is a range, not a date. This post gives you the ranges we actually quote, what pushes a project to the top or bottom of each range, and what you can do before kick-off to land on the short side.

The short version

• A focused MVP or internal tool, web or mobile, usually takes 4 to 8 weeks from kick-off to production.
• A platform with several apps, roles and third-party integrations usually takes 2 to 4 months.
• Mobile apps add store review time on top: typically a day or two for the App Store, and up to a week for a new Google Play developer account.
• A rescue or performance project on an existing codebase is measured in weeks, not months, because the first fixes are usually architectural, not a rewrite.

These are the numbers behind the answers on our services page. They assume one small team that owns design, web, mobile and backend together. Splitting the work across three vendors adds coordination time that no estimate can hide.

What actually sets the timeline

Features are only one input. In practice five things decide where a project lands inside a range.

• How many decisions are already made. A project with a clear owner, a written list of what is out of scope, and a decision on the first user flow moves twice as fast as one where every screen is a debate. Discovery exists to make those decisions early.
• Integrations. Each payment provider, CRM, ERP or partner API adds its own sandbox, its own quirks and its own approval process. Three integrations can cost as much as the rest of the product.
• Roles and permissions. An app with one kind of user is simple. An app with customers, operators and admins who each see different things needs a permission model, and that model touches every screen.
• Design readiness. If a design system or brand already exists, we build straight into it. If not, the first one or two weeks produce the screens that everything else depends on.
• Mobile specifics. Offline mode, background sync, push notifications and store compliance are not add-ons. Each one is a week of work and testing on real devices.

Typical ranges, by project type

Marketing site or landing pages: 1 to 3 weeks. Content and design are the long pole, not code. Passing Core Web Vitals is part of the definition of done, not a later optimisation.

Internal tool or dashboard: 3 to 6 weeks. One or two user roles, a database, a handful of screens and an authentication layer. These are the fastest projects to ship and the ones that pay back first.

MVP of a web or mobile product: 4 to 8 weeks. A real product, deliberately small: one core flow done well, analytics, crash reporting and a release pipeline from day one. The point is to learn from real users in week eight, not to launch everything in month six.

Platform or multi-app product: 2 to 4 months. A web app, a mobile app and the backend they share, with integrations and several user roles. We phase these: a usable first release in the first six to eight weeks, then increments on top.

Rescue, audit or performance work: 2 to 6 weeks. A profiling pass, a written list of what is slow or fragile, then fixes in order of impact. A ground-up rewrite is almost never the answer, which is why this is measured in weeks.

How we estimate

• Discovery call, 30 to 45 minutes. What you are building, who uses it, and what it costs the business if it fails.
• Written scope. A short document: what we will build, what we will leave out on purpose, the phases, the timeline and the price. Not a 40-page proposal.
• Phases, not a single deadline. Each phase ends with working software on a staging link or a test build, so the plan gets corrected every week or two instead of at the end.

How to shorten the timeline without cutting corners

• Name one decision-maker on your side and keep feedback rounds short.
• Write down what the first release does *not* include. Every item on that list is a week saved.
• Bring the accounts early: app store developer accounts, domain access, payment provider and API keys. Waiting for a login is the most common idle week in any project.
• Prefer boring, proven technology. Exotic choices cost time twice: once to build and again to maintain.
• Launch the smallest version that real users can use, then iterate. Month eighteen matters more than launch day.

Get a real estimate

Tell us what you are building through the project form or write to hello@alaz.pro. After a short call you get a written scope with phases, a timeline and a price, usually within a week. Every message is read by an engineer, and we reply within one business day.