WEB DESIGN QUOTES / COMPARE THE WORK, NOT THE PAGE COUNT
How to Compare Web Design Quotes Without Comparing Page Count Alone
Two website proposals can both say ten pages and describe completely different projects. The useful comparison is what each provider is planning, designing, building, testing, transferring to you and supporting after launch.
THE SHORT ANSWER
Do not compare website quotes by page count until you know what each provider means by a page, a design, SEO, development and launch.
A five-page custom WordPress project can involve more strategy, design systems, integrations and QA than a twenty-page template build. Start by aligning the business outcome and scope, then compare what is included, what is excluded, what you will own, what the provider expects from you and what happens when the website goes live.
A website quote is difficult to compare when every provider uses the same broad words for very different levels of work.
One proposal may say custom design and mean a fully considered visual system built around your content. Another may mean changing colours and fonts inside a purchased theme. One proposal may say SEO included and mean sitemap planning, titles, headings, internal links, redirects, Search Console and indexation controls. Another may mean installing an SEO plugin.
That does not automatically make the cheaper quote bad or the more expensive quote better. It means the decision should be based on fit. If you only need a small, fast brochure site, a lean scope can be exactly right. If the website needs to rank across several services, integrate with business systems or support ecommerce, a quote that omits those responsibilities may simply move the cost to later.
The practical way to compare proposals is to normalise the scope first. Put the same business requirements beside each quote and ask where each requirement is handled, excluded, assumed or priced separately.
01 / PAGE COUNT IS NOT PROJECT DEPTH
Ten pages can mean ten different layouts, or ten pages generated from one repeated template
Page count is useful for estimating content volume, but it says very little about strategy or implementation by itself.
A pricing page, WooCommerce catalogue, location hub, service detail template and simple legal page are not equivalent pieces of work. A good quote makes those differences visible.
02 / ALIGN THE OUTCOME BEFORE THE DELIVERABLES
If two providers are solving different problems, the totals cannot be compared fairly
Start with the job the website has to do for the business.
Lead generation
Clarify the services, enquiry paths, tracking and proof needed to turn search or referral traffic into qualified conversations.
Conversion outcomeEcommerce
Compare catalogue structure, payments, shipping, tax, product setup, checkout, transactional email and ongoing store operations.
Commerce outcomeRedesign and migration
Check whether the quote protects existing URLs, content, redirects, analytics and search visibility rather than treating the project as a blank new site.
Migration outcomeContent and authority
If the site needs case studies, resources, people profiles or a scalable content system, make sure the proposal includes how those content types will be structured and managed.
Growth outcome03 / FIND OUT WHAT CUSTOM DESIGN ACTUALLY MEANS
The word custom is only useful when the proposal explains what is being created from scratch
Visual quality matters, but the commercial value usually comes from the decisions behind the design.
Template configuration
A proven theme or builder can be a sensible option for a lean budget when the limitations are understood and the design still supports the content.
Lower design depthCustom visual system
Typography, spacing, colours, components, states and responsive behaviour are designed as one system around the brand and content.
Higher design depthCustom UX and page systems
Wireframes, content hierarchy and conversion paths are planned around different page purposes rather than applying one layout everywhere.
Higher strategy depthMotion and interaction
Animations, accordions, sliders, menus and interactive tools should be scoped according to their purpose, device behaviour and performance impact.
Implementation depth04 / COMPARE THE WORDPRESS BUILD, NOT JUST THE FRONT END
A website can look identical on launch day and be completely different to manage six months later
Ask how the site will be built, edited, updated and extended after handover.
Editing model
Clarify whether you will edit reusable blocks, structured fields, a page builder or code-dependent templates, and what that means for day-to-day changes.
Plugin strategy
Ask which plugins are essential, which are premium, who owns the licences and whether several overlapping plugins are being used to simulate one requirement.
Custom functionality
Where bespoke code or integrations are included, the quote should identify what is custom, what is third-party and what ongoing dependencies exist.
Responsive behaviour
Confirm the build is tested across relevant mobile, tablet and desktop layouts rather than simply assuming a desktop design will collapse correctly.
Performance approach
Hosting, image handling, caching, code weight and third-party scripts should be considered during the build, not postponed until the site feels slow.
Handover and access
You should know what admin access, documentation or training is included and whether another WordPress professional can maintain the site later.
05 / DEFINE WHAT SEO INCLUDED MEANS
SEO should be compared as specific work, not a checkbox beside the price
A new site can launch with strong search foundations without promising that rankings will magically appear.
Search and sitemap planning
Is keyword/search-intent research influencing which commercial pages are created and how they relate to each other?
On-page implementation
Are page titles, headings, metadata, internal links, canonical settings and indexation controls included where appropriate?
Technical launch checks
Does the project cover crawlability, XML sitemap handling, robots directives, status codes and Search Console setup?
Redesign redirects
If URLs are changing, is a redirect map and post-launch testing included or left to the client?
Measurement
Are analytics and conversion actions configured so the business can evaluate the website after launch?
Ongoing SEO boundary
Does the proposal clearly separate launch foundations from ongoing content, authority building, digital PR or monthly optimisation?
06 / CONTENT CAN CHANGE THE PROJECT MORE THAN PAGE COUNT
Find out who is responsible for turning business knowledge into finished website content
A quote can appear inexpensive because the provider assumes every word, image and proof point will arrive ready to paste.
Copy supplied by you
A lean quote may reasonably assume you provide final copy. Confirm the required format, deadlines and who fixes gaps when content does not fit the design.
Client responsibilityCopy editing
Light editing can improve clarity and structure without becoming full research or copywriting. Check whether this is included and how much is allowed.
Shared responsibilityFull copywriting
Research, interviews, messaging, service copy, SEO integration and approval rounds can be a substantial scope of their own.
Provider responsibilityPhotography and project assets
Clarify whether the quote includes image sourcing, editing, professional photography, portfolio preparation or only placement of supplied assets.
Asset responsibility07 / THE EXPENSIVE PART CAN BE WHAT THE WEBSITE CONNECTS TO
Integrations, migration and QA deserve their own comparison because they carry hidden risk
These items often create the largest gap between a simple marketing site and a business-critical WordPress project.
List every system connection
CRM, booking, email marketing, payment gateways, accounting, inventory, APIs and forms should be named rather than hidden under the word integration.
Clarify data responsibility
Who provides credentials, field mappings, test accounts and access to external platforms? A quote should make those dependencies visible.
Define migration depth
Moving five pages is different from migrating hundreds of posts, products, redirects, customer records or legacy media.
Compare QA scope
Look for browser/device testing, forms, tracking, links, checkout, redirects and production checks that match the actual project risk.
Confirm fallback and support
When an external service changes or launch exposes an issue, know whether the provider will diagnose it and where the support boundary sits.
08 / KNOW WHAT YOU OWN AND WHAT CONTINUES AFTER LAUNCH
A low project price can become expensive when essential accounts or licences remain under someone else's control
Ownership and recurring cost should be visible before you approve the project.
Domain and DNS
Know whose account controls the domain and DNS, and whether you will have the credentials required to move providers later.
Business-owned accessHosting
Clarify whether hosting is included, recommended or mandatory, what it costs after the initial term and how migration works if you leave.
Ongoing infrastructurePremium licences
Identify paid themes, plugins, fonts, APIs or SaaS products and who is responsible for renewing them after launch.
Recurring softwareCustom work and admin access
Confirm what access you receive to WordPress, custom code and content, subject to the normal licences of third-party software.
Operational control09 / PERTH MARKET CONTEXT
A Perth quote should still be compared by scope, even when providers use very different pricing models
Local agencies, freelancers, offshore teams and subscription-style providers can all be legitimate choices. The useful question is which model fits the risk and depth of your project.
A Subiaco professional-services site may need careful credibility and content structure; an Osborne Park B2B company may need integrations and deeper service architecture; a Fremantle hospitality site may depend on bookings and visual content; a Cannington retailer may need ecommerce. Those differences can change price more than the suburb itself.
If two Perth proposals appear far apart, line up the actual deliverables before deciding one provider is expensive. Often the gap comes from research, content, custom design, development depth, migration, testing or support that is present in one scope and absent in the other.
10 / BEFORE YOU ACCEPT A QUOTE
You should be able to explain exactly what the price buys, what you need to supply and what happens after launch
If the proposal leaves one of these unclear, resolve it before the project starts rather than after the first invoice.
The business goal is written in plain language
Both sides should agree what the website is expected to improve — enquiries, ecommerce, credibility, service discovery, publishing or another measurable outcome.
Every major inclusion has an owner
Design, copy, images, integrations, migration, SEO, analytics and approvals should not sit in a grey area between client and provider.
Exclusions are visible
Photography, premium software, hosting, maintenance, ongoing SEO, ad management and other recurring services should be clear when they are outside the project.
Revision and approval stages are defined
Understand where feedback happens and what changes become new scope rather than assuming unlimited revisions.
Launch and handover are included
Know who moves the site live, tests production, supplies access and trains the people who will use WordPress.
Support after launch is specific
A promise of ongoing support should state whether it means a warranty period, maintenance plan, ad-hoc help or a separate monthly service.
WEB DESIGN QUOTE FAQS
Questions worth resolving before you choose between two website proposals
A clear proposal makes these answers easy to find. If you have to infer them, ask before signing.
Clear answers to the decisions that usually affect cost, scope and ownership.
Because the providers may be pricing different work under similar headings. Research, custom UX, copywriting, SEO implementation, integrations, migration, QA and post-launch support can materially change the scope. First make the deliverables comparable; then compare price.
Choose the leanest scope that still solves the problem properly. A cheaper quote can be excellent when your requirements are simple and clearly defined. It becomes expensive when important work is omitted, then has to be rebuilt, migrated or added after launch.
No. A good template or framework can be efficient for a straightforward site. Custom design becomes more valuable when your content hierarchy, brand, conversion paths or functionality do not fit a generic structure. The important part is understanding which approach the quote actually includes.
There is no universal definition, which is exactly why you should ask. A useful build scope can include search-informed architecture, titles, headings, metadata, internal links, crawlability, sitemap/indexation setup, redirects where needed, Search Console and measurement. Ongoing content growth and authority building are separate services.
They can be included or separate, but the commercial model should be explicit. Hosting is recurring infrastructure; maintenance is ongoing operational care. Ask for the ongoing cost, renewal terms, access and migration options instead of assuming the project fee covers them forever.
Ask what is custom, what you need to supply, who owns the domain and hosting, which premium licences continue, how SEO and redirects are handled, what integrations are included, how testing works, what access you receive and what support exists after launch. Those answers reveal the real scope quickly.
COMPARING WEBSITE QUOTES NOW?
Send us the brief and the outcome you are trying to achieve — we will show you what our WordPress scope includes so you can compare it line by line.
A quote makes more sense when you can compare it against another real local provider. Creative Agency X is a useful Perth reference point for looking at differences in positioning, design approach and the scope behind a website proposal.