Tamar Levi-Ahdut ← All work

Case study 02 · Duda

Form Conditional
Logic

Smart forms that respond to every visitor differently.

Role
UX owner
Team
Duda’s Editor
Timeline
1.5 months (three sprints)
Conditional logicLogic 1IFOccupationis equal toStudentTHENShowStudent IDTell us about youWe'll tailor the next steps to you.Full nameDana LeviOccupationSelectStudentStudent IDe.g. 204518ContinueEmployeeStudentFreelancer

Why form? Why now?

Forms are where conversions happen

{{n1}}%of marketers rank forms as their top lead gen tool
~{{n2}}%completion boost from removing one field
{{n3}}%average form abandonment rate

Source: HubSpot · WPForms · Zuko Analytics

"The problem isn't the form. It's that every visitor sees the same one."

Form abandonment

Every field is a decision point - and a potential exit

* company name shown conditionally - only when visitor selects "Business"Source: Zuko Analytics benchmarking study · 93M+ sessions

Why we needed it

Every form field, shown to every visitor, every time.

  1. Fix a real conversion problemLong forms hurt completion rates, short forms generate unqualified leads. Conditional logic lets builders collect the right data without overwhelming visitors.
  2. 534 votes. Our most-requested feature.The top idea on Duda's board by a wide margin - a clear signal that users had hit this wall repeatedly.
  3. Even our direct competitors had moved onWix, Framer, and Webflow all offer at least basic conditional logic. Brizy offers none. Duda offered none. The gap was visible.
  4. Designed with AI in mindConditional logic is the foundation AI-powered forms will run on - we built it right so it could scale there

Research

Meet the form users

The Agency Designer

Alex · Builds 3-5 client sites per month

"My clients want smart forms. Right now I have to choose between clean and useful."

  • Builds the same form types repeatedly but can't make them smart
  • Clients complain about low-quality leads but blame the site, not the form
  • Has to create multiple form versions to simulate conditional behavior

The Business Owner

Sarah · Runs a boutique interior design studio

"I keep getting inquiries that aren't relevant to my business. The form doesn't filter anything."

  • Wastes time responding to unqualified leads
  • Can't tell Alex exactly what's wrong - just that "the form isn't working"
  • Losing trust in her website as a business tool

The End Client

Dan · Looking for a service provider

"Why am I being asked for my company name? I'm just a person looking for a service."

  • Abandons forms that feel generic or irrelevant
  • Loses trust when a form asks for information that doesn't apply to them
  • Never thinks about the form again - just moves on to a competitor

Based on user voice requests and agency partner interviews

Competitive landscape

FeatureWixFramerWebflowBrizyElementor
Show / Hide field✓✓✕✕Plugin
Enable / Require field✓✕✕✕Plugin
Skip step✕✓✕✕✕
And / Or logic✓✕✕✕Plugin

Competitive landscape · 2025

How others solved it

Typeform conditional logic UI
TypeformM size modal, the fields are colored and numbered (scannable)
Wix conditional logic UI
WixDashboard overlay, form preview
Monday (automations) conditional logic UI
Monday (automations)Sentence flow
Jotform conditional logic UI
JotformOld UI, but tight & clear
Jira (automations) conditional logic UI
Jira (automations)Many options, overwhelming

Key insights

Product decisions

Key insights

UX decisions

The solution

Project prioritization

  1. 1Logic entry point & architectureEstablish where logic lives in the editor - the structural decision everything else depends on.mvp
  2. 2Modal UI upliftRedesign the form content modal based on the architecture decision - build on a clean foundation before adding logic.mvp
  3. 3Google Sheets integrationForms are only useful if submissions go somewhere actionable. Before shipping logic, we ensured non-technical users could access their data instantly - no CRM, no setup, just a live spreadsheet.Quick win
  4. 4Show / Hide logicSingle condition per field type, single action. The most requested behavior - enough to unlock real use cases.mvp

Extended conditions, multi-step logic and more - scoped for future phases based on adoption.

1 · Architecture

Where should the logic live?

V1Existing modal
  • Logic buried among tabs
  • No dedicated focus

Poor hierarchy

V2New dedicated modal
  • Purpose built space
  • Clear entry point
  • Large Dev effort

Selected- main form

V3Floating bar icon
  • Small dev effort
  • Entry point not enough discoverable

Selected- nested elements

2 · Discoverability

Entry points

We used a dedicated modal, and later the floating bar button as a shortcut.

The form floating bar Settings button and a field-level logic button both lead into the Advanced form modal, to Settings and to Logics

3 · Modal UI uplift

A foundation worth building on

Designed by me, grounded in Duda's system.

Before: the old Advanced Form panel with Content, Settings and Integrations tabs After: the Manage form modal with Settings, Logic and Integrations, and an empty state for adding the first conditional logic rule

3 · Modal UI uplift

Integrations uplift

Integrations list now aligned to industry standards

Before: the old Contact Form Content integrations list After: Manage form integrations as a grid of app cards: Zapier, Google Sheets, MailChimp, ActiveCampaign, HubSpot, Albato

4 · Quick win

Google sheets integration addition

The quickest path from form to spreadsheet

Form conditional logic full flow

5 · Error handling

Edge cases

What happens when user deleted a logic related field?

The form floating bar Settings button and a field-level logic button both lead into the Advanced form modal, to Settings and to Logics
Before: the old Advanced Form panel with Content, Settings and Integrations tabs After: the Manage form modal with Settings, Logic and Integrations, and an empty state for adding the first conditional logic rule

Before: the old Contact Form Content integrations list After: Manage form integrations as a grid of app cards: Zapier, Google Sheets, MailChimp, ActiveCampaign, HubSpot, Albato

Reflections

What I'd have shipped

I left before handover. Next, I'd invest in onboarding and progressive disclosure - power only matters when users feel confident.

  1. 1Simplify onboarding
  2. 2Reduce complexity for single-step forms
  3. 3Improve information hierarchy
1223

A fluid starting point

AI scans your form fields and offers ready-to-use rule suggestions - no configuration needed to get started.

Design constraints

  • Scoped to existing logic capabilities
  • Field naming quality affects suggestion quality
  • Trust is fragile - one miss matters
Mockup was made with Claude Design
Next case study · 01 The Dynamic Repeater →

Let’s talk

Tamar Levi-AhdutPortfolio2026