ishaninit
All posts
Build log · Lead Engine

How a gym lead got booked in 1 minute and 45 seconds, with no one at the desk

I built an AI system that answers a new lead, scores it, emails it, calls it and books the visit. Here's the real test run, the tools behind it and what broke along the way.

Ishan Sachdeva
· 5 min read

At 9pm on a Tuesday, someone finally decides to join a gym. They fill in the form on the gym's website, hit send, and go to bed. The gym sees it the next morning, somebody calls at lunch, and by then the person has either cooled off or signed up somewhere that answered first.

That gap between "I'm interested" and "someone got back to me" is where small businesses quietly lose customers. So I built a system that closes it. I call it the Lead Engine, and in its first real test it took a lead from a website form to a booked visit in 1 minute and 45 seconds, without a person touching anything.

Here's how it works, what it runs on, and what broke while I built it.

The test gym

I didn't want to test this on a real business first, so I set up a demo gym called Forge Fitness. It has its own website, its own email account, its own phone number and its own lead spreadsheet. Everything you'll read below happened with real tools, real emails and a real phone call. The only thing that isn't real is the gym.

What happened, second by second

I filled in the free-pass form myself, the way a new member would. I said I wanted to build muscle, I wanted to start this week, and I could come in most evenings after 6. Then I watched.

  • 0:00. The form is submitted on the gym's website.
  • 0:01. The system captures the lead, tidies up the phone number and gives the lead an ID.
  • 0:08. The AI reads the lead and scores it 8 out of 10. Its reason was that I wanted to start this week, had a clear goal, and my evenings fit the gym's hours.
  • 0:10. A personal email lands in my inbox. It's written around my goal and my note, not copied from a template.
  • 0:11. The lead, the score and the reason are saved to the gym's spreadsheet, which works as its CRM.
  • 0:20. My phone rings. It's the gym's AI front desk, calling because I was a hot lead and I had ticked the box agreeing to be contacted.
  • 1:45. By the end of the call, I'm booked in for Tuesday at 7am, and it noted that I was interested in personal training.
  • 1:55. A confirmation email arrives, and the spreadsheet row flips to "Booked".

What it's built on

None of this is magic, and none of it is one giant piece of software. It's a handful of well-known tools connected together.

  • n8n runs the whole thing. Think of it as the conductor. When a form comes in, it decides what happens next and in what order.
  • Claude, an AI model, does the thinking. It reads each lead like a sharp front-desk manager would, scores it, explains why, and writes the first email.
  • Gmail sends the emails from the gym's own address.
  • Google Sheets is the CRM. Every lead, score, call and outcome ends up there, where the owner can actually see it.
  • A voice agent makes the phone call. It uses the gym's own phone number, so the lead sees a local number and not some random one.
  • A private cloud server keeps it all running around the clock, and the business keeps control of its own data.

If you want to see every connection drawn out, the full case study has the diagrams.

What broke along the way

This is the part most people skip, so here it is.

The first problem was that one step in the workflow quietly connected itself to the wrong Google account. Nothing crashed. It just would have sent emails from the wrong place. Now I check every single connection by hand before I run a test, because "it didn't crash" is not the same as "it works".

The second problem was the phone call results. The call itself went fine, but the details never came back to the spreadsheet. It turned out the voice agent's settings page didn't save the address it reports back to until I clicked somewhere else on the page. One click fixed it, but it took a while to find.

Neither of these is exciting. That's the point. Most of the work in a system like this is making sure the boring parts are actually right.

The rule it never breaks

The Lead Engine only contacts people who reached out first and agreed to be contacted. It doesn't buy lists and it doesn't cold-call anyone. If someone replies "stop", they're marked as do-not-contact and never hear from it again. Fast follow-up only feels helpful when the person actually asked for it.

What I'm adding next

Right now the website form, the AI scoring, the emails, the CRM and the phone call all work. Next I'm adding Instagram and Facebook lead ads as new ways in, WhatsApp messages, automatic follow-ups on day 1, 3 and 7 for people who don't answer, an agent that reads replies and acts on them, and booking straight into a real calendar.

If you run a business where leads come in faster than you can answer them, this is the kind of thing I build. You can see the whole system, or tell me about your business and I'll tell you honestly which parts could run on their own.

Written by Ishan Sachdeva

I build AI systems and automations for small businesses, and I show every build on Instagram.

Small business·4 min read

Five jobs in a small business that AI can already handle well

Not someday, but today. The repetitive tasks I'd hand over first, what AI actually does in each one, and the catch you should know about.

Explained·3 min read

What an automation actually is, explained without the jargon

Every automation has three parts: a trigger, some steps and a result. Here's how they work, where AI fits in, and when you shouldn't automate something at all.

Work with me

Got a task you never want to do again?

Tell me about it. I read every enquiry myself and reply with an honest answer on whether it can be automated, and what it would take.

Start a projectFree to ask, with no obligation.