ICP-qualified enquiries from the site rose by 23% thanks to a personalized interactive flow
The existing Webflow site needed an interactive questionnaire integrated into it. The user goes through a sequence of multiple-choice questions and, on the final step, receives a result with tailored recommendations. Questions, answer options, and scoring logic live in an external service exposed via API. For the visitor, it feels like a native part of the site — no redirects, no page reloads, no third-party UI elements.
Shiksha is the Founder & CEO of Think ABM, based in London. Her company generates leads through content and educational materials: she runs an expert blog and webinars, marketing drives traffic to landing pages and articles, and sales converts those leads into consultations. Site traffic was growing — but so was the volume of low-quality enquiries. A meaningful share of visitors didn't fit the ICP, and the team was wasting hours explaining basics and filtering random submissions instead of working with warm leads.
Webflow platform limitations
There was already an established structure to fit a complex interactive component into, within what the platform allows.
Fixed external API contract
The API was built by another team and its contract was set in advance, so our integration had to fit a finished interface, without the ability to influence it.
Unified UX
The questionnaire had to feel like an organic part of the site, with no external windows and without feeling redirected to an external service.
Stability
Site editors update Webflow pages regularly, so the integration couldn't fall apart every time text or surrounding blocks changed.
We built the questionnaire as an embedded frontend component inside Webflow that owns the UX and step management, while all business logic (questions, scoring, segmentation, result) stays on the external API side. We split responsibility between frontend and API this way so marketing could keep updating Webflow content fast, and the questionnaire stayed stable and controllable through a minimal set of "anchors" on the page.
Discovery and API contract
We validated the API against a real scenario: how a session opens, how questions come back, what counts as a valid answer, by what logic the result is formed. Separately we designed the rules for error handling and timeouts.
On-page UX flow
We designed the flow to feel like a native block. Static copy, headings, and styling stayed in Webflow; the dynamics (questions, options, states) rendered through the component. We planned button behavior, loading states, back navigation, and resume functionality so the user always understood where they were and what to do next.
Component and state management
We built a component that mounts into a specific page block and handles the full user journey, from start to result. We anticipated double-click protection, locked actions during pending requests, and graceful UX recovery when the API returned non-standard responses.
API integration and fallback paths
We built the integration so that at every critical point users always receive clear feedback and next steps. We anticipated the need to put guardrails on the potentially fragile spots.
Completion analytics
We implemented tracking for the key events: start, intermediate steps, drop-off, and completion with a result. That let marketing see exactly where users fall off, which segments complete most often, and how the questionnaire moves enquiry conversion.
Rules for the content team
We locked in the need for a short rule set for editors with a clear list of what's safe to edit in Webflow and protected script anchors that must not be modified.
At the first call the marketing lead described the core problem: plenty of leads, but their quality was off and team hours were going nowhere. Within half an hour we defined the key success metrics — ICP-qualified enquiries, completion rate, drop-off points — and pinned the hard constraints: no migration off Webflow, no redirects, no high-touch maintenance.
+1 Resource
Across the first 6 weeks after launch, the share of ICP-qualified enquiries rose by 23%, questionnaire completion climbed 14%, and irrelevant sales enquiries fell 28%.
in the first 6 weeks, driven by questionnaire-based segmentation
on the questionnaire — from 40% to 54%
reaching sales, because part of the audience self-filters during the questionnaire
sales spends on initial qualification, since segment and context land with the lead
from result screen to target action, since recommendations are tied to the user's own answers
thanks to the editor rule set
Or send us a message and we'll get back to you within 15 minutes during business hours