7 Signs Your Business Has Outgrown Spreadsheets (And What to Build Instead)
Start with the workbook you use: who edits it, which checks fail and how much time reconciliation takes. Replace a workflow only when its measured constraints justify the migration work.
A replacement deserves review when your workbook cannot support required permissions, validation or workflow steps. Measure reconciliation time and billing errors, check whether existing tools can fix them, then compare migration and operating costs. There is no universal headcount, weekly-hours threshold or annual loss for spreadsheet users.
1. The 7 Critical Warning Signs
If Sarah is the only person who understands column AD, document the formula and test it with another team member. Include this handover in any replacement scope; undocumented rules will also cause problems in custom code.
Log the minutes spent copying records, checking billable hours and preparing reports over a representative period. Identify which steps a formula, import or existing integration can remove before commissioning a portal.
Someone accidentally drags an incomplete formula or inserts a row, silently skewing monthly revenue totals. You only discover the error three months later when an accountant asks why invoices do not match bank deposits.
Shared online workbooks can support collaborative editing. Check whether your problem comes from exported copies, offline work or an unclear owner. Establish one authoritative file before treating concurrency as a software limitation.
Test what each role can read, copy and export, not only which cells it can edit. Google warns that protected ranges are not a security measure. Move confidential rates out of a shared workbook if its readers should not see them.
Review the history and administrative logs available in your current plan. If you need recorded approvals or tamper-resistant events, define those requirements and test who can alter or delete the records in both the current and proposed system.
Ask clients which tasks they need to complete themselves, such as approving a deliverable or finding an invoice. A portal is useful when it supports those tasks; a branded screen alone does not justify migration.
2. Review Sharing and Personal Data
Check the actual storage and sharing setup rather than assuming every spreadsheet lacks encryption or access control. Inventory exported copies, review public links and remove access people no longer need. Keep personal data limited to the purpose of the workflow.
Sign in as a client and as a junior employee in a test environment. Try reading another client's records, exporting confidential fields and opening an old shared link. Document the result. The ICO's data-minimisation guidance supports limiting collection; it does not certify a portal or spreadsheet as compliant.
3. A Hypothetical Capacity and Cost Worksheet
Assume 15 hours of avoidable work per week at £35 per hour for 52 weeks: 15 × £35 × 52 = £27,300 in annual capacity value. Add a separate, assumed £3,500 of irrecoverable billing errors to reach £30,800. These are hypothetical inputs, not a LookADev client result; do not count the same error twice.
- Assumed recoverable capacity: 15h/week at £35/h = £27,300/yr
- Assumed unrecovered billing errors: £3,500/yr; a delayed invoice is not automatically a loss
- Not priced here: key-person handover and training
- Scope first: agree delivery after inspecting formulas and data quality
- Recurring costs: hosting, support and maintenance need a separate budget
- Payback: use realised cash benefit, not the full capacity estimate
Released capacity is not a cash saving unless it reduces paid overtime, contractor spend or another cost. Additional billable work needs demand and delivery capacity. Add migration, training, maintenance, hosting and any applicable taxes to your comparison; the £12k–£18k budget is a reference scenario, not a proposal or guaranteed return.
4. Plan a Staged Migration
Export a backup, map the formulas and permissions, then run a sample import. Reconcile counts and financial totals before a parallel run; agree a cutover window, staff training and a rollback owner.
We extract historical records from your existing sheets, clean anomalies, and structure a normalized PostgreSQL database with strict data constraints and foreign keys.
We configure granular database-level rules. Clients only see their own projects and invoices; employees see assigned tasks; only directors see margins and executive financials.
Scope the screens and integrations your team needs, then test them with representative data and devices. For invoice integrations, check duplicate prevention, failed writes and reconciliation. Set performance targets from a measured baseline rather than promising an untested load time.
Frequently Asked Questions
When should a growing business stop using Excel or Google Sheets?
Review a replacement when your actual workbook cannot enforce the access, validation or workflow rules you need. Concurrent editing alone is not a reason to migrate; first check whether a better-configured spreadsheet or existing product solves the problem.
What are the biggest compliance and security risks of spreadsheets?
Check sharing permissions, local copies, protected ranges and the edit history your provider offers. Google says protected sheets and ranges are not a security measure. A spreadsheet is not inherently unencrypted or unlawful; the configuration and data use matter.
How long does it take to migrate a complex spreadsheet into custom software?
Tab count does not define the work. Scope the formulas, record quality, integrations, permissions and cutover window, then test a sample import and rollback. Agree the delivery schedule in the proposal instead of assuming uninterrupted service.
Is custom software cheaper than subscribing to a heavy enterprise ERP/SaaS?
Either can cost less. Compare the required features and full operating costs, including maintenance, hosting, migration and staff training. Custom code may avoid a per-seat software fee while still incurring usage and support costs.
Assess Your Spreadsheet Bottlenecks with an Architect
Review your reconciliation log, permissions and migration requirements with Lucas Martins. Compare the smallest viable fix with a portal build before agreeing scope or price.