Our other projects
The brief was to improve the public instant quote experience so visitors could get a more useful project estimate without turning the Webflow page into a fragile custom-code island.
Basic Webflow calculators can show a number, but they often become hard to maintain when pricing logic changes, new input fields are added, or the same estimate logic needs to be reused in another funnel.
The calculator needed to work inside Webflow, support the existing field names, provide richer output for future redesigns, and keep a fallback estimate available if the Worker is unavailable.
SoFlow implemented a quote script that reads Webflow fields, calls the shared estimate API, and renders a structured estimate response. The same engine can support the general instant quote page and audit-derived quote pages.
The Webflow page supplies form inputs and display slots. The quote script collects the current values, sends them to the Cloudflare Worker quote API, and renders the returned range, timeline, confidence, breakdown, assumptions, and source status.
- Shared project estimate endpoint
- Compatible with existing Webflow field names
- Optional richer output fields for redesigns
- Fallback local estimate when the Worker is unavailable
- Reusable quote logic for public and audit-derived flows
The quote engine gives SoFlow a reusable lead tool that can explain scope earlier in the buying journey and connect estimates to audit results or consultation requests.
- Reads existing Webflow fields such as pages, services, animations, timeframe, SEO, legal, and booking
- Can render low, high, midpoint, timeline, confidence, and assumptions
- Supports a safer fallback when backend calls fail
Does the calculator give a fixed price?
No. It should be treated as a planning estimate. The final scope depends on content, integrations, timeline, migration risk, and implementation detail.
Why not keep all pricing logic inside Webflow custom code?
Centralizing the estimate engine makes it easier to reuse, test, and update the logic without editing every page where the calculator appears.
Can the same system support other calculators?
Yes. The same pattern can support migration estimators, maintenance plan selectors, audit-to-quote flows, or product recommendation tools.
This implementation proves that SoFlow can turn Webflow forms into reusable business tools by separating the public interface from the pricing and recommendation logic behind it.
Does the calculator give a fixed price?
No. It should be treated as a planning estimate. The final scope depends on content, integrations, timeline, migration risk, and implementation detail.
Why not keep all pricing logic inside Webflow custom code?
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Before the implementation, the estimate experience depended on page-level calculator behavior that was harder to reuse and evolve across multiple funnels.
After the implementation, estimate logic could be centralized in a Worker-backed engine while Webflow stayed responsible for layout, fields, and conversion design.
Simple page custom code can read fields and update a total, but it is not ideal when estimate logic should be shared across public quote pages, audit-derived quote pages, and future productized flows.
A backend endpoint gives SoFlow one place to evolve the estimate model without rewriting every Webflow page.
