The Bakery Doors Are Open

The doors to Little Loaf Bakery are open.

Updated September 10: this post records the opening prototype. The financing explanation below has been corrected; batch sizes, prices, and market limits remain the historical examples from that opening, not a current play guide. Read From a Bakery to a Company for the latest features.

New players in Megacorp Empire now begin with a lender-financed bakery, one oven, and $500 of working capital. Brook Mill has flour for sale across the neighborhood. Corner Café has a breakfast crowd to feed. Between them sits the first complete business in the game: buy, make, sell, and understand what happened to the money.

This is not the whole empire compressed into a tutorial. It is the first working chapter and the foundation we can safely build on.

Your first morning, step by step

The opening is lender-financed: a $5,000 advance pays for a $4,500 equipped bakery and leaves $500 to get the business moving. That cash is not revenue or profit, and the loan remains a company liability.

Brook Mill sells flour for $1 per kilogram. You can buy 20 kilograms for one batch or stock up with 40 kilograms for two. The game will not let you spend so aggressively that you forget the $20 needed to operate the oven. That small guardrail introduces the first important distinction: owning ingredients is useful, but ingredients are not cash.

One batch uses 20 kilograms of flour and a further $20 of operating costs for other ingredients, energy, and kitchen hire. After 30 seconds, the oven produces 40 loaves. The flour has not vanished economically; its cost has moved into work in progress and then into finished bread on the rack.

Corner Café buys 40 loaves at $2.50 each. Delivering the batch brings in $100. The bread cost $40 in total to make—$20 of flour and $20 of operating costs—so the receipt shows $60 profit.

The arithmetic is intentionally approachable:

• $40 batch cost becomes 40 loaves
• $100 sale returns the batch cost and adds cash
• $60 profit records what the business earned after those costs

The important part is not solving the subtraction. It is seeing when each value changes and why.

Why the actions stay separate

We could have reduced the entire loop to a button marked “Run bakery.” It would have been faster, and it would have removed most of the game.

Buying, baking, and selling are separate because they represent different commitments. Buying flour moves cash into raw materials. Starting the oven commits those materials and another operating payment to production. Finishing the batch creates inventory. Delivering it exchanges that inventory for cash and records the result.

Separating the actions creates room for future decisions without inventing a different game later. More suppliers, products, and customers only matter if purchasing, production, and sales are already meaningful.

The current loop is simple by design, but its shape is meant to last.

A market with boundaries

Brook Mill and Corner Café are non-player businesses with limited offers. The mill begins each market window with 100 kilograms of flour. The café can buy up to 80 loaves. Every two minutes, outside deliveries refill the mill and the café's customers create fresh demand.

Missed windows do not pile up. The mill does not accumulate infinite flour while you are away, and the café does not owe you an ever-growing backlog of orders. Your own flour and bread remain saved without spoilage, but the external opportunity resets.

The neighborhood refreshes, yet nothing purchases, produces, or sells on your behalf. When you return, your ingredients and finished bread are where you left them.

Prices are fixed in this opening build. Brook Mill always charges $1 per kilogram and Corner Café always pays $2.50 per loaf. Dynamic pricing may become interesting later, but it would make the first test harder to read. Before asking whether a changing price is fair, we need to know whether the player understands the product flow at all.

Making time useful

The oven takes 30 seconds to finish a batch, and the timer persists. You can leave the page or close the browser; when the bakery reconnects, a completed batch moves onto your rack.

This is an early answer to a larger design question: how can time matter without demanding constant attention? The bakery does not run itself. It simply respects the time that passed after a decision you made.

The receipt matters

After a delivery, the game shows more than “+$100.” The receipt separates sales from profit and explains the cost of the bread sold. It also keeps the opening financing in the right category: borrowed cash is not presented as something the bakery earned.

That may sound like a small interface detail, but it protects the central promise of the game. If revenue and profit blur together in the first sale, every later financial system will rest on a false understanding. We want a player to be able to look at the bakery and answer four different questions:

• How much cash can I spend now?
• What ingredients and finished goods do I own?
• What did the customer pay?
• What did the company actually earn?

The answers are related, but they are not the same number.

What this version taught us

Building the loop forced abstract ideas to become physical. Flour lives in storage, bread lives on the rack, the oven changes while a batch is active, and the mill and café show their limits beside the next refresh. The header reports when an action is being saved and reconnects to the server's state.

The strongest lesson is that accounting becomes easier when it follows the story of an object. A player does not need to begin with debits and credits. They can begin by watching $20 become flour, watching flour enter an oven, and watching finished bread leave in exchange for payment. The ledger underneath can remain rigorous because the surface has a narrative.

What is not here yet

The original opening focused on one supplier, one recipe, one oven, one customer, and fixed prices. Setting a bread price, hiring staff, adding another production line, selling directly to consumers, negotiating additional loans, buying the mill, and competing with another player were outside that opening's scope.

Those omissions are not hidden. Some are future directions we want to explore; others may change as playtesting tells us what deserves depth. The bakery's job is to prove the operating foundation first.

The next useful improvements are the ones that make the current decisions clearer and more satisfying. After that, we can test which new constraint adds the most: another customer, a capacity choice, a variable price, or a supplier relationship. Each addition should change how you think, not merely add another button.

Come run the first batch

The prototype is free and playable in your browser. Open your bakery, buy flour, keep enough cash for the oven, and make the first delivery to Corner Café. Follow the quantities and prices shown in the game; the opening examples above are a record of an earlier build.

If you want the wider design philosophy behind this small beginning, read Hello, Empire. We will keep using this devlog to show what changes, what we learn, and how the road beyond the bakery takes shape.

The doors are open. The first customer is waiting.