Internal tools · SOULTWARE LLC
When a spreadsheet is no longer the system of record
Spreadsheets are excellent for analysis. They become fragile when they are also the place where work is assigned, approved, and reported as done.
Several copies are already in circulation
The warning sign is not that a workbook exists. It is that people keep private copies, rename columns, and disagree about which file is current. A shared link does not fix that if two people can overwrite the same row without a record of who changed it.
Look at one recent job. If reconstructing what happened requires the workbook plus an email thread plus someone’s memory, the sheet is no longer a reliable record.
Approval lives in an inbox
A status column that says “waiting” is incomplete when the real status is a message nobody else can see. The next person does not know whether they can proceed, and the approver cannot see the queue without being asked.
An internal tool is useful here when it gives the request one owner, one status, and a place for the decision. The email can still notify people. It should not be the only place the decision exists.
The first release can be a single record
The smallest useful system lets someone create the item, fill the fields the team actually needs, assign it, and move it from one agreed status to the next. Files that belong with the item should sit on the same record.
Charts, bulk imports, and connections to other products can wait until the team trusts the record. Adding them first often recreates the spreadsheet, with more screens.
Name the person who will keep it accurate
Software does not retire a workbook by itself. Someone has to stop accepting the old file as proof, train the people who use the new record, and decide what happens to the history left in the sheet.
Soultware builds internal tools for this kind of handoff. The scope starts from the workbook and the exceptions around it, not from a generic feature list.