We didn't plan to rebrand.
We went to a brand agency for a logo refresh. Small job. Two weeks before launch, we wanted the visual identity to feel cleaner. That was the scope. That was all it was supposed to be.
The agency delivered what we asked for. Then, almost as an aside, one of them said: "Can I ask, why Secret Sauce? Because what you're actually building sounds more like Secret Source."
Source. Not Sauce.
The thing you draw from. The origin of the advantage. The place where the value actually lives.
We sat with that for about four seconds before we both knew they were right.
What happened next is the part that matters more than the name.
The moment we accepted the spelling could change, that it wasn't fixed, we found ourselves asking a different question entirely. Not should we change the spelling? but is the name actually right at all?
Secret Sauce started as a podcast. The premise was simple: spill the beans on what business owners actually get up to. Candid conversations. Behind the scenes. It was a good premise for a podcast.
The business grew out of that. The diagnostic, the platform, the methodology, none of it was in the original brief. The name stayed because it was a good name, and because changing it felt like it wasn't in scope. Nobody put it on the agenda. Nobody questioned it. It just persisted.
The moment we realised the spelling was changeable, the name became a decision again. And once it was a decision, the answer was obvious.
It wasn't right for what we'd built.
So two weeks before launch, we renamed the business lifestack.
Claire called her brother about this. He's a brand consultant. His response was immediate and unambiguous.
Do not do this.
He was probably right. For most businesses, at most stages, a rebrand two weeks before launch is exactly as chaotic as it sounds. We are not suggesting you do what we did.
We are suggesting something else.
The pattern underneath
We didn't make a bad decision when we kept the name for two years. We made no decision at all. The name persisted not because we'd weighed it and chosen it, but because it had never occurred to us that it was still a choice.
That's a different problem. It's also the problem we now build our work around.
Most things inside a business are running on defaults nobody actively chose. Pricing set in year one when the operator had no leverage. Services on the menu because a client once asked for them. Decision rules that exist nowhere but in someone's head. Standards that everyone follows and no one has ever written down.
These are not necessarily wrong. Some of them will turn out to be exactly right. But until they have been examined, they are not decisions.
They are inertia wearing the costume of strategy.
This matters more now than it used to, because AI is about to amplify whichever version of your business you have. If your business is running on codified, deliberate standards, AI will scale them. If it is running on defaults nobody chose, AI will scale those instead: faster, further, and with a confidence that makes them harder to dislodge later.
The work to do first is not technological. It is analogue. Make the defaults visible. Sort the ones that are working from the ones that are drifting. Name the judgement underneath the ones that stay. Only then does it become safe to let any system, AI or otherwise, run on top.
This is what lifestack is. The method we built for ourselves, so that we could carry what we carry without it consuming us. We are now putting it in front of other operators who want the same.
The practical: the Default Inventory
Each edition of Running Cost ends with something you can actually run. Most will be small. None will fix everything. Together, they start to surface what your business is quietly built on.
This one takes about twenty minutes.
Take a blank page. Three columns.
Column 1: What it is. A specific thing inside your business. A pricing model. A service line. A team structure. A piece of positioning. A regular meeting that exists for reasons nobody is quite sure of.
Column 2: When you decided it. Honestly. If you can't remember when, write never properly. If you decided it under different conditions than the ones you are operating in now, note that too.
Column 3: Is it chosen, drifted, or load-bearing? This is the column that matters.
Chosen means you'd make the same call today. Leave it.
Drifted means it's inertia. It's a decision waiting to be made.
Load-bearing is the category most operators miss: things that look like defaults but are actually holding judgement, standards, or relationships you have never made explicit. These are the most dangerous to tidy up without examining first.
Here's what one row might look like:
What it is | When decided | Status |
|---|---|---|
Monthly retainer pricing (day-rate × 3) | 2019, when we had no leverage and needed predictable cash | Drifted. We now have a waitlist. Pricing no longer reflects demand or value delivered. Decision waiting to be made. |
Work through four areas: pricing, positioning, structure, and the things you offer. Don't fix anything yet. You're not optimising. You're seeing.
When you're done, look at column three. The chosen items can be left alone. The drifted items are decisions waiting to be made. The third category is where the slow, careful work begins.
That third category is also where most "let AI handle it" initiatives quietly destroy value. Worth knowing before you get there.
Know someone running on defaults they haven't examined? Forward this to them.
Running Cost is the newsletter from lifestack. Claire and Steve are the co-founders. lifestack is the practice, and the tool that holds it, for operators who want to build seriously without it costing them everything else. We are building it in public. This is us, working it out.