Prepping for a call meant hunting through six systems, for every call, every day. Now the day arrives as one card per call, holding everything those six systems know.
/ The problem
Everything a salesperson needed before a call already existed. It was just scattered across six places: the booking tool, for what's booked, when it was made, and whether it's been moved; the intake form, for what the person said they wanted; the customer records, for which ad or channel brought them in; the calendar, for whether they've accepted the invite; the outreach log, for whether anyone has already been in touch; and the call recordings, for what was said last time, if this isn't their first call.
So prepping meant opening six things, doing the research by hand, then doing it again for the next call, and again for every call the next day. When the day is busy, that doesn't happen. Calls started cold, a name and a time and nothing else, while the answers the person had already typed out sat unread.
/ What we did
We built one page for each rep's day. It pulls from all six systems and lays out one card per call, in order: who's coming, how to reach them, and a link to join; whether they've accepted the calendar invite yet; which form they came through, and which ad or channel brought them; their own answers about timing, budget, and what they're trying to fix, all eleven of them, not a summary; what was discussed last time, if they've spoken to someone before; and a note when a call was booked at the last minute, or has already been moved once.
The whole day loads in about a second and a third. Before we split how it fetches things, it took closer to twelve seconds.
all 11 of their own answers on every card, not a summary
/ What changed
Nobody hunts through six systems before a call, and nobody does that research twice for the same person.
The answers people typed on the way in actually get read.
A last-minute or rescheduled booking is obvious at a glance, instead of a surprise on the call.
/ Decisions worth explaining
About one booking in four is made less than twelve hours before the call, so a page built in advance would be missing calls. But the answers barely change minute to minute, so those are prepared ahead of time and served instantly while quietly refreshing in the background. That split is the whole reason the page is fast and current at the same time.
Matching on how a form was worded missed every live entry form and pulled in eight retired duplicates instead. Matching on the naming convention picks up all seventeen live ones and nothing else.
A summary decides in advance what matters. The reps are the ones who know which detail is going to matter on their call.
A private log records each day's prep so it can be studied. It is never linked from the page reps actually use.