What changes a small business website quote? Compare scope before price
A useful website quote is more than a total. It should show what will be built, what the business must supply, which tests define completion, what happens after launch, and which costs sit outside the project.
The short answer to "Is this a good price?" is: only if the quote covers the result you need. A lower total may cover the same result efficiently, or it may leave out copy, migration, integrations, accessibility work, testing, training or ongoing costs. The number alone cannot tell you which is true.
Compare every proposal against the same scope. Sort each line into included, your responsibility, or excluded or separately priced. Then compare what you will receive rather than averaging prices for different jobs.
Define the result before counting pages
Two five-page websites can be very different jobs. One may use approved copy, a simple contact form and no existing data. Another may need interviews, new service copy, appointment booking, payment, customer records, redirects from an old site and several approval rounds.
Write one sentence that gives every studio the same job to price:
The website must help [specific visitor] complete [specific action], and we will accept the work when [observable result].
For example: "The website must help homeowners in our service area request a repair from a phone. We will accept the enquiry path when a valid test reaches the monitored inbox and the visitor sees a clear confirmation."
This sentence defines the result without designing the site. If you have not settled the job yet, complete the WPShip website design brief template before requesting quotes.
Compare eight parts of the job
Read each proposal row by row. A blank cell is an open question, not an inclusion.
| Scope area | What the quote should make clear | Evidence to request before acceptance |
|---|---|---|
| Pages and content | Page list; new, revised or migrated copy; who supplies text and images; revision limits | Approved page inventory and named content owner |
| Design and build | Custom or existing foundation; responsive page types; reusable sections; browser and device scope | Staging review and agreed page-type checks |
| Forms and integrations | Enquiry, booking, payment, email, map or customer-system connections; account ownership; fees | A test for success, errors, notifications and receipt |
| Store or catalogue | Product count; variants; tax, shipping and payment setup; who enters data | Sample product and order journey plus unresolved rules |
| Migration and search continuity | Content, media, users or products to move; old URLs; redirects; metadata; analytics setup | Migration inventory, redirect list and agreed checks |
| Accessibility and quality | Named standard or checks; keyboard and form behavior; performance and security work | Test scope, tools, human review and defect process |
| Launch and handover | Hosting and deployment responsibility; backups; domain and administrator access; documentation and training | Launch checklist, access record and recoverable backup evidence |
| Support and outside costs | Support period; maintenance; licences; hosting; domain; premium services; future changes | Renewal owner, billing frequency and separately priced items |
Broad labels hide different promises. "SEO included" might mean page titles and indexable pages, or it might imply a ranking outcome the provider cannot guarantee. Google's SEO Starter Guide says no particular change guarantees that a site will be indexed or rank first. Ask for the work and the check, not a promised position.
"Contact form included" is also incomplete without a delivery test. W3C's forms guidance covers labels, instructions, validation and success or error notifications. The quote should name the agreed behavior and who verifies receipt. A success message by itself does not prove that the enquiry arrived.
Six decisions that change the scope
1. Is the content ready, revised or created?
"Five pages" does not say who writes them. Ask whether the quote assumes final copy and licensed images are ready, includes editing existing material, or includes research and new drafts. Record who approves facts, claims, prices and legal text.
Late content can change the work. If design starts with placeholder words and the final copy is much longer or introduces another service, the templates may need another pass. The quote should say how that change will be handled.
2. What must the website do?
A basic enquiry form is different from live appointment availability, deposits, product sales, customer accounts or a connection to a customer relationship management system. An integration is a connection between the website and another service. It can involve account setup, data mapping, test cases, subscription fees and support.
Describe the visitor's action before naming a plugin. "A customer chooses an available appointment and receives confirmation" is clearer than "add booking." Ask which service is proposed, who owns its account, which fees are external, what happens when it fails and what evidence will show that it works.
3. What must move from the old site?
A redesign may need to move posts, products, images, users, orders or form records. Count the items and identify which need cleaning, transformation or manual review. "Migration included" should have a boundary.
For WordPress, a content export is not a complete recoverable backup. The WordPress export documentation lists content such as posts, pages, comments, custom fields, taxonomies and users in its XML export. The WordPress backup handbook explains that a typical full restore needs both site files and the database. If recovery or transfer matters, ask which artifact the quote includes and how it will be tested.
4. How will both sides recognize completion?
Replace words such as "professional," "fast," "accessible" or "SEO-friendly" with observable checks. Name the pages, browsers, devices, user journeys and standards in scope. Decide who records defects, which defects block launch and how fixes are verified.
The owner does not need to prescribe the technical solution. An owner can ask for a keyboard-completable enquiry journey and verified message receipt while leaving implementation to the studio.
5. Which decisions control the timeline?
A launch date depends on content, account access and approvals. Ask the provider to list what must arrive, from whom and by when. Ask what a revision round covers and what happens when the business adds a page, integration or requirement after approval.
Separate corrections from changes. A correction brings the work back to the agreed scope. A change adds or alters the scope. The quote should explain the process for each.
6. What happens after launch?
Confirm where the site will run, who controls the domain and hosting accounts, what administrator access the business receives, and whether licences continue if the relationship ends. Keep the build fee separate from renewals, support and future content work.
Ask what "backup" means, where it is stored and whether anyone has demonstrated a restore. Ask whether the support period covers defects, training, content changes, software updates or a defined combination. A number of days does not define the service.
Copy this quote-comparison worksheet
Use one copy for each proposal. Keep an unanswered item marked unknown.
| Question | Included | Business supplies or decides | Excluded or separate cost | Evidence or open question |
|---|---|---|---|---|
| Which pages and reusable page types launch? | ||||
| Who writes, edits and approves each page? | ||||
| Which forms, booking, payment or other integrations work? | ||||
| What existing content, data and URLs move? | ||||
| Which accessibility, search, performance and security checks apply? | ||||
| How many review stages and revision rounds are included? | ||||
| Who controls the domain, hosting, licences and WordPress administrator account? | ||||
| What launch, backup, training and support evidence will be delivered? | ||||
| Which one-time and recurring third-party costs remain? | ||||
| How are scope changes approved and priced? |
Send the same open questions to every provider. If a proposal remains ambiguous, ask for an updated scope or a written assumption rather than deciding for the provider.
A worked comparison
Imagine a small repair company reviewing two proposals. This is a hypothetical example, not a WPShip customer result. Both proposals say "six-page website with booking," but the work behind that phrase differs.
| Requirement | Proposal A | Proposal B | Owner's decision |
|---|---|---|---|
| Copy and images | Final material supplied by the business | Interviews and new copy included | Does the business already have approved material? |
| Existing site | No migration or redirects | 25 old pages reviewed, migrated or redirected | Which old URLs still matter? |
| Booking | Existing configured account connected | Provider selected, configured and tested | Is the account ready, and who pays its fees? |
| Review | One form test | Keyboard test, booking journey and two revision rounds | Which checks are required for launch? |
| After launch | Not stated | 30-day support period with stated scope | Who handles defects and changes? |
Proposal A is not automatically incomplete, and Proposal B is not automatically better. If the company has approved content, a configured booking account and no content worth moving, the narrower job may fit. If those inputs are missing, Proposal B may cover work the owner would otherwise have to arrange.
The comparison becomes fair when the same requirement belongs to the same party in both proposals.
Is $1,000 or $1,500 a good price for a small-business website?
There is no useful yes-or-no answer without the scope, responsibilities and outside costs. A US-English search sample for "small business website quote" on 17 September 2026 showed this type of price question in Google's People also ask results. The organic snippets displayed widely different ranges. That sample confirms cost-led intent; it is not a market-price benchmark, and it does not describe demand outside the United States.
Judge the price against a defined result:
- Does it cover the pages, content and functions needed at launch?
- Does it identify the business's work as well as the provider's work?
- Are exclusions, renewals and third-party fees visible?
- Are acceptance, handover and support concrete?
- Can later-stage ideas be removed without underfunding the launch requirement?
A price may suit a small, well-prepared project and fail a complex one. A larger number can also be poor value when the scope remains vague.
How WPShip states its website-build scope
WPShip's current website pricing page separates its standard WordPress build from project-specific work. It lists the page limit, staging review, revision rounds and launch support. Domain registration, hosting, premium third-party services and work outside the agreed scope are separate. Larger migrations, extra pages and custom integrations require a quote.
That package is one provider's published scope, not a market average or a promise that every project fits it. If your project appears suitable, send WPShip your brief with the page list, main customer action, integrations, existing content to move and unresolved decisions. WPShip can then respond to the same scope you use for every other provider.
Keep the worksheet with the agreement
Attach the completed comparison to the agreed scope. Update it when a requirement changes. At handover, use the same rows to check what was delivered, what remains open and who owns each renewal or follow-up.
A dependable quote lets both sides see the same job, test the same result and identify a change before anyone treats it as included.