Webflow development, and the work around it

All services

• Development

  Content management systems

  Simple or complicated CMS setups in Webflow: collections, the relationships between them, and the front end logic that ties the whole thing together.

• Development

  Reusable component systems

  A component library your marketing team can build new pages from, so a new landing page does not need a developer every time.

• Development

  Cleanup and class organization

  A disorganized site restructured into a naming convention and class system that stays manageable as the site grows instead of getting worse.

• Development

  Filter, sort and search

  Resource libraries with real filtering, sorting and instant search. Blogs, help centers, podcast archives, video libraries.

• Development

  Design systems and variables

  Color, type and spacing held as Webflow variables, so a rebrand is a change to the tokens rather than a pass over every page.

• Development

  Figma to Webflow

  A finished Figma file built out properly in Webflow, matched to the design rather than approximated and explained away. What carries and what does not.

• Development

  Custom code components

  The parts Webflow will not do natively, written as clean embeds that your team can still place and configure themselves.

• Development

  Localization

  Multi language sites using Webflow Localization, including localized CMS content and the hreflang setup that makes it count.

• Development

  Dashboards

  Data heavy views built inside Webflow and wired to wherever the numbers actually live.

• Development

  Calculators

  Pricing, ROI and sizing calculators built into the page, with the math and the states handled properly.

• Development

  Source control

  Supports the work

  Git based version history for the custom code and project assets around a Webflow site, so changes there are tracked and reversible. The Designer keeps its own backups, which are a different thing.

• Development

  Headless front ends

  Webflow kept as the CMS with an Astro front end in front of it, for sites that have outgrown what Webflow renders.

• Development

  Astro builds

  Sites built in Astro when speed is the point: no client side framework by default, and only the JavaScript a given page actually needs.

• Development

  Sanity CMS

  Sanity as the content backend, with schemas shaped around how your team actually writes and live preview so nobody has to publish blind to see a change. How it connects.

• Development

  Webflow to Astro migration

  Outgrown Webflow, or paying for a CMS nobody edits? I move the site to Astro with the design and the content intact, the addresses preserved where that is practical, and what changed mapped and then checked after launch. See how that runs.

• Development

  Webflow to Next.js migration

  The same move, where the destination is an application rather than a content site: the marketing pages rebuilt as components, the content given a backend somebody chose, and the routes kept so the site keeps its search history. What that involves.

• Development

  Website migrations

  WordPress, Drupal, Contentful, Framer, Wix and the rest, rebuilt in Webflow with the content model, the URLs, the search footprint, the integrations and the DNS cutover all handled rather than handed back to you. Twenty-one platform guides.

• E-commerce

  E-commerce development

  Your commerce backend connected to a Webflow front end, with the technical functionality intact on both sides of the join.

• E-commerce

  Shopify storefronts

  Design the storefront in Webflow and let Shopify handle cart, checkout and tax, which is where that work belongs.

• E-commerce

  Stripe payments

  Checkout, subscriptions and the webhook plumbing that keeps your records honest after the charge goes through.

• E-commerce

  Marketplace front ends

  Listings, profiles, acquisition pages and submission flows in Webflow, connected to the systems that own accounts, transactions and live inventory. How I draw that line.

• E-commerce

  Job boards

  Job board and freelancer marketplace builds, including the automation scenarios that keep listings current without manual work.

• Interactions

  Custom animations

  Scroll driven animation, 3D and animated product demos. You bring the idea and I work out how it survives a real page.

• Interactions

  Text animations

  Custom GSAP text animation, from a subtle reveal on a headline to a full typographic set piece.

• Interactions

  Interactive maps

  Google Maps or Mapbox connected to the Webflow CMS so locations stay editable. State maps, world maps, 3D globes.

• Interactions

  Charts and data visuals

  Chart.js visualizations wired to CMS content or live data, styled to look like part of the site rather than a widget.

• Interactions

  Page transitions

  Cross page transitions that keep the site feeling like one surface instead of a stack of separate documents.

• Automation

  CRM integrations

  HubSpot, Salesforce and Pipedrive wired into Webflow, with fields mapped and the source attribution surviving the handoff. The guides for each.

• Automation

  No-code automations

  An automated backend for the site: form data into your tools, database storage, notifications and CMS updates. Built on Webflow and configured in Zapier, Make or a custom integration, depending on what the workflow needs.

