The Practical Alternative to Expensive Ops Software (And How to Set It Up in an Afternoon)

Somewhere along the way, the idea took hold that running a business well means using a lot of software.

A CRM for contacts. A project management tool for tasks. A separate platform for invoices. A shared drive for documents. Slack for team comms. A spreadsheet for the things that don't fit anywhere else.

For lean teams — ten, twenty, fifty people — this stack creates a specific kind of overhead that's hard to see on any one day but adds up fast over a quarter. Time spent switching contexts. Information that lives in four places and is current in none of them. The mental load of remembering which tool holds what.

The alternative isn't more software. It's less — built on a foundation that almost every ops person already knows how to use.

The Real Cost of Fragmented Tools

Fragmentation has two costs: the visible one and the invisible one.

The visible cost is subscription fees. Three to five SaaS tools at $15–$80/month each adds up quickly for a small team, especially when you're paying for seats across the org.

The invisible cost is harder to measure and considerably larger. It's the time your team spends finding information instead of acting on it. It's the client who slipped through follow-up because the contact note was in a CRM your EA doesn't have access to. It's the invoice that didn't get chased because the financial view and the project view are in separate tools that nobody reconciles.

Fragmented systems look organized from the outside. From the inside, they create constant low-level friction — and over weeks and months, friction compounds.

What a Useful Ops Hub Actually Contains

A practical business operations tracker for a lean team doesn't need to be complex. It needs to answer the questions that come up every day:

Contact and client tracking. Who are we currently working with? What's the status of each relationship? When did we last touch base?

Task and project management. What's due this week? Who owns it? What's blocking it?

Financial visibility. What invoices are outstanding? What's been paid? What's the current monthly run rate?

Document and asset tracking. Where's the contract for this client? Which proposal version did we send?

These four categories cover the majority of what an ops manager, EA, or chief of staff needs to stay on top of a business. The goal isn't to replace every specialized tool — it's to have a single place to check before decisions get made.

Why Google Sheets Is the Right Foundation for Lean Teams

Google Sheets has a reputation as a backup solution — something you use when you can't justify the "real" tool. For lean teams, that framing is backwards.

Sheets is free. Everyone on the team already has access. It's infinitely customizable without a developer. It integrates with almost everything via Zapier, Make, or native connectors. It's fast to update, easy to share, and doesn't require onboarding.

More importantly: people actually use it. The best operations system is the one your team opens every day. A lightweight, familiar tool beats a powerful one that nobody keeps current.

The objection is usually scale — Sheets doesn't work at 500 employees. That's true. It works well at five to fifty, which is exactly the team size where most ops software is either overkill or too expensive to justify.

How to Set Up a Google Sheets Business Operations Tracker in One Afternoon

The setup problem isn't concept — most ops people can design a tracker in their head. The problem is the blank spreadsheet. Starting from scratch means building every tab, every formula, every validation dropdown before you can use the thing.

A structured template solves that. You're populating, not building. Import your existing contacts, update the task list, enter the open invoices. Two to three hours and you have a working system.

The key habits once it's running:

• Open it before your daily standup or first calendar block
• Update deal and task status in real time, not at end of day
• Review financials once a week, not once a quarter
• Keep one tab as a "command center" that surfaces the most important view first