The right shape for the right problem.

A short, clearly scoped discovery engagement is useful when a team needs to organize the brief before committing to production. Start with the situation, the audience and the decisions that the next stage needs to support. The work can turn existing material into a useful direction without pretending that every uncertainty has disappeared.

Agree what the studio will review, who will contribute and how recommendations will be discussed. New research, recruitment or production work needs its own scope. The handover is a working brief and a recommended next step, not a promise of a finished identity, website or measurable commercial result. At the end, agree who owns the next decision and which unresolved questions need further work before a production schedule or budget is committed.

An identity project gives the team a structured way to move from a shared brief to a coherent visual system. The scope should explain the number and purpose of concept directions, how one is selected and which everyday applications will be used to test it. An open-ended promise of every possible format makes neither the proposal nor the handover clearer.

Define review rounds, decision responsibilities, source-file access and the agreed usage guide. Fonts, photographs and other licensed assets remain separate rights questions. The final system is a set of useful design decisions and files; the engagement does not guarantee market response, trademark availability or manufacturing outcomes. Use the agreed applications to review the system in context, and identify any additional output or technical specification that needs a separate production phase.

A digital engagement begins by agreeing what visitors need to understand or do and what content can support that journey. The proposal should distinguish information structure, visual design, native implementation and any operational systems. A visible button or form does not make a secure account, payment processor or functioning receiving system part of the delivery.

State the intended platform, the page and component scope, who provides content and who controls domain and hosting access. Testing and handover should be planned around the agreed deliverable. Ongoing support, content migration, analytics and integrations belong in the proposal if they are required rather than being silently assumed. Before launch, agree who will verify the receiving systems, publish approved content and retain access to the accounts needed to operate the actual website.