Where You Get Paid Twice

There are two kinds of work in your business and almost nobody separates them properly.

The first kind you get paid for once. You do it, you invoice, it's done. The client is happy, the money lands, and the value of that work to your future is precisely zero. Tomorrow you start again from the same place.

The second kind you get paid for twice. Once by the client, and then again, and again, by every subsequent version of your business that gets to use what you built. The process you documented while doing the work. The template that came out of it. The answer you wrote down instead of just saying. The automation you built to handle the annoying part.

Almost all of your revenue comes from the first kind. Almost all of your leverage comes from the second. And the ratio between them, over a couple of years, is roughly the whole difference between a business that gets easier and a business that gets heavier.

Today is about deliberately shifting that ratio. Not by working more, which is not available to you, but by changing what you do with work you were already going to do.

Here's the pattern I want you to notice, because once you see it you'll see it constantly.

You take on a project. Somewhere in the middle of it you solve a problem. Maybe you work out how to structure a particular kind of engagement, or you build a spreadsheet that does something clever, or you figure out the right sequence of questions for a specific kind of client. You solve it, you use the solution, the project ends.

And then the solution disappears. It exists in your head, and in one folder somewhere, attached to one client, in a form nobody else can use.

Six months later you hit a similar problem, and you solve it again, slightly differently, slightly worse, because you're rebuilding from memory instead of from an asset.

This is the single most expensive habit in small business and it's invisible because the cost never shows up as a cost. It shows up as normal work. You don't feel like you're paying for it. You just feel like everything takes about as long as it always did, forever, no matter how much experience you accumulate.

Experience should compound. In most businesses it doesn't, because nothing was built to hold it.

So here's the question for this morning, and it's one question rather than a framework, because frameworks don't get used on a Sunday.

Look back over the last ninety days. What did you solve that you're going to have to solve again?

Not what did you deliver. What did you figure out. The difference matters. Delivery is the thing you got paid for. Figuring out is the thing you threw away.

Write down five. Be specific. Not "improved our onboarding" but "worked out that asking for the three things in this order stops the delays we kept having in week two." Not "got better at proposals" but "found the paragraph that stops people asking for a discount."

Those five items are assets you already own and haven't collected. Every one of them is currently stored in the worst possible place, which is your memory, where it will degrade and eventually vanish.

Now pick two. Only two. And this Sunday, turn them into something that exists outside your head.

There are four forms this takes and they're worth distinguishing, because people default to the least useful one.

The written down version. The lowest form and still enormously better than nothing. A document that describes the thing, why it works, and when to use it. Ten minutes of talking into a recorder and running the transcript through a cleanup prompt gets you here, and this is where most of your five should land because it's cheap.

The mistake is writing it as a description. Write it as an instruction to a competent person who doesn't have your context. That framing forces you to include the conditionals, and the conditionals are where the actual value is.

The template version. The thing itself, ready to reuse. The proposal structure, not the description of your proposal approach. The question list, not the article about asking good questions. This is a step up because it removes the translation step, and translation is where reuse dies. If you have to interpret a document to apply it, you probably won't.

The automated version. The thing runs without you. This is where the biggest wins live and where the most misplaced ambition lives too. Not everything should be automated and trying to automate a process you've run four times is how you build something that encodes your early mistakes permanently.

The honest threshold is roughly this: if you've done it more than a dozen times, if it's stable, and if you'd bet money on the steps being right, automate it. Otherwise document it and wait. Make will handle the mechanical version once the process has earned it, and the process earns it through repetition, not enthusiasm.

The published version. The one nobody thinks of as an asset and probably the most valuable of the four.

You take the thing you figured out and you publish it. Not the whole system, the insight. It does three things at once. It forces you to articulate it properly, which is where you discover the parts you hadn't actually worked out. It becomes findable by future you, which is more useful than it sounds. And it becomes the reason somebody hires you, because publishing specific hard won process detail is the most credible marketing available to a small business and it costs you nothing you weren't already carrying.

