Four ways to work with me.
Choose a workshop to help your team use AI in daily work, a scoped build to get a workflow shipped, an hour for a second opinion, or the cohort to build it yourself.
You work directly with me from the first call through handoff, so the person scoping the work is the person delivering it.
What you can buy, how pricing works, what you leave with.
Every engagement starts with a call, ends with something your team can operate, and is scoped so you know the finish line before it starts.
Your team has the tools. The usage isn't sticking.
For: non-engineering teams with AI access and uneven adoption. People, Finance, Ops, Support, Legal, Strategy/PM.
Shape: a 2.5-hour working session, a 1-day foundations day, a 2-day operator bootcamp, or a 3-day clinic with 6-week follow-through.
Price: working sessions start at $5,000 and credit toward a larger format booked within 60 days. Day formats are scoped on the call.
You leave with: a rebuilt workflow, a tool-choice map, a measurement card, and a named next step.
Compare the four formats →One process is broken, or an idea needs to get real enough to decide on.
For: teams that need a scoped prototype, workflow audit, or agent build.
Shape: a workflow prototype sprint in 1–2 weeks, or a context audit or agent-and-Skills build in 2–4 weeks.
Price: fixed after a 30-minute scoping call. Before any work starts, you get the total price, deliverables, timeline, and what's out of scope; that price only changes if we agree to change the scope.
You leave with: a working v1 for a sprint, a context map and rollout plan for an audit, or a repeatable workflow and operating notes for an agent build.
See the three project shapes →Your team already built something and you need a straight read on it.
For: whoever owns the decision to scale it, fix it, or quietly retire it. Including operators doing the building themselves.
Shape: a free 30-minute intro, then a one-hour teardown. This is also the ongoing lane: book more hours as the work needs them, no retainer and no monthly minimum.
Price: $175 an hour, one session at a time.
You leave with: written teardown notes, a short list of what to change first, and a decision you can defend internally.
Book the free intro →You'd rather own the skill than buy the output.
For: PMs, operators, consultants, and indie builders who want to ship the real thing with Claude Code.
Shape: From Chatbot to Builder, a 4-week live cohort. The founding cohort sold out and wrapped in June 2026, so the next date goes to the waitlist first.
Price: $697 a seat.
You leave with: a tool that's live, your own Skills library, and a next-project brief.
Join the waitlist →From first email to handoff.
Same five steps whether it's a workshop or a build. You should know what happens next at every point.
- You send context. A form or an email describing what's stuck. Two business days to a reply, usually faster.
- We spend 30 minutes on the actual problem. Not a discovery call in the sales sense. If I'm the wrong person, I say so on this call and point you somewhere better.
- You get a written scope. Deliverables, timeline, price, and what's explicitly out. You approve it before anything starts.
- The work happens in the open. Small increments you can see, not a reveal at the end. Workshops run labs on your real work; builds ship in reviewable pieces.
- You get the handoff. The artifact, the operating notes, and enough documentation that your team can change it after I'm gone. That's the point.
These case studies show versions of this loop under different constraints. A hackathon prototype isn't the same as a client handoff, and the provenance label says which is which.
Where the evidence comes from.
Employer work, hackathon builds, and personal projects are all real evidence; they just prove different things.
Built on the job
Enterprise sales at Cision: promoted three times, a $1.6M ARR book across 125+ mid-market accounts. While carrying that number I built the team's 50+ entry Skills library, ran AI workflow sessions at the company summit, and won a company-wide hackathon with a private-equity research prototype in 48 hours.
Employer workPublic builds, written up
Eight case studies on this site, each with the problem, the approach, what got built, and the parts that broke. Most include either a public repository or a link to the tool; each case study says what is available.
Hackathon & personal buildsThis site, as the sample
This site runs deterministic link, SEO, copy-consistency, design, unit, and DOM checks on every change. Four case studies also link to public repositories you can inspect, and the write-ups keep the parts that broke.
MethodTwo things you can use today, for free.
Both are useful on their own. Neither is a trial of anything.
Run the scope filter
Seven checks on the thing you're thinking about building. It picks the lane, names the v1 cut line, and hands you a build brief with a starter AGENTS.md. Five minutes, no email.
No email requiredTake the agent harness
The AGENTS.md, CLAUDE.md, slash commands, and Skills scaffold I use on my own projects. Drop it into any repo. Works in Claude Code, Cursor, and Codex.
Free downloadThe jobs I turn down.
Saying this out loud saves us both a call. If you need one of these, I'd rather point you elsewhere than take the work and do it badly.
- Staffing a full-time engineering role. I'm not a contractor you embed for six months. The engagements are scoped and they end.
- Training, fine-tuning, or self-hosting a model. Different discipline, different toolchain, and there are people who do it far better.
- Machine-learning research. If the answer needs a data-science team behind it, I'm the wrong call.
- Procurement-heavy platform rollouts. Enterprise SSO, a six-month transformation program, a steering committee. I'm best on a narrow workflow that needs to work quickly.
- Rubber-stamping a decision that's already made. The coaching hour is a teardown. If you want someone to agree with the plan, you don't need to pay for it.
Before you send the form
How is project work priced?
Workshops and coaching have published prices because the scope is fixed. Project work gets a fixed total after a 30-minute scoping call because a two-week prototype and a four-week agent build aren't the same purchase. The written price only changes if we agree to change the scope.
Do you do ongoing or retained work?
Ongoing yes, retained no. Coaching hours are booked one at a time as the work needs them, with no monthly minimum. Teams that want steady help usually run an hour every week or two between project sprints.
How fast can we start?
Most projects kick off within a week of the first call. If something is urgent I can sometimes start within a few days. I'll confirm real timing on the call rather than guessing here.
What's the tech stack?
Claude, GPT-5, Gemini, ElevenLabs, Vercel AI SDK, Cursor, Amp, Codex, Python, React, Next.js, Vite, Supabase, and Vercel. I pick tools based on the problem, not brand loyalty, and I'll work inside whatever your company has already approved.
Can you work inside our security constraints?
Usually. Bring the constraint to the first call. We'll map what data may go where, what has to stay in approved tools, and which architecture fits before any work starts.
Tell me what's stuck.
A few sentences about the workflow, the team, or the thing that isn't landing. If I'm the right person you'll know on the first call, and if I'm not I'll tell you that instead.
Start a project conversation