How to write a technical brief
A technical brief is a description of what you want to get. The clearer you describe your idea, the more accurately we can estimate timelines and cost, and the fewer revisions there will be. Below is a simple guide on how to prepare a brief. You don't need to know technical terms.
Not sure where to start? That's fine. Describe your idea in your own words, and we'll help shape the rest during a free consultation.
1. Why you need the project
Explain what problem the site or app should solve and what you want to achieve: more leads, more sales, automating routine work.
Example: "We need a site so customers can order delivery online and we take fewer phone orders".
2. Who it's for
Describe who will use the product: your customers, staff, a certain age group or region. This affects the design and usability.
3. What the product should do
List the features you need in plain words. Don't worry about wording, the gist is what matters.
- registration and login for users
- a catalog of products or services with search
- cart and online payment
- a request or contact form
- personal account, reviews, blog, if needed
4. How it should look
Show examples of sites you like, and what exactly you like about them, plus your colors, logo and style if you have them. If you don't have a style yet, we'll suggest one.
5. Content and materials
Note what you already have: texts, photos, logo, video. For anything missing, we'll advise what to prepare or create it ourselves.
6. Timeline and budget
State your desired launch timeline and an approximate budget, at least a range. That lets us propose the best solution right away without extra back-and-forth.
In short: what to add to the brief
- the project goal and expected result
- who the product is for
- a list of needed features
- examples of design you like
- available materials: texts, photos, logo
- desired timeline and approximate budget