Price the outcome before counting pages
Two websites with five pages can involve very different work. One might use supplied text and a familiar layout; another might need interviews, translation, photography and a booking integration. Start with the result you need: a credible online presence, more useful enquiries, online transactions or access to a business service. Then identify what must be delivered to support it.
Separate launch requirements from later improvements. A complete, focused first release is easier to estimate than a brief that treats every possible feature as essential.
Make the main cost drivers visible
Ask suppliers to describe the work behind their price. A page allowance tells you little about the preparation, functionality or review included. The following questions make proposals easier to compare without assuming that a higher or lower price is automatically better.
- Content: who writes, translates, supplies images and approves the final wording?
- Design: is the layout adapted from an existing system or developed around your content?
- Functionality: which forms, booking tools, payments and business systems must connect?
- Delivery: which devices, accessibility checks, review rounds and migration tasks are included?
- Handover: who owns the accounts and what editing guidance or documentation is supplied?
Compare two briefs, not two headline prices
Consider an illustrative brochure website with ready-to-use text, one language and a contact form. Its scope is materially different from a bilingual site that imports existing articles, coordinates appointments and connects enquiries to a CRM. Neither description specifies a market price; it shows why the same page count does not mean the same project.
For a fair comparison, send each supplier the same content inventory and customer journey. Ask them to list assumptions, exclusions and dependencies. If an important requirement is absent, request a revised proposal before choosing.
Separate the project from the cost of running it
Build a simple first-year budget: the agreed project total, required external services, optional care and an allowance for planned changes. List domain renewal, hosting, platform subscriptions and any payment or booking fees separately. Identify who pays each provider and whether a quoted service is optional or necessary for the website to function.
Ask what happens when a subscription ends, which data can be exported and who performs updates. A low launch price can suit a small brief, but it is less useful if essential running costs remain unclear.
Use a written scope to control changes
Agree deliverables, acceptance checks, payment stages and how extra work is approved. Changes should have a stated effect on cost and timing before implementation. Skulbyte's pricing page provides current starting points; the written proposal confirms your scope and total before you commit. Where integrations or business rules are still uncertain, a scoping session can establish the requirements before a larger build is priced.