Gemin
Get in touch

Webflow for B2B SaaS

Let marketing ship without waiting on engineering. Your product team should not be spending Thursday fixing a pricing page. I build Webflow sites that give SaaS marketing teams control of the website while keeping the CRM, analytics, experiments and product handoffs working behind it.

Start a project

Built for Unify, UserGems, Collage and ProductPlan.

What these builds involve

What these sites need, and what we figure out first.

What these sites need

  • Programmatic pages for feature, comparison and use-case sets built from one collection
  • Trust content a procurement committee asks for, not just the pages a champion reads
  • Forms that reach the CRM with the campaign attribution intact
  • Product analytics on the marketing site, so pre-signup behavior joins the funnel
  • A component system the growth team can assemble pages from without a developer
  • Docs, changelog and careers kept on the marketing domain rather than a subdomain

What we figure out first

  • Where the marketing site stops and the product starts. The boundary decides what belongs in Webflow and what stays in the app. It is usually further into Webflow than teams expect, and pulling it back later is expensive.
  • Which system owns the lead. HubSpot, Salesforce or Pipedrive as the destination changes what the form does, how attribution is carried and what happens when a write fails.
  • Whether the comparison pages are a set or a handful. Four pages are four pages. Forty are a collection, a template and a decision about which competitor names you are willing to publish.
  • Who edits, and how often. A team shipping weekly needs a different component system from one shipping quarterly. Building for the wrong cadence is how a site ends up needing a developer again.

SaaS sites tend to grow in predictable directions: more features, more use cases, more integrations, more competitors and more campaigns.

I build the structure for that growth upfront.

Feature, integration, comparison and use-case pages become reusable CMS systems instead of dozens of individually maintained pages. Landing pages are assembled from a consistent component system. Forms carry the right attribution into your CRM. Marketing events connect cleanly to the analytics stack you already use.

The goal is simple: your team should be able to launch the next page without rebuilding the site around it.

Keep your engineers on the product

Where the line usually falls

Webflow

The marketing site

  • Pages, and the components behind them
  • The CMS, and who can publish to it
  • SEO and the structural work under it
  • Experiments on the marketing pages

The handoff

Signup, and what follows

  • Form to record
  • Campaign attribution
  • Analytics events
  • Route into auth

Your product

The application

  • Login and account data
  • Billing, plans and entitlements
  • Provisioning
  • Anything reading live data
The pitch for Webflow here is not that it is cheaper. It is that the marketing site stops competing with the product for engineering time. The middle is the only part that needs both teams, and it is smaller than either of them expects.

The pages worth turning into systems

Integrations. One CMS structure for every tool your product connects with.

Comparisons. Consistent pages for the competitors buyers are already evaluating.

Alternatives. Pages for buyers actively looking to replace another product.

Use cases and industries. A scalable way to speak to different jobs, teams and markets without creating another one-off page every time.

The integrations matter as much as the pages

A beautiful demo form is useless if the submission never reaches Salesforce.

I test the entire path: form submission, CRM record, attribution, analytics event and failure state.

I have worked with stacks involving HubSpot, Salesforce, Pipedrive, Segment, Amplitude, Statsig, GTM and other tools sitting behind modern SaaS marketing sites.

Built to be operated without me

The finished site should not become another developer dependency.

Components stay consistent. CMS structures are understandable. Custom code is used when it earns its place, not because I can write it.

Your team should be able to handle everyday publishing themselves and bring me in for the things that actually need a developer.

If your growth team is currently filing tickets to change a headline, that is the thing worth fixing first, and it is usually a smaller job than a redesign.

What it connects to

The stack these sites usually run on.

And what they are usually moving off

Before you ask

Questions I get asked about B2B SaaS.

Can our marketing team publish without waiting on engineering?

Yes, and that is usually why the site moved to Webflow. Pages, posts, case studies and campaign pages are CMS content with the Editor scoped to them, so the people who write the copy publish it. If your team still files tickets to change a headline, something was built wrong.

How do you handle programmatic or templated pages?

As a collection with one template, which is what Webflow is genuinely good at. Adding the fortieth page costs what the second did. The decision worth making early is what the collection actually is, because restructuring it later means redoing the URLs.

Will moving to Webflow hurt our search rankings?

The honest answer is that search equity can be protected and a position cannot be promised by anybody. What is in my control: every existing URL mapped and 301'd before launch, the pages earning your traffic rebuilt first, and a dip in the first weeks treated as normal while the new addresses are recrawled. Rankings lost in a migration are lost to redirects nobody wrote, not to the platform.

Can you connect the site to HubSpot, Salesforce, or Segment?

Yes, and attribution matters more than the connection. A form that reaches your CRM without the campaign, source and page it came from is worse than no integration, because the data looks real. I wire it so the record lands complete and the event names match what your data team expects.

What happens when we outgrow Webflow's CMS limits?

Worth knowing the ceiling before you build against it rather than after an import fails. Collection and item caps are real and not raisable by asking. Most B2B sites never come close; a large resource library can. If yours is heading that way I will say so up front.

Does Webflow itself cost money on top of what I charge?

Yes, and you pay Webflow directly rather than through me. A site plan for hosting and a workspace seat for building, with the tier depending mostly on CMS content and how many people need access. I will tell you which plan you actually need, not the easiest one to recommend.

Do you write custom code, or only what the Designer can do?

Both, and knowing where the line is matters more than either. Custom CSS and JavaScript, GSAP, Lottie where it earns its file size, API work behind forms. The restraint is deliberate: every piece of custom code is something your team cannot change without me.

I already have a site and it needs work. Can you improve it rather than rebuild?

Often, and I will say which before you commit to either. Abandoned projects and class lists nobody can safely touch are normal. Sometimes the fix is three specific things; sometimes the structure underneath makes a rebuild cheaper than the repair. You get the honest read either way.

Can our in-house team take over afterwards?

Yes, and the site is built for that rather than against it. Consistent classes, a component system documented by being obvious, no clever dependency only I understand. A retainer should be something you keep because it is useful, not something you cannot leave.

Do you work with us continuously or just build and leave?

Most of my SaaS work is ongoing, because a marketing site is never finished. It runs as a monthly retainer, one request at a time, cancel any month. The rates are published and the same for everyone.

Other industries

Building something else?

Reach out and see if we are a good fit.

Start a conversation

Currently booking two to four weeks out.