Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
What is this?
Less
More
28 contributions to AI Automation Agency Hub
How do you transition from a cold call to a discovery call without pitching?
I'm currently doing cold outreach to business owners for my AI automation consulting business. My goal isn't to sell AI solutions immediately. I want to understand their operations, identify real bottlenecks, and see whether there's an opportunity to help. I'm comfortable making cold calls and reaching decision-makers, but I'm trying to improve the transition into discovery. My question is: When you reach the business owner, do you start a short discovery conversation right there on the cold call, or do you briefly explain what you do and schedule a separate 15-minute discovery call? And how do you explain the value of that discovery call without turning it into a sales pitch? I'd appreciate hearing what actually works for you.
1 like • 19h
@Shubham Gupta That's really solid advice, and I think you're right. My biggest challenge right now is getting past the gatekeeper and speaking directly with the business owner. Once I do, I want to identify a genuine pain point and use that as a reason to book a discovery call. Thank you!
0 likes • 19h
@Yonas Workayehu That's a great point! On cold calls, I try not to explain AI solutions too early because, without seeing anything concrete, some people might think it's just another sales pitch or even a scam. I usually introduce myself and Prosovio, then ask to speak with the owner about improving their booking management or business processes. These past few days, I've been calling HVAC companies but haven't managed to speak directly with a single owner. Last week, when calling restaurants, I had better results: I spoke with a few owners, one invited me to stop by (although we didn't schedule a specific date), and another seemed interested and agreed to follow up in mid-November. Your advice makes a lot of sense. I should use the cold call to identify whether there's a real problem worth exploring, rather than trying to explain a solution. That way, the discovery call becomes a natural next step to better understand their business. Thanks for the insight!
What Should I Learn and Build First So I Can Actually Sell AI Automation?
“When starting an AI automation agency, what type of automation should I build and sell first: a traditional workflow automation, or an AI-powered automation that uses LLMs/RAG?”
1 like • 20d
I'd say don't start by asking yourself what automation you should build. Start by asking what problems businesses are willing to pay to solve. My approach would be: 1. Pick a niche and talk to business owners. 2. Identify their biggest pain points through a discovery call or a free audit. 3. Find out how much those problems are costing them. 4. Validate that they're willing to pay for a solution. 5. Build or adapt an automation that solves the problem, then make it repeatable. As for traditional workflows vs. LLMs/RAG, I'd start with the simplest technology that gets the job done. Not every problem needs AI. You also don't need to reinvent the wheel for every client. Once you find a problem that multiple businesses share, you can build a solution and sell it repeatedly. The key is to validate the problem before investing time in building the solution. Businesses don't buy AI because it's cool. They buy outcomes: more revenue, fewer missed opportunities, lower costs, or time saved. That's how I'd approach it!
Second audit booked!!
Just booked my second free business audit for October 13th at 1 PM! This one came from a cold call. ✅ Made the cold call ✅ Got the prospect interested ✅ Sent over a questionnaire to understand their business and pain points ✅ Scheduled the Google Meet Now the goal is to prepare a valuable, personalized audit, identify opportunities where AI and automation can actually help, and hopefully turn it into a great case study. Still early in the journey, but it's good to see that taking action is starting to create opportunities. A little nervous, but excited. Hopefully it goes well! One call at a time.
First Project Closed!
Just closed my first full AI voice agent project for a restaurant. The client will pay €1,000 now and another €1,000 in 3 months, so €2,000 total for the setup. The project was for Sushi Maison Boltiere, an Italian restaurant. I built an AI phone receptionist that can: - Answer incoming calls naturally - Check table availability - Book reservations - Modify or cancel existing bookings - Send WhatsApp confirmations automatically - Update a CRM with the reservation data and changes The system is built mainly with Retell AI + n8n, connected to the restaurant's booking platform, with Telnyx handling the WhatsApp side. The biggest part of the work wasn't just building the workflows — it was testing everything properly. I ran hundreds of test calls and worked through edge cases like changing dates/times, unclear customer requests, duplicate checks, cancellations, large groups, notes, and making sure the AI didn't repeat or ask for information it already had. It took much longer than I originally expected, but the project is now finished and ready for the client. Definitely learned a lot from actually building something that has to work with real customers, not just in a demo. €2K project closed. Now onto the next one.
3 likes • Sep 15
@Shanmugan Reddymalla YEssirr!!
2 likes • Sep 15
@Jacqueline Hill Thank you!!
Double win this week 🎉
Two updates from the restaurant niche I've been working: Win #1 — Sold an AI-built menu. Closed and delivered a digital multilingual menu for a restaurant client, built with AI. First paid deliverable in the pocket. Win #2 — Same client, bigger scope. Because they were happy, they came back and asked me to build them a reservation management system + a voice agent to handle bookings. Ran my first audit on their current setup, and I'm sending over the report today. Biggest lesson so far: land the small win, deliver clean, and the upsell comes to you. One good menu turned into a full system + voice agent conversation.
3 likes • Sep 15
@Okasha Khan Thank you Mr.Khan
2 likes • Sep 15
@Kelly Lynch Spot on, and that's exactly one of the things the audit flagged. The happy path is easy — it's the messy calls that make or break it. Big party, special requests, someone trying to change a booking three times mid-call. If the agent tries to force its way through those, it loses people fast. So the plan is to build in clear handoff points: when a request goes outside what it can handle cleanly, it takes a message or routes to the staff instead of faking confidence. Better to say "let me pass this to the team" than to lock in a wrong booking. That's the trust killer you're pointing at. Appreciate the input
1-10 of 28
Kunal Singh
5
153 points to level up
@kunal-singh-7541
Driven by growth & logic. I’m here to master AI Automation, deconstruct complex systems, and turn theory into measurable execution.

Active 9h ago
Joined Feb 27, 2026
Powered by