Agencies quote what you describe. If you send three agencies the words “we need a new website,” you will get three quotes that cannot be compared, because each agency has imagined a different website. A scope of work fixes that. It is a short document that says what you want built, what it needs to do, who supplies what, and how decisions get made.
You do not need to be technical to write one. You need to know what you like, what matters most, and what you can spend. This guide walks through how to work that out and ends with a template you can copy. If you are still deciding whether to hire an agency at all, read how to hire a WordPress agency first.
What a scope of work is, and what it is not
A scope of work describes outcomes and requirements. It is not a design. You do not need to choose fonts, draw wireframes, or pick plugins. That is what you are paying the agency for.
A good scope answers five questions:
- What is the site for, and how will you know it is working?
- What pages and features does it need?
- What does it connect to?
- Who provides the content, and by when?
- What is the budget, the deadline, and who signs off?
Anything the agency needs to price belongs in the document. Colors, fonts, and other matters of taste can wait for the design stage.
Step 1: Use AI to brainstorm and structure your requirements
An AI assistant such as ChatGPT, Claude, or Gemini is useful when your ideas are scattered across notes and emails. It asks questions you had not thought of and turns a messy list into a structured one.
Try a prompt like this:
I run a [type of business] with [number] staff in [location]. I want a new
website. Our main goal is [more enquiries / online bookings / selling products].
Our customers are [describe them]. Interview me one question at a time to work
out the pages, features, integrations, and content I need. When we are done,
organize my answers into a website scope of work with must-haves and
nice-to-haves.
Answer honestly and let it run for ten or fifteen questions. Then treat the output as a first draft, not a decision. Three cautions:
- AI pads requirements. It will happily suggest a chatbot, a blog, a members area, and multilingual support. Each one adds cost. Keep only what serves your main goal.
- It does not know your customers. If you know that most of your bookings come by phone, a booking system may matter less than a click-to-call button.
- Do not paste confidential information. Leave out customer data, passwords, and financial details.
Step 2: Collect reference sites and pull the concepts you like
Words like “modern” and “clean” mean something different to everyone. Spend an hour collecting reference sites from three places:
- Award galleries such as Awwwards. These show what is possible in layout, typography, and interaction. Many featured sites use heavy animation and custom development, so treat them as inspiration for ideas, not as a quote target.
- Competitors in your category. Look at the five or six businesses your customers compare you with. Note what they all have in common, because customers will expect it, and what none of them do well, because that is your opening.
- Sites you use as a customer. The booking flow you enjoyed, the restaurant menu that was easy to read on a phone, the checkout that did not ask for too much.
The trick is not to pick one site and say “make it like this.” Instead, pull a specific concept from each one. Keep a simple table:
| Site | What I like | What I do not like |
|---|---|---|
| Competitor A | Prices are on the services page | Too much text above the fold |
| Award site B | Large project photos with short captions | Slow to load on my phone |
| Booking site C | Three-step booking with no account needed |
Five to eight references with one or two notes each is enough. An agency can design from that; it cannot design from “we want it to pop.”
Step 3: Decide what matters most
Every project trades off budget, timeline, and features. If you rank nothing, the agency will rank it for you. Before you write requirements, decide:
- Your one primary goal. More enquiries, online sales, bookings, recruiting, or credibility for a sales team. Pick one. Secondary goals are fine, but one has to win when they conflict.
- Your must-haves. The features without which the site has failed. Keep this list short.
- Your nice-to-haves. Things you would add if the budget allows. Agencies can price these as options.
- Your fixed constraint. Is the deadline fixed (a launch event, a trade show) or is the budget fixed? Usually one can move and the other cannot. Say which.
Step 4: Write clear requirements
The difference between a vague requirement and a clear one is whether someone could test it. “Booking system” is vague. “Visitors can book a 30-minute consultation from available slots in our Google Calendar and receive an email confirmation” is clear. Cover these areas:
- Pages. List them as a simple sitemap: Home, About, Services (with one page per service), Pricing, Contact, and so on. Say roughly how many pages of each type.
- Features. Forms, bookings, online payments, search, a blog, galleries, a members area. Describe each as something a visitor can do.
- Integrations. Every outside system the site connects to: your email marketing tool, CRM, booking calendar, payment provider, accounting software, or inventory system. Name the actual products.
- Content. Who writes the copy, who supplies photos, and whether existing content needs moving from an old site. Content is the most common cause of delays, so give it a date.
- Platform and ownership. If you want WordPress or another open source platform, say so. State that the domain, hosting, and all licenses must be in your business name. Our guide to agency red flags explains why.
- Timeline. Your target launch date and any fixed dates the project must work around.
- Budget range. Give a range. It does not weaken your position; it saves everyone time by filtering out agencies that cannot work within it. If you are not sure what is realistic, see how much a website costs.
- Who approves. One named person with final sign-off, and how many revision rounds you expect.
- After launch. What you need at handover and whether you want the agency to maintain the site. Our website handover checklist lists what to ask for.
Step 5: Send it and compare like for like
Send the same document to every agency on your shortlist. Ask each to respond against your headings, price must-haves and nice-to-haves separately, and list assumptions. Then you are comparing one project three times, not three different projects.
If an agency pushes back on part of your scope, listen. A good agency will tell you when a requirement costs a lot for little return, which is a good sign.
Website scope of work template
Copy this into a document, fill in the brackets, and delete any section that does not apply.
WEBSITE SCOPE OF WORK
Company: [name]
Prepared by: [name, role, email]
Date: [date]
1. BACKGROUND
What we do: [one or two sentences]
Current website: [URL, or "none"]
Why we need a new site: [the problem we are solving]
2. GOALS
Primary goal: [one goal]
Secondary goals: [up to two]
How we will measure success: [e.g. enquiries per month, online sales]
3. AUDIENCE
Main customers: [who they are, what they need from the site]
4. REFERENCE SITES
[Site URL]: [what we like] / [what we do not like]
[Site URL]: [what we like] / [what we do not like]
[Site URL]: [what we like] / [what we do not like]
5. PAGES (SITEMAP)
[Home]
[About]
[Services: list each service page]
[Contact]
[Other pages]
6. FEATURES
Must-have: [describe each as something a visitor can do]
Nice-to-have: [price these as options]
7. INTEGRATIONS
[Product name]: [what it needs to do]
8. CONTENT
Copy written by: [us / agency]
Photos supplied by: [us / agency / stock]
Content to move from old site: [yes or no, roughly how many pages]
Content delivery date: [date]
9. PLATFORM AND OWNERSHIP
Platform: [WordPress / other open source / open to recommendation]
Domain, hosting, and all paid licenses registered in our business name.
We own the design, custom code, and content on final payment.
10. TIMELINE
Target launch: [date]
Fixed dates to work around: [events, campaigns]
11. BUDGET
Range: [low] to [high]
Fixed constraint: [budget / deadline]
12. DECISIONS AND APPROVALS
Final sign-off: [one name]
Revision rounds expected: [number]
13. HANDOVER AND AFTER LAUNCH
Admin access, documentation, training, and a full backup at launch.
Ongoing maintenance: [quote requested / not needed]
14. PLEASE INCLUDE IN YOUR RESPONSE
Price for must-haves and each nice-to-have separately
Payment schedule
Timeline with milestones
Assumptions and anything you think we have missed
Next step
Before you send your scope to agencies, compare it with the packages on WP Services. Many small-business sites fit a fixed-price package with the deliverables already written down. If yours does not, you will have a useful benchmark for the custom quotes you receive.