Project details do not need to be long or full of technical terms. They should explain the current situation, the desired result and the project constraints. With this information, the studio can propose the right solution, estimate the work realistically and reduce revision rounds.

At a glanceThe article's main ideas
01Start with the problem, not the solution02Define the audience and its decision03Inventory existing content and materials

Start with the problem, not the solution

Describe what does not work today and what should change. It may be a lack of qualified enquiries, an inconsistent identity, too many repetitive questions or a slow manual process. A clear problem leaves room for a better solution than a rigid list of effects and functions chosen before analysis.

Define the audience and its decision

Explain who the right customer is, what they already know, what questions they have and what stops them from acting. For a website, define the primary action. For branding, describe the desired perception and where the identity will be used. For AI, show who uses the system, what information it may access and when it must hand a case to a person.

Inventory existing content and materials

List existing copy, photographs, logos, guides, documents, data and accounts. Mark what is current, what needs rewriting and who can approve it. Many delays happen not in design or code, but because content and decisions are unavailable at the right time.

Separate requirements from preferences

Requirements are items without which the project cannot do its job: languages, integrations, accessibility, legal deadlines or mandatory workflows. Preferences are directions to explore: style, animation and visual references. This separation helps prioritise when time or budget is limited.

Finish with budget, timing and success criteria

A budget range helps the studio select a realistic scope and propose stages. Timing should be tied to a real event rather than a general desire to finish quickly. Define how success will be recognised: more relevant enquiries, a smooth launch, time saved or an identity used consistently by the team.

A good project description does not dictate every detail. It provides enough context for sound decisions to be made quickly.

Frequently asked questions

How detailed should the project information be?

For many projects, one to three clear pages are enough. The quality of the answers matters more than the document length.

Do I need to know the required technology?

No. Explain the functions, users, volume and required integrations. The studio can recommend technology after understanding the project and maintenance conditions.

Can I send examples of websites or brands?

Yes. Explain exactly what you value in each example: structure, clarity, tone, motion or atmosphere. Examples are references for discussion, not templates to copy.

Do you have a specific project?

We clarify the solution before estimating.

Send us the context, goal and indicative budget. We will reply with the right questions and next steps.

Discuss your project ↗