Sell the problem to the end user. Deliver it with a trusted integrator.
This course turns Alex Hormozi's sales-team training into a working method for SmartICS: one script structure, one objection method, one follow-up rule, and eight role plays built around the way we really sell, to end users (EU) and systems integrators (SI).
How to run it
- Read one module, 10 to 15 minutes.
- Run its role play in threes: seller, prospect, observer.
- Observer scores on screen. Swap roles. Repeat until it is boring.
- Finish with the quiz. Tick each module done.
What we kept from the source
- A written script. No script means no definition of good.
- Intro, Discovery, Pitch, Close. Discovery wins the deal.
- Questions, never arguments, when the buyer hesitates.
- Never end a meeting without the next one booked.
- Role play every day. Selling is a perishable skill.
What we changed
- The source is built for one-call phone sales. Ours is a multi-meeting industrial sale, so we write one script per meeting, as the source itself advises for long cycles.
- "Close" here means the next committed step: audit, site visit, pilot, purchase order.
- Every play has an SI in it, because SmartICS does not install hardware.
Our selling model: EU-led, SI-delivered
SmartICS is software. We create demand with the people who own the problem, the end user, and we bring a trusted integrator to supply and install hardware and commission the site. Three parties, one plan, named owners.
Who owns what
- Marketing or outreach reaches the plant, utility or facility.
- We run discovery and show the platform.
- We introduce a trusted SI early, before scope is fixed.
- Three-way meeting: EU, SI, SmartICS agree scope and owners.
- SI quotes hardware and installation. We license and support.
- SI registers the opportunity with us.
- We help the SI with discovery questions and the demo.
- SI leads the customer relationship. We back them in the room.
- We support the proposal with licence scope and proof.
- SI delivers. We train, support and stay visible to the EU.
Four rules that protect trust
- Say it first. Tell the EU in the first meeting that an integrator installs. Raised late, it sounds like a weakness.
- Never surprise an SI. If their customer contacts us directly, the SI hears it from us the same day.
- The EU's own integrator comes first. If they already trust one, we train that SI instead of replacing them.
- Follow the partner policy for deal registration and the thresholds for direct engagement. If unsure, ask before the meeting.
Before the meeting: educate and qualify
The source gives a sales motion two levers. Education puts the right information in front of the buyer. Qualification puts the right person in the meeting. A buyer who arrives informed needs fewer meetings.
What to send before every first meeting
Build each pre-meeting pack on five parts: Promise, Pain, Proof, Plan, Picture.
| Part | For an end user | For an SI |
|---|---|---|
| Promise | One view of the whole site, on top of what you already run. | A platform your engineers can build on quickly, with leads from us. |
| Pain | Data sits in separate systems. Problems are seen late. | Engineering hours eat margin. Vendor support is far away. |
| Proof | [insert] a case from the same industry. | [insert] a partner story or a joint project. |
| Plan | Audit, pilot on one line or area, roll out. | Training, first joint project, deal registration. |
| Picture | A screenshot of a dashboard for their industry. | A screenshot of the drag-and-drop builder. |
The automation audit (smart index) is our strongest pre-meeting tool for end users: they score their own gaps before we speak.
Qualify with BANT, two versions
| End user | Systems integrator | |
|---|---|---|
| Budget | Is there capex or opex for monitoring, automation or digitalisation this year or next? | Will they invest engineer time in training and a first project? |
| Authority | Who signs: plant manager, engineering head, IT, procurement? Get them in the next meeting. | Are we talking to the owner or technical director who picks platforms? |
| Need | A desired state in their words and a real obstacle with a cost. | Named customers with the mixed-system or visibility problem. |
| Timing | A shutdown window, audit, expansion or incident that sets a date. | A live tender or project in the next two quarters. |
Two of four is a conversation. Four of four is an opportunity. Missing authority means the next meeting is a briefing for the decision maker, booked now.
The meeting script: Intro, Discovery, Pitch, Close
Every meeting uses the same four parts. Most of the time goes to discovery. If discovery is done well, the pitch is short and the close is a formality.
Time shares are a guide for a 30 to 45 minute first meeting.
1 · Intro: set the agenda and get a small yes
If the buyer opens with "so what is this about?", you did not set the agenda. Lead the meeting.
2 · Discovery: find the gap, then the pain
Three systems, manual reports, faults noticed by operators.
what it costs
One screen, alarms in time, reports on demand.
- Current state. "Walk me through how you see what's happening on site right now."
- Desired state. "If this worked the way you want, what would you see and when?"
- Obstacle. "What's stopping that today?"
- Dig. "Tell me more about that." "Give me an example." Keep going until you have a number, a date or a name.
- Recap, label, confirm.
No urgency at the end means you did not dig deep enough. Do not move on without a clear yes to the recap.
How many screens do you open to answer one question? What happened the last time a fault was caught late? Who builds a new report today, and how long does it take? Who do you call when the system stops, and how fast do they come?
Which platforms do you deliver today? Where do projects lose margin? How long does vendor support take to answer? Which three customers have data stuck in separate systems?
3 · Pitch: three problems, three answers, under two minutes
Use only the problems they told you. Anything extra creates a new objection.
| Their problem | SmartICS answer | Benefit, then confirm |
|---|---|---|
| Data locked in separate systems | Connects almost any protocol, including data from other SCADA | One view without replacing what works. "Would that help?" |
| Every change needs a programmer | Drag-and-drop, low-code dashboards you build and test yourself | Your own team makes changes in hours. "Would that help?" |
| Vendor support is slow or far away | Local presence, with a trained SI on site | Someone near you answers. "Would that help?" |
4 · Close: ask for the next step, then stay silent
Then say nothing. The source reports that reps who wait eight seconds or more after the ask close noticeably more. The first person to speak usually gives ground.
One script per meeting
| Meeting | Who is in the room | The close you ask for |
|---|---|---|
| 1 · Discovery | EU sponsor, SmartICS | Technical meeting or audit, with the SI and the decision maker |
| 2 · Technical / audit | EU engineering and IT, SI, SmartICS | Agreed pilot scope and who quotes what |
| 3 · Commercial | EU signer, procurement, SI, SmartICS | Purchase order or signed pilot |
Tonality: five controls
- Always: loud enough, slow enough, clear enough.
- When it matters: pause before the important words, and raise your pitch on a question.
Objections: ask again, with a question in between
A "no" is the job. Hesitation is a sign of interest, since people with no interest leave. The method is a loop: whatever they say that is not yes, you respond and ask again.
First response, always
Do not answer the first thing they said. It is rarely the real one.
Five universal closes
- Reason. Their reason not to act is the reason to act.
- Hypothetical. "If we solved X, would you go ahead?"
- Zoom out. Leave the detail, return to the goal.
- One to ten. "What would make it a ten?"
- Best case, worst case. Make the step low-risk, then name the cost of doing nothing.
Three rules
- Questions only. People believe what they say, not what you say.
- Never prove them wrong. Leave them a way to change their mind with dignity.
- Use a story: "Can I tell you what I told a plant manager in the same position?"
The objections we hear
Follow-up: book a meeting from a meeting (BAMFAM)
Every meeting ends one of two ways: a committed step, or the next meeting booked before anyone leaves. Keep the last three minutes for it. If you cannot close the appointment, you will not close the deal.
Booking it
- Offer two times. Do not ask "when works for you?"
- If they resist, shrink it: 45 minutes becomes 15.
- Still no: "When were you planning to let me know?" Book that as the meeting.
When a deal goes quiet: the value ladder
One rung at a time, bottom first.
Call notes, six lines, same day
- Who, role, site.
- Current state.
- Desired state, in their words.
- Obstacle and what it costs.
- Decision makers and which SI.
- Next step with a date and owner.
The SI should never have to make the customer explain everything again.
Ask for referrals
EU "Which of your other plants or sister companies has the same visibility problem?"
SI "Which three of your customers should see this next? Shall we call them together?"
Compliment, ask for an introduction, give them the exact words to send.
Weekly pipeline inspection
- Every open deal has a dated next step.
- Stage matches evidence, not hope.
- No reply in 14 days: move it to the value ladder.
- Every deal names its SI, or says "SI needed".
Role-play exercises
Role play is the one training tool the source would keep above all others. Run each exercise in five moves: frame it, model it, copy it, practise it, recap it.
Feedback names a behaviour: "you answered the objection before isolating it", not "that felt weak".
Team rhythm: keep the skill sharp
Train one part of the script each day, every week, at the quietest calling hour. All four parts must work, like the wheels of a car.
| Mon | Tue | Wed | Thu | Fri |
|---|---|---|---|---|
| Intro and early pushback | Discovery | Pitch and the SI introduction | Close and objection loops | Hot topic of the week, random-call role play, pipeline review |
15-minute huddle
- Shout-out for a specific behaviour worth copying.
- One customer or partner win.
- Script drill on the day's theme.
- One role play on the week's biggest sticking point.
Daily five
- 20 minutes learning one focus industry: its terms, its pains.
- One role play.
- One call or meeting review.
- Pipeline follow-ups before new outreach.
- Call notes in the CRM the same day.
Weekly one-on-one
- Personal check-in.
- Last week's one focus: did the number move?
- Data against the team average.
- This week's one focus: one metric, one behaviour.
- Actions with dates for rep and manager.
Manager cheat sheet: metric, likely cause, fix
| If this is low | Likely cause | Fix |
|---|---|---|
| Outreach volume | Activity and time blocks | Fixed outreach blocks. Back to work straight after a win. |
| Replies and first conversations | Wrong list, wrong timing, weak first 30 seconds | Review ten openings. Role-play the reason for the call. |
| First meeting to opportunity | Discovery: no clear desired state or no real obstacle | Review where the gap was missed. Drill "what's in the way?" |
| Meetings held vs booked | Weak qualification, booked too far out, nothing sent beforehand | Check BANT, book within days, send the pre-meeting pack. |
| Opportunities stalling | No next meeting booked, decision maker missing | BAMFAM rule. Ask "what would they object to?" |
| SI introductions not converting | SI introduced late, customer re-explains everything | Introduce the SI by meeting two. Share call notes before. |
Check yourself
Eight questions. Tap an answer to see why.