• Automation

  API integrations

  A custom interface over GET and POST against a third party tool, for the bespoke sales, HR and marketing systems nobody sells off the shelf. The named ones have their own guides. See those.

• Automation

  Email marketing sync

  Signups landing in your email platform with the right tags, and a double opt-in that actually completes rather than stalling.

• Automation

  Slack and email alerts

  New leads arriving in the channel that should see them, formatted well enough that someone can act on them without opening anything else.

• Forms

  Multi-step forms

  A long form broken into steps, so you collect everything you need without losing people at the halfway point.

• Forms

  Conditional forms and surveys

  Questions that branch on the previous answer, so nobody reads a field that does not apply to them.

• Forms

  Form validation

  Supports the work

  Custom validation, error and success handling, instead of leaving people to guess what the browser meant.

• Forms

  Spam protection

  Honeypots, rate limiting and challenge handling, so the inbox stays worth checking every morning.

• Access control

  Membership portals

  Accounts, logins and gated content, with an auth provider holding the accounts and Webflow holding the pages. Courses, client portals and anything else that needs a door. One way to build it.

• Access control

  Gated downloads

  Content held behind a form, with the file released once the email is in and recorded where you can use it.

• Access control

  Location based content

  Content adapted to approximate location, read from the request rather than by asking the browser, so nobody gets a permission prompt for a headline. Precise location needs the visitor to agree to it, which is a different build and a different conversation.

• Access control

  Cookies and cache

  Supports the work

  Cookie and cache driven segmentation for conditional content, marketing triggers and front end classification.

• Access control

  Cookie consent

  A consent banner that genuinely gates the tags it claims to, rather than one that sets everything before you click.

• SEO

  SEO fundamentals

  Heading structure, media attributes and image and video optimization, so the crawl and the page speed both hold up.

• SEO

  Programmatic SEO

  The CMS used to publish a large set of optimized pages from one template, and a structure that does not collapse at volume.

• SEO

  Structured data

  Schema markup that makes the important facts on a page explicit to search engines and anything else reading the site. What it cannot do is decide how you get quoted.

• SEO

  Redirect mapping

  Every changed URL mapped to a deliberate destination before launch, so existing links and the signals attached to them are not discarded for nothing. How that runs on a migration.

• AI readiness

  Machine-readable site summary

  An llms.txt at the root of the site: what the business is and which pages are worth reading, written as Markdown, so a model gets the shape of the site rather than inferring it from forty pages. Mine is here.

• AI readiness

  Answer engine optimization

  Pages built to be quoted rather than paraphrased: the claim stated plainly, the facts behind it made explicit in markup, and a structure an assistant can attribute. What it cannot do is make anybody cite you.

• AI readiness

  Agent-callable actions

  The things the site can actually do, described as tools an agent could call, with every one of them pointing at an endpoint that responds rather than at a description of one.

• AI readiness

  Crawler access policy

  Supports the work

  A robots.txt that names the model crawlers rather than inheriting a default, so letting GPTBot, ClaudeBot and the rest read the site is a decision somebody made and can revisit.

• Analytics

  Analytics experiments

  Goals, events, triggers and tests configured on both sides: the scripting on Webflow and the setup inside your analytics platform.

• Analytics

  A/B testing

  Page level tests you can run quickly, so a question about conversion gets an answer from data rather than from the loudest person.

• Analytics

  Conversion rate optimization

  Measurement set up properly first, then the changes worth making, then the evidence that they worked.

• Analytics

  Accessibility review and remediation

  The agreed pages and flows checked against WCAG 2.2 AA: contrast, keyboard paths, headings that describe the page, forms usable without a mouse. The fixes get made rather than handed over as a spreadsheet. This is a review and the work that follows it, not a formal audit, and it does not produce a VPAT.

• Performance

  Core Web Vitals

  LCP, CLS and INP diagnosed against what the deployed site actually reports, then worked on in the order that moves them. Field data is the measure, which also means devices, networks and third-party scripts are part of the answer. What I measure.

• Performance

  Speed audits

  A full pass over what is slowing the site down, ranked by what actually moves the number rather than what is easiest to write up.

Nothing in that category yet. Try another one, or ask me directly.