H Harry Stubbs
open to: full-time roles in AI adoption, managed services & GTM strategy

Got an idea, a problem, or something that just isn't working?

Good. Those are usually the interesting parts. I like bringing people together, asking the questions nobody's asked yet, and turning possibilities into something useful.

no powerpoint required

Three things I believe

Three different problems. Same test on all of them. Does it grow revenue, keep the client, or save real money. If it doesn't, I'm not interested.

🔧

AI moves the bottleneck

It doesn't remove it. Every cycle promises to eliminate constraints and just relocates them. This one makes effort cheap and judgment scarce. That's where the value moves too, and I build around it.

🛎️

Experience is the differentiator

Most people treat experience like it's soft. Something nice, hard to measure, easy to cut in a downturn. It isn't soft. It shows up in renewal, expansion, and referral. That's revenue, not a mood.

🤝

Transformation decides trust

AI is forcing this everywhere right now. Anyone can run a stable operating model. The real test is moving to a new one without losing the people, the trust, or the revenue that took years to build. That's the work I've built a career on.

work in progress

Build this with me

Small things I'm working through right now. Not finished. React honestly — it helps more than praise does.

experiment one

Support, run like hospitality

What would a help desk look like if it borrowed its playbook from the Four Seasons instead of a ticketing system? Sketching it out.

experiment two

Paying for outcomes, not seats

A credit-bucket pricing model for AI-assisted support, where you pay for problems solved instead of licenses held. Still testing the math.

experiment three

This website

This used to be a brochure. Then it turned into a blueprint. Now it's trying to be a conversation. You're the test case.

receipts

What this actually looked like

field note

A Fortune-500 manufacturer needed more than a cloud migration. It needed a new service and commercial model underneath it. That model, not the server count behind it, was the actual deliverable.

field note

A client had a service-disrupting outage. The fix was technical. Keeping the account was personal. What saved it was years of relationship capital, built before anything ever broke. Most people go quiet when things go wrong and hope time heals it. That's backwards. Showing up while it's bad is what actually saves the relationship.

the standard

I do the job to leave the situation better than I found it.

That's true whether it's a client relationship, a team going through change, or a program under pressure.

your move

Have something that isn't working yet?