Hello, Empire

Every empire needs an origin story. Ours begins with a lender-financed bakery, one oven, $500 in working capital, and a café waiting for fresh bread.

Updated September 10: the financing description has been corrected. The rest of this post describes our original opening prototype and its ambitions. For the latest chapter, read From a Bakery to a Company.

That beginning is deliberately modest. Megacorp Empire is meant to become a business simulation about building, operating, financing, and connecting companies. But a large economy is only interesting if running one small company already creates decisions worth caring about. Before there can be an empire, there has to be a business.

Today, that business is Little Loaf Bakery.

What you can play today

The current free browser prototype contains one complete operating loop. You open Little Loaf, buy flour from Brook Mill, turn it into bread, and sell a finished batch to Corner Café.

The loop is small, but the parts are real and visible:

• Your bakery begins with a fixed amount of cash
• Flour costs money and remains in storage until you use it
• Baking consumes flour, cash, and time
• Finished bread sits on your rack until you decide to sell it
• A completed delivery produces revenue, cost of goods sold, and profit
• Your bakery is saved, so you can leave while a batch is baking and return later

There are no automatic sales and no invisible manager making the useful decisions for you. Cash becomes an ingredient. An ingredient becomes inventory. Inventory becomes a sale. The point is not to make the numbers disappear; it is to make their movement understandable.

That is the whole public game right now. It is an early prototype, not a miniature version of every system we eventually want to build.

Why begin this small

It would be easy to describe a giant economy first: suppliers bidding for contracts, competitors changing prices, banks assessing risk, investors demanding returns, and companies buying stakes in one another. Those ideas are exciting. They are also several layers removed from the question that matters most:

Is it satisfying to operate the business underneath all of that?

The bakery gives us a clean place to answer it. There is one raw material, one production step, and one customer. When something feels unclear, there are very few places for the problem to hide. If buying flour is confusing here, adding a dozen suppliers will not improve it. If earning the first dollar does not feel meaningful, a larger balance sheet will only make the emptiness harder to diagnose.

Starting small also lets every object have a home. Flour appears in storage. The oven shows when production is active. Bread appears on the rack. Cash, stock, sales, and profit are visible together. The interface can tell a business story instead of presenting a wall of unrelated figures.

What makes it a business simulation

The fantasy is not simply “watch a number rise.” It is deciding where money should go and then living with the consequences.

Even the opening loop contains the beginnings of that idea. Money spent on flour is no longer available cash, but the flour still belongs to the company. Baking requires another operating payment before the bread can be sold. Buying two batches of flour may be efficient, but only if enough cash remains to run the oven. Finished stock has value, yet it cannot pay for the next action until a customer buys it.

Those distinctions matter because revenue, profit, cash, and inventory are not interchangeable. A business can make a profitable sale and still create a cash problem with its next decision. It can own useful stock and still be unable to operate. It can have capacity and no customer. Megacorp Empire should make those tensions playable without asking people to study accounting before they can begin.

Our design target is simple to state and difficult to earn: the numbers should be legible enough for a new player, but connected enough that an experienced player can form a plan.

The larger ambition

Little Loaf is Chapter 01, not the permanent boundary of the game.

We are exploring a wider economy with more ways to sell, additional production capacity, changing market conditions, connected farms, mills, restaurants, and other businesses. Farther beyond that are questions of debt, ownership, control, and what happens when one company depends on another.

Those are directions, not promises of features available today. They will only deserve a place in the game if the underlying operating decisions are enjoyable and understandable. A complicated system is not automatically a deep one, and a long feature list is not the same thing as a living economy.

The bakery is therefore more than a tutorial. It is the test bench for the larger game. Can a supplier feel like part of a market instead of a shop button? Can a production timer communicate commitment without becoming busywork? Can a sales receipt make profit clearer? Can a player understand why cash moved without opening a separate accounting screen?

Every future layer has to build on those answers.

Principles for the road ahead

As we develop the game, a few principles will keep the ambition grounded:

• Operating comes first. A company should make or provide something before finance enters the picture.
• Money must have a path. Purchases, production, inventory, sales, and profit should connect visibly.
• Time should create decisions, not chores. A committed batch can finish while you are away; the game should not punish you for having a life.
• Growth should change the problem. A larger company should create new trade-offs rather than simply producing a larger number.
• Future systems must earn their complexity. Markets, loans, ownership, and competition belong only when they make the player's choices richer.

What we want to learn

The most useful feedback at this stage is concrete. Did you know what to do next? Did the first purchase make sense? Did waiting for the oven feel like anticipation or interruption? After the delivery, could you explain where the profit came from? Did anything make you expect a feature that was not there?

Those answers are more valuable than asking whether the prototype already feels like a finished empire. It does not, and it should not pretend to.

Megacorp Empire is free to play in the browser while we build this foundation. These devlogs will document what changes, why we made the trade-offs we did, what did not work, and which larger ideas remain on the horizon.

If you want to see the current game rather than the vision, open Little Loaf Bakery. For the exact thinking behind its first operating loop, read The Bakery Doors Are Open. You can also follow future notes through the RSS feed.

Every empire starts with a dream. This one starts with a working business.