How to brief a web developer (without knowing the jargon)
You don't need a technical spec to get a good quote. You need to answer four questions clearly.
Clients often apologise for not knowing what they want technically. They don't need to. The best briefs we receive contain no technical language at all.
What genuinely helps is knowing what the site is for. Is it there to take bookings, sell products, generate enquiries, or establish credibility? A site optimised for one of those looks different from a site optimised for another.
It also helps to know who's visiting and on what. A local service business with older customers on phones needs different choices from a B2B firm whose clients browse on desktop during work hours.
Then: what already exists? A logo, brand colours, photography, existing copy, an old site with content worth keeping. Anything you have shortens the timeline.
And finally, examples. Two or three sites you like, with a sentence on what you like about each, communicates more than a page of description. That's often where the whole project starts.
Thinking about a new site?
Tell us what you need and you'll get a fixed, itemised quote — no obligation.
Start a project