You don’t need technical knowledge to start a web or software project, but you do need to explain what you want to achieve. A short, clear brief helps any developer understand your business, ask the right questions and give you a realistic plan. Here is a simple way to write one.
Describe your business in a few sentences
Who are your customers, what do you offer and where do you work? A few plain sentences give a developer the context they need to make sensible suggestions.
Include what makes your business different and what customers usually say when they choose you. This helps a developer understand which strengths the project should highlight.
Explain the problem, not just the solution
It is tempting to write “we need an app” or “we need a new website.” Try to describe the problem behind it instead: customers can’t book online, your team re-types orders into three systems, your site is hard to use on phones.
A clear problem lets a developer suggest the simplest solution, which may be different from what you first imagined.
Mention who is affected by the problem: customers, staff, or both. A problem that frustrates customers usually calls for a different solution than one that slows down your team behind the scenes.
Define what success looks like
Write down how you will know the project worked. Keep it practical:
Try to describe success from the point of view of the people who will use the result. “A customer can find our prices and book a call in under a minute” is more useful than “a modern website,” because it tells everyone what to design and test for.
- Customers can request a booking from their phone
- Your team stops copying information by hand
- You can update your own website text without help
List what you already have
Mention your current website, the tools you use (calendar, invoicing, customer lists), your domain name and who has access to them. This avoids surprises later and shows what can be reused.
If you have examples of websites or tools you like, add links and a sentence on what you like about each. “The booking steps are simple” or “the text is easy to read” is far more useful than “it looks nice.”
Keep it short
One page is usually enough. A good developer will ask follow-up questions; the brief is the start of the conversation, not a contract.
Leave space for what you don’t know yet. Writing “we’re unsure whether we need an app or a website” is perfectly fine and often leads to the most useful advice. The aim is to share your situation honestly, not to have every answer before the first conversation.
A simple template you can copy
If a blank page feels daunting, answer these headings in a sentence or two each. You can write it in a document, an email or even a voice note that you transcribe later. What matters is that the answers are honest and specific.
Once you have a draft, read it aloud or share it with a colleague. If something is unclear to them, it will probably be unclear to a developer too. A brief rarely needs to be perfect; it needs to be clear enough to start a useful conversation and to make the first meeting productive.
- About us: who we are, who we serve and where
- The problem: what isn’t working and who it affects
- Success: how we will know it worked
- What we have: website, tools, domain and access
- Timing and budget: any key dates and a rough range
- Examples: links we like and why