Your business is harder to run than it should be.
You can feel it in the day-to-day. Work gets stuck in the same places. The same questions come back around. Information lives in someone’s head, or in five apps that don’t talk to each other, and the whole thing leans a little too heavily on you.
It usually shows up as something ordinary:
- a quote that takes three people and half a week to get out the door
- a process only one person really knows how to run, so everyone holds their breath when they take a day off
- the same order or record keyed in by hand in two or three places
- a monthly report somebody rebuilds from scratch every single time
- a handoff between people or systems that quietly drops something every time
On the surface these look like different problems. Underneath, they’re the same one: a system nobody has made legible yet.
Most owners assume that’s just what running a business feels like. Usually it isn’t. Usually there’s a system underneath the mess, and that system can be understood, then improved.
That’s the work Legible Systems does.
Who this is for
Owner-led businesses that have outgrown their informal systems.
Legible Systems works best with businesses that are already functioning but have outgrown what got them this far: memory, spreadsheets, inboxes, manual handoffs, and one person who knows how everything works.
The signs are usually some of these:
- You're still inside the day-to-day, connecting people and systems that should connect themselves.
- Critical processes run on what people remember, not on anything written down.
- The business runs across tools that don't talk to each other, and you're the bridge.
- A previous automation or software project moved the friction around instead of removing it.
- Growth is limited less by demand than by how much of the operation has to pass through you.
You don't need to check every box. Two or three are enough to be worth a conversation.
How it works
Make the system legible, then improve it.
- Make the system legible. First see how the work actually flows: the real path, not the org chart. Map the tools, the decisions, the handoffs, and the unwritten rules.
- Find the constraint. Most operations queue behind one step and a few fragile handoffs. Find the one that actually governs your throughput, your quality, and how much lands on you.
- Build the smallest durable fix. Sometimes that's software or automation. Sometimes it's a process change, a document, or removing work that never needed to happen. The fix is whatever removes the constraint and holds.
- Leave you owning it. You end up with a system you can understand, run, recover, and change. Not a dependency on me.
The first engagement
Operational Systems Review
I map how the work actually moves through your business, identify the real constraint, and recommend the smallest durable fix. You leave with a clear diagnosis and a concrete next step, whether or not Legible Systems builds the solution.
You leave with:
- A plain-language diagnosis of the operation
- A map of how the work actually flows today
- The primary constraint, named
- The hidden dependencies and failure points
- The recommended fix, and the order to do it in
- The risks and assumptions, stated honestly
- An implementation proposal, if you want one
It's a small, bounded engagement with a defined end, not an open-ended consulting arrangement. And if the honest answer is that you don't need me, that's the answer you'll get.
Who you'll work with
Founder-led, on purpose.
Legible Systems is founded and run by me, Nick Gomez. When you work with Legible Systems, you work directly with me.
I’ve spent about sixteen years at the harder end of computing: offensive security research, then years taking apart hostile software as a malware analyst, then rebuilding and running the platforms that do that analysis at scale. The through-line is walking into systems that are complex, opaque, or actively fighting back, working out how they really behave, and building something that holds. A business that’s harder to run than it should be is the same problem in friendlier clothes.
I hold my own operation to the standard I sell: everything I depend on runs on infrastructure I can rebuild from nothing, written down, tested, and owned outright. I’ve written up that discipline, and what it cost, on my personal site.
My faith shapes how Legible Systems operates: tell the truth about the problem, avoid unnecessary complexity, keep commitments, and leave you with systems you can understand and own.
Essays and personal work live at nickgomez.me.
Where is your business fighting you?
Describe the operational frustration in plain language. You don't need to know what the solution is yet; that's the point of the conversation. No pitch, no obligation, and you'll hear back from me within a few days.
Or write directly: contact@legiblesystems.io