No review needed, no catch. Just the founding price, locked in for as long as you stay subscribed.
When Two Became Five: How a Small Sourdough Operation Finally Got Its Paperwork Under Control
Growing a small sourdough operation from a solo hobby to a five-person team taught me more about systems than baking. Here's what actually changed.
Photo by Wesual Click on UnsplashThere's a specific kind of August chaos that hits small food businesses. The farmers' markets are packed, everyone wants sourdough for their garden parties and bank holiday tables, and somewhere in the middle of all that, you realise you've got three people making dough using three slightly different versions of the same recipe, written on the back of three different notebooks. That was us, roughly eighteen months ago.
What started as a Saturday morning side project, a few loaves for friends and a stall at a local market in East London, had quietly turned into something bigger. Five of us, a rented kitchen space, and a weekly output that had grown to the point where 'I'll just remember it' was no longer a viable system. This is the story of what happens when your baking outgrows your notes app.
The Problem With Growing Organically
Most small sourdough operations don't plan to scale. They bake, people love it, they bake more. That's a genuinely lovely way to build something. But it comes with a specific set of headaches that nobody warns you about, and none of them are about the bread itself.
Our recipes were technically consistent, in that the same person making the same loaf on the same day got the same result. But spread that across five people, different kitchen shifts, a summer heatwave that was making everyone second-guess their fermentation timing, and suddenly 'consistent' was doing a lot of heavy lifting. We had version drift. Not dramatically, but enough. One person's 'four sets of coil folds' was another person's three-and-a-half.
The real problem, though, was the numbers. Flour costs had gone up. We were buying in larger quantities, which helped, but nobody had sat down and properly worked out what each loaf was actually costing us to produce at scale versus at smaller batch sizes. We were pricing on feel, which works fine when you're making ten loaves, and becomes genuinely risky when you're making a hundred.
What Scaling a Recipe Actually Means
Here's something worth understanding if you're moving from home baking to any kind of production environment: scaling a sourdough recipe is not just multiplication.
Larger batches behave differently. A 5kg mix retains heat differently to a 500g one. Your starter percentage might need adjusting depending on ambient temperature and batch size. The time between mixing and achieving the same level of fermentation activity can shift, sometimes significantly. If you've only ever baked by feel and observation, scaling forces you to become much more deliberate about the variables you've previously left vague.
The practical advice here: before you scale up, document your current process in obsessive detail. Not just the recipe, but the ambient temperature when you mix, the dough temperature after mixing, what 'ready to shape' actually looks like for that batch size, and how long each stage genuinely takes. Build that baseline, then adjust methodically when you change batch size. Treat it like debugging. Change one variable, observe the result, adjust again. The bakers who struggle most when scaling are the ones who change three things at once and then can't work out what went wrong.
Getting the Team Onto the Same Page
The version drift problem mostly solved itself once we had a shared, living document that everyone could access and that reflected our actual current process rather than the process from eight months ago. But we also needed the cost side to make sense.
That's where DoughRise Bakery came in properly. The commercial batch scaling tools meant we could put our recipes in once and have them scale correctly for whatever quantity we were producing that week, without someone manually doing the maths at six in the morning. The bakery cost reporting meant we could actually see, clearly, what each loaf was costing us as ingredient prices shifted through the summer. And the team accounts, up to five, meant everyone was working from the same version of everything, not their own slightly evolved copy.
It's not glamorous stuff. But running a food business without a clear picture of your costs is genuinely precarious, and the dedicated support meant that when we had questions about setting things up properly, we weren't left guessing.
What August Looks Like Now
We're still in a rented kitchen. We're still doing markets. The bread is still the thing that matters most, and honestly, the team makes better and more consistent loaves now than we did eighteen months ago, partly because they have clearer recipes to work from, and partly because we've removed a lot of the ambient stress that comes with not knowing whether the numbers are working.
If you're at that point where your baking is good, people want more of it, and the operational side is starting to feel like it might swallow you whole, the answer is rarely to bake better. The bread is usually fine. It's the systems that need attention.
Get those in order and you get to spend your August actually thinking about the next loaf, rather than trying to remember which notebook has the current recipe in it.
Ready to give it a go?
Find DoughRise Bakery, with commercial batch scaling, team accounts for up to five, bakery cost reporting, and dedicated support, alongside everything else you need at doughrise.store.
Happy baking! Find everything you need at doughrise.store
Photo by Wesual Click on Unsplash
Continue reading
The American Recipe, the British Kitchen, and the Bake That Finally Made Sense
Sourdough Pizza with Roasted Tomatoes, Caramelised Onion & Taleggio: The Late-Summer Flatbread Worth Making on a Hot Evening
The August Loaf That Made Me Stop Guessing and Start Asking