
Imagine knowing exactly where everything is.
Sally Brown's husband is going to collect the cake next Tuesday at 2:30.
Not next Wednesday at 4pm. Tuesday. 2:30.
You said it out loud on the way home, into your phone, because that is when she called. And now it is filed.
Not photographed and buried in your camera roll. Not jotted on the back of an envelope that will be in the recycling by Thursday. Not on a Post-it note that was on the noticeboard until it wasn't.
Filed.
Against Daisy's cake.
With everything else about Daisy's cake.
Imagine that.
WHAT "EVERYTHING ELSE ABOUT DAISY'S CAKE" ACTUALLY MEANS
Because there is a lot of it. There always is.
There is the inspiration image Sally brought in on her phone, that you photographed and then worried about finding again.
There is the long conversation about the cake itself, the wavering back and forth between the chocolate cake with white chocolate decorations and the strawberries and cream with the acrylic cut-out that says Daisy is 5, and the way Sally kept saying she would think about it and then calling back with new thoughts.
There is the note about the extra small cake, the one for the private family gathering after the party children went home, just for the grandparents and the aunties, added almost as an afterthought at the end of a conversation about something else entirely.
There is the deposit. How much it was. When it was paid. How much Mr Brown needs to hand over when he arrives at 2:30 on Tuesday, slightly harassed, probably running a few minutes late, hoping this is going to be straightforward.
And it is going to be straightforward.
Because you know exactly where all of this is.
It has been no trouble to keep. It will be no trouble to find.
THE PART THAT USED TO BE TROUBLE
For years, information in my own commission businesses lived everywhere and nowhere simultaneously.
An inspiration image could be somewhere in a camera roll, between a photo from a different client and a screenshot of a supplier's price list.
A deposit amount might be in a note on a phone, or possibly in a message thread, or written in the job book in handwriting done in a hurry while the next client arrived.
The detail about the extra cake for the family gathering might be in your head, which feels fine at the time and considerably less fine at eleven o'clock the night before collection when you are trying to remember whether you actually confirmed a price for it or just said you would sort it.
None of this is carelessness.
It is what happens when information arrives at the speed and randomness of real life, and the only place available to put it is wherever is nearest.
The trouble is not capturing the information.
The trouble is that it lands in seventeen different places, and finding it later requires knowing which of those seventeen places it chose on that particular day.
WHAT ACTUALLY CHANGES
When every piece of Daisy's cake information lives in one place, something shifts that is hard to describe until you have felt it.
Mr Brown arrives on Tuesday.
He is a few minutes late. He is slightly harassed. He asks, as people do, whether everything is confirmed for the small family cake as well, just checking.
In the old version of this moment, you feel a flicker.
You think you said yes to a price.
You think you wrote it down.
You are almost certain you confirmed it.
In the new version, you already know.
You did confirm it.
The price is there, next to everything else about this commission, in a record that took about forty seconds to update when the call ended.
You tell him the total with complete confidence.
He pays.
He leaves with the cakes.
It took very little extra effort to make that moment feel effortless.
It happened because the information was captured when it existed and stored where it could be found when it was needed.
That, for me, is what a useful system should do.
Quietly make the ordinary moments in a commission easier.
"BUT I'D HAVE TO REMEMBER TO USE IT"
This is one of the difficulties with any system.
It only works if you actually use it.
And that means the amount of friction involved matters enormously.
When I started thinking seriously about this in my own engraving business, I didn't want another complicated piece of software that required me to stop what I was doing and "do the admin".
I needed to be able to capture information at the point it arrived.
So the system I eventually built for myself uses simple forms I can open from my phone.
If somebody gives me information while I'm out, I can capture it there. If there's an image or document relating to the job, it can be stored with the job. If something changes, I can record the change while it's still fresh.
The important bit isn't the technology.
It's that I've reduced the distance between "I need to remember this" and "this is now somewhere I can reliably find it again."
Because the greater that distance becomes, the more likely I am to think I'll do it later.
And "later" has never been a particularly reliable filing system.
THE PART THAT TAKES ALMOST NO EFFORT
You did not organise Daisy's commission.
You ran it.
You took the calls, had the conversations, made the decisions, baked and decorated and delivered something beautiful.
The organising happened alongside it.
The deposit is recorded because you logged it when it was paid.
The collection time change is captured because you recorded it when you heard it.
The extra family cake is there because you added it after the call, instead of trusting yourself to remember it later.
When Mr Brown arrives on Tuesday, slightly late and slightly harassed, you are calm.
Not because you have a brilliant memory.
Because you have somewhere reliable for things to live.
That is the whole difference.
And it is a bigger difference than it sounds.
SOMEWHERE RELIABLE FOR THINGS TO LIVE
I originally built my own system because I needed it in my engraving business.
I've continued developing it as I've used it, because real businesses have a habit of exposing the things that looked perfectly sensible when you first designed them.
And I've learned something quite important from doing that.
The cleverest part of a business system isn't necessarily what it can do.
It's how little it asks you to do in order for it to be useful.
I'm currently rebuilding and testing the next version of mine, and I'll share more about it when I'm ready.
But whatever you use - a notebook, a spreadsheet, a CRM or something you've built yourself - I think this is a useful test:
When Sally Brown rings while you're on your way home and changes the collection time to Tuesday at 2:30, how easy is it to put that information somewhere reliable?
And when her husband walks through the door on Tuesday, how easy is it to find it again?
Those two moments tell you quite a lot about whether your system is actually working for you.
Rosie
