Website technical specification: a template and an example
A website specification template in 11 sections: goals, audience, structure, features, integrations, languages, timeline and budget, with a filled-in example.
A website technical specification describes why the site exists, which sections it has, what it does, which systems it connects to, which languages it needs, and when and on what budget it has to launch. To get an accurate estimate you do not need a huge document: a one- or two-page brief is enough. Below is an 11-section template, a filled-in example for a corporate website and the mistakes that make estimates grow mid-project.
Brief vs specification
| Brief | Specification | |
|---|---|---|
| Written by | The client | The developer, together with the client |
| When | Before the first estimate | Before development starts |
| Length | 1–2 pages | Depends on the project |
| Answers | What is needed and why | How exactly it will be built |
| Result | A price and timeline range | An estimate, timeline, scope and acceptance criteria |
You write the brief in plain words, without technical terms. The developer turns it into a detailed specification after a call: pages, features, integrations and how the work will be accepted. For complex products — customer accounts, services, apps — the spec comes out of a separate stage: our discovery and prototype starts at ₸190,000 (about $420) and takes 1–2 weeks.
The 11-section template
Copy the table into a document and answer in your own words. If you have no answer yet, write “don’t know” — that is useful information too.
| Section | What to write |
|---|---|
| 1. Goals | The action a visitor should take: send an enquiry, call, order, book, register |
| 2. Audience | Who your clients are, where they come from, which language they search in |
| 3. Structure | The list of sections and pages, with one page per service |
| 4. Features | Forms, calculator, booking, catalogue, payments, account — split into must-have, nice-to-have and later |
| 5. Integrations | CRM, accounting system (such as 1C), Kaspi Pay or other payments, delivery, WhatsApp and Telegram, analytics |
| 6. Languages | Russian, Kazakh, English — which at launch, which later, who writes the texts |
| 7. Content | Who prepares texts and photos; whether there is a logo and brand style |
| 8. Design references | 3–5 sites you like and what exactly you like; 1–2 you do not, and why |
| 9. Timeline | The target launch date and the reason for it |
| 10. Budget | A range you are prepared to spend |
| 11. Access | Domain, hosting, analytics, CRM — what exists and whose name it is registered in |
Example: a corporate website brief
This example is hypothetical. An air-conditioning installer in Almaty wants a website instead of an Instagram page.
- Goal: enquiries for site visits and installation; calls come second.
- Audience: flat owners and office managers searching from their phones in Russian and Kazakh.
- Structure: home, four services (installation, maintenance, repair, sales), prices, projects, about, contacts.
- Features: must-have — an enquiry form, a WhatsApp button and a price list; nice-to-have — an installation cost calculator; later — a blog.
- Integrations: enquiries go to amoCRM and to a manager’s WhatsApp.
- Languages: Russian and Kazakh at launch; the client writes the Kazakh texts.
- Timeline and budget: launch in May, before the summer heat; ₸500,000–700,000.
What this adds up to: nine pages with forms is a corporate website, from ₸320,000 (about $710) and 4–6 weeks. The Kazakh version adds ₸95,000 (about $210) and a week. Sending enquiries to amoCRM is one integration, from ₸160,000 (about $360) and 1–2 weeks. In total: from ₸575,000 (about $1,280) and roughly 6–8 weeks, within budget. The calculator is a nice-to-have, so it can be priced separately and added later.
Common mistakes
- Describing design with adjectives (“modern, stylish”) instead of links with comments.
- Forgetting integrations — the main reason estimates grow mid-project.
- “Like our competitor” without saying what exactly you like.
- Not deciding who prepares the content, so the launch slips by weeks.
- No budget, so proposals from different studios cannot be compared.
- Every feature marked “must-have”, so the first version cannot be trimmed.
- Leaving the domain and hosting in the contractor’s name.
- Writing a 50-page spec before the first conversation: a short brief and a call work better.
Summary
The client writes the brief; the developer writes the specification together with the client. For an estimate, a one- or two-page brief covering the 11 sections is enough. Name integrations and languages up front, even if they come later.
See what projects look like: a landing page from ₸160,000 (about $360) in 2–3 weeks, a corporate website from ₸320,000 (about $710) in 4–6 weeks. All options are on the website development page, and the calculator gives a rough figure. When you are ready, fill in the brief on the contact page and we will estimate the cost and timeline within one business day.
Let's build something useful.
Tell us what you're working on. We'll review the idea and get back to you with the next steps.
Read next
Kaspi marketplace or your own online store: what to choose in 2026
An honest comparison of selling on Kaspi and running your own store in Kazakhstan, and a setup where the two work together.
ReadHow to connect Kaspi Pay to a website: step by step
What Kaspi Pay requires, which Kaspi payment options a website can use and how they differ. Based on the official Kaspi partner guide.
Read