Scan time: 2-4 minutes / Read time: 4-6 minutes
⠀
Hey rebel ideapreneurs 🦸♂️🦸♀️
⠀
🙋♂️ Nate’s Monday morning inbox
Nate is a software engineer who runs a podcast on the side.
Monday morning is the only quiet time he has to record this week’s episode.
But the inbox has forty unread emails, and he answers those first.
So he records the episode on Friday night, tired and rushed.
🧩 His struggle:
He gives his best hours to whatever feels urgent, so the show gets his tired ones.
At lunch, he clicks on a video with the true story of a man
who also once spent a whole hour on something that barely mattered,
and still built a one-person business past $10 million in sales.
And he still catches himself breaking his own rule.
⠀
📈 The hour he spent on one subject line
Justin Welsh runs a one-person business that passed $10 million in total sales in 2025, with no employees and no paid ads.
His newsletter, The Saturday Essay, goes out to 175,000+ readers every Saturday.
One day in early 2025 he sat at his laptop, working on the subject line of a single email.
He tried one version, then another.
He went back through old issues to see which subject lines got opened.
He weighed one word against another.
Then he looked at the clock.
An hour had gone by.
He laughed, because he knew the truth: the best subject line in the world would change the result by maybe one percent.
He had spent one hour to make one email about one percent better.
It reminded him of a friend.
The friend had spent six months polishing the sales page for his course.
At the end of the six months, the page sold two percent better, which came to about $10,000 more on his next launch.
That sounds good, until you ask what else he could have done with those six months.
In those same six months he could have made three new products, or written twenty-four newsletters.
Any of those would have paid him ten times more than the polished page did.
So Justin decided to run a test on himself, with something much bigger than a subject line.
He was in France at the time, on a sabbatical, a long break from normal work.
He cut back the hours he spent on social media: the commenting, the replying, the scrolling.
Then he watched what happened to the money.
His revenue dropped about three percent.
Get this — in return, he got back about ten hours a week.
He used those ten hours to work on a brand-new business idea, and to have lunch with his wife.
The new idea alone may earn back that three percent, and probably more.
So here is what Justin learned.
An hour spent making a subject line one percent better is an hour wasted.
The same hour spent building a new product can pay you for years.
You only get so many hours in a week.
Justin spent one of them polishing a subject line, and it earned him almost nothing.
He spent ten of them on a new business idea, and that could earn him for years.
So give your hours to the work that pays you the most, and do that work first.
⠀
🔥 The recipe
➡️ The Impact-to-Time Ratio
Justin cut about ten hours a week of social media, and his revenue dropped only about three percent.
He spent those hours on a new business idea, and that idea could earn him for years.
Justin’s strategy is called The Impact-to-Time Ratio.
For each task, ask two questions: how much will this grow my business, and how many hours will it take?
The task that grows it most per hour goes first.
Justin could have kept replying on social media first, because the notifications never stop.
He didn’t.
So on Monday morning, when the inbox is full and the episode is not recorded, you record the episode first.
Recording it brings in listeners every week; the forty emails bring in nothing.
The emails get answered later that day, after the important work is done.
⠀
🛠️ Nate’s turn
Let’s check in on Nate, who keeps losing his quiet Monday mornings to forty emails instead of recording his podcast.
That night, he runs the prompt at the bottom of this email, and gives it this week’s list, with the hours each task takes.
His AI sidekick says:
Your episode brings in listeners every week, and the forty emails bring in nothing,
so record the episode first on Monday morning, and answer the emails after work.
The next Monday, he leaves the inbox closed until the episode is recorded.
He answers the emails that evening.
⠀
🌅 Two months later
Nate records every episode on Monday morning now, before he opens his inbox.
He hasn’t recorded on a Friday night since.
About two hundred people listen to each episode now, up from ninety.
Your quiet hours probably go to whatever feels urgent, the way Nate’s did.
Give your best hours to the work that grows your business the most, and do that work first.
That’s it, my fellow contrarians!
Yours ‘proving one person with an AI sidekick can build something amazingly big’ Vijay Peduru 🦸♂️
⠀
⠀
⠀
⠀
⠀
🏄♀️ The prompt
The prompt below scores everything on your list by what it returns against the hours it costs.
🧰 What you’ll need
Everything on your list this week, and roughly how long each one takes
- Type it, or say it out loud with a voice tool.
- e.g. record the episode 4h, redo the logo 6h, reply to 40 emails 3h, fix the signup page 1h, write show notes 2hWhat each one actually gives back, as best you can tell
- e.g. the episode keeps the show alive, the signup page maybe doubles conversion, the logo returns nothing I can nameWhen your best hours are, and what you did with them last week
- e.g. 6am to 8am before work, and last week they went on email, mostly
🚀 How to run it
Open your AI sidekick, ChatGPT, Claude, or whichever one you use.
Swap the three examples, the text inside the curly brackets, for your own, then run it. If your AI sidekick can already see your notes, you can run it as is.
🧪 Want to test it first? Run it without changing anything, and it will use the examples.
CONTEXT:
- Use my own material first. If you can see my episode list, my show notes, or my download numbers, pull the real details from there instead of the examples below.
- If you know how I write, use my voice. Otherwise, write in a clear, warm, no-jargon voice — first-person, plain words, no startup-speak.
- If you know who my readers are, write for them. Otherwise assume people learning to code after thirty.
- If I have replaced the examples, use only mine. If an example is still there, fill it in from what you already know about me, and mark it as your assumption. If you don't know anything about me yet, use the example exactly as written.
- Score every item on return against hours. Urgency is not a score. "Someone is waiting" is not a score. Say so when that is the only thing an item has going for it.
=============== INPUTS — edit these, or just run as is ===============
Everything on my list this week, and roughly how long each takes:
{e.g. record the episode 4h, redo the logo 6h, reply to 40 emails 3h, fix the signup page 1h, write show notes 2h}
What each one actually returns, as best I can tell:
{e.g. the episode keeps the show alive, the signup page maybe doubles conversion, the logo returns nothing I can name}
When my good hours are, and what I did with them last week:
{e.g. 6am to 8am before work, and last week they went on email, mostly}
======================== END OF INPUTS ========================
Outputs:
1. The scores — each task with its return, its hours, and the ratio, ranked.
2. The mismatch — what got my good hours last week versus what should have.
3. This week's good hours — exactly what goes in them, by day.
4. The bottom of the list — what returns almost nothing per hour, and what happens to it: dropped, batched, or done badly on purpose.
5. The urgency trap — the items that scored low but feel pressing, and what to say to whoever is waiting.
Then tell me which task I keep doing because it feels productive rather than because it returns anything.