Does Webflow have a CRM? The straight answer and what to use

What Webflow does with a lead today

Forms are one of Webflow's strengths. You can design a form to match the rest of the site exactly. When someone fills it in on a hosted Webflow site, three things can happen: the submission is saved in the site's form list, an email notification goes to whoever you set in that form's settings, and the data can be passed on to an app, an automation tool or a webhook.

At the time of writing (October 2026), both of Webflow's paid site plans include unlimited form submissions: Basic costs $15 a month and Premium $25 a month on annual billing. The free Starter plan caps a site at 50. You can read submissions in the dashboard and download them as a CSV file for a spreadsheet.

What you do not get is anything that happens after the enquiry arrives:

• A contact record that groups every enquiry, email and order from the same person
• Pipeline stages (new, quoted, won, lost) with deal values
• Tasks and reminders, so nobody forgets to call back
• Automatic follow-up emails or texts
• Quotes, invoices and payment chasing
• Reports on where leads came from and how many became customers

Webflow used to have a light automation tool called Logic that could send form data elsewhere. Webflow retired it on 27 June 2025, turned the forms that used it back into standard forms, and pointed people to Zapier and Make. So today every route from a Webflow form to a CRM runs through an app, an embedded form or a third-party automation tool.

Do you actually need a CRM yet?

Be honest with yourself here. If you get three or four enquiries a week and one person answers all of them the same day, Webflow's email notifications and a tidy inbox may be enough. A CRM you never open is just another monthly bill.

You have outgrown the inbox when two or more of these are true:

• More than one person replies to enquiries, and leads have been answered twice or not at all
• Deals take more than one conversation to close (quotes, consultations, proposals)
• You cannot say how many enquiries came in last month, or how many turned into paying work
• You chase unpaid invoices from memory
• Past customers get in touch again and you have no record of what they bought

Three ways to connect Webflow to a CRM

1. A native app or integration. HubSpot's integration lets you pick your Webflow forms and map each field to a HubSpot contact property, so every submission creates or updates a contact. Attio has its own Webflow app, available on every Attio plan, which uses new submissions as a trigger for Attio workflows. This is the cleanest route: no extra subscription and fewer moving parts. The catch is that you can only do what the app supports. Integration guides warn that unusual field types can be fussy, and that copied forms sharing the same name can break the mapping.

2. Embed the CRM's own form. You can paste a HubSpot form straight into a Webflow page, and Pipedrive's web forms, which come with its LeadBooster add-on, can be embedded the same way. Data goes straight into the CRM with nothing in between. The trade-off is design: the CRM styles the form, not Webflow, and that kind of design control is often why people chose Webflow in the first place.

3. Zapier, Make or a webhook. A Zapier Zap or a Make scenario watches for new Webflow form submissions and creates a contact, deal or task in almost any CRM. This is the most flexible route and the usual one for CRMs without a Webflow app. It also needs the most care, because three systems (Webflow, the automation tool and the CRM) now have to keep working together. Developers can skip the middleman and use Webflow's form submission webhook to send data to their own code, but then someone has to maintain that code.

What it costs per site

Here are typical setups for one small business site, using list prices on annual billing at the time of writing (October 2026), in US dollars. CRM prices are per seat (per user), and we have assumed two people use the CRM.

A few things the table does not show:

• HubSpot often runs introductory discounts on Starter, so the first year may cost less. Budget for the list price.
• Zapier counts a task every time an action runs. A Zap that creates a contact and then a deal uses two tasks per enquiry, and spam submissions count too. Zapier's free plan gives 100 tasks a month and only two-step Zaps.
• Make is usually cheaper at volume. Its free plan includes 1,000 credits a month, and its paid plans cost far less than Zapier's for the same number of runs, although the editor takes a little longer to learn.
• Pipedrive's own web forms come with the LeadBooster add-on, which is why the table uses Zapier for Pipedrive.
• If the business sells online, Webflow's Ecommerce plans replace the site plans above. They start at $29 a month, and the entry Standard plan adds a 2% transaction fee.
• The WebNewBiz figure is the monthly rate. Yearly billing is cheaper.

The money is rarely the hard part. Webflow Basic with a free CRM is about as cheap as a professional setup gets. The real cost is keeping it working.

The hidden cost: keeping the connection alive

The link between Webflow and a CRM is a small piece of plumbing, and plumbing fails quietly. A lead that never reaches the CRM does not set off an alarm. You find out weeks later when a customer mentions that nobody called back.

The common ways it breaks:

• Someone renames a form field or adds a new one, and the mapping no longer matches
• A form is duplicated for a new landing page and keeps the old name, so submissions go to the wrong place or arrive twice
• The person who authorised the connection leaves, and their login is removed
• The automation account hits its monthly limit, often because of spam
• A vendor changes or retires a feature, as Webflow did with Logic

A short monthly routine prevents most of this:

