Website technical specification: how to write one yourself
A website technical specification is a document of one to five pages in which you describe, in your own words, why the site is needed, what it must contain and how you will know the work is done. You can write it without any technical background: the studio adds the technical requirements later. For businesses in the regions, such as Samarkand, Fergana, Namangan, Bukhara or Andijan, this matters even more: communication often happens in Telegram, voice messages and phone calls, and without a written record agreements drift apart quickly.
Why you need a spec even for a small site
Without a written spec, a studio works from verbal wishes that each side remembers differently. A month in, the client says 'that's not what I meant' and the studio replies 'you never asked for that'. A document removes the argument: there is a list of pages, features and acceptance conditions that both sides can point to.
A brochure site needs one or two pages of spec; an online shop or a catalogue with filters may need five to ten. Length is not the point. What matters is that every item can be checked: done or not done.
Where to start if you are not a developer
Do not describe technology; that is the studio's job. Your part is the business: who your customer is, what action they should take on the site (call, message you in Telegram, leave a request, order), what doubts they have and why you are better than the competitors around you.
A useful exercise: write down the ten questions customers ask you most often by phone and in Telegram. The answers become the skeleton of the site, because behind them is real demand rather than guesswork.
Also answer separately where your customers come from. If you work in one city or region, the site should show the address, landmarks, opening hours and how to order or get delivery within seconds. If you serve several regions, list them.
Structure: what a website technical specification contains
The minimum sections: the goal of the site and the main target action; the audience, meaning who these people are, which language they read and which device they use; a page list with a short description of each page; language versions, which in Uzbekistan usually means Russian and Uzbek, sometimes English.
Functional requirements: request forms, catalogue filters and search, a price calculator, a personal account, a cart. For each feature write what must happen after the user acts. For example: 'after the form is submitted, the request reaches the manager in Telegram and the visitor sees a success message'.
Integrations: a Telegram bot for notifications, a CRM, Payme and Click if you need online payment, Google Analytics and Yandex Metrica, a map with your address. Admin panel requirements are a separate item: list what you want to change yourself without a programmer, such as texts, prices, photos and products. This is the item people forget most often.
What almost everyone forgets
Content. Who supplies the texts, photos, logo and product descriptions, and by when. A common reason for missed deadlines is that materials arrive late while the spec never said this was the client's responsibility.
Organisational questions: whose name the domain is registered in (preferably yours, not the contractor's), who pays for hosting and renews it, who sets up email on the domain, what happens to the old site and its addresses, and whether data must be migrated.
For regional businesses add: a speed check on mobile internet (many visitors use phones and the connection is not always fast), call and Telegram buttons on every screen, a map and landmarks for your address, prices in soums. Also state who answers requests and how quickly: a site does not help if an enquiry sits unanswered for a day.
Design, timeline and acceptance without being a specialist
Describe design through references. Collect five or six sites you like and write one phrase for each: 'calm colours', 'obvious where to click', 'works well on a phone'. Add the same number of examples you dislike; this often works even better. Words like 'modern', 'expensive-looking' or 'eye-catching' mean something different to everyone.
Split the timeline and payment into stages: structure and prototype, design, layout and programming, content entry, testing, launch. For each stage write what is delivered, how many days the studio has and how many days you have to approve. Paying by stages protects both sides.
Acceptance criteria work as a checklist: every page opens on phone and desktop; forms send requests and notifications arrive; texts and prices are correct in all languages; there are no broken links; loading speed is acceptable; access to the admin panel and the domain has been handed to you. Sign off only after checking against this list.
Revisions: define how many rounds are included in the price and what counts as a new task. This removes the most common disputes.
FAQ
How long should the spec be? Long enough that every item can be checked: one or two pages for a brochure site, several for a shop.
Can I skip the spec? For a very simple page a short brief is enough, but write down the goal, the list of blocks, the deadline and the price, at least in a message that both sides have confirmed.
Who writes the spec, the client or the studio? The client writes the business part and the studio writes the technical part. The best result comes from working together on one shared document.
What if requirements change along the way? Record every change in writing and recalculate time and cost. Keep the spec in a shared document with revision history rather than in files passed around in chat.
Is writing the spec charged separately? Often a basic spec is included in the project price, but confirm this before signing the contract.
What to do next
If you want help, the 4 Digital studio builds turnkey websites starting from 1,399,000 soums and helps put the spec together with the client: describe your business and send examples of sites you like. The final price depends on the number of pages, languages, integrations and the amount of design work, so it helps to have a draft following the structure above before you talk to a studio.