A project note that shortens the build
Discovery is not moodboard tourism. It is writing down what success looks like, who the work speaks to, and what is out of scope. Vague input produces expensive loops. Specific input lets design and code move.
Four blocks: goal, audience, constraints, references
Goal names an observable change: first screen states positioning clearly, inquiry form completes, dealer locator gets used — not a mood word like modern or premium.
Audience names who decides, what they fear, what proof they need. Constraints list timeline, budget band, existing assets, integrations, and legal lines you cannot cross.
References show tempo and structure, not theft targets. Include anti-references: sites or styles you reject and why.
Good sentences beat long decks
One page beats ten scattered docs. If stakeholders disagree, the note surfaces it early instead of at round four of revisions.
Replace we want it cleaner with we need one primary call above the fold and specs downloadable without login. The second sentence is buildable.
Lock early — or pay later
Strategy, identity, interface, development, launch. Each phase assumes the last is settled. Changing positioning after components exist costs multiples of changing a sketch.
The project note is the first lock. A founder-led studio can move fast when intent is written; we still need that anchor to ship custom work without theme drift.
Write it together
Best notes are co-authored. You bring domain knowledge; the studio asks the questions that expose gaps. Shared language reduces this is not what we meant later.
Before you email a studio, finish this sentence: When we launch, we will know it worked because ___. If you cannot fill the blank, discovery still has work to do.
Send that sentence with links, constraints, and anti-references. You will get a sharper proposal and a shorter path to launch.
If this matches a problem you have, start a project conversation for your brand.