The week a wholesale account doubled its order and nearly cost me the account
A microgreens teardown built around the decision, not the outcome: what happens when a wholesale account asks for close to double on the next order and a fixed growing cycle means you cannot make more in time. Kept qualitative because the ledger records the situation but no figures; the only numbers are the recorded "five to ten accounts" range and the "doubled" framing from the idea.
The message
It arrived the way the good orders usually do. Not a phone call, a message, dropped into the same thread as everything else. An account I was glad to have wanted more. A lot more, close to double what they had been taking, and they wanted it on the next order.
For about a second, that is nothing but good news. Someone likes what you grow enough to build more of it into their week. Then you do the sum in your head, and the good news turns into a problem you cannot fix by working harder or sleeping less.
I couldn't grow it any faster.
The clock you can't reset
This is the part that is hard to explain to anyone who has never produced anything on a living schedule. Microgreens grow at their own pace. You sow, and the crop takes the days it takes. Wanting it sooner does not move that date forward, and neither does paying more for it or staying up later.
So when a doubled order lands for "the next order", the honest answer is that some of it does not physically exist yet, and cannot be made to exist in time. What I had coming was already sown. Whatever I had not started, I could not conjure.
I was the whole operation back then. I did the growing, the packing, the deliveries and the invoicing, all of it myself. There was no spare capacity sitting in a fridge waiting to be sold. There was what I had planned to grow, and that was the whole of it.
The decision, not the outcome
Here is where it stopped being a scheduling puzzle and became a choice about people.
At my busiest I was supplying somewhere between five and ten accounts. Every one of them had asked for a certain amount, and every one of them expected roughly that amount to turn up. The trays coming out of the next cycle were, in effect, already spoken for.
To fill the doubled order in full and on time, I would have had to take the shortfall from somewhere. That somewhere was other people's orders. Accounts that were already on the book, already relying on me, already building their own week around what I had promised them.
So the real question was never "can I grow more". It was "who do I disappoint". The new volume, or the customers who were there first.
That is the decision the whole week turned on, and no amount of good intentions made it go away.
What I told them
I had spent about a decade in kitchens before any of this, most of it on the receiving end of producers. I have been the chef waiting on a delivery, and I know exactly what a shortfall feels like at that end. A quantity you were promised does not arrive, and now there is a hole in the menu at service with no time left to fill it. That is not a mild inconvenience. That is your evening broken.
Which is why the tempting answer, say yes to everyone and hope it works out, is the one that actually loses you the account. Hope is not a growing method. If I had promised the full doubled order and delivered short with no warning, I would have let down the new demand and the existing accounts in the same week.
So I did the less comfortable thing. I told them what I could do now and when I could do the rest. Part of it on the next order, the balance once the following cycle came through.
A chef can plan around "half this week, the rest next week" if you tell them early enough. They put it on the specials board, they hold a dish back, they order something else alongside. What they cannot plan around is a yes that turns into a gap on the day, discovered at the pass. A delay you flag is a scheduling note. A shortfall you spring is a betrayal. Same missing trays, completely different relationship afterwards.
The crisis was really a planning gap
When I look back, the thing that made that message land like a crisis was not the growing cycle. The growing cycle is just physics, and you learn to work with it.
It was that I was planning production from scattered messages and memory. Orders and changes came in across different threads, at different times, from different people. So-called standing orders rarely stood, and the recurring order was a fiction I kept alive by hand. I did not have one clear view of what I had already committed to across all those accounts.
That is why a big new ask felt like an ambush. It collided with promises I had already made, but the collision was invisible until I sat down to plan the sow and finally saw everything in one place. By then the choice was already forced.
The fix is not a cleverer growing method. It is being able to see, before you answer, what you have already promised and when it is due. If a doubling request lands and you can look at the full picture in a few seconds, "yes to part of it now, the rest by this date" stops being a panicked calculation and becomes a normal reply.
That is the gap makeweek is built to close: your orders and standing orders in one place instead of buried across a dozen threads, so a big new ask lands on top of a picture you can actually see. It will not grow the trays for you. Nothing will. But it means the hardest decision of the week arrives with the facts attached, and early enough to be a decision rather than an apology.
What I'd take from it
The order that nearly cost me the account did not cost me the account. Being straight about what I could and could not do is what kept it.
If you sell something that takes time to make, the lesson holds whoever you are. You cannot compress the making. You can only decide honestly who gets what and when, and tell them before the day it matters. The producers who keep their trade are not the ones who never run short. They are the ones whose customers were never surprised by it.