Webflow development for a site marketing can edit

What we build in Webflow

Home, services, the offer, about, and contact are static pages. Posts, jobs, events, and stories are Webflow CMS: one template per collection, listed and filtered elsewhere. An empty field can hide its block.

Nav, footer, hero, and form are components. Type scale and palette are variables. Where the plan includes the role, marketers build from components and editors change copy. Figma to Webflow syncs auto-layout frames, variables, and text styles a section at a time, after custom fonts are uploaded. Phone layout, CMS bindings, and forms are still built in Webflow. No auto-layout means the quote says whether we fix the file or build directly.

Jobs that arrive in the inbox

A new site is for a team that files a ticket to change a headline. Collections start from one real sample.

Fixes on an existing Webflow site start with its classes, collection fields and publication settings. Examples include a form reaching an old address, a layout that fails at a phone breakpoint, or a CMS item that was saved but never published. We check the current editing roles and permissions; Webflow’s legacy Editor has been retired.

To migrate to Webflow from WordPress, Squarespace, Wix, or static files, a CSV maps into collections once the plan can hold the items, pages are rebuilt, and forms point at your inbox or tool. Visited URLs get a 301, with a folder wildcard where the pattern matches. Review stays on the webflow.io host, out of the index, until you approve DNS. A short product list can use Webflow checkout. Subscriptions or many variants are Shopify. Titles, canonicals, and the sitemap are included. We do not promise search placement. We implement the technical side of WCAG and do not certify compliance.

From the first note to handoff

Send the URL or the Figma link, who publishes after launch, and where forms go. A booked campaign, or a domain that must move, is a date.

A page or a bug we can reproduce is hourly. A new site or a migration is a fixed quote once pages and content are visible. An open brief starts as paid discovery, and you keep the write-up if you stop.

Open the workspace on an account your company owns. The site plan for the domain is billed there, separate from the workspace plan. Removing our invite leaves the site up. Handoff names the component to copy, the fields that matter, and where forms go. Outside scripts live in a repository you keep. The project stays in Webflow. A small number of projects run at once.

Designer, CMS, and when to stop

Tools include the Webflow Designer, CMS, components, variables and the current content-editing roles. We test changes on staging before publishing to the custom domain. Images match their containers; animation follows reduced-motion settings. Custom embeds can add HTML, CSS or JavaScript, while the hosting and CMS remain managed by Webflow.

Sign-in, a complicated checkout, or a Git-based site is the wrong Webflow job. Use Next.js, React, and TypeScript, or Shopify for the store. We say so before building. On a slow page we remove the cause: an oversized hero, phone video, a heavy embed, or a collection list with no limit.

Who should write to us

Marketing leads in Canada or the United States who want a Webflow developer and can name the pages, the collections, and the editor. An agency sub-project, under their name or with a credit. A team that already has a designer or developer and wants only the Webflow part.

If the brief is still open, paid discovery can turn it into a defined feature list and acceptance checks. If you already have a developer or agency, we can take a bounded part of the work and agree how it joins the wider project. Share the target date so we can assess capacity and dependencies before committing.

The studio is in Vancouver, British Columbia, on Pacific Time. Work across Canada and the United States is remote. There is no other office.

What we can show, and what to send

Our website and nine App Store apps are products we own; the website is hand-built rather than a Webflow project. For a Webflow engagement, you review the pages in staging, exercise the CMS and forms, and check what the assigned editing role can do. The handoff documents components, collection fields and the release process for that site.

Send a page list, Figma or the live URL, one sample per collection, logos and fonts, form destinations, and old paths a move must keep. Name the workspace owner.