Building systems that support your business.
Every business has its own weird details. Here's what it looks like when the systems are designed around them instead of flattening them into a template.
A few things I've untangled.
$200K in recurring revenue. Hidden in spreadsheets.
Sometimes you don't need a "CRM project."
You need someone to notice where the business is leaking money, and figure out what the systems should do about it.
The problem
A spreadsheet-based renewal process was making it nearly impossible to see what revenue was coming up for renewal, or make sure someone was actually following up on it.
When we dug into the process, we discovered roughly $200K in recurring revenue that wasn't being actively managed.
The account manager knew it was "a mess," but she didn't know that putting a system in place would unlock $200K in ARR.
What I built
I designed a Salesforce + DocuSign renewal process that brought the entire workflow into one place.
The new system gave the team visibility into upcoming renewals, created a repeatable process for managing them, and made it much easier to see what needed attention before revenue slipped through the cracks.
The result
With renewals finally visible and on a repeatable process, the team captured that $200K in ARR.
"Renewals no longer bring a sense of anxiety or dread."
CFO
Less admin. More time with patients.
Finishing the "setup wizard" isn't enough. You need someone who knows what questions to ask (and what buttons to push) to make a system truly fit your team.
The problem
A growing pediatric therapy practice had a very specific client journey, and a whole lot of little administrative tasks required to keep families moving through it.
The owner tried to implement a system several times, to no avail. The system was forcing her team into a generic sales pipeline designed for a completely different kind of business.
What I built
I built their GoHighLevel system around the real-life client journey.
That meant creating workflows for new inquiries, intake, client communication, reminders, follow-up, and the administrative processes happening behind the scenes.
Instead of expecting the team to remember every next step, and the exact context for every patient, the system helps move each client towards their correct path.
The result
Automatic billing means the team is no longer chasing payments for half of every month, and automated admin tasks save hours of work every month.
Less confusion and admin work for the team, more consistency in the client experience, and a system designed around the reality of running a pediatric therapy practice.
"I don't know how we ever operated in that level of chaos before."
Practice Owner
Meet Follow-Up Frank.
The AI agent that makes sure your momentum doesn't die when the meeting ends.
AI is most useful when it isn't another tool you have to babysit.
It should be solving real problems, like removing you from a process you hate doing.
The problem
The meeting ends. Everyone says they'll follow up.
And then somebody still has to turn the conversation into notes, figure out the next steps, look up the contact in the CRM, remember what was already discussed, and write the email.
It's exactly the kind of repetitive work technology should be doing.
What I built
I built Follow-Up Frank, an AI-powered agent designed to handle the gap between having a conversation and actually doing something with it.
Frank takes a meeting transcript, identifies the important context and action items, checks HubSpot for the contact and relevant CRM information, and uses that context to prepare the appropriate follow-up.
Instead of starting from a blank email, or letting a good conversation disappear into meeting notes, the next step is already waiting.
The result
Less time spent turning meetings into administrative work, more consistent follow-up, and a practical example of AI working inside an existing business process instead of becoming another standalone tool to manage.
Frank runs on my own meetings, and I've shared my how-to so others can build their own.
The Missing Revenue Roadmap
A framework I built, and now share with other Salesforce teams.
Sometimes growth doesn't require another tool, campaign, or lead source. It requires making the system you already have work better.
The problem
Businesses spend a lot of time asking: How do we get more leads?
But after years of working inside Salesforce orgs, I kept seeing another problem: existing opportunities were getting lost inside the CRM. Stale deals. Missing follow-ups. Opportunities sitting in the wrong stage. And nobody could clearly point at where in the pipeline the problem lay.
Before spending more money putting leads into the top of the funnel, there was often an opportunity to fix what was already happening inside it.
What I built
I created the Missing Revenue Roadmap, a practical system for finding where revenue is slipping through the cracks in Salesforce, and fixing the processes behind those leaks.
The Roadmap includes step-by-step flow guides and a report and dashboard building tutorial to make sure that anyone, working with any sales team, could provide this level of visibility to their leaders.
The result
A repeatable framework businesses can use to examine their Salesforce pipeline, identify overlooked opportunities, and improve the systems and behaviors that help move revenue forward.
It started as my own playbook. Now others have bought it and used it to implement the same process in their own orgs.
Your business could be the next one on this page.
Tell me what you're working around right now. Let's build something that fits.