Ten minutes with a senior developer can save weeks of wrong-direction work, but only if you brief the problem clearly. Many business owners in Uganda spend a paid consultation explaining background, searching for passwords or describing what they think is wrong, and run out of time before the developer has understood the real issue.
This guide gives you a simple structure for briefing a web developer quickly, whether you have a broken website, a slow online shop, a new feature idea or a quote you want reviewed.
Why the brief matters so much
Developers solve problems by narrowing down possibilities. Every minute spent on vague descriptions is a minute not spent on the solution. A clear brief also protects you from paying for work that was never needed, because the developer can tell you quickly whether the fix is small, large, or not a development problem at all.
1. State the symptom, not your theory
Describe what is actually happening (a page that times out, a build that fails) before offering your guess at the cause. "Our checkout page shows a white screen after customers click Pay" is far more useful than "I think the server is broken". Include:
- What you expected to happen
- What actually happens
- When it started, and whether anything changed just before (a plugin update, new hosting, a new payment gateway)
- Whether it happens every time or only sometimes, and on which devices or browsers
2. Show, do not just tell
Screenshots, a short screen recording from your phone, and exact error messages save enormous time. Copy and paste error text instead of retyping it. Share the link to the exact page with the problem.
3. Share the context
- What platform the site runs on: WordPress, Shopify, a custom build or something else
- Where it is hosted and who manages the domain
- Any integrations: mobile money or card payment gateways, booking systems, email services
- Who built it, and whether documentation exists
If you do not know some of these, say so. That is useful information too.
4. Prepare access, safely
Many problems cannot be diagnosed without access to the admin panel, hosting or code repository. Before the call, confirm you can log into these yourself. Instead of sharing your main password, create a separate account for the developer with the minimum access needed, and remove it afterwards. Never send passwords over public chats.
5. Define what "done" looks like
Agree on how you will know the problem is solved: "customers can pay with MTN MoMo and receive a confirmation email" or "the homepage loads in under three seconds on a phone". A clear definition prevents disagreements and repeat work.
6. Say what matters most
Is it speed, cost, or doing it properly for the long term? A quick patch may solve today's problem, while a proper fix may cost more but prevent recurring issues. Tell the developer your priority and budget so they can recommend the right option.
A ten minute briefing template
- Minute 1 to 2: What the business does and what the website or app is for
- Minute 2 to 4: The symptom, when it started and what changed
- Minute 4 to 6: Screenshots, links and error messages
- Minute 6 to 8: Platform, hosting, integrations and access
- Minute 8 to 10: Definition of done, priority and budget
Briefing a new project instead of a fix
If you want a new website or feature, the same principles apply. Describe the business goal first, such as more bookings or online orders, then list must have features, examples of sites you like, your timeline and your budget range. Our guide on building a website for your business in Uganda covers planning in more detail.
Reviewing a quote with a developer
A short consultation is also useful when you have a quote from an agency and want a second opinion. Share the quote and ask: is the scope clear, are the timelines realistic, who will own the domain, hosting and code, and what is missing?
Common briefing mistakes
- Starting with a long history instead of the problem
- Not having access ready
- Describing the cause instead of the symptom
- Asking for "everything" without priorities
- Sharing sensitive passwords insecurely
Frequently asked questions
Can a developer fix my website on a short call?
Sometimes. Many issues can be diagnosed quickly and small fixes done immediately. Larger issues get a clear plan and estimate.
What if I am not technical?
You do not need to be. Describe what you see as clearly as you can, and a good developer will ask the right questions.
Talk to a developer today
Book a verified web developer on The Quick Consult and use this template to get the most from your call.