Apr 4 • General discussion
Saturday question: what's one automation you built that actually stuck?
Most automations get built once and abandoned within a week.
They break. They need babysitting. Or they just get ignored.
The ones that actually stick have one thing in common: they solve a problem you run into every single day. Not once a week. Every day.
Here's how I think about it.
Before building anything, I ask three questions:
1. How often does this problem show up?
2. How long does it take me to deal with it manually?
3. If I never had to touch it again, how much would that change my week?
If the answer to all three is "a lot," that's your first automation.
For me it was content repurposing. I was spending 45 minutes every time I wanted to turn a LinkedIn post into something else. Built a simple Claude workflow. Now it takes 5 minutes. That one ran for months before I touched it again.
The automations that fall apart are usually built to solve a problem you only care about in theory.
Build for the daily friction, not the interesting use case.
Your turn. What's one automation you built that's actually still running? What problem does it solve? Drop it below.
0
0 comments
Saturday question: what's one automation you built that actually stuck?
powered by
skool.com/ai-mastermind-3877
Weekly AI mastermind for builders, founders & operators. Real conversations about using AI to grow your business.
Suggested communities
Powered by