BookFront
Solo · 2026A better front door for client calls
- Booking flow
- 5 stepsQualify through prep brief
- Fit scoring
- DeterministicTraceable and testable today
- Security posture
- CSPSelf-locked with XSS-safe rendering
Overview
A booking workflow that qualifies visitors, collects context, supports payment, and prepares a brief before a call is confirmed.
What I built
- →Full pre-call flow: qualify → intake → pay → book → prep brief
- →Deterministic qualification behind a replaceable scoring interface
- →Optional payment and a structured prep brief before confirmation
- →DOM rendered without innerHTML and a content security policy restricted to the app
- →Warm-editorial design system on Tailwind v4 tokens
Key product decision
Keep qualification behind a replaceable contract so the booking flow can be tested independently from the scoring implementation.
Case study notes
Context
A calendar link hands strangers your availability and hopes for the best — it never asks who's booking, what they need, whether they're a fit, or what you should prep. Creators burn time on bad-fit calls.
Implementation
I separated qualification from scheduling, defined a structured intake, and kept scoring deterministic behind a small interface. That makes the complete booking path testable before changing how a fit result is produced.
Current state
The interactive landing page and complete booking demo are live at bookfront-nine.vercel.app. Accounts, persistence, and payment infrastructure remain active development work.
Source is private — want a walkthrough or a deeper look? Email me.