Built for messy businesses

Real businesses rarely look like the diagram. They have a CRM that was introduced three managers ago, a Sage setup that finance understands better than anyone else, shared drives full of old versions, and old servers in the corner that nobody wants to reboot during trading hours.

There are forms that are technically obsolete but still useful. There are job sheets, customer trackers, price lists, renewal notes, and handover documents with names like "final-final-v3". There is usually a perfectly good reason for each one.

The official process might be in one system, but the operational truth is often spread across several places. Some of it is structured. Some of it is not. Some of it is in a spreadsheet because that was the fastest way to solve the problem at the time.

• Disconnected systems: CRM records, finance data, job history, stock notes, and customer emails that do not quite line up.
• File shares: SharePoint folders, network drives, PDFs, scans, and old templates that still carry business-critical context.
• Spreadsheets: trackers, imports, exception lists, forecasts, pricing sheets, and "temporary" tools that became permanent.
• Legacy systems: old databases and servers that still answer questions nobody has rebuilt elsewhere.

Every SME has some version of Dave. It might be Sarah in finance, Imran in operations, Jo on customer service, or the person who has been quietly fixing the same awkward exception for eight years.

That tribal knowledge is valuable. It is also fragile. When the answer depends on finding the right person at the right time, the business is carrying risk it may not be able to see. AskBob is interested in making that knowledge easier to find, easier to question, and easier to pass on without pretending people are the problem.

Operational chaos is not always failure. Sometimes it is the history of practical decisions made under pressure. A workaround kept a customer. A spreadsheet saved a department. A file share became the place people trusted because the official system did not quite fit the work.

The danger comes later, when nobody can tell which parts are deliberate, which parts are accidental, and which parts are now holding the business together through habit alone.

AskBob is designed for imperfect environments. It should not require a business to clean everything up before it can be useful. It should help people understand what is already there: the systems, documents, exceptions, relationships, gaps, and judgement calls that shape the day-to-day operation.

That means being practical about sources, honest about uncertainty, and respectful of the people who know the business. AskBob should help teams see the shape of their operation more clearly before they decide what to fix, migrate, document, automate, or leave alone.