Start with the customer journey
Write down what visitors need to understand and do: explore a service, view a product, call, or send a WhatsApp enquiry. A brochure website and a store with checkout have different requirements. Count distinct page layouts, rather than assuming every page takes the same effort. Repeated service pages can share a layout, while a booking journey may need additional development and testing.
Make the first scope specific
List the required pages, mobile behaviour, forms, languages and integrations. Identify who supplies photographs, product information and approved copy. Mention your existing domain, hosting and website access. If the budget is limited, agree a useful first release and record future additions separately. This keeps the initial proposal reviewable and helps avoid unplanned changes.
Compare what the quote includes
Ask whether design, content entry, image preparation, revisions, basic search metadata, testing and launch are included. Confirm the number of review rounds and the person approving them. Ask what final files and access you receive. A lower headline figure may cover a smaller scope; compare the deliverables and responsibilities before deciding.
Plan recurring costs
Domain renewal, hosting, paid plugins, licences, payment-provider charges and ongoing support may continue after launch. AI and messaging integrations can introduce usage or platform fees. Ask which accounts are held in your name and who manages renewals. Discuss these costs separately from the build rather than assuming a one-time payment covers every future expense.
Prepare a useful enquiry
Share your business type, current URL, main customer action, proposed pages and required deadline. Add references and a budget range if you have one. D’zines Hub scopes pricing after reviewing these details; this guide does not publish a universal rate or promise a delivery date. Explore website development or plan an existing-site redesign.