“Show me the spreadsheet” is good discovery
If you build software for smaller businesses, you probably already ask to see the files people use alongside their formal systems. Excel and Google Sheets can make existing calculations, exceptions and manual coordination visible. Sometimes the spreadsheet is effectively the working specification. That is valuable information for technical discovery.
But a spreadsheet is not evidence that the business needs a bespoke application. It may be inexpensive, transparent, flexible and entirely adequate. Converting it into software can add cost and maintenance without improving a business result.
The file has a boundary, just like the software brief
A spreadsheet represents an activity that someone has already chosen to track, calculate or coordinate. It says less about decisions that nobody currently records in one place. These may cross finance, operations, sales or customer service. The person who commissioned your original software may not own those decisions.
That is why technical discovery and wider business research are different tasks. Technical discovery establishes what a particular proposed system needs to do. Research before a new requirement exists examines whether there is a business question worth putting to the client in the first place.
Existing tools are not a diagnosis
One company can run an important operation in spreadsheets without difficulty. Another can have an expensive integrated system while still relying on the owner's memory to connect decisions across functions. Neither situation proves the absence of an organisational capability.
The relevant distinction is not Excel versus a database. It is whether the business has a reason to coordinate, know or decide something differently. That reason needs to be established with the people responsible for the activity before anyone proposes a build.
Where independent research fits
An existing developer often knows a client's systems well, including the unofficial ones. An outside-in review takes the project's known scope as a starting point, then considers the wider business and what can be established from public evidence. It may return a specific question for the developer to check with the client, or find no defensible reason to continue.
ProperBizFix offers that bounded review as an Account Screen for £50. It does not inspect code, access client systems, contact the end client or promise another software project. See how it works for independent developers and why a software brief has organisational boundaries.