AI & Me
AI & Me —
I'm my own first client
Most people use AI as a tool. I use it as a cognitive partner — the entity I think with, not through — and I built an operating system on the partnership. The first place I deployed it was on myself.
The bar has moved. So has mine.
Two years ago most people used AI like a smarter search box. Not fair anymore — the world upgraded. Projects, custom instructions, chained research: being "good at AI" is table stakes now.
So here's the sharper version of the difference. Most professionals — even skilled ones — use AI as an assistant: it produces, they consume. I use it as a cognitive partner: the entity I think with, not through. Some of my most valuable sessions produce no deliverable at all — they stress-test a thesis, argue against a position I've staked out, or force me to articulate something I only half understand. The output isn't a document. It's a sharper mind.
And a partnership, unlike a tool, deserves infrastructure. So I built it some — an operating system that runs on three working rules.
Three working rules
Everything does one of three jobs
When I mapped my own systems, a pattern emerged: every agent, workspace, and skill does one of three jobs — and the verbs turned out to matter more than the tools. Run me: agents that execute the mechanical work of being a founder, so my attention goes only where judgment is needed. Inform me: agents that bring the world to me — filtered, prioritized, delivered — so information reports to me instead of me hunting it. Grow me: systems that track what I know, hunt my blind spots, and drill me before it counts — the rarest layer, and the one I value most.
I run two companies' worth of identity through one attention span. The personal stack is what makes that survivable:
Early on, I caught myself presenting AI-generated work I couldn't fully defend — the artifact was ahead of me. So I inverted the sequence: generation became the cheap step, internalization became where the work lives.
Same verbs, three altitudes
What runs me also runs Giant Leap. Every new opportunity — a forwarded message, raw meeting notes, a half-formed idea — enters a structured launch system and comes out the other side as a full working environment: an opportunity brief, a deep research package, and a dedicated workspace with instructions, context, and a solution hypothesis. What used to take a week of setup now takes a day, and it's the same quality every time.
Around that sits the internal machinery: agentic email pipelines feeding our client operations, a hiring system that carries candidates from JD to interview, a skills library that encodes how we present, how we document, and how we think — versioned like software, because it is software. Our delivery methodology itself, APDLC, was codified this way: not a slide, a system.
And I'll be honest about the frontier: the company's Grow layer — every engineer authoring skills, a shared pattern library in daily use — is this quarter's build, not last quarter's achievement. I know exactly where my own fluency ends and the organization's begins, because I audit it. An AI-first company where only the founder is AI-first isn't AI-first yet. That gap is my current project.
| RUN (ops) | INFORM (intel) | GROW (learning) | |
|---|---|---|---|
| Me | email triage → Slack · invoicing from the books · hiring pipeline | CTO brief · CRM sales intelligence | knowledge OS · pre-meeting coaching drills |
| Giant Leap | opportunity launcher · internal agent stack · email pipelines | per-engagement workspaces · deep research on every pursuit | team-wide skills authorship · shared pattern library |
| Clients | agentic ops in production (CS triage, live today) | decision intelligence for operating leaders | learning loops on governed decisions |
We sell what we live
Here's the part that makes this more than personal productivity: Run, Inform, Grow is also what Giant Leap ships. Agentic systems that run our clients' operations — including customer-service triage live in production today. Decision intelligence that informs their leaders. And a learning loop that makes every deployed system better with use, governed at the level that actually matters: the decision itself.
Every pattern we propose to a client, I've usually run on my own life first — the agent designs, the memory architecture, the skills system. By the time it reaches an enterprise, it isn't theory. It's my Tuesday.
The leveler (why I run it this hard)
Start with an uncomfortable truth about how advantage has always worked. The best thinking in business was never evenly distributed — it was concentrated inside elite institutions, storied consulting firms, celebrated engineering studios, and the global technology majors, and rented out at prices only a few could pay. If you weren't inside those rooms, you competed against them. Every operator building from outside those circles knows exactly what that tilt feels like. Here's the irony: I spent years inside those rooms — and the tilt was never about the quality of the thinking inside. It was about who held the key to the door. And what that door protected was knowledge capital — decades of doctrine, precedent, playbooks, and reference architectures, compounded one engagement at a time, growing richer with every client who paid to touch it. You could rent it by the hour. You could never own it.
AI just broke that concentration. A cognitive partner operating at that level — analytical depth, breadth of exposure, speed of synthesis — is now available to anyone willing to build the partnership seriously. Access used to be the moat. Now the moat is what you do with the partnership. That is the single most democratizing shift I've seen in three decades of technology, and I intend to use every inch of it.
But the leveler comes with an obligation, and this is why the Grow layer exists at all. If the partnership produces thinking ahead of my own, my job is to close that gap — to interrogate it, defend it, and imbibe it until it's genuinely mine. Anyone can rent intelligence now. The leverage goes to those who absorb it. That's not philosophy; it's the operating discipline behind every coaching drill and knowledge session in my stack.
And yes — the company is called Giant Leap for a reason.
I run it on myself. I run it on my company. We build it into our clients' platforms. Same three verbs at every altitude — run, inform, grow — which is exactly what you'd expect if the frame is real and not a slide. The architecture doesn't change. Only the scale does.
"I'm really good at prompting" "it's a productivity tool"
The honest answer: I don't use it at all. I think with it, and I operate on it. And the first system the partnership ever shipped was a better version of me.
