OpsAuditTraditional business case study
The owner knew everything.
He was also the single point of failure.
How a family-run billboard business turned 30 years of institutional knowledge into software that any team member can use. A 3-hour process now takes 8 minutes.
3 hrs → 8 min
for every proposal
1 person
previously holding all operational knowledge
1 insight
starting point: a son recognising a risk his parents couldn't see
The business
A family-run outdoor advertising business operating in India. Established, profitable, and well-regarded in their market. The owner had built the business over decades and knew every aspect of the operation: which roads performed best for which advertiser categories, the full history of what had been charged to each client, which billboard faces had the best visibility at different times of day. This knowledge was the foundation of the business. It was also entirely locked inside one person.
The problem
The knowledge that built the business lived nowhere but one person's memory.
Building a proposal for a new client required the owner's direct involvement. He had to remember or find which billboards were available, recall what similar clients had been charged in the past, identify which locations matched the brief, and then assemble the proposal document by hand. Every single time.
If the owner was in a meeting, on holiday, or simply unavailable, the business slowed down. Proposals took hours because there was no system to hold the information. There was just memory.
Beyond proposals, the same problem existed throughout the business. Client preferences. Historical performance data. Pricing rationale. Inventory details. All of it existed only in the owner's head or in scattered papers and informal notes.
The risk was clear to anyone looking at the business from the outside. The owner himself was less concerned, because the business was working. Why fix what is not broken?
The introduction
The owner's son brought us in. He had been watching the business for years and understood the risk his parents could not fully see from the inside. The business depended entirely on one person. If that person retired, became ill, or was simply unavailable for an extended period, the operational knowledge would be gone.
The owner was skeptical. He had seen technology fail before. He was skeptical of paying someone in India to build something he was not sure the business needed. The son convinced him to give it one project.
This is the honest version of how most traditional business engagements start. The decision-maker is skeptical. The champion is the person who can see the risk clearly.
The build
How we worked
The first session was spent entirely learning the business. Not the technology. The business. How proposals were actually built. What information the owner used and where he found it. What the edge cases were. What made a good billboard location for which kind of advertiser.
Only after understanding the operation fully did the build begin. This is not standard practice for most development engagements. It is the only way to build something a traditional business will actually use.
By the end of the project, the owner was the most enthusiastic user of the system he had been skeptical about building.
What changed
Proposals that took 3 hours now take 8 minutes
Any team member can build a proposal without the owner's involvement
30 years of pricing history is queryable in seconds
The business no longer depends on any single person being available
The knowledge that built the business is now in a system that will outlast any individual
Additional outcome
This project is the direct origin of Adgrid, a SaaS product built for the OOH advertising industry. The operational problem solved here exists across every independent billboard operator and OOH agency. The product is the productised version of this engagement.
What this shows
The hardest part of this engagement was not the technology. It was convincing the people running a successful business that the way they had always done things was a risk they should not be carrying.
When knowledge lives in one person, the business is not a business. It is a person doing a job. The difference matters when that person retires, is unavailable, or wants to bring in new staff who can operate independently.
The technology is not the point. The point is that the business survives and grows beyond the person who built it.
Is your business carrying the same risk?
The blueprint identifies exactly where knowledge needs to be captured and what systems need to be built to hold it.