Starting a project moves faster when the first request is clear about the business goal, the scope you already know, and any fixed dates that matter. A short, specific brief is usually enough to start the conversation.
- The main goal for the work, such as launch, redesign, migration, or support.
- A target date if the request depends on a campaign, event, or billing cycle.
- Any existing files, links, or examples that explain the request faster than a long email.
Describe the outcome you need
Start with the result, not the tool. For example, say that you need a new landing page for lead capture or a checkout fix before renewal invoices go out.
Share anything that already exists
Include links to the current page, brand assets, content drafts, or access notes. This prevents duplicate discovery work and shortens the scoping round.
Confirm scope and next steps
After review, you will typically receive a follow-up with scope, timing, and the next action needed to begin. If anything is still unclear, we will ask for the missing details before kickoff.
You're ready to reach out
Once you have the outcome, timing, and any existing references together, you have enough to start the project conversation.
You do not need a perfect brief. A clear goal, rough scope, and any existing references are usually enough to start.
Yes. It is often better to define the first milestone clearly and then expand after the initial phase is underway.