FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 1 of 6

Brief and Figma handover

A build should start from decisions, not guesses. A one-page brief, a pass or fail gate for the Figma file, and what to do when the design arrives in another form.

6 min readUpdated 2026-11-07
All chaptersChapter 1 of 6
  1. 01Brief and Figma handover
  2. 02Client-First, classes and variables
  3. 03Components and CMS model
  4. 04Interactions that stay fast
  5. 05Editor handover
  6. 06Pre-launch checks

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.

QuestionWhat it changes in the buildA good answer
Who signs off?How questions get closedOne named person, plus a backup
Which pages are in scope?Build order and estimateA 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 workCurrent URL, plus who owns the redirect list
Where do forms send?Form setup and testsA named inbox, CRM or sheet for each form
What needs tracking?Events, consent and scriptsA short list of events, and who reads them
Which tools connect?Custom code and integrationsTool 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.

ItemReady meansIf it fails
Page statusFinal pages are marked. Old ideas sit on a separate Figma page.Designer marks them. Build waits on that page only.
Phone layoutEvery 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 stylesNamed styles cover every heading and body size.List the one-off sizes. Designer merges or confirms them.
ColoursNamed colours, with no near-duplicate greys.Same as text styles.
SpacingA visible scale, with sections using it.Agree a scale before the build. See chapter 2.
Auto layoutSections and cards use it, so intent is readable.Ask about the sections that are hard to read.
StatesHover, focus, error and empty states are drawn for buttons, forms and lists.Agree one rule per element, then apply it everywhere.
Repeated partsCards, buttons and nav are Figma components, used the same way each time.Point out the differences. Are they on purpose?
MotionEach animation has a note or a reference.Static build first. Motion is added once it is agreed.
AssetsIcons export as SVG. Photos are high resolution. Fonts have a web licence.The licence is a blocker. The rest can follow.
Real contentLong 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.

ResultWhat it looks likeWhat happens
ReadyEvery row passes, or the gaps are small.Start the build.
Ready with gapsA few rows fail, each with an owner and a date.Start with the pages that pass. Keep a shared list of gaps.
Not readyNo 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 haveTreat it asFirst stepReal example
A finished Figma fileThe source of layout and styleRun the gate abovePetavue came with a finished design, built page by page, on desktop, tablet and phone.
A set of fixed layouts for one pageA rule the build has to followAsk what happens to items the layouts do not coverBailey shared three works grid layouts in Figma, and new projects get placed in rows automatically.
HTML prototypesThe source of layout and behaviour, not of codeMap its fonts, colours and scripts to the site's own systemCUBE sends prototypes that we rebuild as native Webflow on their existing style guide.
Content and no designThe content sets the layoutAgree the order of sections, and one class systemBaraka 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.

ContentNeeded before the buildCan follow
Home and key service headingsYes, or a near-final draft
Pricing tables and comparison tablesYes. Rows and columns shape the design.
CMS fieldsYes, a sample of three real itemsThe remaining items
Legal pagesFinal text, before launch
Blog back catalogueImport once the CMS is agreed
Alt text, titles and descriptionsA plan and an ownerThe 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.

Takeaways

What to remember from chapter 1.

  • One page of answers comes before the first class: owners, scope, editors, forms and tracking.
  • Mark the Figma file pass or fail, row by row. Each failed row needs an owner and a date.
  • A font without a web licence is a blocker. Most other gaps can follow.
  • HTML prototypes are a source for layout and behaviour, not code to keep.
  • Size the gate to the job. A single launch page needs far fewer checks.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.