Spreadsheets running the part of your business that should be software

A lot of small UK businesses still run the awkward bit of their operation in Google Sheets or Excel. Quotes, job tracking, stock moves, client portals in disguise, handover checklists. It works until two people edit at once, a formula breaks, or someone exports the wrong tab and emails yesterday's numbers to a customer.

I keep getting the same call. The sheet has become the product. Nobody planned it that way. It just grew, cell by cell, until the business depends on it and nobody wants to touch the formulas.

When a spreadsheet stops being enough

Spreadsheets are brilliant for exploring a process. They are a poor place to park logins, permissions, audit history, or anything that has to talk to Stripe, Xero, or your website in real time.

The cracks show up in familiar ways. Duplicate rows after a bad paste. A shared link that was meant to be view-only. Version names like "final_v7_REAL". A new starter who breaks a lookup and the whole team spends Tuesday fixing it.

If your "system" needs a staff training session every time someone joins, it is already software. It just happens to be living in a grid.

What a small custom build actually replaces

I am not talking about a twelve-month enterprise rebuild. Most of the jobs I see need a focused Laravel or app build around one painful workflow.

• A client-facing portal so customers stop emailing for status updates.
• Internal job or order tracking with proper users, roles and history.
• Imports and exports that talk cleanly to Xero, FreeAgent or your bank CSV, instead of weekly copy-paste.
• A thin admin that sits beside WordPress or WooCommerce when the plugin route has run out of road.

The goal is boring and reliable. Same process every day. Less tribal knowledge. Fewer "who has the latest file" moments.

How I usually approach it

First I map what the sheet actually does today, including the messy bits people do by hand. Then we pick the one workflow that costs the most time or risk, and build that properly. Leave the rest of the spreadsheet alone until it earns its own upgrade.

Sometimes the answer is still a tidy sheet plus a better CSV path. Sometimes it is a small SaaS-style tool your team logs into. I would rather say that early than sell you a platform you do not need.

Who this is for

Owners and ops leads who know the spreadsheet is holding them back, and who will pay to get that lane into proper software. Design agencies and bookkeepers with the same pain on behalf of clients are in the same boat.

It is not for people who want another DIY "build a CRM in Sheets" tutorial. If you enjoy living in formulas, fair play. If you want the process off your plate and into something staff can use without fear, that is the hire lane.

I also build around existing WordPress and WooCommerce setups when the store is fine but the back office is the mess. Details sit on the Laravel development and service pricing pages.

Custom Laravel and small app builds

If the sheet has become the system, you do not need a pep talk about pivot tables. You need a calm build that takes the risky bit out of the grid. Cheers.