
⚡ Quick answer: A website technical specification is a document in which the client and the developer agree on what site is being built: what it is for, which pages it has, what each page does, which services it connects to, and how the finished work will be accepted. It exists so that price, timeline and result don’t depend on who “meant” what. Below you’ll find a section-by-section template, a filled-in example for a small business, and the most common mistakes.
“Just build us a proper website” sounds clear until you start asking questions. To the owner, “proper” means a contact form that pings the sales manager in Telegram. To the designer, it means a beautiful homepage. To the developer, it means five WordPress pages with no integrations, because nobody mentioned any. A month later, all three honestly believe they weren’t listened to. A technical specification removes that gap before work starts, on paper, where a change takes minutes rather than a week of rework.
This guide is for business owners, not programmers. You won’t find database architecture or PHP versions here; that is the studio’s job. Your part of the spec is about the business, pages, content, features and agreements, and that’s exactly what we’ll cover, along with a website requirements document template you can copy and fill in.
A website technical specification is a description of the future site that both parties sign off on. It answers four questions: why the business needs the site, what will be on it, how it should work, and how you’ll check that you got what you ordered. A good spec doesn’t have to be long: for a site of a few pages, 3–6 pages of text is enough, as long as it’s specific rather than vague.
The spec becomes the basis for the estimate, the schedule and project acceptance. If a feature isn’t in the document, it isn’t in the price. If there are no acceptance criteria, the “is it done or not” argument gets settled by emotion. That’s why a spec mainly protects the client: it guards your budget as much as the developer’s sanity.
The two documents are often confused, though one follows the other. A brief is the intake questionnaire: you describe your business, customers, competitors and wishes. A spec is the decision: what exactly will be built, in what scope, and how it will be checked.
| Brief | Technical specification | |
|---|---|---|
| When it appears | At the first meeting, before the estimate | After the brief and discussion, before work starts |
| Who fills it in | The client (often using the studio’s questionnaire) | The studio together with the client |
| What it covers | Business, audience, goals, preferences | Pages, features, integrations, content, timeline, acceptance |
| Typical wording | “We want booking to be easy for customers” | “Booking form: name, phone, service, date; submissions go to the CRM and the admin’s email” |
| What it drives | Understanding the task | Price, timeline and scope |
In other words, the brief is “what we want” and the spec is “what we agreed to build”. For a simple landing page, a detailed brief is sometimes enough. For a corporate website or an online store, don’t start without a spec.
The worst option is when only one side writes it. A client with no development experience doesn’t know which questions need closing: the admin panel, mobile layout, redirects from old pages, access to accounts. A studio without the client doesn’t know the business: which services matter most, who answers enquiries, what customers ask most often.
The approach that works: you fill in the brief and gather what you already have (logo, copy, price list, sites you like). Then, at the discovery stage, the studio asks follow-up questions, proposes the structure and features, and turns it all into a document. You read it, edit it and approve it. After that, the spec becomes part of the contract or an annex to it. We describe how this stage fits into the overall process in our article on turnkey website development stages.
If you’re still choosing between a landing page, a corporate site and a store, settle the format first, because most sections of the spec depend on it. Our guide on which website format to choose will help.
Below is a template that covers a typical small or mid-sized business website. Copy it into a document and go through it line by line. If you don’t have an answer to something, write “need the studio’s advice”: that’s more honest than guessing.
| Spec section | What to write | Example wording |
|---|---|---|
| 1. Business and site goal | What you do, what action a visitor should take, how you’ll know the site works | “Main goal: consultation requests. Benchmark: enquiries the sales manager can handle during working hours” |
| 2. Audience | Who your customers are, which devices they use, what they ask before buying | “Apartment owners aged 30–50, mostly on mobile; they ask about price, timing and warranty” |
| 3. Site type and sitemap | The site format and the full list of pages with their hierarchy | “Corporate site: Home, Services (4 pages), Portfolio, Pricing, About, Contact, Privacy Policy” |
| 4. Page-by-page content | Which blocks each page has, in what order, and what the main action is | “Service page: what’s included, starting price, process, examples, FAQ, enquiry form” |
| 5. Design | Brand identity, 2–3 reference sites with what exactly you like, what to avoid | “We have a logo and colours. We like the clean typography on site X and the portfolio filter on site Y” |
| 6. Functionality | Forms, calculators, filters, online booking, customer account, search | “Enquiry form on every service page; cost calculator by floor area” |
| 7. Integrations | CRM, payments, messengers, analytics, delivery services, email marketing | “Enquiries go to the CRM and the sales team’s Telegram chat; Google Analytics 4 and ad pixels” |
| 8. Languages | How many languages, who translates, whether content is the same for each | “Ukrainian is primary; English for 5 key pages, translation supplied by the client” |
| 9. Admin panel (CMS) | What you want to edit yourself, how many people need access and with which rights | “We edit prices, portfolio and news ourselves; two users: administrator and editor” |
| 10. SEO basics | Meta tags, page URLs, XML sitemap, redirects from the old site, speed | “Readable URLs, a title and description for every page, 301 redirects from old URLs” |
| 11. Domain, hosting, access | Who buys the domain and hosting and in whose name, where credentials are stored | “Domain already registered to the company; studio recommends hosting, account in the client’s name” |
| 12. Content and owners | Who writes copy, takes photos, prepares the price list, and by when | “Studio writes service copy after an interview; client supplies project photos by the end of week two” |
| 13. Legal | Privacy policy, cookie banner, consent checkbox on forms | “Privacy policy page, cookie banner, consent checkbox on forms” |
| 14. Timeline and stages | Stages, approval dates, who makes decisions on your side | “Prototype — 1 week, design — 2 weeks, development — 2 weeks; decisions made by the director” |
| 15. Acceptance criteria | How you’ll verify the site is finished | “Every page from the sitemap exists; forms reach the CRM; the site displays correctly on phone and desktop; number of revision rounds as per contract” |
Section 4 is the easiest to underestimate, and it’s the one that decides whether the site sells. Page structure is best agreed on a diagram, which is what a website prototype is for: the spec says what goes on a page, the prototype shows where it sits. For writing the page copy itself, see our separate guide to service page copy that converts.
For section 8, decide right away whether you need a second language at launch: translated pages multiply content and revisions. We’ve covered what breaks on a multilingual website separately. For section 10, Google’s own baseline is enough (Google Search Central, SEO Starter Guide): unique titles, descriptive URLs, crawlable pages. For section 13, list the documents the site needs; we explain the legal requirements for a website in a dedicated article.
To make the template concrete, here’s a shortened example. The company is fictional and the numbers are illustrative: this shows how to phrase things, not a real project.
Example: “Level Wall”, an apartment renovation company in Kyiv
Note the last point: “the manager added a project on their own” tests not just the site, but whether the admin panel is genuinely usable by the person who’ll work with it.
A website’s price is driven by scope, and scope is only visible in the spec. Each line of the template either adds work or doesn’t: CRM integration, a second language, a calculator, a portfolio filter, migrating old pages. That’s why two “identical” requests for a corporate site can differ in price several times over.
For reference: a corporate website at Netloria costs $1,500 and takes 3–5 weeks; a landing page starts from $300 and takes 2–14 days; an online store starts from $550 and takes 4–7 weeks. What goes into the corporate package is broken down in how much a corporate website costs. We don’t charge separately for writing the spec: it’s part of the discovery stage at the start of the project.
The same goes for timing. Projects are most often delayed not by development but by waiting: for copy, photos, a decision on the second language, domain access. When the spec states who supplies what and by when, the timeline becomes predictable for both sides.
If the answer to any question is “we’ll sort it out later”, add it to the spec now. Surprises in development almost always start with something that was agreed verbally.
Don’t want to put the spec together on your own? At the discovery stage we go through every section of this template with you, propose the page structure and features, and record what we agree in a document that the price and timeline are based on. Tell us about your project on the corporate website development page and we’ll start with the brief.
Once the spec is written, the next question is budget — here is how much a website costs and what drives the price.
For a simple landing page, a detailed brief is sometimes enough. For a corporate site, an online store or any project with integrations, skipping the spec makes disputes over scope and price far more likely. The spec records exactly what’s included and protects the client’s budget.
Ideally both. The client brings knowledge of the business, customers and processes; the studio asks the technical questions and drafts the document. The client then reviews, edits and approves it, and it becomes part of the contract.
A brief is an intake questionnaire where you describe your business, goals and wishes. A spec is the agreed decision: the list of pages, features, integrations, responsibilities and acceptance criteria. The brief helps understand the task; the spec sets the price and timeline.
Length isn’t the point. For a small corporate site, a few pages of text are usually enough if every item is specific and verifiable. A long spec full of generic phrases helps less than a short one with clear criteria.
Yes, but every change affects scope, and therefore price and timeline. Changes are best documented separately: what’s being added, what it costs and how the dates shift. That way both sides know what they’re paying for.
Обговорюємо саме цю послугу у вашому проєкті?
Corporate Website