Bez Glutenu Piekarnia
Five years of bakery wisdom — finally queryable
A small artisan bakery had years of WhatsApp threads, supplier contacts, and recipe tweaks living in the founder's head. CompanyAura turned it into a wiki every baker on shift can search.
Project overview
The kind of team this fits:
- Small operations (bakeries, restaurants, agencies, studios) where the founder holds most of the operating knowledge
- Teams running on WhatsApp, Messenger, or Slack — not on a wiki
- Businesses where every supplier change, recipe tweak, or process change lives in a chat thread somewhere
The problem
"Everyone called me. The flour supplier changed the spec — call me. New baker doesn't know the proofing time — call me. I couldn't take a week off without the bakery slowing down."
Five years of recipe tweaks, customer-feedback adjustments, and supplier negotiations were captured in WhatsApp threads — but only readable by the founder. The team kept asking the same questions on rotation.
What changed at Bez Glutenu
Three shifts that pulled the bakery's brain out of one head and into a wiki the whole team uses.
Bus factor went from 1 to 7
Every baker on shift can now answer customer questions, dose recipes, and contact suppliers without paging the founder. Vacation is finally possible.
42 recipe SOPs auto-drafted
Every recipe with its history: original spec, tweaks over five years, why each tweak was made, and the WhatsApp thread that proves it. Bakers read the page, not the founder's mind.
Suppliers in one place
Every supplier — flour, packaging, allergen-free certification — with the right contact, current price, last conversation, and why we use them. No more "who do we call for X?"
What was breaking
The bakery ran on WhatsApp
Orders, recipe tweaks, supplier negotiations, customer complaints — all in chat threads. Searching for "what did we change about the sourdough proofing in 2023" meant scrolling for an hour.
One person held all the context
The founder was the wiki. Every supplier relationship, every recipe iteration, every "why we stopped using X" — only she could answer. Onboarding a new baker took months of "ask if you're unsure."
The same questions came back every week
"What's the hydration ratio for the rye bread now?" "Which packaging supplier did we switch to?" Asked, answered, forgotten, re-asked. No place to write it down — and no time to write it down.
Vacations slowed the bakery
A week off meant texts every hour: "what does X mean," "who do we call about Y." Real rest was impossible until the brain became a wiki.
Our approach
One simple idea framed the whole project:
"The founder's head is the dataset. Let's just compile it."
Don't ask the founder to write SOPs. Read the WhatsApp history, draft the SOPs, let her review. The wiki gets written from how the bakery actually runs.
The solution, from the inside
Four pieces that turned a founder's head into a wiki seven bakers can use.
WhatsApp ingest of five years of history
CompanyAura processed the WhatsApp Business export. Recipes were grouped by product, supplier contacts by category, customer feedback by month. The first wiki had 42 recipe pages, 18 supplier pages, and a 60-page "how we run the bakery" section — all citing the original WhatsApp threads.
The founder reviewed 120 draft pages in two evenings. Most just needed a green tick.
Recipe pages with full iteration history
Every recipe page lists the current spec at the top — and below it, every tweak made in the last five years, with the WhatsApp date and the reason. "Hydration upped to 78% in March 2024 because the new mill flour absorbs more."
New bakers see why a recipe is what it is, not just the numbers.
Searchable on the shop floor — via Claude
The team queries the wiki through Claude on their phones. "What's the rye bread hydration?" gets the page, the number, and the iteration history — in seconds. The founder gets messaged maybe once a week now.
Phone in flour-dusty hand → answer in five seconds.
Quiet, ongoing maintenance
The team kept using WhatsApp. CompanyAura keeps watching. New recipe tweaks get folded into the existing pages with a one-line edit suggestion the founder approves in the morning. The wiki stays current without anyone "doing documentation."
Five minutes of approvals over morning coffee replaces "write the SOPs someday."
"Half my day used to be phone calls — where's the flour, what time for what, which supplier. Now they ask CompanyAura. I'm back to actually running the business — or just enjoying life."
Bez Glutenu Piekarnia
Artisan gluten-free bakery · 7 people · founder
Is your team's brain in one head too?
If most of the "how we run things" lives in chat threads and the founder's memory, we'd love to talk. Two weeks to first useful wiki.
hello@companyaura.com