In short: My scripts are deliberately linear: one common thread from A to Z, not a flowchart with branches. A human leads the conversation. AI handles everything around it: preparation, follow-up, review. Systems belong behind the conversation, not inside it.
Why people buy
Nobody buys because the salesperson found the right branch in a diagram. People buy when they feel understood and when they believe the person across from them. That feeling doesn't come from a perfect sentence. It comes from listening, from pace and pauses, from an honest follow-up question, from the courage to bring up something uncomfortable.
That's why I say emotion beats systems. Not because systems are bad – I built my whole company on them. But because inside the conversation they're in the wrong place. If you're thinking about your process during the conversation, you're not thinking about the person sitting across from you.
The script as a common thread
My sales scripts are linear. They run from A to Z, in one order, without branches. That's not laziness and not a beginner's mistake, it's intentional.
A linear thread gives the salesperson confidence without taking away their attention. They always know where they are and where the conversation goes next. They don't have to think about which branch is up now. The headspace that frees up is needed for the only thing that really counts: the person on the other end.
A common thread doesn't mean reading word for word. It means the order is fixed and the voice stays alive. If the other person drifts off, you bring them back to the thread. If they ask a question, you answer it and carry on where you were. The thread is the handrail, not the staircase.
Why I don't build flowcharts
You might think a script becomes more "professional" if you expand it into a decision tree – with if-then branches and a path for every objection. I deliberately don't do that. And it's not a gap I'm planning to close, it's a decision.
On paper, a flowchart looks complete. In the conversation, this is what happens: the salesperson hears an answer, looks for the matching branch and reads on. In the moment they're searching, they're gone. The other person notices, even if they couldn't say how. A conversation turns into a questionnaire.
On top of that, every branch doubles what you have to learn and maintain. A team that's supposed to know twenty branches ends up knowing none of them properly. A team that has truly internalized one thread from A to Z can lead it with full presence.
The conversation stays with a human
I build AI clones, AI agents and my own AI operating system. You'd expect me to hand the sales conversation over to a machine too. I don't.
The reason is the same as with the flowchart: a model can say the perfect sentence, but trust isn't a template. A closed deal depends on things you can't pack into an answer – on whether someone senses that a human is taking responsibility. That's why there's no clone on the phone in my sales, and during the conversation nobody is looking at suggestions on a screen.
Where AI belongs in sales
Everything around the conversation is a different story. There, AI isn't optional for me, it's a given. Three places carry the most weight:
Preparation
Before someone picks up the phone, they should know who they're talking to: what the company does, what stands out, which question opens the conversation. A machine can do that work in a fraction of the time, and the salesperson goes into the first seconds prepared.
Follow-up
Many deals aren't lost in the conversation but afterwards, because nobody follows up. Reminders, prepared drafts, clear next steps – a system does that more reliably than any person. A human still hits send.
Review
After the conversation, AI is gold. What was said, where did it tip, which objection came up, what's the next step. You can learn and train from that without anyone typing up notes.
In my own company, part of this is handled by ESIS, my internal AI operating system: it flags new leads instantly, writes daily reports and summarizes the calendar. People lead the conversations. There's a longer version with seven concrete places in Using AI in sales (German). Which tools fit is in AI tools for business (German).
Systems have their place – behind the conversation
After my four failed attempts at 18 I learned to build systems instead of tactics. That applies to sales just the same. The system just looks different from what many people think: it isn't the diagram the salesperson works through during the conversation. It's everything that makes sure they go into the conversation with a clear head, good preparation and a clear thread – and that nothing gets dropped afterwards.
A good sales system makes the conversation more human, not more mechanical. If a system makes the salesperson listen less, it's a bad system, no matter how elegant it looks.
What I'd tell anyone who sells
- Write one thread, not ten branches. From the greeting to the next step, in one order.
- Practice the thread until you no longer have to think about it. Only then is your head free to listen.
- Let the machine do everything that comes before and after the conversation. Research, reminders, summaries.
- In the conversation itself, use only one tool: attention.
That's my stance from my own practice, not a universal truth. But it's exactly the stance my own sales is built on.
How I came to see AI as an employee rather than a tool in the first place is in the idea behind the Clone Looping System and in my piece on Jarvis, my own AI clone. More about me is on About Mario De Luca.
Mario De Luca Founder and systems builder from the German-speaking region (DACH). With NextCore I build AI agents and automations for businesses, and I founded the Clone Looping System (CLS). Here I write about what I've built, tested or messed up myself. More about me · All journal posts