⏳ The problem with 10-hour tasks
Every routine has a task nobody wants to do: one that takes up an entire afternoon, is purely mechanical, and repeats every week. Copying data from one place to another, consolidating spreadsheets, formatting reports, answering the same questions. That’s what we call 10-hour task — and it is your biggest hidden source of opportunity.
💡 The central concept
A 10-hour task has three characteristics that make it a perfect target:
- •Repetitive: happens many times, always the same way.
- •Mechanics: doesn't require judgment, only execution of steps.
- •Predictable: the input and output follow a stable pattern.
The cost of these tasks is invisible because it's scattered across small chunks. Twenty minutes here, an hour there. But add it all up at the end of the month and you'll find that entire days were spent on work a machine could do better—without getting tired, making mistakes, or complaining.
📊 The math of hidden costs
- 2 h/day in mechanical tasks = ~40 h/month = ~480 h/year.
- 480 h are equivalent to 3 months of work wasted on copying and pasting.
- You could spend that same time on strategy, sales, or creating the next automation.
🎯 Practical tip
For a week, write down every task you’ve repeated more than twice. The list that remains is your map of opportunities—and it almost always has a “10-hour task” at the top.
How many times the task repeats.
How little judgment it requires.
The time added up over the course of the month.
The potential gain from automating.
🧠 Strategic automation vs. just using tools
There’s a huge difference between strategic automation and "knowing how to use tools." Most people confuse the two—and that’s why they accumulate software subscriptions without ever saving a real hour. Strategy is deciding what e why; the tool is just the how.
✓ Strategic automation
- ✓Starts with the most painful problem.
- ✓Measures the return before building.
- ✓Choose the tool after the plan.
- ✓Delivers measurable results.
✗ Using tools alone
- ✗Starts with the trendy tool.
- ✗Builds without knowing the return.
- ✗Looks for a problem to fit the solution.
- ✗Accumulates automations that no one uses.
The tool is a commodity: it changes every week, and everyone has access to it. What's rare—and valuable—is the strategic judgment of knowing which problem to tackle first. This judgment is what you develop in this course, and it’s what no one can copy from you.
🔬 Why this matters
Professionals who master tools but don’t think strategically get stuck executing. Those who think strategically first decide what will be built—and that’s the position that pays better, inside or outside a company.
Decides what and why.
Solves the how—it’s a means.
What everyone has access to.
The judgment that’s yours alone.
🔑 The principle of "knowing what to build"
If this course had just one sentence, it would be this: the differentiator is knowing what to build, not just the tools. Knowing what to build means looking at a confusing workflow and seeing clearly exactly where automation fits, in what order, and what the result will be.
🧭 What “know what to build” means in practice
- •Recognize an automatable pattern where others see only work.
- •Choose the problem with the highest return and lowest risk.
- •Define the expected result before touching any software.
- •Knowing where to stop—what to leave for a human to do.
This skill is durable. The tools you use today may not exist in two years, but the judgment to spot opportunities and design the right solution applies to any future tool. It's an asset that appreciates over time.
🎯 Practical tip
Before opening any tool, write one sentence: "I want you to, when X happen, the system Y, generating Z." If you can't complete this sentence, you still don't know what to build — and building before that is wasteful.
See what repeats.
Choose the best target.
Define the destination first.
Applies to any tool.
🚀 The 10h→10s case in practice
Let’s move beyond the abstract. Imagine a real workflow: every Monday, someone has to gather data from several sources, put together a report, and send it to the team. Done by hand, it takes an entire morning. See how the same workflow becomes 10 seconds.
The manual process (~10 h)
How it was before
Open 4 systems, copy numbers, paste them into a spreadsheet, check them, format them, write the summary, attach it, and send it. Every week, from scratch, with a risk of error at every step.
The one-time setup
The investment
You design the workflow: a trigger (Monday morning), connections to the data sources, AI to summarize the data, and automatic delivery. It takes a few hours to set up — just once.
The automatic execution (~10 s)
The recurring return
From then on, every Monday the report builds and sends itself in seconds. You don’t touch a thing. Ten hours of work became a 10-second event that repeats forever.
🧮 The gain calculation
10 h/week × 52 weeks = 520 h/year
# automated
setup: 6 h (once) + 10 s × 52 = ~6.1 h/year
# savings
520 h − 6,1 h = ~514 h/year recovered
What triggers the workflow.
One-time cost.
Where the savings add up.
The more it repeats, the more it pays off.
📈 Leverage mindset: time as an asset
The shift isn’t just technical—it’s mental. People who automate well stop treating time as a cost to spend and starts treating it as a asset to invest. Automation is an investment: you pay once in build time and reap the rewards forever in time saved.
⚙️ Linear effort × compound returns
Manual work is linear: to get twice the result, you spend twice the time. Automation is leverage: you build it once, and the result repeats at no additional cost.
- •Linear: more results require more of your hours.
- •Leveraged: the system produces while you do something else.
- •Composite: each automation frees up time to create the next one.
✓ Time as an asset
- ✓Invest hours today to gain days later.
- ✓Sees every automation as an asset that generates returns.
- ✓Reinvest the freed-up time in more leverage.
✗ Time as a cost
- ✗Accepts redoing the same task forever.
- ✗"I don’t have time" to build what would save time.
- ✗Trades hours for results, always at a 1:1 ratio.
🎯 Practical tip
Before doing a task manually for the third time, ask: "how long would it take to automate this, and in how many weeks will that investment pay for itself?". If the payback is short, stop and automate before continuing.
Time paid once.
Result with no extra effort.
A gain that funds the next one.
When the setup pays for itself.
⚠️ Mistakes people make when starting with the tool
The most common mistake beginners make is getting the order backward: choosing the tool first and only then looking for a problem for it to solve. This leads to months of wasted effort on automations no one uses. Knowing these pitfalls before being aware of them is halfway to avoiding them.
🚨 Attention: the 3 classic pitfalls
- ✗Solution looking for a problem: buying a tool and then inventing where to use it.
- ✗Shiny object syndrome: switching tools every week without finishing anything.
- ✗Automate the irrelevant: invest time in a task that happens once a year.
The cure for all these mistakes is the same: always start with the problem. Define what needs to be solved, calculate the return, and only then choose the tool that best delivers that result. The tool is the last decision, not the first.
✓ The right order
- ✓1. A painful, recurring problem.
- ✓2. Expected return (time × frequency).
- ✓3. Solution design.
- ✓4. The tool that delivers it.
✗ The order reversed
- ✗1. The trendy tool.
- ✗2. Random tutorial.
- ✗3. Look for where to fit it in.
- ✗4. Abandon it due to lack of use.
🎯 Practical tip
Create a personal rule: no new tool gets added without a written problem it will solve and an estimated return. If there's no problem and no number, there's no tool.
Always before the tool.
A number that justifies the effort.
Finish before switching.
Automate what matters.
✅ Module Summary
Next Module:
1.2 — Where AI creates real value: ROI, jagged intelligence, and how to prioritize opportunities.