Jordan Shaw - Operator, Builder, Consultant

Work smarter. Build a system.

I work with owner-led businesses that know something is getting in the way but need a clearer view of the problem and a practical way forward. The aim is always the same: the smallest durable fix that you can own and run.

Schedule a conversation How I can help

The Story

The record, in five beats.

2001 — Founded.

An LLC and hard years of pure consulting. Nobody hands you a services business.

2005 — Built the first product myself.

I engineered our offsite backup and remote management platform. Managed services was born on my workbench.

The reinventions.

The company changed identity three distinct times — consulting, then a professional-services MSP, then a leading national Healthcare EMR Hosting and Managed Services provider: three divisions, HITRUST- and SOC 2-certified operations, VMware and Microsoft partnerships, hundreds of clients nationally — through three downturns, HIPAA, and an industry consolidating around us.

The chair.

I moved up to Chief of Operations. The company kept growing. My weeks became operational meetings and finance reviews — and the part I loved, building, belonged to other people.

The return.

AI changed what one operator can build. Lookingglass Works is me going back to the workbench.

25 yearsone company, three reinventions

Est. 2001founded, still standing

Hundredsof clients, served nationally

HITRUST + SOC 2certified operations run

"I didn't do it alone — but I drove it, and I navigated the ups and downs along the way."

Consulting

Useful work starts with the real constraint.

This is not a menu of products. The work is shaped around the decision, workflow, or operating problem in front of you.

Find the constraint

Make the problem specific enough to solve. What is actually slowing the work, decision, or handoff down?

Design the way forward

Turn the right answer into a process, operating rhythm, or system that fits how your business really works.

Build what matters

Use practical tools, including AI where it helps, without turning the work into a technology project for its own sake.

Leave you in control

The finished work should be clear, usable, and yours to carry forward without an unnecessary dependency.

One useful diagnostic

Three places worth checking when a customer conversation stalls.

The response arrives late, follow-through loses its next step, or the message does not fit what the buyer is trying to understand. Before adding automation, find which failure is actually present.

Read the workbench note

Timing: Did the response arrive while the need was still active?
Follow-through: Did the conversation keep a clear and useful next step?
Fit: Did the message meet the question the buyer was ready to ask?

How I Work

Six moves, in order. Then you own it.

Every engagement has a defined end state: you own the system and run it without me. If you come back, it's because you want to build something new — not because I made you need me.

Audit readiness.

Every engagement starts with an honest read of where you actually stand — no build before the audit.

Find where the value sits.

The first move goes where it will make the clearest difference.

Process discovery.

I map how work actually flows — not how the org chart says it does.

Identify the risks.

Data, security, dependency — named early, before they name themselves.

Set the foundation.

Governance and structure before scale. Foundations are what make speed safe.

Build to win, not to wow.

The demo isn't the goal. The system your team runs without me is.

See the gap. Build the fix.

Start with a conversation. If there is useful work to do together, we will know quickly.

Schedule a conversation Book a working session

Not a sales funnel. A conversation about the work in front of you.