This is why I keep pushing operators toward a real publishing habit rather than social posting. Social evaporates. An archive compounds. Beehiiv is where I'd put it, because the thing you write in August is still working in February, and a post that keeps closing deals eighteen months later is the clearest possible example of getting paid twice.

Want the collection system built for you?

The AI Workflow Blueprint includes the capture routine that turns finished projects into reusable assets automatically, the prompts that convert a recorded explanation into a working template, and the file structure that means you can actually find things a year later. Forty seven dollars. Reply with BLUEPRINT and it's yours.

A word on selection, because picking badly is how people do this once and conclude it wasn't worth it.

Don't pick the most interesting thing on your list. Pick the thing you're most likely to face again within ninety days. Frequency beats sophistication here by an enormous margin. The clever thing you solved for one unusual client is a fun write up and a bad asset. The boring thing you've now done four times and will do four more times before Christmas is the one that pays.

Second filter: pick the one where you currently rely on remembering. If it's already written somewhere, even badly, it's partly captured. If the only copy is in your head and you'd have to reconstruct it, that's the fragile one, and fragility is the real cost you're trying to eliminate.

Third, and this one people resist: pick at least one thing that's about how you sell rather than how you deliver. Operators overwhelmingly capture delivery knowledge and almost never capture sales knowledge, which is strange given that sales is the part with the higher variance and the bigger consequence for getting wrong. The sequence of questions that surfaces a real budget, the way you handle the timing objection, the thing you say when somebody asks why you cost more. Write one of those down this week.

You'll notice the good candidates are usually the unglamorous ones. That's consistent. The assets that compound hardest are almost never the ones that felt impressive to solve.

Doing this retroactively works and it's not the goal. The goal is that it happens by default, at the point where the knowledge is fresh and the cost of capturing it is nearly nothing.

The mechanism is a single question at the end of every project. Not a retrospective, not a meeting, one question: what did we work out this time that we should keep?

Ask it in the last five minutes of the wrap up call while everyone still remembers. If your calls are recorded, Fathom will capture the answer without anyone taking notes, and the answer to that one question across twenty projects a year is a genuine body of institutional knowledge that would otherwise not exist anywhere.

Then it needs somewhere to go, and this is where these systems usually die. If capturing the answer requires opening a tool, choosing a folder, and naming a file, it won't happen. Wire it so the output lands somewhere automatically. Same principle as everything else: the step that depends on discipline is the step that fails.

One last thing about timing, because it explains why you've never done this despite knowing you should.

This work is never urgent. It has no deadline, no client waiting, and no consequence for skipping it today. It's the definition of important and not urgent, and important and not urgent loses every single time it competes with a Tuesday.

It also feels indulgent, which is the real blocker. Spending an hour turning something you already did into a reusable asset feels like admin, like tidying, like the thing you do when you're avoiding real work. It isn't. It's the only work that changes your future capacity rather than just spending it.

So it goes on Sunday, deliberately, before the week starts making claims on you. An hour. Two items from your list of five. Turn them into something that exists outside your head.

Do that weekly for a year and you'll have somewhere north of ninety assets. Some will be trivial. A dozen will change how your business runs. And the compound effect is that the version of your business operating next August will be starting from a completely different place than the one operating this morning, without having worked a single additional hour.

That's the whole strategy. Everything else is tactics.

Go find your five. Pick two. Spend the hour.

Ready to make the compounding automatic?

Capturing assets by hand works until the week gets loud. Inside the AI Business Accelerator we build the capture, the storage, and the reuse into the way your business already runs, so the knowledge collects itself and the leverage builds whether or not you remember to do it. Ninety seven dollars, for owners who want a business that gets lighter instead of heavier. Reply with ACCELERATOR and we'll build it.

Jordan

The AI Newsroom | Jordan Hale | ainewsroomdaily.com