He spent decades as a social dance professional, teaching, organizing events, and building community around the world. Along the way he saw the same problem again and again: the instructors and organizers who keep dance culture alive are also, by necessity, small business owners, and the business side often runs on duct tape. DMs, spreadsheets, cash boxes, last minute venue changes. So he set out to build a piece of software specifically for people like him, a platform meant to give social dance professionals the tools to run their businesses with less chaos and less stress. As the founder of that platform, he was now facing the exact challenge his own product was meant to solve, just at a bigger scale.

The Problem

Before the CRM work began, the booking experience for anyone requesting a demo of the platform was inconsistent and largely manual. There was no clear structure for how a prospective customer would move from filling out a form to actually landing a meeting on the calendar. Meeting durations, buffer times, and scheduling windows had never been formally set. Reminder emails did not exist in any dependable way, which meant demo requests and confirmations depended on someone remembering to follow up by hand.

That created a deeper frustration. Every prospect who requested a demo and never got a reminder, and every lead who said "follow up with me in two weeks" and then got forgotten, represented a real opportunity slipping away quietly in the background. For a growing platform trying to build trust with the very community it was designed to serve, that inconsistency carried real weight. A placeholder privacy policy page and a demo request form built without much intention were small details, but they chipped away at the professional first impression a new software company needs to make. And because the founder relied on more than one calendar tool to manage his own schedule, there was a genuine worry about double booking prospects who were excited to see the product.

Underneath all of it sat a bigger concern. As the platform grew, so would the number of demo requests, follow ups, and customer records. Without a clean, well organized system underneath, that growth would just mean more chaos, not less, which was the exact opposite of what the company existed to prevent for its own customers.

Meeting the Guide

I came into this project as his CRM consultant. My role was not to be the hero of this story. It was to bring both technical expertise and genuine empathy for what it feels like to run a growing business without the right systems in place. I understood that every workflow I built needed to feel calm and dependable, because that same feeling was exactly what his platform promised its own customers.

The Plan and the Features

I started by building a dedicated demo request calendar, organized inside a clear folder structure so it would always be easy to find. I set the meeting duration and interval to thirty minutes, added buffer time so back to back demos would not overlap, and configured the calendar to connect to his preferred video conferencing tool so every meeting had a reliable link attached automatically.

To make the booking flow feel intentional rather than accidental, I built a short intake form that captures first name, last name, email, and business type before a prospect ever sees the calendar, with an optional comments field so he walks into each demo already knowing what the person cares about. Once a meeting is booked, an automated internal notification alerts the team, an email confirmation goes to the prospect with the meeting details, and reminder emails go out one day before and again fifteen minutes before the call, all with editable wording so the tone always matches his voice.

Because he manages his availability across more than one calendar tool, I set up conflict calendar checking so that every booking source references the same underlying availability, which closes the door on accidental double bookings.

For everything that happens after the demo, I built a follow up email snippet so that once a prospect is marked as having shown up to the call, sending a warm, consistent follow up takes seconds instead of starting from a blank page. Paired with that, I built a nurture workflow that lets him set a specific follow up date based on what the prospect actually told him, for example "check back with me in two weeks." The system automatically tags and enrolls that contact and reaches out on exactly the date promised, so no opportunity is left to memory alone.

I also gave every custom workflow a clear naming convention, separate from the platform's default template workflows, so the team can find and understand any automation at a glance rather than guessing what each one does. I added trigger links with tracking so he can see who actually clicked through to book, which turns booking activity into real data rather than a guess. And when a notification link started failing due to a domain verification issue, I diagnosed the root cause down to the DNS configuration and flagged exactly what access was needed to fix it, rather than leaving it as a mystery.

Finally, because his account had inherited a large number of default fields and workflows from the platform's underlying template, many with unclear internal names, I went through them methodically, checking which were still referenced by active workflows and which served no current purpose. Rather than deleting anything outright, which can quietly break a system if a retired workflow is ever revived, I recommended sorting the unclear ones into a dedicated unused folder while confirming that everything tied to contact records, deal context, and instructor specific fields should stay exactly where it was.

The Transformation and Results

What had been an ad hoc, easy to forget booking process became a fully automated sequence, from the first form field to the reminder that lands fifteen minutes before the call. Follow up no longer depends on someone remembering to send an email at the right moment. It happens on the date the prospect actually asked for, every time. Double booking across his calendars is no longer a background worry. And instead of an account full of unlabeled legacy fields that nobody could confidently explain, he now has a system with a clear naming standard and a clean, documented structure his team can actually understand and maintain going forward.

Success Achieved or Failure Avoided

Today, every person who requests a demo moves through a smooth, professional experience that reflects the same calm his platform promises its own customers. Prospects get timely reminders, thoughtful follow up, and a nurture cadence that respects their own timeline instead of hoping someone remembers to circle back. Had this gone unaddressed, the platform would have kept growing on top of an increasingly cluttered, undocumented foundation, one where good leads quietly fell through the cracks and where every new hire would have had to reverse engineer a system nobody fully understood.

Built to Last: The Training Library Advantage

For every feature I build, I also create a custom training video walking through exactly how that piece of the system works, tailored to that client's own setup rather than a generic tutorial. Those videos become a permanent training library, which means his team, and anyone he brings on in the future, can learn to operate the CRM independently without leaning on me for every small question. That saves real time and money during onboarding, gets new team members productive quickly, and strengthens adoption across the whole organization over time. A CRM only creates value when the people using it actually understand it, and a well used system like this one becomes a genuine asset for building relationships, generating business, and supporting sustainable growth.

If you have questions about how a system like this could work for your own business, I would love to talk it through. You can schedule a CRM consult below 👇