What to bring to your first project conversation.
You do not need a finished brief. A few concrete examples help us understand the problem and identify a useful first scope.
Show us where the work gets stuck.
Share your current website, a repeated manual task, or a customer journey that is hard to complete. Tell us who uses it, what happens today, and what you want to improve.
Known budget limits, timing constraints, existing tools, and the people who need to approve the work help shape a realistic proposal. It is fine to start with open questions.
Leave room for review and handoff.
A project also needs decisions along the way. Identify who can provide feedback, supply content, and manage the result after launch. We use the scope to clarify what is included and where responsibilities sit.
For the full sequence, including what you review at each stage, see our project process from scope to handoff.