When you’re running a direct-pay medical practice, every patient lead matters. There’s no insurance funnel doing the work for you. Every inquiry is someone actively deciding whether to pay out of pocket for your care. Lose track of one lead, and that’s real revenue walking out the door.
That’s exactly where this client was: a concierge medical practice in the US with a growing sales team and absolutely no system for managing leads.
The Situation
The practice was handling everything manually. Leads came in, someone wrote down the details, and the follow-up process lived entirely in people’s heads. There was no way to see which leads were brand new, which had been called, which needed a second touch, or which had gone cold.
Worse, leadership had zero visibility. They couldn’t tell how many calls the team was making, who was converting, or what the practice’s actual conversion rate looked like. And with multiple salespeople working the same lead pool, there was no structure to prevent overlap or dropped balls.
They’d looked at traditional CRMs, but the team wasn’t deeply technical. The tools they evaluated were either overbuilt for their needs or required a learning curve nobody had time for. They needed something their staff could actually use on day one.
The Approach
When the client reached out, they came with a detailed brief; they’d clearly thought through what they needed. That’s always a good sign. It tells me the problem is real and urgent, not theoretical.
I reviewed their requirements and within an hour, I’d mapped out the full system architecture in Whimsical and recorded a Loom walkthrough explaining my proposed structure. This is how I typically work. I don’t just quote a price. I show the client exactly what I’m planning to build and why, before they commit.
The architecture centered on three connected databases: a Leads database as the central hub, an Interactions log to capture every touchpoint, and a Sales Team database for individual performance tracking. Metrics and leaderboards sit on top of these as views, not as a separate database.
The key design decisions:
Make interaction logging frictionless. If logging a call takes more than 10 seconds, the sales team won’t do it. I built a one-click button that auto-creates a linked log entry, captures the timestamp and user, and only asks the employee to select an interaction type and add optional notes. That’s it. One click, two fields, done.
Route leads automatically based on status. Instead of expecting staff to check multiple lists, I designed filtered views that update themselves. Log a “Left Voicemail” interaction? That lead appears in the Follow-Up queue automatically. Mark it “Converted”? It moves to the Converted view. The staff’s workflow becomes: open your view, work your list, log your calls.
Build the metrics layer invisibly. The client wanted leaderboards and organizational stats, but the sales team doesn’t need to see the formula columns making that happen. I used hidden properties (labelled A1, A2, etc.) to run the calculations in the background, surfacing only the clean metrics on the dashboards.
Design for growth from day one. The client mentioned wanting web form automation in the future. Rather than building a quick-fix system now and rebuilding later, I structured the Leads database to accept entries from Notion forms, website forms, or third-party tools without any structural changes.
The Build
The final workspace included:
A Leads Database with full patient details, status tracking, and individual lead profile pages. Each profile shows every interaction logged against that lead, a complete history at a glance.
An Interactions Database where every call, voicemail, and email is recorded with the employee who made it, when, and the outcome. This feeds both the lead profiles and the performance metrics.
A CRM Dashboard with filtered views serving as the daily workflow for staff: Inbox for new leads, Follow-Up for leads needing another touch, and Resolved views for Converted, Failed, and Junk leads.
An Admin Dashboard giving leadership the bird’s-eye view: total leads, conversions, failure rates, conversion percentages, monthly trends, and per-employee breakdowns.
Personal Dashboards for each salesperson showing only their assigned leads, their call history, and their individual stats.
And a Leaderboard, because a little healthy competition between salespeople never hurts conversion rates.
The system was designed so multiple employees could interact with the same lead over its lifetime, with every interaction attributed to the person who made it. Employee A makes the first call, Employee B follows up; both touchpoints show in the lead’s history and both employees get credit in their individual stats.
The Result
The real test of a Notion workspace isn’t the delivery. It’s what happens in week two, when the client starts using it for real and wants to tweak things.
This client came back with exactly the kind of questions I love: “Can I add more status views myself?” and “If I add new interaction types, will it break the stats?” The answers were yes and no, because the system was built to be extended, not just used.
I recorded Loom walkthroughs for every question. When the client accidentally modified a formula column, I fixed it on camera and showed them exactly what happened and why. No additional charges, no paid support session. That’s included.
The workspace didn’t just solve their lead tracking problem. It gave them something they didn’t have before — data. For the first time, leadership could see actual numbers: how many leads came in this month, how many got converted, who on the team was performing, and where leads were falling through the cracks.
The Takeaway
If you’re running a small team and your lead tracking lives in spreadsheets, sticky notes, or people’s memories — you don’t need an overbuilt CRM with 50 features you’ll never touch. You need a system that matches how your team actually works, is simple enough to use on day one, and gives you the data you need to make decisions.
That’s what Notion does well when it’s built right. And “built right” is the key phrase, because a Notion workspace is only as good as the thinking behind its structure.