Contents
The short answer: 2 to 4 weeks to turn a website into a PWA, 1 to 3 months for a focused business app, 3 to 6 months for an ERP or a full platform. The useful answer depends mainly on the scope of the first version and on your availability to approve each stage.
Timelines by type of project
| Project | Indicative timeline | What drives it |
|---|---|---|
| PWA from an existing website | 2 to 4 weeks | The state of the starting website |
| AI integration (first use case) | 2 to 8 weeks | Data quality and the number of tools to connect |
| Focused business app | 1 to 3 months | The number of screens and business rules |
| ERP or multi-portal platform | 3 to 6 months or more | The number of user types and integrations |
These timelines run from quote approval to launch. They assume a first version focused on the essentials.
The stages of a project
- Scoping (1 to 2 weeks): workshops, requirements document, firm quote and schedule.
- Mock-ups (1 to 3 weeks): you test a clickable version of the app and approve it.
- Development in batches (4 to 12 weeks): each batch is delivered, tested by your team and adjusted, then we move on to the next.
- Launch (about 1 week): data import, training, go-live, then 3 months of support.
Working in batches has a major advantage: you use part of the app well before the end of the project, and feedback from the field improves what comes next.
What saves time
- A clear, prioritized scope: knowing what is essential for the first version.
- An available point of contact: quick approvals avoid downtime between batches.
- Data that is ready: a clean client file imports in an hour; an inconsistent one takes days.
- Reusing what already exists: a proven base (as with club or route planning apps) shortens the project significantly.
What wastes time
- Changes of direction during development: a change after approval costs more than at the mock-up stage.
- Integrations discovered late: third-party software with no API, or documentation nowhere to be found.
- Approvals that drag on: two weeks waiting on a mock-up means two weeks of delay.
- Wanting everything in the first version: the number one reason projects drag on forever.
Can it go faster?
Yes, in three ways: cut the first version down to the bare minimum, start from an existing base, or run some tasks in parallel. The last option increases the budget; the first two reduce it.
My advice: set a realistic first launch date and build the first version for that date. The following features will arrive faster, because they will build on a tool that is already in use.