When a spreadsheet is evidence of a startup opportunity

Founders often encounter intricate workbooks and see a product waiting to be built. Some do contain costly coordination problems. Others are effective tools maintained by people who understand their limitations. The relevant question concerns the work and risk around the spreadsheet.

Identify what the workbook makes possible

List the decisions supported, the inputs required and the people relying on its output. Distinguish calculation from coordination. A simple formula may be reliable while collecting the input takes several days.

The GOV.UK approach to planning user research starts with questions and assumptions. Here, the assumption to test is that the workbook creates more burden than the proposed replacement.

Observe version disputes, copying, access problems and corrections. Do not infer error rates from the number of tabs or the visual complexity of the file.

Understand why the current tool survives

The workbook may be easy to change, usable offline or familiar to the finance team. A new application that removes those advantages may lose even if it looks more sophisticated.

Consider an illustrative Malaysian services company maintaining project margins in Excel. Its main concern may be that only one employee understands the model. A documented process and controlled input sheet could solve the immediate risk more cheaply than a new subscription.

A founder should be willing to discover that result. It prevents development around a problem the customer can resolve without the product.

Test replacement at the decision boundary

Choose one recurring output and compare how the existing and proposed methods produce it. Include setup, correction and explanation time. Ask whether the customer can inspect how a result was obtained.

A sensible prototype might initially export a familiar workbook rather than demand a full process change. That can help isolate the value of better data collection from the disruption of replacing the final reporting tool.

A replacement comparison should include who maintains the current workbook and who would maintain the proposed service. If the new product still requires exporting, repairing and reconciling the same inputs, the expected improvement needs a more specific explanation. The presence of software on both sides does not settle the comparison.

GAT’s enterprise pilot guide connects tests to a buying decision. A spreadsheet opportunity deserves the same discipline: evidence that a defined customer gains enough from changing the process to justify the change.