A useful brief makes better decisions.

Describe the problem before the solution

You do not need a technical specification to start. Explain what is difficult today, who is affected and what a useful outcome would look like. “People cannot understand our services” is more useful context than a request for a particular animation.

• What is happening now?
• Who is the project for?
• What should someone be able to do afterwards?

Bring the material that already exists

An existing website, sales process or product sample can reveal both useful work to keep and problems to address. Include the parts you want to preserve and flag anything that is outdated. Do not send passwords or sensitive customer information in an initial enquiry.

• Current website, profiles or product references
• Brand files, copy, photography or artwork
• Known integrations and the people who manage them

Make constraints visible

A target date, available budget range, internal approval process or delivery location can change the approach. For merchandise, add an approximate quantity, size range and material preferences. Uncertainty is fine — state it so it can be resolved in the discussion.

Choose the next step

Use the enquiry form to describe the service and the main challenge. We can use that information to discuss the scope and decide what needs closer review. A brief starts a conversation; it does not commit you to a quotation or production order.