How do I brief a Webflow developer for site updates?

Start with the outcome, not a task dump

A useful brief answers what should change on the live site and how you will know it worked. Lead with the outcome, the audience, and any hard dependency. Vague asks such as make the homepage better force guesswork. Specific outcomes such as replace the three outdated service blurbs on /services with the attached copy and keep the current layout cut revision cycles.

Include who owns approval. If marketing writes copy and a founder signs off, say that up front so the developer does not treat a draft as final.

List pages, CMS items, and change type

Spell out every URL or Collection item. Note whether the work is:

• Copy or image swap on an existing section
• New section using current components
• CMS field or Collection structure change
• Form, redirect, domain, or SEO setting change

Structure work (new fields, template redesign) risks more pages than a text swap. Call that out so the developer can suggest a backup or a staging-only publish first. If multiple locales exist, list which locales must update together.

Attach final assets and write acceptance checks

Paste final copy in the brief or attach a single source document. Provide image files at the size you want on the page, plus any alt text you already decided. Link to referencing designs only when they are current; outdated Figma frames cause mismatches.

Write three to five acceptance checks the developer can tick before asking for review:

• Desktop and mobile screenshots of the changed section match the brief
• Links and buttons go to the listed URLs
• Forms still submit a test record after the change
• No unrelated pages were published by accident

Example brief block: Page /pricing. Replace annual plan price with $1,188 and keep the monthly line. Asset: pricing-hero.jpg with Descriptive alt annual pricing overview. Done when /pricing shows the new numbers on mobile, the CTA still goes to /contact, and a test form submit appears in Site settings > Forms. If legal must approve the price line, say so and attach the approved PDF so the developer does not invent wording.

Set priority and keep communication written

Mark urgent versus normal, and say what blocks a launch (campaign send, legal review, partner go-live). One board card or email thread with the full brief beats fragmenting the same request across chats. Reply in the same thread when copy changes so history stays searchable.

When updates are frequent across the same Webflow site, a month-to-month membership can keep one person familiar with the structure. Webflower's plan is $999 per month with 10 hours included, overage at $75 per hour only after a written estimate you approve, unused hours that expire each period, async written communication only, pickup within 24 hours for urgent requests and 48 hours for others, and your Webflow account staying in your name. New sites and full redesigns stay separate projects.