What I’ve Learned

I’ve spent my career in industries where the work isn’t glamorous: telecommunications, workforce management, distribution. Places where software enables the service, and the real work happens away from a screen. Places where you can’t just move fast and break things because real operations depend on what you build.

At Charter/Spectrum, I spent a decade building the digital platforms that connected business operations to customer experience. The biggest challenge was always the same: 40+ disconnected systems, each making smart decisions with partial information, none of them talking to each other. The solution was always the same too. Build the context layer that connects them.

That’s context engineering. I didn’t have a name for it then. I just knew that the integration layer, the thing that tells every system who this customer is and what they need, was where the real value lived.

Why This Work

AI changed the economics. The same approach I used at enterprise scale (unifying systems around a customer identity, making implicit business logic explicit, building the integration infrastructure) is now viable for a ten-person service business. The tools are free. The AI is built. What’s missing is someone who knows how to capture the context and wire it all together.

That’s what Human Context does. The name is the job: I capture the human context about your business (your knowledge, your customers, your processes, the way you make decisions) and make it usable by AI. The technology is the easy part. Understanding how a business runs and why it runs that way is where the real work lives.

I also teach. What works at the business level works at the personal level too. Most people are using AI like a search engine when it could be a working partner. The training curriculum takes people from “I can see AI changing how work gets done but I don’t know where to start” through building a personalized AI workflow for their specific work.

And I still do strategic consulting for mid-market companies building product teams and operating models. That’s where the approach was born, and it’s still where some of the most interesting problems live.

How I Work

I take on work where context engineering creates the most impact. For small businesses, that’s usually a website migration that demonstrates the model, then expanding into CRM and lead management as it makes sense. For mid-market companies, it’s diagnostic work when teams feel stuck, or fractional partnerships when they need someone who’s done this before.

Every engagement delivers something you own. I’m not building a dependency. I’m building capability and handing it over.

The Writing

I write about the intersection of technology, operations, and the humans caught in between at inspirednonsense.com. It’s where I think out loud about where this is all going.

Let’s Talk

If you’re paying for tools that don’t fit, managing systems that don’t connect, or wondering how AI could help your business, I’d be glad to have that conversation.

Book a 30-minute intro call

The first step is a conversation.

Book a 30-minute call. No pitch. Bring a system that's messy, a workflow that's eating your time, or a question that won't go away.

Book a 30-minute intro call