Three situations that change the decision
You need one clearly scoped landing page
With approved copy, existing brand assets and one contact form, the main work may fit one person’s skill set. Confirm that design, mobile behavior, testing and handover are covered. See the landing page scope before adding features.
You need a business website but have no content ready
The project needs someone to interview stakeholders, write or edit the content and coordinate approvals. Ask whether the provider owns those tasks or expects you to arrange them. Use the business website checklist to identify the gap.
You are launching a product or migrating a store
Find evidence that the assigned team can handle the workflow, testing and operating requirements. Ask about failure recovery and ongoing responsibility. A SaaS scope or ecommerce scope needs more detail than a generic feature list.
Normalize the quotes before comparing totals
Use one checklist for page types, original layouts, content, integrations, testing, migration, launch and training. Mark each item as included, excluded or unresolved. Request a separate price for omitted work that is necessary for launch; do not fill an unknown with a guess.
Then compare recurring charges over the same period. Ask about revision rounds, change requests, payment milestones and cancellation terms. The worked quote comparison shows how a cheaper launch price can differ from the first-year total.
Why SiteCost shows different delivery amounts
The model applies factors of 1, 2.2 and 5 to a shared base scenario. Matching agency outputs also apply the Neaptide minimum recorded in the model. These are fixed planning assumptions, not measured market averages, actual quotes or evidence that an agency provides proportionally more value.
Real proposals may overlap. Use the amounts to explore a scope and prepare questions, then assess the actual proposal. The methodology explains the arithmetic and its limits.