How I sell AI to people who don't know what AI is.

I take the first customer call for every GOGOGO LLC product. Most of those calls are with an HR director, a retail operations manager, a marketing lead, or a small-business owner. Almost none of them can define "multi-agent system" if you offered them a salary for it. They don't need to. My job is to find the bridge between what they already do every Tuesday and what we can ship by Thursday.

Three years and a few hundred of these calls later, here is what works.

Three reframes that close

1. "Imagine if your WhatsApp was a coworker."

I use this on every GoPeople call. Almost every Turkish HR director already operates a corporate WhatsApp inbox manually. She knows what it feels like to triage 200 messages a day, where two of them are urgent and the other 198 are leave requests, documents, or duplicate questions. She doesn't want a chatbot. She wants the WhatsApp to behave like a calm junior coworker who already knows the company's policies. That sentence works because she has the mental model already. The agent system is just the implementation detail. I never lead with the implementation detail.

2. "Imagine if every screen in your store knew what just got picked up."

On GoTrack calls with retail-operations managers, this is the line. They're trying to understand what a computer-vision pickup detection system does. The phrase "a camera connected to a vision model that triggers signage updates" puts them to sleep. The phrase above wakes them up. It moves the conversation immediately to "oh, so the price tag can change when someone picks up the last item?" — yes — and we are now talking about their store, not our architecture.

3. "You don't need to learn the system. The system learns you."

This is the most-used reframe across all four products. Every non-technical buyer worries about onboarding. They've seen a SaaS implementation drag on for nine months. They've watched a team member quit because the new tool was too complicated. The fear is real, the fear is unspoken, and the fear is what kills 70% of deals. The sentence above kills the fear. It also happens to be true — most of our products fine-tune to the customer's data in the first week. But even if it weren't perfectly true, naming the fear is more important than not.

Two phrases I refuse to say on a sales call

"LLM." Nobody outside engineering knows what it means. If they did know, they'd be in a different conversation. The word adds zero information and three units of customer anxiety. I say "the AI" or "our system" instead.

"Orchestration." This is the worst word in our category. It means exactly the right thing technically and exactly nothing emotionally. I say "the agents work together" or "the system routes the message to the right place automatically." Same meaning. Five fewer eyebrows raised across the table.

The one question that closes

Toward the end of every demo, I ask the same thing:

“"Walk me through your Tuesday morning. Where would this product fit in?"”

Three things happen when I ask this.

1. The buyer self-discloses the actual workflow. Not the workflow they put on the slide. The real one — the one with the WhatsApp group, the messy spreadsheet, the colleague they don't trust to send the right reply.
2. The buyer self-discloses the actual decision-maker. "I'd have to check with my team" means there's a team. "I'd have to ask the GM" means there's a GM. "I can decide today" means we close today.
3. The buyer self-discloses the actual budget. Not the headline number — the real one. "We have a small line for tooling" is a different conversation than "I'd have to put this in the Q4 plan."

After the question I shut up. Long pauses are uncomfortable for me. They're more uncomfortable for the buyer. The buyer fills the silence with the exact information I need to close.

What I don't do

I don't send a PDF before the call. PDFs let buyers form a position in their head before I've understood their Tuesday morning. I'd rather walk in cold and let them tell me what they need. The PDF goes out after the call, customized to what they actually said.

I don't demo the product first. I ask the Tuesday-morning question first, then demo only the parts that map to what they just told me. A 40-minute demo with three relevant features beats a 40-minute demo with twelve generic features every time.

I don't use the word "AI" more than three times in any call. I count. If I'm using it more than three times, I'm hiding behind it instead of selling the outcome.

Why this matters for the four products

Each product has a slightly different version of the Tuesday-morning conversation. Goddo is for marketing leads who need image and video drops weekly. GoPeople is for HR directors with WhatsApp pain. GoVista is for retail operators who manage screens across many stores. GoTrack is for category managers who need pickup-event data. Same script structure, four different domains. Same closing question every time.

“Selling AI to non-AI buyers is not about translating jargon. It's about refusing to use jargon in the first place. The buyer doesn't need to meet you on your terms — you meet them on theirs, and the technical layer disappears.”

If you sell technical products to non-technical buyers and you want to compare notes, I genuinely enjoy these conversations. [email protected].