How I scope a site before I draw a screen
A clear brief beats a long fight later. Here's what I lock in so design, build, and launch stay aligned.
I don't start in Figma or in code. I start with what you need the visitor to do, who they are, and what "done" looks like for you. That sounds obvious, but skipping it is how projects drift.
We agree on scope in writing: pages, sections, integrations, and what is not in this phase. Everyone sees the same list before I spend time on layout or components.
When something new appears mid-build, we treat it as a change - we discuss it, quote if needed, and then I ship it in code. No surprise scope on either side.