The short answer
Before a Webflow build starts, you need three things: a one-page brief with named owners, a design file that passes a readiness gate, and real content for the pages that matter most. If one is missing, the build can still start, but only when someone has written down who fills the gap and by when.
The aim is to find open questions while they are cheap. A mobile layout decided in Figma takes minutes. The same decision made in Webflow, after classes and components exist, means rework. If you want the full list of build stages, our Figma to Webflow checklist covers them. This chapter covers one moment: the go or no-go before anyone opens the Designer.
The one-page build brief
Put these answers on one page. Each one changes how the site is built, which is why they come before the first class is named.
| Question | What it changes in the build | A good answer |
|---|---|---|
| Who signs off? | How questions get closed | One named person, plus a backup |
| Which pages are in scope? | Build order and estimate | A list of page names, with final and draft marked |
| What repeats, and how often? | Components or CMS | "Two or three case studies a month, written by marketing" |
| Who edits after launch? | Roles, props and how much is locked | "Two marketers: copy and images, and new landing pages" |
| Does this replace a live site? | URLs, redirects and SEO work | Current URL, plus who owns the redirect list |
| Where do forms send? | Form setup and tests | A named inbox, CRM or sheet for each form |
| What needs tracking? | Events, consent and scripts | A short list of events, and who reads them |
| Which tools connect? | Custom code and integrations | Tool names, with an owner who has the login |
Decision rule If two people give different answers to "who signs off?", stop there. Every other open question waits on that one.
The Figma readiness gate
Go through the file against this table and mark each row pass or fail. "Ready" has a plain meaning here, so nobody has to argue about taste.
| Item | Ready means | If it fails |
|---|---|---|
| Page status | Final pages are marked. Old ideas sit on a separate Figma page. | Designer marks them. Build waits on that page only. |
| Phone layout | Every page has a phone frame, or a written rule for how sections stack. | Designer decides the hard sections. Simple stacking can be agreed in the brief. |
| Text styles | Named styles cover every heading and body size. | List the one-off sizes. Designer merges or confirms them. |
| Colours | Named colours, with no near-duplicate greys. | Same as text styles. |
| Spacing | A visible scale, with sections using it. | Agree a scale before the build. See chapter 2. |
| Auto layout | Sections and cards use it, so intent is readable. | Ask about the sections that are hard to read. |
| States | Hover, focus, error and empty states are drawn for buttons, forms and lists. | Agree one rule per element, then apply it everywhere. |
| Repeated parts | Cards, buttons and nav are Figma components, used the same way each time. | Point out the differences. Are they on purpose? |
| Motion | Each animation has a note or a reference. | Static build first. Motion is added once it is agreed. |
| Assets | Icons export as SVG. Photos are high resolution. Fonts have a web licence. | The licence is a blocker. The rest can follow. |
| Real content | Long titles and real names on key pages. | Test key layouts with the longest real text you have. |
Three results, three actions
A gate is only useful if the result changes what happens next. Score the file, then act on it.
| Result | What it looks like | What happens |
|---|---|---|
| Ready | Every row passes, or the gaps are small. | Start the build. |
| Ready with gaps | A few rows fail, each with an owner and a date. | Start with the pages that pass. Keep a shared list of gaps. |
| Not ready | No phone thinking, no styles, or pages still changing. | Hold the build. Send one list back to the designer, and agree a new start date. |
Decision rule Send gaps back as one list, once, grouped by page. Twenty questions in one message get answered in an afternoon. Twenty separate pings slow down everyone.
When the design is not a Figma file
Not every build starts from a neat file, and a different start is fine as long as you are clear about what the source is for.
| What you have | Treat it as | First step | Real example |
|---|---|---|---|
| A finished Figma file | The source of layout and style | Run the gate above | Petavue came with a finished design, built page by page, on desktop, tablet and phone. |
| A set of fixed layouts for one page | A rule the build has to follow | Ask what happens to items the layouts do not cover | Bailey shared three works grid layouts in Figma, and new projects get placed in rows automatically. |
| HTML prototypes | The source of layout and behaviour, not of code | Map its fonts, colours and scripts to the site's own system | CUBE sends prototypes that we rebuild as native Webflow on their existing style guide. |
| Content and no design | The content sets the layout | Agree the order of sections, and one class system | Baraka Impact was a single page, shaped around their content by hand in the Designer in about two hours. |
The last row shows the point of a gate: it should fit the job. A single launch page does not need eleven rows of Figma checks. It does need a sign-off, final words, a title, a description and a social image.
Content: what must be final
Waiting for every word is the wrong rule, and so is starting with none. Sort content by how much it can change the layout.
| Content | Needed before the build | Can follow |
|---|---|---|
| Home and key service headings | Yes, or a near-final draft | |
| Pricing tables and comparison tables | Yes. Rows and columns shape the design. | |
| CMS fields | Yes, a sample of three real items | The remaining items |
| Legal pages | Final text, before launch | |
| Blog back catalogue | Import once the CMS is agreed | |
| Alt text, titles and descriptions | A plan and an owner | The final words, checked in chapter 6 |
Freeze the design, and agree how changes work
Once a page is being built, changes to it have a cost. That does not mean no changes. It means one simple route for them.
- One list. Changes go in one shared place, with no side messages.
- Marked in Figma. Changed frames get a visible note, with the date in the note.
- Sorted by size. Copy and image swaps go in right away. A new section or a new template is a scope question, for the person who signs off.
- Figma stays true. If a decision gets made in Webflow, record it in the file or the list, so the two do not drift.
Done when Start the build when the brief has no blank owners, the gate has a result, and there is a date beside every gap. If you want us to run this review on your file, send it through our Figma to Webflow page.


