# Psychology Brief: Demo Booking Drop — April 13, 2026

**Prepared for:** Growth Team Sync (2:00 PM PT)
**Context:** v2.14.0 shipped Apr 11. Trial signups up ~54% (196 → 302/day). Demo bookings down ~39% (67 → 41/day). Trial-to-demo rate collapsed from 34.2% → 13.7%.

---

## Diagnosis: What's Happening Behaviorally

The old booking flow was a **low-friction, low-cognitive-load** Calendly embed (3 fields, calendar visible immediately). The new flow introduces:

- **5 additional form fields** (8 total), including a sensitive "budget range" question
- **~3 screens of content** (feature cards, testimonials, FAQ) placed *above* the calendar
- Calendar pushed **below the fold** on most screens

Hotjar confirms the damage path:
- 72% of visitors never scroll to the calendar
- Form abandonment jumped 19% → 61%
- Drop-off spikes at "budget range" (field 6)
- Time on page up 68% (28s → 47s) — not engagement, but confusion/hesitation

**In short:** We traded a 30-second booking action for a mini sales pitch + interrogation. Users who were ready to book now encounter enough friction to abandon.

---

## Top Psychological Models (Scored via PLFS)

### 1. Cognitive Load Theory

**PLFS: `+14`** (High-confidence lever)

| Factor | Score |
|---|---|
| Leverage | 5 |
| Fit | 5 |
| Speed | 5 |
| Ethics | 5 |
| Implementation Cost | 1 |

- **Why it works:** Working memory can hold ~4 chunks. An 8-field form + testimonials + FAQ + feature cards overwhelms processing capacity. Users default to *leaving* rather than *continuing*.
- **Behavior targeted:** `/book-demo` completion (visitor → booked demo)
- **Where to apply:** Booking page form and page structure
- **How to implement:**
  1. Cut form to 3–4 fields max on initial screen (name, email, company, role)
  2. Move remaining qualification fields to a *post-booking* follow-up email or pre-demo Typeform
  3. Move calendar back above the fold
- **What to test:** 3-field vs 4-field vs current 8-field form
- **Ethical guardrail:** Transparent about why additional info will be collected later. No bait-and-switch.

---

### 2. Paradox of Choice / Hick's Law

**PLFS: `+13`** (High-confidence lever)

| Factor | Score |
|---|---|
| Leverage | 5 |
| Fit | 5 |
| Speed | 4 |
| Ethics | 5 |
| Implementation Cost | 1 |

- **Why it works:** The page now presents multiple competing actions — read testimonials, browse FAQ, fill 8 fields, pick a time. Each additional element increases decision time logarithmically (Hick's Law) and increases choice avoidance (Paradox of Choice).
- **Behavior targeted:** Scroll-to-calendar rate (currently 28%)
- **Where to apply:** Page layout — strip to single clear action path
- **How to implement:**
  1. Remove or collapse FAQ and testimonial sections (move to pricing page where they aid *consideration*, not *action*)
  2. Single visible CTA path: short form → calendar → confirm
- **What to test:** Minimal page (form + calendar only) vs current page
- **Ethical guardrail:** Social proof is fine on consideration pages; removing it from the booking page respects users who've already decided.

---

### 3. Loss Aversion + Commitment Escalation

**PLFS: `+11`** (Strong)

| Factor | Score |
|---|---|
| Leverage | 4 |
| Fit | 4 |
| Speed | 4 |
| Ethics | 4 |
| Implementation Cost | 1 |

- **Why it works:** Asking for "budget range" and "timeline" before a user has received any value triggers loss aversion — *"I'm giving away negotiating leverage before I've even seen the product."* This is the #1 drop-off field per Hotjar.
- **Behavior targeted:** Form field 6–8 completion
- **Where to apply:** Budget range and timeline fields specifically
- **How to implement:**
  1. Remove budget/timeline from pre-booking form entirely
  2. If sales needs this data, collect it via a brief pre-demo questionnaire sent after booking confirmation (when commitment is already made and sunk-cost works *for* us)
- **What to test:** With vs without sensitive fields; pre-booking vs post-booking collection
- **Ethical guardrail:** Never hide that sales will discuss budget. Frame post-booking survey as "help us prepare a relevant demo for you."

---

### 4. Status-Quo Bias

**PLFS: `+10`** (Strong)

| Factor | Score |
|---|---|
| Leverage | 4 |
| Fit | 4 |
| Speed | 4 |
| Ethics | 5 |
| Implementation Cost | 2 |

- **Why it works:** Users who'd seen the old Calendly flow (including returning visitors and word-of-mouth referrals) now face a completely different experience. The disruption violates expectations, and the default response to unexpected friction is *abort*.
- **Behavior targeted:** Returning visitor booking rate
- **Where to apply:** Overall flow familiarity
- **How to implement:**
  1. Restore a Calendly-like simplicity as the default experience
  2. If qualification is needed, introduce it *progressively* over time — not all at once
- **What to test:** Segment new vs returning visitors in the A/B test to isolate this effect
- **Ethical guardrail:** None needed — reducing friction is pro-user.

---

## Recommended Action Plan for Today's Decision

### Immediate (this week)
| Action | Owner | Rationale |
|---|---|---|
| **A/B test: old-style minimal form + above-fold calendar vs current page** | @jlee / @agarcia | Fastest path to signal. Use current 100% traffic as control, redirect 50% to lightweight variant. |
| **Move budget/timeline fields to post-booking email** | @mchen / @sales-ops | Unblocks the #1 abandonment point without losing the data sales needs. |

### Short-term (next sprint)
| Action | Owner | Rationale |
|---|---|---|
| Move testimonials & FAQ to pricing page | @mchen | Social proof helps *consideration*, not *action*. Put it where it matters. |
| Progressive qualification: collect extra fields in pre-demo email (post-booking) | @sales-ops | Preserves lead quality goal with zero booking friction. |

### Do NOT do
- ❌ Full revert without testing — we'd lose the chance to learn which specific elements hurt
- ❌ Add *more* social proof to overcome friction — it's additive load, not a counterweight
- ❌ Make fields optional but visible — optional fields still create cognitive load (users deliberate on whether to fill them)

---

## The Core Tradeoff

**Sales wanted richer lead data → added friction. Growth wanted more volume → reduced friction elsewhere. These goals collided on the same page.**

The fix isn't to choose one side. It's to **sequence the asks**: get the booking first (low friction), then qualify the lead second (post-commitment). Behavioral science strongly predicts that once someone commits to an action (booking), they'll comply with reasonable follow-up requests (commitment & consistency principle).

---

*Models scored using PLFS framework. Brief limited to top 4 models per selection rules. All recommendations pass ethical guardrails — no dark patterns, no hidden defaults, no false urgency.*