A credible price comes from named scope drivers, delivery risk, and the operating model the work requires, not from a mysterious number after a sales call.
A project range narrows as the team understands goals, page and content volume, integration count, migration risk, decision ownership, and launch constraints. Fixed-scope work prices a defined outcome; an ongoing partnership prices continuing capacity and priority. They solve different problems.
A range exists because the problem is not fully observed
Before discovery, a partner can usually identify the class of work and a credible investment band. The exact number depends on what must be designed, migrated, integrated, written, tested, and supported. A range is useful when the assumptions behind it are visible. It is evasive when nothing is named that would move the price.
Specific factors move scope
Content volume changes modeling, writing, migration, and quality assurance. Integrations add technical dependencies and failure states. A platform move adds redirect and data risk. Multiple audiences or approval groups add decision work. Accessibility, localization, commerce rules, and a fixed launch event can all change the delivery shape. Complexity should be named at this level, not used as a catch-all.
Projects and partnerships price different things
A fixed project is appropriate when the outcome, boundaries, and release point can be defined. An ongoing partnership is appropriate when priorities will keep changing and the client needs access to a stable senior team over time. A monthly model is not a discounted project divided into installments. It prices continuity, active capacity, and a way to reorder the queue.
The fit and scope conversation tests readiness
A useful first conversation establishes the business change behind the request, who can make decisions, what evidence exists, what systems are involved, which date matters, and what happens if nothing changes. It also surfaces whether the team has content access, stakeholder time, and operational capacity to support the work.
Ask how the number was built
A prospective partner should be able to explain the scope assumptions, what is excluded, how changes are handled, who performs the work, what the review cadence looks like, and what remains after launch. The explanation does not need to expose private payroll math. It should make the connection between the work and the price understandable.
Questions that follow.
They may include different levels of strategy, content, design, engineering, migration, testing, senior involvement, and post-launch support. Compare the operating model and scope, not only the total.
It depends on the uncertainty. Fixed pricing works when outcomes and boundaries can be defined. Time-based or capacity models can be clearer when priorities are expected to change.
Look for goals, deliverables, assumptions, exclusions, roles, timing, review points, change handling, price, payment schedule, and the support or ownership model after launch.