1. Send a test enquiry through every live form and check it reaches the CRM with every field in the right place
2. Look at the automation tool's error log and how much of the monthly allowance has been used
3. Make sure each connection belongs to a shared business account, not one person's login
4. Keep Webflow's own email notification switched on as a backup, so no lead depends on a single path
5. Keep a simple list of every form, where it sends data and who owns each login

For one site this is a quick check. For an agency with 30 client sites it is real work, and it belongs in the monthly care plan rather than being done for free.

Which pairings suit agencies with many Webflow clients

Agencies have a different problem: not only which CRM to pick, but how to run the same setup 10, 20 or 50 times without it turning into a support queue.

A few rules that save agencies trouble later:

• Let the client own the CRM and automation accounts, with your agency invited as a user. Running every client's Zaps from one agency account creates a single point of failure, a confusing bill and a painful handover if a client leaves.
• Standardise. Use the same form names, field names and mappings on every site, so a fix on one can be copied to all.
• Charge for monitoring. Put the monthly routine above into your care plan.
• Consider one platform. If clients want their website and leads behind one login with your brand on it, a white-label platform may be less work than wiring Webflow to a CRM for each client. Our guide to white-label CRM for agencies compares the options, and Webflow alternatives for agencies covers what you gain and give up by moving.

When an all-in-one builder is simpler

The reason to join separate tools is that you get the best of each. The reason not to is that every join is one more thing to maintain. For a small business that wants a decent website and a reliable list of leads, a builder with a CRM inside removes the join entirely.

That is the approach WebNewBiz takes. On the Growth plan ($79 a month after a $1 first month) and above, website enquiries land in the AI CRM automatically, and store buyers become contacts. The CRM reads and scores leads, tracks deals, tasks and bookings, and sends invoices that chase themselves. Workflow automations run on triggers such as a form submission or a scheduled date, and opt-ins from the built-in funnel builder land in the CRM too. From Pro ($149) you also get email campaigns and social media posting, covered on our marketing automation page.

The honest limits:

• It is a young platform with a much smaller app ecosystem and community than Webflow, Wix or Shopify
• Design control is nowhere near Webflow's. You change the site by chatting with the AI Copilot or, from Starter up, in the Design Studio visual editor, but you will not get Webflow's depth of layout and animation control
• The CRM starts at Growth, which costs more than Webflow Basic with a free HubSpot account
• There is no free plan
• The AI's first draft still needs your own photos, facts and edits
• A site cannot be exported as files to another host. Content and domain move, but the layout has to be rebuilt

If you are comparing other builders, we have answered the same question for whether Wix has a CRM and whether Squarespace has one.

When Webflow's design control is worth keeping

Keep Webflow and add a CRM when:

• The brand depends on distinctive design, custom animation or a complex CMS structure that a template-led builder cannot match
• Your designers know Webflow well and would lose time learning a new tool
• The sales team already works in HubSpot, Pipedrive or another CRM, so the website only has to feed it
• The site is mainly for marketing and a separate sales process handles the leads

An all-in-one is likely the better fit when:

• One or two people run the business and nobody wants to look after integrations
• You want the website, store, CRM and invoices in one login and one bill
• Leads are going missing between tools today
• You are an agency selling straightforward sites to small businesses that care more about leads than animation

Neither answer is wrong. Webflow with HubSpot is a strong combination as long as someone looks after it.

Quick answers

Does Webflow have a built-in CRM?

No. Webflow stores form submissions and sends email notifications, but it has no contact records, pipelines, tasks or invoicing. To manage leads you connect a separate CRM such as HubSpot, Pipedrive or Attio.

How do I send Webflow form submissions to HubSpot?

Use HubSpot's integration to map each Webflow form field to a HubSpot contact property, embed a HubSpot form on the page, or use Zapier or Make to create or update contacts when a form is submitted.

What replaced Webflow Logic?

Webflow retired Logic on 27 June 2025. Forms that used it became standard Webflow forms, and Webflow recommends Zapier or Make for automations.

What is the cheapest way to add a CRM to Webflow?

At the time of writing (October 2026), Webflow Basic at $15 a month on annual billing plus HubSpot's free CRM (up to 2 users) or Attio's free plan (up to 3 seats), connected through their own integrations, costs about $15 a month in total.

Does Webflow limit form submissions?

At the time of writing, the paid Basic and Premium site plans include unlimited form submissions. The free Starter plan allows 50 per site.

Is an all-in-one builder better than Webflow plus a CRM?

It is simpler, not always better. Keep Webflow if design control matters most or your team already uses a CRM. An all-in-one such as WebNewBiz, with its CRM from the $79 Growth plan, suits businesses that want leads in one place without connectors to maintain.

If you want to try the all-in-one route

If you would rather skip the plumbing, our AI website builder drafts a full site from a short description of your business, and from Growth up every enquiry goes straight into the CRM. You can start for $1 for the first month and cancel any time. To see a design before you sign up, the free AI Website Preview designs a homepage from one sentence. Agencies that want to resell sites and CRM under their own brand can talk to us about white-label.