Website technical specification: how to write one yourself
A spec does not need to be a fifty-page document full of jargon — what matters is that the studio and the client agree on exactly what the result should be.
Why a spec matters even for a simple site
Without a written spec, a studio works from verbal wishes that each side remembers and interprets differently. A month in, the client says 'that's not what I meant' and the studio says 'you never said that' — both correct from their own view. A written document removes the problem entirely.
Even for a simple brochure site, a one- or two-page spec saves time: the studio immediately understands scope and can quote a precise price instead of a rough range.
Required sections
Site goal: what should happen after a visitor lands — submit an enquiry, call, buy. Target audience: who they are, what language, what device. Page list: home, about, services, portfolio, contacts, each with a one-line description.
References: two or three sites you like the style of, noting exactly what you like — colours, structure, typography. This saves dozens of revision rounds.
What people often forget to include
Language versions and which is primary. A list of integrations — a Telegram-connected form, payment, CRM. Requirements for copy and photos — whether the client supplies them or the studio must prepare them.
A simple template to start from
Company name and field. Site goal in one sentence. Target audience. Page list with one line each. Three references with notes. Languages. Needed integrations. Who prepares copy and photos. Rough budget and desired timeline. That covers 90% of brochure- and catalogue-level projects.