A fintech founder asked how long does it take to build a custom web application for a loan origination platform. They received two quotes: 6 weeks from a freelancer and 11 months from an agency. Neither came with a scope document.
The freelancer disappeared at week 9. The agency's first milestone arrived in month 4. Both quotes were guesses.
The project only got delivered when a proper scoping process came first. This post explains what actually drives timelines and how to spot unrealistic promises.
Why the same project gets quoted 6 weeks and 9 months
Scope is the variable. Scope means the features, integrations, user roles, and data complexity your application must handle. Two companies quoting without a proper scope are both guessing.
The fintech founder's loan platform needed credit checks, document uploads, and approval workflows. The freelancer assumed simple forms. The agency assumed enterprise compliance. Neither asked the right questions first.
Ask any partner: "What assumptions are you making about my requirements?" If they cannot name them, they are not scoping — they are selling.
Realistic timelines by project type
A booking and availability system for a service business typically takes 10 to 14 weeks. This assumes calendar sync, staff permissions, and customer notifications are defined upfront. Add payment processing or multi-location support and the timeline grows.
A multi-role business management system with reporting and user permissions typically takes 16 to 24 weeks. This includes role-based access, audit logs, and custom dashboards. The range depends on how many user types need different views and actions.
A customer-facing SaaS product with subscription billing and a client dashboard typically takes 20 to 30 weeks. This assumes Stripe or similar integration, usage tracking, and self-service account management. Complex billing rules or enterprise SSO add time.
Every range above assumes a properly scoped brief. Without that, estimates are guesses.
What actually causes projects to run late
Incomplete briefs are the most common cause. If requirements are vague at the start, they become expensive changes later.
Changing requirements mid-build adds time. This is not a developer problem — it is a planning problem. The honest answer is to lock scope before coding begins.
Slow client feedback creates bottlenecks. If your team takes two weeks to review a milestone, the project slips two weeks. This is normal and should be planned for.
Adding features after scope is locked is scope creep. It happens. The question is whether your partner has a process to handle it without breaking the timeline.
What a proper scoping process looks like and why it matters more than the development itself
A well-scoped project runs on time. An unscoped project runs over time regardless of how good the team is.
Scoping produces three things: a defined feature list, a realistic timeline, and a fixed delivery plan. It also documents assumptions and risks upfront.
The scoping phase typically takes 1 to 3 weeks. This is not wasted time — it is the foundation that prevents months of rework.
A logistics client needed real-time tracking. Scoping revealed they needed offline sync for drivers in low-connectivity areas. That requirement changed the architecture and the timeline. Discovering it early saved the project.
How Cresbyte scopes and estimates projects
We start with a discovery call focused on your users, your data, and your success metrics. We ask what could go wrong before discussing timelines.
Next, we map features and integrations in writing. We identify technical risks and dependencies. We document assumptions so nothing is left to guesswork.
What you receive is a milestone plan with a timeline and the assumptions it rests on. You can take this document to any partner. It is yours.
[INTERNAL: See our scoping process → /process]
This is how to get a timeline you can trust. You evaluate partners on process, not promises. You ask about scope before cost. You avoid the mistakes that cost the fintech founder so much time.
If you want a timeline you can actually rely on, start with a scoping call. We map out exactly what your application needs, define the feature set, and give you a milestone plan with honest assumptions stated. Book your free scoping call.
Frequently Asked Questions
How long does it take to build a web app from scratch?
It depends on scope. A simple internal tool with defined features can take 8 to 12 weeks. A customer-facing platform with integrations and complex workflows typically takes 20 to 30 weeks. The key is a properly scoped brief before any estimate is given.
Why do software projects always take longer than expected?
Most delays come from incomplete requirements, changing priorities mid-build, or slow decision-making on the client side. These are not developer failures — they are planning realities. A proper scoping process surfaces these risks before work begins.
Is 3 months enough to build a web application?
For a well-defined system with limited integrations and a single user type, yes. For a multi-role platform with payment processing, reporting, and external APIs, 3 months is usually not enough. The question to ask is not "how fast" but "what can we deliver properly in that time."