How do I explain what I want to a web developer?
Key takeaways
- You do not need technical words; describing your goals and customers in plain language is more useful.
- A short written brief covering goals, customers, pages, examples, content, languages and must-haves saves time.
- Showing websites you like, and saying why, is the easiest way to describe a look.
- Explain features as steps a customer or staff member takes, such as placing an order or adding a promo code.
Many business owners worry that they will not be able to talk to a web developer because they "don't know the technical words". The good news is that you do not need them. A good developer's job is to turn your business needs into technical decisions. Your job is to explain your business, and you already know it better than anyone.
Do I need to know technical terms to talk to a web developer?
No. Describe what you want in your own words, the way you would explain it to a new employee. A professional developer will ask questions and translate your answers into a plan.
For example, you do not need to say "I need a responsive layout with a lead-capture form". You can simply say "Most of my customers use their phones, and I want them to be able to ask for a quote easily". That sentence is actually more useful, because it explains why, not just what.
What should I tell a web developer before they start?
The most helpful things are your goals, your customers, the pages you think you need, examples you like, and what content you already have. You can use the checklist below as a simple brief. Copy it, fill it in, and send it before your first meeting.
| Topic | Questions to answer in your own words | Your answer |
|---|---|---|
| Goals | What should the website do for the business? More calls, more enquiries, online sales, fewer repeated questions? | |
| Customers | Who are your customers? Where are they, how old are they, and what do they want to know before buying from you? | |
| Pages | Which pages do you imagine? For example: home, about us, services, products, news, gallery, contact. | |
| Examples you like | Two or three websites you like (and what you like about them), and one you dislike. | |
| Content | Do you have a logo, photos, page text and product details ready? Who will write what is missing? | |
| Languages | Arabic, English or both? Should both languages have the same content? | |
| Must-haves | Anything the site must have: an online store, booking requests, a newsletter, downloadable files, delivery areas. | |
| Who updates it | Who in your team will update the website after launch, and how often? | |
| Timing | Is there a date you need it by, such as a product launch, an exhibition or a season? |
Do not worry if some answers are "I'm not sure". That is useful information too. It tells the developer where you need advice.
How do I describe the look I want?
The easiest way is to show, not tell. Send links to websites you like and say what you like about each one: "the calm colours", "the big photos", "how easy the menu is". Screenshots with a short note work well.
- Feelings: choose three words for how the site should feel, such as "modern, trustworthy, warm".
- Colours: mention your brand colours, or colours you definitely do not want.
- Competitors: share competitors' sites and say whether you want to look similar or different.
- Dislikes: what annoys you on other websites? Pop-ups, tiny text, too much going on?
If you are unsure what makes a design work, our article on what makes a good website design explains it in plain terms.
How do I explain the features I need?
Describe what you want a customer or your staff to be able to do, step by step. This is the clearest way to explain any feature.
- "A customer finds a product, chooses the size and colour, and places an order."
- "We get a notification and see the order in the admin."
- "The delivery fee depends on the customer's area."
- "Our marketing person can add a promo code for the weekend sale."
Sentences like these are exactly what a developer needs. Every website we build runs on our own CMS, the admin panel you use to edit your website, which already covers many everyday needs like pages, articles, galleries, forms, products, orders and delivery areas. When you describe a need in plain words, we can usually tell you straight away whether it is already there or something we will add for you.
What questions should I ask the developer?
A conversation goes both ways. These simple questions help you understand what you are getting:
- Will I be able to change text, photos and products myself after launch?
- Will you train my team to use the admin panel?
- How long will the project take, and what do you need from me at each stage?
- Who owns the domain and the content?
- What happens if I need help or a new feature later?
For more on the timeline side, see how long it takes to build a website. For ownership, read will my web designer own my website.
What if I still feel unsure?
That is completely normal. A good first meeting should feel like a conversation about your business, not a test. Bring your filled-in brief, even if half of it is empty, and let the developer guide you through the rest.
When you are ready, send us your brief or just a few lines about your business, and we will take it from there.
How Kensoftware approaches this
- We start with a conversation about your business and customers, and we ask the technical questions so you do not have to.
- We turn your brief into a clear list of pages and features in plain language and confirm it with you before design begins.
- Because every site runs on our own CMS, we can tell you early which needs are already covered by the admin panel and which we will add for you.
- We show you design examples and working pages as we go, so you react to something real instead of imagining it.
Frequently asked questions
What if I do not know which pages I need?
That is fine. Tell the developer what customers usually ask you and what you want them to do, and they can suggest the pages. Most business sites start from a familiar set such as home, about, services and contact.
Should I write the brief in Arabic or English?
Write it in whichever language you are most comfortable with. What matters is that your goals and needs are clear, not the language of the brief.
How long should a website brief be?
One or two pages is plenty. Short, honest answers to the main questions are more useful than a long document full of guesses.