The new game
AI already does the repetitive work
In this video
Everything the video says.
Lesson 1We free human capacity
Reality
Inside most companies, talented people spend their day on tasks a machine could do.
The problem
Copying data, chasing follow-ups, dialing numbers. The work that needs a human — judgment, trust, relationships — gets whatever time is left.
What it costs
The company pays for talent and gets repetition. The people get tired of work that never uses what they are good at.
The idea
Our job is not to replace people. It is to free their capacity, so humans do human work and systems do the rest.
How to do it
- Find the repetitive work.
- Prove what it costs.
- Build the system that takes it.
- Give the time back to the people.
Example
A sales team that spends mornings updating the CRM gets those hours back — and spends them talking to customers.
Your turn
Write down three tasks from your own week that a system could do. Be honest.
Lesson 2Nobody should make a thousand calls by hand
Reality
Growth used to be a volume game: more calls, more messages, more people making them.
The problem
Thousands of manual conversations: someone on the phone, calling and calling, most of it to people who never pick up.
What it costs
Expensive teams, burned-out people, and leads that go cold because nobody can keep up.
The idea
Today, AI systems can take the volume: call, qualify, follow up and hand the right conversation to a person.
How to do it
- The system handles volume and repetition.
- The person handles trust, judgment and the close.
- You design where one ends and the other starts.
Example
Instead of a rep dialing all day, a system works the list and passes over only the people ready to talk.
Your turn
Think of a job you know that is mostly volume. Which part should stay human?
Lesson 3This is for pioneers
Reality
AI is moving faster than any company, school or job description.
The problem
Some people try to convince themselves the world is still the same. It is not.
What it costs
What you do today may be done by AI tomorrow. Standing still is the riskiest move.
The idea
This faculty is for sharp people who choose to be early: the ones who build the systems instead of waiting to be replaced by them.
How to do it
- Keep learning what changed this month.
- Look for the work that will disappear, and move ahead of it.
- Never marry a tool. Marry the problem.
Example
A task that took a team a week — cleaning and enriching a list — now takes one person with the right system an afternoon.
Your turn
Name one thing in your field that changed in the last year because of AI. What did the pioneers do about it?
What the video doesn't have time for.
Why this matters now
For years, growth meant hiring more people to do more of the same: more calls, more follow-ups, more data entry. AI changes the math. The repetitive part of revenue work is now the cheapest part to automate — which means the valuable part is the person who knows what to automate, and why.
What "freeing human capacity" really looks like
It is not a robot replacing a team. It is a system taking the first contact, the reminder, the data update — so the team spends its hours on the conversations that close.
- The system does: first contact, follow-up, qualification questions, updating the CRM.
- The human does: judgment, negotiation, trust, the relationship after the sale.
A simple way to find the repetitive work
Take one normal day of a revenue role and write down every task. Then ask three questions for each one:
- Is it the same every time?
- Does it follow clear rules?
- Would a customer notice if a system did it well?
If the answers are yes, yes and no — it is a candidate for a system.
Common mistakes
- Automating the conversation that builds trust, instead of the work around it.
- Selling "AI" to a company before knowing which task it will take.
- Thinking the goal is fewer people. The goal is more capacity per person.
Take it to a company
Ask: "Which task does your team repeat the most every week — and what would they do with those hours back?" The answer is usually your first project.
An honest list: which parts of your current work could a system already do?