How to Estimate a Complex Website Before Development: Discovery, Scope and First Work Slice

A complex website cannot be estimated honestly from two lines in a chat. If the project includes a catalog, roles, integrations, an account area, search, SEO structure or an existing Bitrix backend, a fixed price before discovery usually creates risk: either the vendor hides a large buffer, or important work appears after the project has already started.

What we check before estimation

WGP starts with a compact requirements map, not a huge document: what must be in the base launch, what is optional, where the client-specific logic sits, and which acceptance criteria can be tested on staging.

• business goal: sales, leads, release speed, SEO, lower operational risk;
• data: catalog, attributes, stock, prices, users, content, migrations;
• integrations: ERP, CRM, payments, delivery, search, analytics, external APIs;
• roles and workflows: admins, managers, buyers, B2B clients;
• acceptance criteria: screens, events, forms and edge cases that define done.

Why this is faster than starting immediately

Discovery does not slow the project down. It removes noise from development. Once the base scope is separated from optional work, the team can estimate realistically, suggest a first work slice and show the workflow: Git Flow, staging, production checks, transparent tasks and clear demos.

This matters most for replatforming and headless projects on top of an existing backend. We do not suggest rewriting everything that already earns money. A safer start is often a limited area: category pages, search, catalog listing, lead form or another measurable bottleneck.

The next step

If the problem already looks commercial, the normal entry point is a short audit or pilot. After that, budget can be discussed with context: scope, integrations, data, roles, timeline, team capacity and risk. Fixed packaging is possible for Frontbox product formats. For custom development, an honest price appears only after the requirements are visible.

Related pages: WGP services, why rewrite should not start without discovery, discuss a project.