Project Intake
Let’s scope your project,
the right way.
A short, guided brief — one question at a time. It helps me understand what you're trying to achieve, who it's for, and what success looks like, so our first conversation is focused and any proposal is sharp.
We'll move through it together: the problem, the people, then the outcome — before talking solutions.
Step 1 — About you
First, who am I working with?
Just so I know how to reach you and a little about your organization.
The elevator version is perfect.
Please fill in the required fields before continuing.
Step 2 — The problem
What's the problem you're trying to solve?
Everything good starts here. I want to understand the pain before we talk about any cure.
The situation today, and why it matters now. What prompted you to seek help?
A current tool, a manual workaround, a competitor — or nothing yet.
The cost of inaction — lost revenue, churn, support load, missed launches, team friction.
Please describe the problem before continuing.
Step 3 — The people
Who is it for?
The audiences we're designing for — and who we should learn from first.
Be specific — "B2B ops managers at mid-size logistics firms" beats "businesses."
Your early adopters — the people whose feedback should shape the work first.
Internal teams, admins, partners, regulators.
Please describe your primary users before continuing.
Step 4 — The outcome
What does winning look like?
The outcome you want — this becomes our shared definition of done.
The business or product outcome, not the deliverable. e.g. "Cut onboarding drop-off," "Launch a credible v1."
The one thing that, if we nail it, makes everything else secondary.
Please share what you're hoping to achieve before continuing.
Step 5 — The work
What kind of help do you need?
Pick anything that feels relevant — we'll refine the real scope together.
Fine if not — but if you're picturing a prototype, a report, a design system, say so.
Please choose at least one type of engagement before continuing.
Step 6 — Success
How will we measure success?
Even rough signals help. If we can't measure it, it's hard to know we've helped.
Activation, conversion, task completion, support tickets, NPS, time-to-value — or qualitative confidence.
Step 7 — Timing
When does this need to happen?
Helps me check fit, sequence the work, and flag anything unrealistic early.
A launch, event, funding round, board meeting — the "why" behind the date helps a lot.
Please choose an ideal start before continuing.
Step 8 — Budget
What investment are you working with?
No wrong answers. A rough range lets me recommend a scope that actually fits — rather than over- or under-shooting.
Please choose a budget range before continuing.
Step 9 — Context
Constraints, context & what already exists.
The practical realities — surfacing these now avoids surprises later.
Who signs off, and who's the day-to-day contact?
Tech stack, brand guidelines, accessibility/compliance, legal, existing vendors, internal politics.
Research, analytics, designs, a design system, brand assets. Paste a Google Drive / Dropbox link (set so “anyone with the link can view”).
—
Step 10 — Last thing
Anything else I should know?
The floor is yours — context, questions, hopes, or hesitations.