When spreadsheets stop being enough for ops
When spreadsheets stop being enough for ops: breaking signs, what a proper system is, and how to replace the sheet without a scary IT project.
·
3 min read
Customer portal vs email-and-Excel for trades / clinics / field teams is the fork ops leads hit when quotes, bookings, job updates, documents, and invoice chasing live in threads and spreadsheets. One path keeps the familiar mess; the other puts customers and staff on one login with a single source of truth. Pick when chaser calls and wrong versions start costing real money.
Email-and-Excel means the customer relationship runs through inboxes and shared workbooks: quote attached, status in a reply chain, documents wherever someone last saved them. It works for low volume, a tight team, and customers who do not mind chasing.
It breaks when two people send different quote versions, the clinic cannot find the latest consent form, or a field team asks WhatsApp because the sheet is already stale. I've watched trades offices spend mornings reconstructing "what did we promise?" from email search. That is not free admin. That is margin leaking out of the day.
A customer portal (client area) is a login where customers see jobs or bookings, status, documents, and messages without hunting the office. Staff work from the same record. It is not a brochure website with a password slapped on.
Eight Mile builds portals as part of SaaS customer areas: survey, fixed written price for a ruthless first release, on your accounts, with code and data you own. Soft support sits on software development. TradeOps is one proof Eight Mile already ships customer-facing ops software for trades; many clinics and field firms need a tailored portal instead. Off-the-shelf vertical tools can fit clean workflows; build when your process is weird, you need ownership, or you must match how you already work.
Keep it when volume is low, one person can still run the week, and customers rarely need self-serve status. Move when chaser calls are normal, staff argue about the latest file, or field teams invent side channels because the sheet lies. If you are hiring just to answer "where's my job?" emails, you are already paying for a portal the hard way.
Login, the jobs or bookings that matter, status customers can trust, documents in one place, and a message trail tied to the job. Skip the wishlist marketplace. Ship the workflow that stops the chaser calls first, then add invoicing or deeper ops once that release earns its keep. A boring v1 that customers actually use beats a glossy portal nobody logs into.
If you are weighing customer portal vs email-and-Excel for trades / clinics / field teams, choose the portal when customers and staff need one truth and email is already the support queue. Keep email-and-Excel only while the cost of chaos is still cheap.
Fewer chaser calls beat a prettier inbox. Portals win when the thread is the product.
If you want a portal you own, contact Eight Mile and describe how customers chase you today.
When spreadsheets stop being enough for ops: breaking signs, what a proper system is, and how to replace the sheet without a scary IT project.
·
3 min read
Multi-tenant SaaS mistakes that show up after launch: isolation, roles, files, billing, and when to stop and fix.
·
3 min read
Taking software in-house after a consultancy build: when to move, what must be true, and what a real handover includes.
·
3 min read
You don’t need a 40-page spec to start: what to bring instead, ruthless v1 must-haves, and how a first release gets priced.
·
3 min read
What “first working link in week two” actually means: a real URL for feedback, not a finished SaaS on day 14.
·
3 min read
Rescue a SaaS someone else built: when to take over an inherited product, stabilise vs rewrite, and own the accounts.
·
3 min read
Internal tools: buy SaaS or build on your data: when shelf seats win, and when custom on your stack is the real product.
·
3 min read
Who owns the code when you hire a London software consultancy? You should: repos, cloud, domain and data from day one.
·
3 min read
Fixed-price software vs agency retainers: cost certainty and a finish line versus monthly capacity, and which fits your build.
·
3 min read
Do I need a technical co-founder or a development partner? Equity leadership vs a paid partner who ships and leaves you the IP.
·
3 min read
Build a SaaS in 6 weeks: when a focused MVP is realistic, what you need before week one, and how Eight Mile ships it.
·
3 min read
CRM for a small firm off the shelf or built: when HubSpot-class tools fit, and when a system on your own job data serves trades and clinics better.
·
4 min read
The info@ inbox nobody owns is where a UK SME's enquiries sit with no named owner and no reply time.
·
4 min read
Security audit vs penetration test: when to review config first, when a buyer needs a pentest, and usual order for SaaS.
·
3 min read
Secrets in git repository history outlive a deleted file. Rotate first, then stop the next temporary commit.
·
3 min read
Cloud bill went up and nobody can say why: usually orphaned resources, missing tags, or one shared account. Fix ownership first.
·
3 min read
If one person knows how to deploy it, you have a person, not a process. Fix ownership, access, and a path the team can run.
·
3 min read
Quotes and invoices stuck in email fail as a system of record. Use one quote→job→invoice workflow with clear status instead.
·
3 min read
Field team software fails without offline-first: vans need capture, queue, and sync that works when signal dies.
·
3 min read
Security audit checklist before you go live: access, secrets, backups, auth, deps, alerting, and when to bring in an auditor.
·
3 min read