Custom web platforms – marketplaces, member areas, booking platforms, configurators, community apps – are the projects where "how long will it take?" is hardest to answer in general. We have built several, including DropNow, a custom Laravel platform for a Swiss community prize-drop concept. But we have delivered too few custom platforms to publish meaningful timing statistics, and each one differs a lot. So this article describes how we plan them and what determines the timeline, from experience.
Why custom platforms vary so much
A website has a known structure: pages, content, forms. A platform has users, roles, data, rules and processes – and every one of them is specific to the idea. Two "marketplaces" can differ tenfold in effort depending on payments, messaging, search, reviews and admin tools.
How we phase an MVP
Phase 0: scoping
Before any code, we define:
- The core user journey – the one thing the platform must do well
- User roles and what each can do
- The data model: what is stored and how it relates
- Integrations: payments, email, maps, external APIs
- What is explicitly out of scope for version one
The out-of-scope list is as important as the feature list. It protects the timeline.
Phase 1: foundation
Authentication, roles, the core data model, the admin area, and the basic layout. Nothing exciting to show, but everything else depends on it.
Phase 2: core features
The main journey: for a marketplace, listing, searching (for example by location and radius), viewing and contacting. For a booking platform, availability, booking and confirmation.
Phase 3: supporting features
Dashboards, messaging, reviews, notifications, payment flows.
Phase 4: testing and QA
Real scenarios, different roles, mobile devices, edge cases. In one platform build, QA revealed that payment confirmation emails were not arriving – exactly the kind of bug that must be found before users do.
Phase 5: launch and iteration
Launch to a first group of users, collect feedback, fix, and plan version two.
What determines the timeline
| Factor | Effect |
|---|---|
| Clarity of the core journey | The biggest factor. Vague ideas expand during development |
| Number of user roles | Each role multiplies screens, permissions and testing |
| Payments | Provider setup, flows, refunds, emails and legal requirements |
| Integrations | Each external API adds work and a dependency |
| Content and assets from the client | CAD files, images, texts – platforms can be blocked by missing inputs |
| Decisions during development | Changing rules mid-build causes rework |
| Admin needs | A good admin area is often underestimated |
Contracts and phases
Bigger platform projects are contracted in phases, each with its own scope and deliverables. For some, intellectual property is also tracked per phase – what is pre-existing background technology and what is created for the project. Clear phases make progress visible and give both sides decision points.
Realistic expectations
In our experience, a focused MVP with one core journey and a small number of roles is a matter of weeks to a few months. Platforms with several roles, payments and integrations take longer. Anyone who quotes a full-featured marketplace in two weeks is either reusing an existing product or leaving things out.
How to make an MVP faster
- [ ] Define one core journey and build it first
- [ ] Write the out-of-scope list and stick to it
- [ ] Deliver content and assets early
- [ ] Nominate one decision maker
- [ ] Accept "good enough" design for version one
- [ ] Plan version two from real user feedback, not assumptions
What slows platforms down in practice
From our custom projects, the pattern is similar to websites, only amplified. The build itself progresses steadily once the scope is clear. Delays come from inputs and decisions: assets that must come from the client before a feature can be built (in a 3D configurator, for example, nothing can be rendered until the CAD files arrive), business rules that are only defined when the first version is tested, and features added along the way because "users will expect it". Each of these is manageable when it is visible. That is why we keep a running list of open decisions with owners, review it weekly, and move anything non-essential to a version-two list rather than into the current phase.
Budgeting time for testing
Clients often plan for development and forget testing. On platforms, testing is substantial: every role, every journey, every device, and every email the system sends. Plan for a real testing phase with people from your side, not just a quick look before launch.
Laravel, WordPress or no-code?
We choose the stack per project. Laravel gives full control for platforms with complex logic. WordPress with custom development suits content-heavy platforms with simpler logic. No-code tools can validate an idea quickly but may limit growth. We explain the trade-offs at scoping.
FAQ
Can you estimate my MVP before scoping?
We can give a rough range after a first call, but a reliable estimate needs a scoping phase.
Who owns the code?
This is defined in the contract. In phased projects we clarify ownership of project-specific code and pre-existing components.
What happens after launch?
Most platforms continue with a maintenance and improvement phase, driven by user feedback.
Why do custom software projects need an out-of-scope list?
Because new ideas appear as soon as people see working software. In our experience, writing down what is not in the first version is what keeps an MVP on schedule.
How do you test custom software before launch?
On a staging environment with real sample data, followed by a test round with the people who will use it daily. Edge cases from real data find more issues than scripted tests alone.
Planning a custom software project?
If you want a realistic plan for your own project, book a short call with our team and we will walk you through the phases, what we need from you and where projects like yours usually lose time. You can also browse finished work in our custom software portfolio.
Comments