Central record
One clear source for entities, states and owners.
When the spreadsheet carries too much
I help turn shared spreadsheets, fragile formulas and manual steps into a small tool that keeps the useful workflow and reduces avoidable errors.
Problem it solves
Excel works well until multiple users, states, permissions and integrations turn the sheet into an accidental application.
The transition should identify which part needs software and which part can remain an export or one-off analysis.
Investment decision
Several versions exist and nobody knows which is current.
Formulas or macros depend on one person.
Data is copied from forms, email, CRM or ERP.
History, permissions or consistent validation are needed.
Frequent work
Scope should start with an observable problem and a clear way to verify the improvement.
One clear source for entities, states and owners.
Tasks, reviews and state changes with history.
Rules at entry instead of corrections at the end.
Keep Excel where it remains useful without using it as the operational database.
Possible scope
Working criteria
Execution
I review the spreadsheet and how it is actually used.
I separate data, rules, reports and tasks.
I build a first version for the frequent path.
I migrate in phases and retain a safe exit while validating.
Useful context
No. A gradual transition validates the workflow and keeps exports while the tool earns trust.
Yes, after reviewing format, duplicates, missing values and rules hidden in formulas or macros.
By users, workflows, data, permissions, integrations and exceptions rather than the number of sheets or columns.
Next step
You do not need a formal specification. Who uses it, what they copy and where it fails usually reveals a sensible first version.