How Bookingbird uses Overwise.
Booking software for padel courts. The founder built Overwise as much for himself as for anyone else — Bookingbird is customer #1, dogfooded weekly. The workflow shipped to other customers is the workflow he uses Monday morning.
The challenge
Bookingbird sells booking software to padel courts. The buyer is a family-run business operator, not a LinkedIn-active founder — Apollo's contact database has close to zero coverage of the segment. Without a usable list, the best cold-email tool in the world is useless. The team had spent weeks on manual Google Maps scraping and address-by-address lookup before deciding the bottleneck was the list itself, not the outreach copy.
The approach
Three absence-signal probes configured for the padel-court ICP — no online booking widget, no live chat, no payment integration on the website. Two weeks of Discovery-only mode first, to compare the surfaced leads against the manual scraping baseline. Once the quality matched, the agent switched to autopilot with brand-voice extracted from the founder's own sent folder. Per-lead reasoning was the trust unlock — the founder could open any lead in the timeline view and see exactly which absence signal triggered it, which website paragraph the draft cited, and why the agent picked email over a manual outreach task.
The result
The list problem went away. Padel-court owners reply because the message references their actual website — the specific page that's missing a booking widget — rather than a LinkedIn job title. The founder reads the AI Inbox once a day for AI-drafted reply approvals, hot-lead handoffs, and the occasional verification-failed escalation. The rest of the loop runs itself. Bookingbird is still customer #1, which means the workflow that doesn't work for the founder doesn't ship to anyone else.
Apollo had founders. Overwise had the actual padel-court owners I needed to talk to. The only outbound tool that found leads we couldn't find anywhere else.