A website design package is a way of selling an unpredictable job at a predictable price. The agency picks a bundle of pages, revisions and features, gives it a name, and prices it so that the average project inside the bundle is profitable. That is a reasonable thing to do, and it can be good value if your project resembles the average. The risk is entirely in what sits outside the boundary, because everything outside is billed separately at rates you did not compare when you chose. Reading a package well means reading the exclusions first, then working out which of them your project will need.
What is nearly always inside the price
Most packages include a fixed number of page layouts, a template built on a common platform, a defined number of revision rounds, basic contact forms, mobile responsiveness, standard analytics, and launch. Some include a modest amount of copywriting, usually meaning your text tidied rather than written from scratch, and a small library of stock imagery. Those things vary less between suppliers than the price suggests. What does vary is the definition of a page: a page layout and a page are not the same, and a package promising five pages may mean five distinct designs with unlimited pages using them, or five pages full stop. Ask that question first, because it explains a surprising share of the difference between two quotes.
The exclusions that generate every dispute
Copywriting from scratch, original photography, extra revision rounds, content migration from an old site, third party integrations such as booking or payment or a CRM, multilingual versions, accessibility remediation, and ongoing maintenance. Any of these can cost as much as the base package. Accessibility deserves particular attention if you serve the public, since the Department of Justice publishes guidance on web accessibility for state and local government and public accommodations, and it is far cheaper to build to a standard than to remediate afterwards. Migration is the other silent cost: moving a few hundred existing pages, preserving their URLs and setting up redirects is real work, and Google's documentation on canonicalization and duplicate URLs explains why doing it badly can cost you existing search visibility that took years to earn.
Comparing packages that are not comparable
Do not compare the headline prices. Build a one page list of what your project actually needs: number of unique page designs, number of total pages, who writes the words, whether photography is required, which integrations must work, whether existing content is being migrated, and what you need after launch. Send that identical list to each candidate and ask them to price it, naming what falls outside. Three quotes against one list are comparable; three brochures are not. Also ask for the hourly or day rate that applies to out of scope work, since that number determines what the project costs once reality arrives, and it is the number packages are designed not to show. Where search performance is part of the goal, agree whether structure and technical setup are included or whether that is bought separately alongside the build.
The ongoing terms that matter more than the build price
Ask four questions before signing. Who owns the domain, the hosting account, the content and the design files at the end, in writing? Is the site built on a platform another supplier could take over, or on something proprietary? What does the monthly fee include, specifically: hosting, backups, security updates, plugin or platform updates, and how many hours of content edits? What is the notice period and what happens to the site if you leave? A low build price attached to a long lock in with no exit is the most common expensive mistake in this category, and all four questions can be answered in one email before you spend anything.
Questions people ask about website design packages
Is a package cheaper than a custom quote?
Usually, if your project fits inside it. Packages are priced for the average project in the bundle, so a simple site subsidises a complicated one. If your requirements are unusual, a custom scope is often cheaper in the end because you are not paying for a bundle that fits badly and then paying again for everything outside it.
How many revision rounds do we actually need?
Two structured rounds are usually enough when feedback is consolidated and comes from one decision maker. Most overruns are caused by scattered feedback from several people over several weeks, not by a genuinely difficult design. Agree who gives feedback, in what format and by when, and the revision limit stops being a problem.
Who writes the copy?
Check this specifically, because it is the most common gap between expectation and contract. Many packages include editing your text rather than writing new text, and copy is usually the thing that delays launch. If you cannot write it yourself, price the writing as a separate line item and compare it separately.
What happens to our existing site's search rankings?
They depend on whether URLs are preserved or properly redirected, whether the content survives the redesign, and whether the new site is crawlable. Ask each candidate to describe their migration plan and their redirect map before the build starts. A redesign that quietly drops half the old content is the most common reason traffic falls after launch.