Most retail chains in India weren't built off a playbook. They were built by someone who opened the first store, figured it out, opened the second, figured out what was different, and kept going. By the twentieth, or even the fiftieth store, an enormous amount of what makes the business work exists in people, not in documents. That's not a gap. It's simply what building something from scratch looks like.

It also means that consistency, in the early years, comes from a founder or a small group of experienced people who are personally involved in how every store runs. That works well, for a long time, because they know the business better than any document could capture.

Why consistency starts to look different as a chain grows

When a founder or a senior manager knows every store personally, knowledge travels at the speed of conversation, and at a smaller number of stores, that's fast enough. As the chain grows, there are simply more stores, more new hires, and more situations to walk through, so the same amount of personal involvement has to stretch further.

A few things tend to show up naturally around this point:

• A new manager gets trained by whoever happens to be available that week, so the same role is explained a little differently depending on who's doing the explaining
• A senior team member handles a certain kind of situation (a tricky customer, a supplier issue) very well, simply because they've seen it before, and that judgment stays with them rather than becoming something every store can draw on
• An issue that comes up in one store gets solved there, and a similar issue in a different city, a few months later, doesn't get connected to it, since there's no shared view across locations

None of this reflects a failure of process. It's a natural result of a business that grew by doing rather than by documenting, which is how a large share of successful retail chains actually grow.

What this tends to cost, quietly

There isn't a line item for the hours spent repeating a training session that's already been given many times before, or for solving the same kind of issue locally, over and over, instead of once. That time exists, though, and it's usually time that could otherwise go toward the next store, rather than maintaining the ones that already exist. It's easy to overlook, mainly because it never arrives as a single expense. It arrives an hour at a time, spread across many small moments each week.

How some retail chains approach this as they scale

The usual first instinct is to write more detailed SOPs, and that helps, up to a point. Written SOPs cover the "what." They rarely capture the judgment behind it. The way a good manager handles an unusual situation, or the small exceptions that come up on the floor, tends to stay with the people who've learned it firsthand.

Some retail chains address this by building a shared system for capturing that knowledge (training content, SOPs, and store-level learning together), so it travels with the business rather than staying with whoever happens to hold it at a given time. In practice, this tends to change a few things:

• Training becomes more consistent because new hires learn from what the business has already worked out, rather than from whoever happens to be training that week
• Judgment built by experienced staff becomes something every store can draw on, not just the one they happen to be standing in
• A pattern across stores becomes visible the first time it repeats, rather than months later, at a review

A quick before and after

Before:

• A new store opens, and someone experienced trains the team in person, drawing on everything they've picked up store by store
• That knowledge stays mostly with the people who have it
• A recurring issue is solved locally each time it appears, without a clear view across the chain

After:

• A new store opens, and the team learns from what the business has already worked out
• That knowledge is available to whoever needs it, not only the people who built it
• A recurring issue is visible as a pattern early on, rather than after it's shown up several times

The takeaway

Building a retail chain by figuring it out, store by store, is how a large part of Indian retail actually got built, and it works well, often for far longer than a formal playbook would predict. The knowledge in a founder's head and a manager's instincts is real, hard-won capital. As a chain scales, it's worth asking what it would look like to make that same capital available to every store, instead of only the people who happen to carry it.

P.S. We work with retail leaders who've built exactly this kind of business, from the ground up, with no playbook required. Frontlyne exists to help that knowledge travel with the business, so it isn't limited to one person's week or one store's experience.