Why custom development needs scope review before an estimate

When a client asks for an estimate for a custom website, portal or integration after the first message, it is tempting to name a range and move into sales. We do not work that way: for custom development, a fixed estimate before discovery usually means that part of the risk is hidden.

What we need before estimating

Before an estimate, we collect preliminary requirements: business goal, user roles, data, integrations, timeline constraints, acceptance criteria and the current infrastructure. Then the scope is split into three groups: base, optional and client-specific.

This shows what is truly needed for the first launch and what can move into the next stage without breaking the project.

Where a test slice helps

If the project has risk, we suggest a small work slice: one bounded task, staging, review and a visible result. The client sees speed, code quality, communication and Git Flow before a larger budget.

What the client gets

• a compact requirements structure instead of vague promises;
• a separate view of integration and data-risk zones;
• a clear sense of what can be staged;
• a decision: stages, T&M, pilot or no large project yet.

This does not slow the start. It protects the budget and helps both sides move faster once the scope is real.

If you have a custom development task, start with the WGP web development page or see how our process works.