Implementing partial submit capture alone could recover 15-20% of abandoned bookings, while embedded calendars could increase self-book rates from ~50% to 80%+ directly impacting client acquisition costs.
Capture 15-20% of abandoned bookings via partial form submission with SMS recovery while reordering intake sequences to prioritize contact capture.
Business Applications
HIGH Booking flow optimization (aias)Modify /webhooks/booking-page to capture partial submissions if user abandons mid-flow. Store incomplete leads in Supabase 'partial_leads' table with 15-min TTL for SMS recovery sequence.
HIGH Qualification sequence (aias)Restructure AIAS intake forms: Question 1 = Name, Question 2 = Phone, Question 3 = Email, Question 4+ = Qualifying questions (budget/timeline). Current order asks qualifying questions too early.
MEDIUM Confirmation page redesign (website)Rebuild TFWW/AIAS confirmation pages with embedded calendar (no redirect) and 2-part thank you video: 1 min 'what happens next' + 4 min 'why this matters'. Current 50s videos too short per this analysis.
LOW FAQ objection handling (website)Replace text FAQs on TFWW services page with 90-second Loom videos (micro-VSLs) addressing 'Will this work for my industry?' and 'Do I need technical skills?' β sell while answering.
Scott Kelly appears to be a growth operator/funnel specialist who critiques and optimizes high-ticket sales funnels, specifically in the real estate wholesaling niche (references 'Modest Mendez' and wholesaling model familiarity)
Hook: Positions himself as analyzing 'Mr. Mendez's' funnel as his 'greatest fear' then 'greatest blessing' β authority through critique
- Mobile optimization failure: Excessive space between top of page and headlines on mobile devices
- VSL lacks chapter markers β sophisticated audiences expect to skip to relevant sections
- Form friction: 'Get Started' button scrolls to a form only half a scroll down (unnecessary step)
- Form field order is wrong: Asking budget before collecting name/phone number
- Partial submit pixel: Capture lead data even if they abandon the form (goes to Slack/team for follow-up)
- Psychological sequencing: Ask what they want to achieve BEFORE budget (they'll state higher amounts)
- Calendar friction: Redirecting to separate Calendly page instead of embedding in Typeform causes auto-fill failure
- Page load speed bottleneck on cellular networks when redirecting between form and calendar
- Thank you video too short (50 seconds) β should be 5-6 minutes: first 1-2 min for next steps, last 4-5 min selling the importance of the call
- Missing product breakdown video/offer doc on thank you page
- FAQ structure wrong: Testimonials before FAQs, dropdowns hide 16-second videos instead of using 2+ minute micro-VSLs that sell while answering
“Either you let them skip around to the parts that they actually want to see, or they click off your landing page altogether”
“You get a partial submit so if they don't finish the application, it goes back to your Slack channel, your team anyways, for them to call”
“Psychologically, they'll put a higher amount we're willing to prior considering what they actually want to achieve”
“Page load speed is gonna be a bottleneck”
“Each of these videos should be at least two minutes. Basically micro-VSLs, not just here's the answer to your question”
What it is: A teardown of a call booking funnel for a high-ticket offer (real estate wholesaling), focusing on UX friction points that destroy conversion rates between landing page β form β calendar β thank you page
How it helps us: Directly applicable to AIAS booking flows and TFWW client funnels. We currently use /webhooks/booking-page and multi-step lead capture β we need to audit for mobile spacing, partial submit capture, and form field sequencing. The 'partial submit' insight is critical for our SMS-based qualification flows.
Limitations: Specific tools mentioned (Typeform, Calendly) don't match our stack (Express + Supabase + native CRM). However, the principles (embed vs. redirect, field order, partial capture) are universal. The 5-6 minute thank you video recommendation may be excessive for our audience β test required.
Who should see this: Dylan for funnel strategy, Dev for booking flow modifications (partial submit implementation), Sales team for qualification sequence restructuring
π€ [PLAUSIBLE] "Separate calendar pages cause 50% or less booking rates vs 80%+ with embedded calendars" — Friction theory supports this β every redirect and manual re-entry of data drops conversion. However, 50% vs 80% is a specific claim without cited data. Comments (@carter_hubbs 'Sauce π₯') suggest audience finds it valuable but don't confirm specific metrics.
Instead: A/B test embedded vs. redirect for our specific audience (local service businesses may tolerate more friction than real estate investors)
β οΈ [QUESTIONABLE] "Thank you video should be 5-6 minutes long (1-2 min logistics, 4-5 min selling importance)" — While post-booking reassurance is important, 6 minutes is long for a thank you page video in 2026 attention economy. Real estate wholesalers (his example) may need heavy convincing, but our TFWW clients (small business owners) may prefer brevity.
Instead: Test 60s version (pure logistics) vs 3-min version (logistics + value reinforcement) vs 6-min version. Measure show-up rates, not just views.
β
[SOLID] "Asking budget after goals psychologically increases stated budget" — Standard sales psychology (anchoring and aspiration). Getting them to state desired outcomes first makes them justify higher investment. No audience pushback on this in comments.
Instead: N/A β implement as suggested in qualification flows