Consulting · fractional engagement

Bring it to your team.

The courses teach the patterns. This is the hands-on version — I work directly inside your tools, with the people who already hold the judgment, and install a system that keeps running after I leave. One team at a time, in any function.

Book the 30-min call → See how it works

First step is a 30-minute call. No pitch.

Who this is for

Three buyers. One decision tree.

Reseek serves two distinct audiences with two parallel courses — and the orgs that need both. Use the cards below to figure out which door is yours.

If engineering

You run an engineering org → Claude Code.

VP Eng, CTO, Staff Eng, Platform lead at 50–2000 people. Your team lives in a terminal. PRs are the artifact. You want CLAUDE.md, hooks, subagents, MCP — and a rollout plan that doesn't rely on a champion who quits in six months. Start with the Code course →

If ops / exec

You run a function that ships docs, plans, decisions → Claude Cowork.

Chief of Staff, COO, Head of Ops, Head of Marketing, founder, principal consultant. Your team lives in claude.ai, Notion, Drive, Gmail. You want Projects, Skills, Artifacts, and connectors — without forcing anyone to learn the CLI. Start with the Cowork course →

If a whole org

You're rolling AI across the whole company → both courses + engagement.

CEO, COO, Chief AI Officer with a board-level mandate. Engineering and ops both need to level up. Start with both courses so everyone shares vocabulary, then bring in a fractional engagement to install the system where it counts. See the engagement →

The engagement

Fractional AI advisor. 30 / 60 / 90.

A monthly retainer designed for one team at a time — in any function. I work alongside the people who already hold the judgment, encode it into substrate and agents, and leave you with a system that keeps running after the engagement ends.

Days 0–30 — Substrate

Make the team explain itself.

Shared context files for the team's domain — code, playbooks, brand, policies
3–5 commands or templates for your most repeated workflows
Guardrails and permissions that match your risk profile
Two power users fluent enough to teach the rest

Days 30–60 — Compounding returns

Encode the standards. Build the agents.

Skills library — your conventions and judgment, made active
First specialist agent shipped (PR review, support triage, deal qual, close prep…)
Integrations with the tools your team actually uses (GitHub, Salesforce, Zendesk, your DB)
Adoption metric you can show your CEO

Days 60–90 — Self-sustaining

Hand off the system.

End-to-end workflow wired into your existing systems
Internal champion identified and ramped
Rollout playbook for the next function in the org
Optional: continue month-to-month for depth, or graduate

ShapeMonthly retainer, fixed scope per phase

TouchI work in your tools. Not a slide deck.

FunctionsEngineering, ops, marketing, finance, support, RevOps

Capacity5–10 active clients max

First step30-min call, no pitch

Book the 30-min call →

Real examples

Same playbook. Different functions.

The substrate-skills-agents pattern shows up the same way no matter which team it's installed in. Three anonymized engagements:

Engineering

PR triage, 40-engineer fintech

~3 hrs/senior/week lost to PR triage. Encoded the review checklist as a specialist agent wired into CI. First-pass review went from human-bottlenecked to instant. Eleven days to ship.

Support

Tier-1 triage, B2B SaaS

Support team drowning in repeat questions. Encoded their playbook and product docs as substrate, built a draft-response agent that respected escalation rules. Median time-to-first-response cut by ~60%.

RevOps

Deal-desk review, mid-market sales org

Every non-standard deal bottlenecked on one director. Encoded approval guardrails and pricing logic as an agent reps run before submission. Director now reviews edge cases, not every line.