About
How I got here
Twenty years of learning this the hard way
I spent five years at Hewlett-Packard leading technical projects before I walked away from corporate life in 2005, exhausted and burnt out, looking for something different. I founded Admentus that September as a one-person technology consulting practice.
I was doing it all myself: the client work, the sales calls, the invoicing, staying up late to keep everything moving. And the clients I was helping were living some version of the same thing. Client after client, I heard the same request: "Can you help us fix our tech?" But the tech was rarely the actual problem.
The real issue was almost always the same: one piece of the business, a specific role, a specific person, was carrying more than it was ever designed to carry. Fix that, and the rest of the system had a chance. Bolt technology onto it as-is, and you just made the same mess move faster.
The turn
Stop speeding up the mess
That's when I stopped trying to fix symptoms with technology and started building the system first, even when that meant doing it manually before automating anything. Only once the system actually worked did automation make it faster.
That order, system first, technology second, is still the whole method today. The technology available now is just a lot more capable than it was in 2005.
The test
I tried the traditional answer first
A few years later I got a real test of that lesson on my own business, instead of a client's. In 2011 I co-founded Affect4 Technology Solutions, a managed service provider, with a business partner. The advice at the time was the standard playbook: hire a team, scale the model. So we did.
What I found was that managing that team pulled my time into overhead, scheduling, oversight, the management work itself, and away from the client work that actually created value in the first place.
Headcount didn't fix the constraint. It just moved it, from the work I was best at into work that kept me from doing it. We closed Affect4 in 2014, and I went back to working directly with clients.
Where it led
Back to hands-on work
That's not a story about disliking managing people. It's the same lesson the whole method is built on now: adding capacity without redesigning where the value actually gets created doesn't scale anything, it just relocates the constraint. I'd already tried the traditional answer, on my own business, before I ever built an AI-operated system for anyone else's.
From there I spent years as a certified EOS Implementer, Scaling Up Coach, and Pinnacle Business Guide, helping business owners build the operating rhythm their business actually ran on, not just a plan sitting in a binder. I saw the same pattern, business after business: growth exposing a piece of the system that was never built to carry the load it was now carrying.
Coaching gave me the framework. It didn't give me a way to actually build the fix. That's what brought me back to hands-on work, and it's what Admentus is now: the same operational discipline I coached for years, paired with the ability to design and build the system myself, not just recommend it.
The belief underneath it
Technology is a magnifier
If the system underneath is weak, technology just amplifies the weakness, faster, at more scale, with more damage when it breaks. If the system is strong, technology, especially AI, takes you further and faster than you could get on your own. The order matters more than the tool.
How I work
Operating beliefs
Design first, technology second.
The system has to exist before anything, a new hire or an AI agent, can run it.
It's a design problem, not a people problem.
Nobody I've worked with was lazy or careless. The system just wasn't built to carry what it's carrying now.
Growth, not headcount, is the goal.
The fix isn't adding people to absorb the load. It's designing the system so growth doesn't depend on adding people at all.
Not everything needs this.
Some problems really are a faster tool or a simpler fix. I'll tell you when that's the case, even if it means a smaller engagement.
Working together
What it's like to work together
Clarity instead of guesswork.
You'll know exactly what's actually constraining your growth, not a guess dressed up as a diagnosis.
Ownership instead of dependency.
The system gets built into the business, not into me. Your people own it when we're done.
Directness instead of a sales process.
If something's tactical, I say so. If it's not a fit, I say that too.
A partner, not a vendor.
I stay in this with you through the build, not just the sale.
This isn't theory. It's working in the real world.
Here's what business owners are saying after building the system first.Jeff has a unique combination of business insight, communication capabilities and technical skills that have been instrumental in the success of our project.
Timothy Howard
Founder & President, Clarity Connect, Inc.
I have worked with Jeff for several years. He is always available, professional, and equipped with ideas on how to address my concerns or implement my ideas.
Stephanie Francois
Client
After working closely with Jeff for nearly six years on several projects and several fronts, he consistently brings a grounded perspective that can simplify and articulate complex projects.
Jennifer Brown
Client
"Everyone who competes goes into strict training. They do it to get a crown that will not last, but we do it to get a crown that will last forever."1 Corinthians 9:25
Next steps
Where to start
If any of this sounds familiar, let's look at your business specifically.
Talk to Tarvi
Free, no form, no pitch. Tell it how your business actually runs and get a first read on where it's stuck.
Start the conversationAlready know you want the full picture?
Book the System Diagnostic directly and let's build an action plan to break down the constraints.
Book the diagnostic