Every time I finish a job, I ask what part of it could become a template, a checklist, or an automation for next time. We stay small by starting from zero on every project. The ones that grow turn each job into a reusable system, so the next one starts faster.
I used to start every project from scratch and then wonder why I was always tired. Every new client, deliverable and campaign began with a blank page. I treated that as a fresh start. It was really a sign I hadn't kept anything from the last time. I was solving the same problems over and over with different names attached, and calling it hard work.
Where this hack comes from
This is hack 30, the last of the original thirty, and the one underneath most of the others: the templates, the checklists, the automations, the "write the SOP the second time" habit. We stay small by starting from zero on every project. The businesses that grow turn each finished job into a reusable system.
If every project takes the same amount of original thinking as the last one, you have a job, not a system. Once a finished project leaves something behind that makes the next one easier, you're building an asset instead of logging hours.
The end-of-project question
When I finish a job, before I move on, I ask one question: what part of this could be a template, a checklist, or an automation for next time? Not "was this a success." Not "what would I do differently." What did I just do that I'll do again, in some form, for someone else?
Most projects have at least one honest answer. The intake questions I always ask a new client on the first call. The steps I follow every time I launch a page, in the same order, because I learned the hard way what happens when I skip one. A repetitive step with no judgment in it that a tool could just run.
How to spot what's actually worth systemizing
Not everything from a finished project deserves to become a system. Some parts were one-off, specific to that client or that moment, and a template for them is overhead. I use two signals to sort them.
Anything you did more than once
A step that showed up twice in the same project, or that I recognize from a past one, is the clearest signal. A step that happens once doesn't need a template. A step that happens every time wastes effort every time it's rebuilt.
Anything that required remembering a lot of small details
If a step depended on me remembering small things (the right order, the setting I always forget to change, the field I always double check), it will eventually get missed. A checklist exists to hold those details so I don't have to.
If I can picture doing this exact step again for a different client next month, I capture it. If I can't, I let it go.
Template, checklist, or automation: they're not the same thing
I used to lump all of this under "documentation," which was part of the problem. The three forms are different, and picking the right one is what gets the system used instead of left in a folder.
A template is a starting document. You duplicate it and fill it in instead of rebuilding the structure: a proposal outline, a project brief, an email sequence, a slide deck skeleton. It saves less typing than it does decisions about what goes where, which is usually the slowest part of starting anything.
A checklist is a sequence to follow. You work through it in order, so nothing gets skipped and nothing depends on your memory that day: launch steps, onboarding steps, a pre-send review. It earns its place the first time it catches something you'd have missed.
An automation is something that runs without you. It's a step that needs execution but not your judgment: a recurring report, a follow-up email, a file that renames and files itself. Automations save the most time of the three, but only for steps with zero decision-making. Automate a step that still needs your judgment and you'll spend more time fixing what it got wrong than you saved.
A template saves you from a blank page. A checklist saves you from your memory. An automation saves you from doing the step at all.
Capture it right after you finish, not later
Do it immediately after you close out the project, not next week when you have "more time." I've tried waiting. It doesn't work. The edge case that almost tripped you up, the order the steps had to happen in, the line a client always asks about: they're sharp for a day or two and then gone. A week later, rebuilding that context takes almost as long as the work did.
So right after I wrap a project, before I open the next one, I spend a few minutes writing down the answer to that question. Not a polished document. Just enough that I, or whoever touches this kind of work next, isn't starting from nothing. The system gets refined the second or third time it's used. The first version just has to exist.
The end-of-project habit, in order
How the thirty hacks connect
The template from writing the SOP the second time, the checklist behind the two-minute rule, the automation that reads your newsletters: each one started as a project that got finished once and then turned into something reusable. A template used ten times has saved you nine blank pages. A checklist that catches one mistake a month has protected a client relationship you never had to think about. None of it looks dramatic. The fortieth project just starts faster than the fourth did.
I help small teams do big things, and a lot of that is making sure the useful parts of yesterday's work don't have to be reinvented tomorrow. Finish your current project, then spend ten minutes on the end-of-project question.
Key takeaways
- At the end of every project, ask what part of it could become a template, a checklist, or an automation next time.
- Look for two signals to decide what's worth capturing: anything you did more than once, and anything that required remembering a lot of small details.
- A template is a starting document, a checklist is a sequence to follow, and an automation is something that runs without you. They solve different problems.
- Capture the system right after finishing, while the details are still fresh. Waiting even a week means rebuilding context you already had.
- Businesses stay small by starting from zero on every project. The ones that grow turn each finished job into a system for the next one.
This series didn't stop at thirty. I keep finding and sharing new hacks, like Hack 31 on giving an AI tool read-only access to read your newsletters for you, all linked from the full hacks index.
Frequently Asked Questions
A template is a starting document, something you duplicate and fill in instead of building from a blank page. A checklist is a sequence to follow, the exact order of steps so nothing gets skipped and nothing depends on memory. An automation is something that runs without you, a workflow or tool that does the repeatable part on its own once it is set up. Most finished projects contain the raw material for at least one of the three.
Look for two signals. The first is anything you did more than once, inside this project or across past ones. The second is anything that required you to remember a lot of small details, the kind of thing you would forget by the next time you needed it. If a step meets either signal, it is worth capturing.
Right after finishing, before you move to the next thing. The details that make a template or checklist actually useful, the edge cases, the order that mattered, the step you almost forgot, are freshest in the minutes after you close out a project. Waiting even a few days means rebuilding that context from scratch, which defeats the purpose.
No, it works at any size, and it matters most for small teams. A solo operator or a small business has the least spare capacity to redo work, so the templates, checklists, and automations built from one finished job are what let the next job start faster instead of from zero.
