Start a brief

What do you need, and what does it have to fit into?

These are the questions I ask before I build anything, so what I deliver drops straight into your systems instead of sitting beside them. Three parts: what you need, what it should achieve, and what it has to fit into. Answer what you can and send it to me. Most answers take a line.

Fastest

Give it to your AI

Copy the brief into ChatGPT, Claude, Copilot or whatever you use, along with your product docs. It fills in what it can, asks you about the gaps, and writes the finished brief for you to email to me.

Download it

Or, if your AI can read web pages, just tell it: Read brief.md on this site and help me fill it in.

Fill it in here

Answer what you can below, skip the rest, then copy or email your answers. Short on time? The four marked "Most important" matter most.

Go to the questions

Just talk

Prefer a conversation? Email me and we'll set up a call. I'll ask the questions.

Your name

Company

1. What do you need?

For whoever owns the project.

1What should it do, and for whom?

One sentence is plenty: "Show buyers why our router keeps calls up when a line fails."

2Where will people use it?

Your website, sales calls, a trade-show screen, the factory floor, inside your own software, or somewhere else.

3What exists today?

Datasheets, decks, old guides, spreadsheets, a competitor's version you like. Links are fine.

4How should it look and feel?

Playful or serious, polished or simple. Any brand colours, fonts or guidelines? Links to sites, videos or apps whose look you like (or hate) are the quickest way to show me.

5What matters more for this job: how it looks, how it works, or both equally?

6Which of these is closest to what you're after?

Every project gets a fixed price once the brief is agreed.

2. What should it achieve?

7When do you need it, and is the date fixed?

8How will you know it worked?

More demos booked, fewer support tickets, faster builds, one happy sales director.

3. What does it have to fit into?

For your developer or whoever runs the system it goes into. One line each. If it's a standalone piece, like an explainer for your website, skip this part.

9Can you send one real example, raw and uncropped?

One complete record, page or section exactly as your system stores it, including the awkward bits. This answers half the questions below on its own.

10Where does the data live, and what format is easiest for you to take?

A database, a CMS, a JSON or PHP file, a spreadsheet. JSON, CSV, a PHP array, something else?

11Which fields are required and which are optional? Any you're not sure about?

12Is the text plain or HTML, and which languages does it need?

13How are labels and markers on images stored?

Baked into the picture, or positions in the data? If positions, pixels or percent? And your image rules: maximum width, format, file size, naming, folders.

14Do items come from a master list with IDs?

Parts, products, SKUs, tools. Are they typed out each time or looked up? If there's a list, can you send it, so everything I deliver uses your IDs?

15What gets saved when someone uses it, and where?

Ticks, form fields, serial numbers, measurements, pass or fail. Saved against a user, a unit or an order?

16How do you handle models, variants or markets?

One version per product, or shared content with conditions?

17What are the limits?

Design system or CSS classes I must use, frameworks, PHP or JavaScript versions, hosting, security and privacy rules (no outside calls, GDPR, single sign-on).

18How do you want it delivered, and who looks after it afterwards?

A zip, a repository, a CMS upload. Where does it go, and who updates it?

19Which current file or tool causes you the most pain, and why?

Size, speed, readability, nobody understands it any more. Often this is the real job.

Email them to Munir

Your answers are saved as a draft in this browser only. Nothing is sent from this page. Clear the saved draft here, or copy your answers and paste them into an email to hello@whackyweather.cloud.