Why Work with Us

Two arguments to make: why now, and why this team.

Why now

The structural conditions that make this offer possible didn't exist five years ago.

• AI substitutes for analyst-tier work at this price point. Big 4 engagements in this scope band typically run roughly 10x our price — they staff a partner over a junior analyst team. We invert that: senior principals everywhere, AI doing the analyst-tier research and synthesis. Same caliber of thinking, roughly 1/10 the price.
• Owner-operators are AI-curious but AI-unable. 78% of contractors believe AI helps; 44% can't deploy it because they lack staff; 38% don't understand the use cases. (ServiceTitan 2025 AI in the Trades report.) There is genuine hunger paired with genuine gap.
• PE-backed consolidators are squeezing the band. Owner-operators in the $3–30M range face competitors with data teams, in-house marketing, and unified tech stacks they can't match. The window to install AI-native infrastructure before consolidators arrive is narrow.
• No senior counsel fits at this scope. Big 4 won't go this small. Fractional CMOs solve only one piece. Marketing agencies sell siloed retainers. Nobody is installing the operating system.

The cost-curve collapse is only realizable by operators who can hold senior judgment and AI fluency simultaneously — which is the bridge to "why this team."

Why this team

What we bring — structural commitments that hold across every engagement:

• Two senior principals on every engagement. No junior staffing. No handoff to associates. Both principals are in scoping, in delivery, and in the agent tuning afterward. Non-negotiable. This is the structural answer to the universal SMB-consulting fear: getting palmed off to a junior team after the pitch.
• Senior judgment over analyst work. AI handles the research, frameworks, and draft synthesis. We bring the questions worth asking, the patterns worth seeing, and the conversations worth having with the owner.
• Modern tech-stack fluency. We deploy on Vercel, build in Next.js, integrate the latest AI SDKs, and ship the Surface in modern frameworks. The website we build for the customer is built the way modern operators expect modern firms to build.
• A methodology that compounds. AARRR + Ops as the spine, plus a hypothesis library and per-vertical templates that get sharper with every engagement.

What I bring — drawing from my own track record:

I built Nookly, the AI-native learning platform I run today as CEO. Before that: University of Chicago Booth MBA, then Accenture Strategy. Building Nookly has taught me a lot — running B2B sales into schools and clinics, acquiring families on the consumer side, and working through the full customer lifecycle. The confidence I'd bring to engagements has been earned by working through what those years have asked of me, more than by the consulting training itself.

• AI in production. Nookly runs on modern AI — content generation, image pipelines, lifecycle orchestration, custom agent systems. The systems I'd install for customers are systems I've already built and shipped in production at Nookly.
• Modern technical stack, hands-on. Next.js, Vercel, Tailwind, AI SDKs, Amplitude / GTM analytics, modern auth. The same stack I work in daily.
• Strategic and financial discipline. Built Nookly's pricing model and unit economics from scratch — sensitivity analysis, scenario stress tests, three-layer risk thinking (parameter, structural, narrative). Same rigor goes into The Lens.
• Cross-functional range. Strategy, revenue, customer insight, and cross-functional alignment all live with me at Nookly. The range required to install across a customer's business is range I've developed by running one — not range I started with.

How the unit economics work

This is the answer to "how can you do this at this price when comparable scope normally runs 10x?"

• Senior hours, not analyst hours. Each pillar takes a small number of principal hours of judgment work — co-defining metrics, shaping the Voice, vetting Lens findings. The rest of the workload (research, draft synthesis, anomaly detection, weekly briefs) is AI.
• Two principals, gating at week 4 and week 8. Quality reviews are run by the principal not leading delivery — no work ships without two senior pairs of eyes.
• Compounding methodology. First customer in a vertical takes the most time. By customer 3 in the same vertical, the hypothesis library and per-vertical templates cut delivery time substantially. That compounds into our margin and back into customer pricing over time.

Structural advantages — paired with the assumptions they depend on

Each advantage carries an assumption we're testing. We surface them rather than hide them.

• AI leverage replaces analyst-tier work. Unproven at this exact scope; we're running a self-test on our own operating business to validate that AI-leveraged delivery feels Big-4-caliber to the buyer. If it doesn't, the price assumption breaks.
• A named, repeatable methodology compounds across customers. Theoretical until we have at least three customers in any vertical. If we don't see template reuse compounding by customer 3, we kill the methodology claim and price differently.
• Custom-code site default gives instrumentation no-code platforms can't match. Commits us to being the maintainer; if customers want self-service editing, the differentiation costs them. We're tracking which buyers raise this in scoping — if it's a frequent disqualifier, we revisit.
• The Cockpit + Agents are persistent assets the customer keeps. True only if owners actually read the agents' outputs weekly. If the weekly brief gets ignored after week three, the retainer logic falls apart — and that's the load-bearing assumption underwriting our LTV math.

Open questions on this page: how aggressive should the "AI replaces analyst tier" claim be in customer-facing copy? Is the assumption-naming framing earning trust, or undermining the offering?