You Don’t Have to Know What to Automate

“I’d love to see what you can do — but honestly, I have no idea what you’d even automate for us.”

That was the first real sentence out of the owner's mouth when I described what we do. Not a problem statement. Not a list of things driving her crazy. Just genuine curiosity from someone who runs a busy boutique fitness studio and was open to the idea of automation without having any frame of reference for what that might actually look like in her specific business.

I told her that was fine. More than fine, actually. That's a pretty good place to start.

When a client already knows exactly what they need, we build what they asked for. When they don't know what's possible yet, we find what they actually need — and that's usually more valuable than whatever they would have thought to ask for. So we ran an audit.

Before we touched a single tool or wrote a line of code, we went through how their operation actually runs. Their class booking platform, their social media setup, their accounting, their website, the integrations sitting in their software accounts, the things they dealt with every week that took longer than they should. The whole picture.

What came back wasn't what either of us expected.

The contact email in their website header had been routing to their web agency's inbox, not to the studio owners. Anyone who clicked to reach them from the site was sending their message to a third party. They didn't know how long that had been happening — but once we flagged it, they were able to get it corrected before we met again.

Their physical address wasn't on the website anywhere. That matters more than most people realize — for local search, for the way AI tools and search engines try to connect a business to a real location, an address in the header and footer is a basic signal that was just missing. They didn't know it wasn't there. Once we pointed it out, they got it updated right away.

They were already ranking number one in organic search results for their category in their city. They had no idea. The SEO foundation was solid and working, they just couldn't see it.

A third-party service was connected to their studio management software under integrations — active, with backend access to their member data — and had never been configured or used. There was no reason to leave that open. We flagged it for removal.

And the QuickBooks backlog they'd been putting off? Solved with a built-in QuickBooks feature called Bank Rules. You set the rules once, they apply automatically to every matching transaction going forward and can be applied retroactively to the backlog. No migration, no new software, no additional cost. Done.

The studio managed instructor scheduling the way most small studios do. When a class needed a substitute, someone had to track down coverage manually — texts, calls, back-and-forth until someone said yes. We built a board that connects directly to their class management platform. When a class needs coverage it appears on the board automatically. Instructors log in with a unique PIN, see what's available, and claim it. No chasing. The owners see the whole picture from an admin view and can configure which instructors get notified first for which classes.

The second thing was a contest leaderboard. They ran member challenges regularly — complete a certain number of classes in a set period, win a reward — but tracking was manual. We built a board that pulls live member data directly from their platform and updates automatically. It runs on their studio TVs in a full-screen display that refreshes on its own, so it stays current without anyone touching it. They can run multiple contests at the same time. They create and manage everything themselves from an admin panel. And it's built the way they actually run their challenges — completion-based, so everyone who finishes is recognized, not just whoever happens to be in first place.

Both apps went live in Phase 1 and are pulling real data today.

The owner came into that first conversation saying she had no idea what we'd automate for her. By the time Phase 1 wrapped, she had two custom tools she didn't know were possible, a handful of quick fixes that should have been caught years ago, and a clear roadmap for what comes next. The audit found all of it. She didn't have to.

That's the whole point. You don't have to walk in knowing what the solution looks like. You just have to be willing to let someone look at the actual operation — not a surface-level demo, not a features list, but the real day-to-day — and find what's there. Sometimes what's there surprises everyone.