A service website, an online shop and a booking platform involve different work. Start with the type of project you need, then look at the content, features and systems behind it.
These are examples of scope, rather than packages or price bands. Your project may combine elements of more than one.
Explain your services, show your work and help visitors make contact. The scope depends on the page layouts, content and editing tools you need.
Service pages · Case studies · Enquiry forms
Example: a clinic with treatment and training pages
See Sculpt ClinicSell products and manage orders. Product options, shipping rules, subscriptions and connections to stock systems each add requirements to the build.
Catalogue · Checkout · Order management
Scope question: what needs to happen after an order?
Explore online shop developmentLet people book, sign in or manage information. Customer journeys, staff permissions and connections to other services all need to be defined and tested.
Accounts · Administration · Integrations
Example: doctor appointments connected to video calls
See ConsultdocUse these examples to identify what a supplier needs to allow for. They explain differences in scope, without assigning a price to an unknown project.
Page layouts
Several service pages sharing one layout.
Different layouts and interactions for each service.
Content
Approved words and images, ready to enter.
Writing, sourcing images, content entry and review rounds.
Features
An enquiry form sent to an inbox.
Booking rules, customer accounts or different staff permissions.
Integrations
The website works on its own.
Data must move between the site, a CRM or a stock system.
Replacing a site
A new site with no content to move.
Existing content, URLs and metadata need mapping, migration and checks.
Share your current URL, who the site is for and what visitors should be able to do. Separate what you need for launch from ideas that can wait.
List the content, designs and systems available. Say what still needs creating and who will approve it. Rough notes and open questions are welcome.
Explain any fixed launch date, access restrictions and budget you are working within. Include when your team can review the work.
Ask each supplier the same questions so you can compare the work included alongside the price.
Check whether both include the same page types, features, content work and integrations. Then compare design reviews, device and accessibility checks, launch work and handover. Ask for unclear assumptions and exclusions to be written down.
Ask about hosting, domain renewals, software licences and any ongoing support agreement. Check who pays for each service and what maintenance includes. Our website support service can be scoped separately from the build.
Ask how changes are assessed and approved. At Felix, we discuss the effect on cost and timing before proceeding. If further discovery is needed to understand the project, we agree the scope of that work before starting.
Check which milestone the date describes. An early build for feedback still needs review and launch preparation. Ask for content deadlines, approval points, testing, redirects and handover to be included in the schedule.
Identify the content and URLs that must be carried across. Ask who handles content mapping, redirects, metadata and checks after launch. See our CMS migration service for the work involved.
Send your current URL, what you need the site to do and any deadline. We’ll use that to work out the next questions.
Or email [email protected].
