Webflow Design and Development Services

Webflow Design and Development

Summary: Sandcastle is a Webflow Partner in Seattle. We design and build Webflow sites, or build from your agency’s finished designs, with the content model planned before the pages, migrations that keep your search results pointing somewhere real, and a handover into your own Webflow workspace.

Webflow is at its best when a site has to look exactly like the design and still be editable by people who do not write code. That combination is hard to get from most content management systems, and it is the reason clients ask for Webflow by name.

Getting there takes more than dragging elements onto a canvas. A Webflow site that works two years later is one where the content model was designed before the pages were, where the styling runs through variables and shared components instead of hundreds of one-off classes, and where somebody thought about the handover before the launch. That is the part we do.

We can start wherever you are. If you have finished designs from your own agency, we build them. If you do not, we design the site as well, which is work we have been doing since 2001, longer than we have been doing any of it in Webflow.

Sandcastle is a Webflow Partner. We have been building content-managed websites since 2001, on Webflow, WordPress, Wix, Umbraco and others, so we come at a Webflow build with opinions about content models formed well before Webflow existed.

Comps waiting on a build, or a site only a developer can edit? Tell us what you have, or call (206) 325-5383.

FREE PROJECT EVALUATION

What We Build in Webflow

Design and build, start to finish. Site structure, page design, and the build, working from your brand or helping you settle one. You do not need designs in hand before you talk to us.
Builds from finished designs. If the designs already exist, bring the comps from your designer or agency, in Figma, Illustrator or PDF. We build them, make the responsive decisions the comps do not cover, and give you back a working site.
Redesigns of an existing site, where the content is broadly right but the design, structure, and navigation are not.
CMS architecture. Collections, fields, templates and the relationships between them, designed so your team adds content through a form instead of asking for a layout change.
Migrations onto Webflow from WordPress, Wagtail, Umbraco, Drupal, or a hand-built site, including the redirect map that keeps your search results pointing somewhere real.
Custom interactions and scripts for the parts Webflow’s built-in interactions do not reach: filtered and sorted lists, tabbed sections, modals, accordions, conditional link behavior.
Analytics and cookie consent, including consent-gated Google Analytics 4 configured for GDPR and US state privacy laws, so no tracking cookie is set before a visitor allows it.
Site handover. Setup in your own Webflow workspace under your own billing, with documentation written for the people who will actually update the site.

What Actually Decides Whether a Webflow Build Works

Most Webflow projects that go wrong do not go wrong in the Designer. They go wrong in decisions made in the first week, or skipped in the last one.

The content model comes before the pages. Anything that appears more than once, team members, press releases, publications, case studies, should be a collection with a template, decided before a single page is built. Retrofitting a collection onto pages that were built by hand means building them again.
Styling belongs in variables and components. Brand colors defined once as variables mean a rebrand is a handful of edits. A header and footer built as shared components mean a nav change is one edit, not one per page. Sites built without this are the ones where a small change quotes surprisingly high.
Redirects are a launch task, not a cleanup task. Old addresses need mapping to new ones before the switch, and the honest source for that list is the old site’s own sitemap rather than somebody’s memory.
Comps specify widths, not a website. A handoff usually covers one or two widths, sometimes desktop alone, sometimes desktop and phone. Everything between and beyond them belongs to the developer. Where two widths are drawn, the right move is to read them as the endpoints of a rule that scales continuously rather than as two fixed layouts with a jump in the middle.
The handover is part of the build. A site nobody can confidently edit is a site that stops being updated. Field-level help text and a written guide cost a day and save a year.

FAQ

What does Webflow cost to run?

Webflow bills in two places: a workspace seat for whoever builds the site, and a site plan for the site itself. The site plan is the one that matters to you. Plans step up by how much content and traffic you have, and a site with a CMS behind it needs one of the CMS-capable tiers rather than the entry-level one.

Two limits are worth knowing before you start. An unhosted site is capped at 50 CMS items, which is fine while a site is being built and not fine once it is populated, so the plan goes on before the content does. And 301 redirects do not work until a paid site plan is attached, which makes redirects a task for the week of launch rather than before it.

Do we need to have designs before we start?

No. Some projects reach us as finished comps from a client’s own agency. Others start with a company that knows what the site needs to do and has no designs at all. Both are normal, and the second is not a lesser version of the first.

If you have designs, we build them and handle the widths the comps do not cover. If you do not, we design the site with you: structure and page hierarchy first, then the pages themselves, working from your existing brand or helping you land on one. Design has been part of what we do since 2001. Either way, the content model gets designed alongside the pages rather than after them, which is the decision that determines how easy the site is to run later.

Can our team update the site without a developer?

Yes, and this is usually the reason people move to Webflow in the first place. Webflow separates content editing from design: the Editor is where someone adds a blog post or a team member, and the Designer is where layout and styling change. A marketing team lives entirely in the Editor.

How well that works depends on how the site was built. If recurring content is set up as CMS collections with templates, adding an item is filling in a form. If it was built as hand-placed elements, every update is a design change, which puts you right back where you started.

Can you take over a Webflow site somebody else built?

Yes. Webflow sites transfer cleanly between workspaces, and the design, CMS and settings all come across intact.

Two things to expect. Transferring a site unpublishes it and removes custom domains until the new owner republishes, so it is done deliberately rather than casually. And a site plan does not travel with a transfer between individual accounts. The old plan is refunded pro rata and the new owner attaches their own, which is a billing detail worth knowing before the day it happens rather than after.

When is Webflow the wrong answer?

When the site is really an application. Webflow is a superb marketing site platform and a limited one for anything with complex business logic behind it. If you need real B2B ecommerce, purchase order payment, procurement integration, ERP data exchange, or customer-specific pricing, you want nopCommerce or AbleCommerce and we will tell you so.

Webflow is also not the cheapest way to run a small brochure site. If your requirements are modest and your budget matters more than pixel-exact control, WordPress or Wix is often the better call. We build on all three and have no reason to push you toward one.

Working With Us on Webflow

We take Webflow projects all the way through to a launched, documented site you own, starting either from our own design work or from comps your agency has already produced. Both routes are normal here, and neither costs you anything in build quality.

If you are moving from another platform, that is a migration before it is a Webflow build, and the redirect map is as much of the job as the pages are. If you want somebody looking after the site afterward, our hosting and maintenance practice covers ongoing work, and analytics covers measurement and consent. For the other platforms we build on, see content management systems.

Start With a Free Project Evaluation

Tell us what you have. A set of comps waiting on a build, a site on a platform only a developer can operate, a Webflow site somebody else started, or nothing yet beyond a clear idea of what the site needs to do. We will tell you honestly whether Webflow is the right home for it. You can also reach us through the contact page.