"I need a website" is where almost every difficult web project begins. Without a written scope, the quotes you receive are built on different assumptions: one company prices five pages, another prices fifteen, one includes content writing and another does not, and none of the numbers can be compared. The disagreements surface later, mid-project, where they are most expensive.
We have built websites for companies across Egypt and the GCC since 2014, and the projects that go smoothly share one habit: a requirements document existed before the first quote was requested. This template is the structure we use in our own discovery phase, simplified so a business owner or marketing manager can complete it without technical background. Read it on this page, or download it as an editable Word file.
How to use this template
- Copy or download: read the full template below, or download the fill-in Word file.
- Start with the business sections: goals, audience and page list matter more than server details.
- Mark unknowns "TBD": an honest "to be decided" beats a guessed answer.
- Send the same document to every company you shortlist: identical input = comparable quotes. You can also send it to us for a free review and a written quote within 24 hours.
The Full Template: 12 Sections
Document Control
Establishes who owns the document and which version is current, so nobody quotes from a stale copy.
| Version | Date | Author / Owner | Status |
|---|---|---|---|
| 0.1 | e.g. 2026-08-01 | Marketing manager's name | Draft |
Business Overview & Goals
A website is a business tool. If the goal isn't written down, "success" cannot be measured and design decisions have no anchor.
Target Audience
A site aimed at procurement managers reads and looks different from one aimed at consumers. Design, tone and content all follow from this section.
Site Map: Page List
The single biggest driver of cost. A quote for an unlisted page count is a guess. List every page, even briefly.
| # | Page | Purpose / key content | Notes |
|---|---|---|---|
| 1 | Home | Value proposition, key services, trust signals | |
| 2 | About Us | Story, team, certifications | |
| 3 | Services (×6) | One page per service | counts as 6 pages |
Tip: pages that share one design but differ in content (e.g. service pages) should be counted but marked as using a repeated template.
Content & Languages
Content is the most common cause of website launch delays. Decide now who writes it and which languages you launch with.
Design & Branding Direction
"Make it modern" means something different to everyone. Reference sites communicate taste faster than any adjective.
| Reference website | What you like about it |
|---|---|
| example-competitor.com | clean product pages, strong photography |
Functional Features (Prioritized)
Use MoSCoW priorities so the budget goes to what matters. "Everything is a must" usually means the list hasn't been thought through yet.
Must launch fails without it Should important, can slip a phase Could nice to have Won't explicitly out of scope now
| Feature | Priority | Notes |
|---|---|---|
| Contact form with WhatsApp button | Must | notifications to sales email |
| Quote-request form with file upload | Should | |
| Client login area | Won't (phase 2) | |
Integrations & Third-Party Services
Integrations are priced individually. Listing them up front prevents the most common "that wasn't included" dispute.
| Service | Needed? | Account exists? |
|---|---|---|
| Google Analytics / Tag Manager | yes | yes |
| CRM (e.g. HubSpot, Zoho, ERPNext) | yes, leads should reach the CRM | yes |
| Live chat / WhatsApp Business | ||
| Email marketing (e.g. Mailchimp) | ||
SEO, Analytics & Migration
If an old site exists, its search rankings are an asset. Redirects and URL planning must be part of the scope, not an afterthought.
Domain, Hosting & Technical Constraints
Clarifies what exists, what needs purchasing, and any constraints from your IT team.
Budget & Timeline
A range is enough. Companies use it to propose the right approach; hiding it usually wastes a round of proposals that miss the target.
Acceptance Criteria & Post-Launch
Defines "done" before work starts, and who keeps the site alive after launch.
- All pages in section 4 delivered, responsive on mobile, tablet and desktop.
- All Must features from section 7 working and tested.
- Page load and Core Web Vitals targets: e.g. LCP under 2.5s on 4G
- Training session for our team on editing content: yes / no
- Maintenance after launch: monthly contract / on demand / TBD
- Ownership: domain, hosting, source code and all accounts belong to us at handover.
Why a written requirements document changes the quotes you receive
When five companies receive the same document, their proposals finally answer the same question. Differences in price start to mean something: this one includes content writing, that one assumed stock photos, the third quoted a heavier custom build. Without the document, differences in price mostly reflect differences in guessing.
It also protects you during the project. Scope discussions come back to a text both sides accepted, instead of memory of a phone call. In our experience the single page listing every page of the site (section 4) prevents more disputes than any contract clause.
How detailed should it be?
For a company website, 3 to 8 pages is plenty. Write short honest answers, and use "TBD" freely; a good agency will turn the TBDs into questions during discovery. If your project is an online store or a web application with user accounts and payments, this template still works as a starting point, but expect the features section to grow significantly, and consider our e-commerce cost calculator to frame the budget first.
Frequently Asked Questions
Do I really need this before asking for quotes?
Yes. Identical input is the only way to get comparable proposals. It also cuts the back-and-forth: companies quote faster when they don't have to interview you first.
What if I don't know the technical answers?
Skip them or write "TBD". The business sections (goals, audience, page list, content) are the ones only you can answer; a competent agency fills the technical gaps in discovery.
Is this template suitable for online stores?
As a starting point, yes. Stores add payment, shipping, product catalog and return-policy decisions, so the features section grows. Start here, then extend it with your store-specific flows.
Can Web Pioneer review my completed document?
Yes, for free. Send it at any level of completeness and we return written feedback plus a quotation within 24 hours, with no obligation.
Have a website project?
Send us your requirements document, or just the idea, and get a written quotation within 24 hours.
Download the Word file + free review
Enter your details and the Word file will download instantly, and our team will gladly review your document for free and send a written quote within 24 hours.
