I stopped chasing the perfect CRM when I realized the real problem was not missing features. It was friction.
Every system promised more visibility. What it actually added was more admin, more fields, more reminders, and more places for client information to drift out of sync.
So I cut the whole thing back.
Instead of forcing Sterling Labs into a giant cloud workspace, I built a local-first operating system around a few tools that do their job and get out of the way. No bloated CRM. No fragile automation maze. No finance app quietly pulling in data I never approved.
That does not mean the business runs on chaos. It means the workflow is simple enough that I can trust it.
This is the stack.
The rule behind the whole setup
I use one rule to decide whether a tool belongs in my workflow:
If the tool creates more admin than clarity, it is gone.
That rule kills most CRM software immediately.
A solo operator does not need six dashboards, forty properties on every contact, and a sales pipeline that feels like a full-time job. I need a clean way to handle inquiries, deliver work, track expenses, and stay organized without turning the system itself into overhead.
That is why the stack stays local where it matters and narrow where it can.
What replaced the CRM
I still need structure. I just do not need a classic CRM to get it.
When a client inquiry comes in, I keep the path tight.
1. The lead arrives through email or the site.
2. I qualify it fast.
3. If it is real, it gets a dedicated project folder.
4. Contracts, notes, assets, and deliverables live inside that folder.
5. Anything financial gets logged separately in the finance layer.
That folder structure does more useful work than most CRMs because it mirrors what actually happens after someone becomes a client.
A simple version looks like this:
/Clients/Client-Name/
/01-intake
/02-contracts
/03-scope
/04-delivery
/05-archive
Inside that setup, everything has a home.
The intake folder holds the brief and early notes. Contracts holds signed docs. Scope tracks what was agreed. Delivery contains the actual work. Archive is where projects go when they are done.
That sounds boring. Good. Boring systems are easier to maintain.
The hardware I actually use
The core machine is a Mac mini M4 Pro. That is the anchor.
I like it for the same reason I like the rest of this setup. It is quiet, stable, and does not ask for attention. It handles research, writing, browser work, terminals, local scripts, and normal business admin without turning the desk into a science project.
Around that machine I keep a small physical stack:
None of that gear is there for status. It is there to reduce drag.
The dock keeps the desk clean. The keyboard and mouse are predictable. The Stream Deck handles repetitive actions. The mic is there when I need quick recordings or clean calls.
The entire point is to make the machine disappear so the work can stay in focus.
How I run client intake without a CRM
Most people treat intake like a database problem.
I think it is a filtering problem.
I do not need a huge system to manage every possible lead. I need a fast way to separate real work from noise and keep the serious opportunities organized.
That is why my intake process is deliberately simple.
When someone reaches out, I look for three things first:
If the answer is yes, they move into a client folder and the conversation gets structured. If not, I do not waste time pretending a cold lead becomes more real because it got tagged in a pipeline.
The immediate win is speed. I can respond, scope, and move the work forward without duplicating notes across four tools.
The longer-term win is cleaner delivery. The information lives where the project lives.
Delivery without platform bloat
Once the work starts, I keep delivery just as lean.
For project tracking, I prefer plain files, scoped checklists, and versioned working documents over giant team platforms. A solo business usually does not need enterprise project management. It needs clear next actions and a reliable place to keep them.
For recurring work, I keep a project-level TODO.md or a short task list tied to the actual deliverables. For anything technical, I keep files close to the project itself so context does not get split across random tools.
That means less hunting.
It also means fewer handoff mistakes, because the source of truth is obvious. If a file matters, it sits with the project, not inside some disconnected workspace that tries to be the center of your company.
Why Ledg is in the stack
Finance is where most software starts getting creepy.
The standard pitch is convenience. Link your accounts, sync everything, let the app categorize your life, trust the dashboard.
I do not want that.
I use Ledg because it keeps the process narrow and private. No bank linking. No cloud-first workflow. No giant data exhaust trail just because I want to track spending cleanly.
The pricing is straightforward: Free, Pro at $29.99 per year, or Lifetime at $74.99.
I like the lifetime option because it fits the logic of the rest of the stack. Buy a solid tool once, keep using it, move on.
Manual entry is not a bug here. It is the feature.
When I enter transactions myself, I actually see the money. That creates cleaner awareness around subscriptions, hardware purchases, contractor costs, and one-off expenses. It also keeps business and personal categories tighter because I am not cleaning up after an auto-import guess.
For a solo operator, that matters more than flashy automation.
The market side of the workflow
Sterling Labs is a business, but I still think in terms of signal and noise. That carries over into the tools I use for market context.
For the broad view, I use TradingView.
For scanning, I use TC2000.
That combination works because each tool has a job. TradingView gives me the wider picture. TC2000 gives me a tighter scan when I want a more focused read on what is moving.
I do not use them as a personality. I use them as instruments.
That same principle applies to the business stack. Every tool should have a clear role. If two tools overlap too much, one of them probably needs to go.
My exact stack
If you want the screenshot version, here it is.
| Layer | Tool | Job |
|---|
|---|---|---|
| Core machine | Mac mini M4 Pro | Runs the day-to-day workload |
|---|---|---|
| Dock | CalDigit TS4 | Keeps peripherals and storage tidy |
| Keyboard | Logitech MX Keys S | Fast, reliable input |
| Mouse | MX Master 3S | Navigation and precision |
| Control | Elgato Stream Deck MK.2 | Repetitive actions and shortcuts |
| Audio | Elgato Wave:3 | Calls and voice notes |
| Finance | Ledg | Private expense tracking |
| Market context | TradingView | Broad chart view |
| Scanning | TC2000 | Focused screening |
| Project structure | Local folders + plain docs | Client ops without CRM bloat |
That table is the whole philosophy in one shot.
Tight stack. Clear roles. No dead weight.
What this setup fixes
The biggest advantage is not that it looks minimalist. It is that it reduces decision fatigue.
I know where new work goes.
I know where contracts live.
I know where deliverables live.
I know where money gets tracked.
I know which tools I open for which jobs.
That sounds small until you compare it with a stack that spreads one project across email, a CRM, a task board, a finance app, a file drive, and three different automation services.
That kind of stack does not feel advanced. It feels expensive.
A simpler system also makes it easier to audit your own business. If a client interaction, expense, or deliverable feels messy, the problem is easier to spot because the workflow itself is not hiding it.
Where I still use software carefully
This is not an argument against software.
It is an argument against software that overreaches.
I still use tools where they save real time. I still automate repetitive steps. I still care about polish. I just do not want critical business context trapped inside products that demand constant babysitting.
The best tool in a solo business is usually the one that does one useful thing, stores data cleanly, and gives you an easy exit if you want to leave.
That is the bar.
Final take
A solo consulting business does not need more complexity. It needs a tighter operating loop.
That is what this stack gives me.
The machine is stable. The folders are clean. The finance layer is private. The market tools are focused. The client workflow is simple enough to trust.
No CRM required.
If you want help building a cleaner local-first workflow for your business, start at jsterlinglabs.com.
And if you want a private finance tracker that stays on your device, Ledg is the move.