Problem statement
The problem in one sentence. If it takes three, the project is not scoped yet.
This is the intake template we actually use before scoping a project — not a marketing checklist. Eight sections that force the questions a build lives or dies on, in a 2-page fillable PDF.
Each one fits in a few lines. All eight together are the difference between a scoped project and a guess.
The problem in one sentence. If it takes three, the project is not scoped yet.
The steps as they happen today, and who owns each one.
Sources, formats, and who can grant access to each.
The systems the build must talk to, and how each handles auth.
One metric, and how it is measured today — not how it should be.
Compliance requirements, timeline pressure, and team availability.
The range the project can operate in, stated plainly.
When a decision gets made, and who makes it.
A blank budget band tells you the project has no sponsor yet. An empty data inventory tells you discovery starts with access, not architecture. A success metric nobody currently measures tells you the first deliverable is instrumentation. Filling this in honestly — including the parts you cannot fill in — is the fastest way to find out whether a project is ready to scope.
Every empty field is a question that would otherwise surface mid-build, at a worse price.
A completed brief lets a fit conversation start at the decision, not at the introductions.
It works with any vendor, internal team, or build path — not just ours.
Request the brief and we'll send the fillable PDF to your inbox.
A completed brief is the best possible starting point for a fit review. We read it before the call, so the conversation starts at your actual constraints — data, integrations, budget band, and timeline — instead of a generic pitch.