“A WordPress website” can describe very different amounts of work. Before comparing quotes, ask what will be delivered and what you will be able to manage once the site is live.
Design and page structure
Agree the pages, layouts and key customer journeys. Your designer should understand the information visitors need before choosing colours or adding effects. Check when you will review the proposed design and what feedback rounds are included. Clarify who supplies copy and images.
An editing setup that fits the content
WordPress provides content management, but the experience depends on how the site is built. Ask which parts you can update and how reusable sections will work. A demo with realistic content is more informative than an assurance that everything is “easy to edit”. Discuss the updates your team actually makes.
Functionality and ongoing costs
List required forms, ecommerce features and integrations. Check what uses third-party software and whether there are recurring licences or service fees. A custom build is not automatically fast, secure or accessible. Those qualities depend on implementation, testing and maintenance.
Testing and launch arrangements
Define the pages and tasks to be tested, including mobile use and accessibility requirements. Include notification delivery and confirmation messages for forms. For a replacement website, discuss existing URLs, redirects and the transfer from the old setup. Confirm domain and hosting access before launch day.
Handover and technical care
Agree training, account access and how issues will be reported. Decide who manages updates, backups and security checks after launch. My WordPress development service covers project builds; maintenance and support is a separately agreed service. Use that distinction when comparing providers and costs.