Live and hands on. Booked when you want it.

Two hours. Then it runs on your machine.

Not a course. Not another recording you will never finish. A live working session where we install Claude Code and Codex on your machine, wire them to your real accounts, and ship one automation before we hang up.

Configured around your stack Recording is yours forever Refund at the 1 hour mark Up to 4 team members, one price

The same two hours, spent differently.

Most people with a Claude subscription have watched the tutorials. Almost none of them have the setup. The gap between those two things is configuration, and configuration is the part no video walks you through on your machine, with your accounts, against your work.

Two hours of tutorials

What almost everyone actually has right now

  • A tool that writes files and forgets everything by tomorrow
  • Copy pasted config from someone whose stack looks nothing like yours
  • Zero connections. It cannot read your calendar, your inbox, or your tracker
  • One agent at a time, because nobody showed you the other way
  • No guardrails, which is fine until the day it is not

Two hours with us

What is running when the call ends

  • Persistent context, so it starts every session already knowing your business
  • A config written during the session against your repos, your tools, your naming
  • Live connections to the accounts you actually work in, authorized by you
  • Parallel agents on separate lanes, plus Codex reviewing what Claude built
  • Guardrails on the commands that cannot be taken back

The Agenda

This is a working session, so the clock moves with your stack rather than a script. The blocks below are the shape of it, and each one ends with something on your disk rather than in your notes.

0:00 – 0:20Map

Your week on the table

What you actually do between Monday and Friday, which parts repeat, and what you are already paying software to do badly. We bring the same process mapping discipline to each engagement. Automation is the easy half. Defining the process is the work.

A written target: the one automation we ship before the call ends.
0:20 – 1:00Superpowers

Claude Code and Codex, past the defaults

Persistent project context. Skills, so a repeated task becomes a named capability instead of a prompt you rewrite. Subagents running in parallel on disjoint file lanes without colliding. Hooks that fire on your rules, not the vendor's. And the guardrail layer, because a command with the wrong blast radius will find you eventually.

Both CLIs installed, configured, and committed on your machine.
1:00 – 1:40Connections

Wire it to the accounts you live in

A model that cannot reach your data is a very expensive text box. We connect the tools you already run: mail, calendar, drive, your task tracker, your billing, your DNS, your database. Every credential is created in your accounts and stays there. We never hold a key, and you can revoke any of it in thirty seconds without asking us.

Live connections, tested against real data while you watch.
1:40 – 2:00Ship

Run the fresh automation

We build the automation you named at the start and run it end to end against real data. Not a hello world. The actual task you were going to do by hand on Thursday. You drive the last one so the muscle memory is yours, not ours.

One automation live, plus a written queue of the next five.

What you keep after the call.

The session ends. Four things do not.

A config built on your stack

Our config would be close to useless to you. It names our repos, our ports, our tools, our failure modes. Yours gets written live, against your work, and you watch every line go in so you can change it later without us.

The MCP connection pack

Working connections to the services you named, wired during the session rather than handed over as a zip you will never open. Mail, calendar, drive, tracker, billing, infrastructure. Yours to extend.

The recording, permanently

The whole two hours, including the parts where something breaks and we fix it. That footage is the useful half. It is your session and it does not get shown to anyone else.

Fourteen days of direct support

Setups break on the Thursday after, not during the call. For two weeks you send us the error and we answer. No ticket queue, no bot, no upsell attached.

Nothing gets installed for the first time on the call.

Two hours only works because the setup is already done when we start. Here is the whole pre-work list, tiered by how long each item takes to get hold of rather than by how hard it is. That distinction is the important one. An approval from someone else's IT team takes days, and no amount of expertise on the call compresses it.

Tier 0

The four questions that block checkout

Install rights on the machine you will use. Both accounts. Willingness to type into a terminal. One recurring task you can name. A no on any of the four and we do not sell you the session, because none of them are fixable once we are on the call.

At checkoutTwo minutes
Tier 1

Both tools installed and signed in

Claude Code and Codex on your machine, authenticated, with git present. Then you run one command and paste back what it prints. Everything here is self-serve and none of it depends on anyone but you.

72 hours beforeAbout 30 minutes
Tier 2

Keys located, not sent

Any API keys you want wired, found and to hand in whatever you already use to store them. You never send them to us and we never hold one. The point is simply that you are not hunting through dashboards at minute seventy.

48 hours beforeAbout 20 minutes
Tier 3

Anything that needs someone else to say yes

Workspace admin consent, a proxy allowlist, procurement. Lead time is days and it belongs to a person who is not on the call. These get started the day you book rather than discovered mid-session, and anything still pending on the day sits outside what we promise to ship. You will know which of your connections these are before you pay.

The day you bookDays, not minutes

If something is blocked, we do not spend your session fighting it

Sometimes an approval does not land in time. When that happens we ship an equivalent automation from your Tier 1 lane instead, and you leave with the blocked one queued and documented. That is agreed before we start, not negotiated at minute seventy.

Reschedules are free and unlimited. If your preflight is red twenty-four hours out, we release the slot rather than hold two hours for a session that cannot run, and you rebook whenever you are ready.

One session. One price. Booked when you want it.

No cohort to wait for, no fixed date, no seat counter counting down at you. You pick a time that works, we show up, we build.

LIVE TRAINING · 2 HOURS Founding rate
$495 once, USD

This is the founding rate while we build the first case studies, and it ends once we have them.

  • Two hours live, screens shared
  • Claude Code and Codex, both
  • Config written on your stack
  • MCP connection pack, wired live
  • Recording, yours forever
  • 14 days of Slack and email
  • Up to 4 people, same price
  • Full credit toward the monthly plan
Book your install

Pick your own time · Refund at the 1 hour mark · No subscription attached

One hour in, you decide.

If we are an hour in and you do not think this is worth $495, say it out loud and we refund you on the spot. You keep the recording of the part we did. We would rather return your money than have you sit through sixty more minutes of something that is not landing.

No form, no window to miss, no clawback on what you already got. We offer this because the failure mode is obvious inside the first hour, to both of us.

Do not book this if any of these are true.

We would rather lose the sale than take money for something that will not work for you. Three honest disqualifiers.

  • You want someone else to build it. Reasonable, and that is a different door. That one is $995 a month and we do the work.
  • A terminal is a hard no. You do not need to be a developer. You do need to be willing to type into a command line. If that is genuinely off the table, this will not land.
  • You are looking for prompt tricks. There is nothing here about phrasing. Configuration is a different discipline from prompting and it is the one that compounds.

Questions people actually ask.

Do I need to be a developer?

No. You need to be comfortable opening a terminal and typing what we tell you to type. Plenty of the people getting the most out of these tools are operators, not engineers. What matters is that you know your own process well enough to describe it.

Claude Code or Codex. Why both?

Because they fail differently. One builds, the other is pointed at the result and told to break it. A second model reviewing the first catches things the first is structurally blind to, including arithmetic errors and invented precision. It is the single highest leverage thing in the whole setup and almost nobody runs it.

What do I need before the call?

A machine you can install software on, a Claude subscription or API key, and a ChatGPT account for Codex. We tell you exactly which tiers before you book so you are not buying blind. If you already have both, you are ready.

Send us your stack ahead of time and we turn up with it mapped, which buys us back most of the first twenty minutes.

My setup is unusual. Is that a problem?

It is the reason to book rather than watch a video. Videos are made for the average stack, and nobody has the average stack. Tell us what is weird about yours when you book.

Can my team join?

Up to four people on the call at the same price. Past four it stops being a working session and starts being a webinar, so ask us and we will scope it properly.

Is my session recorded for anyone else?

No. Your screen, your credentials, your business. The recording goes to you and nowhere else. If we ever want to use a clip for anything we will ask you first, in writing, and a no costs you nothing.

What if a connection needs my IT team's approval?

Then it is a Tier 3 item and we name it the day you book, not at minute seventy. Those approvals have a lead time measured in days and belong to someone who is not on the call, so nothing we do during the session speeds them up.

Anything still pending on the day sits outside what we promise to ship, and we substitute an equivalent automation from your Tier 1 lane instead. You leave with the blocked one queued and documented.

How much work is the pre-work?

About fifty minutes, spread across the three days before. Thirty for the installs, twenty for locating keys, and one command to verify it all. We send you a brief written against your stack within an hour of booking, so you are not guessing at any of it.

If that sounds like a lot for a session you already paid for, it is the reason two hours is enough. Every minute of pre-work buys back two or three on the call.

What if I am not ready in time?

You reschedule, free, as many times as you need. If your preflight comes back red twenty-four hours out we release the slot rather than hold two hours for a session that cannot run, and you take a new one whenever you are green. Nothing expires and there is no fee.

Does the $495 count toward the monthly plan?

In full, against your first month, if you start within thirty days of the session. There is no pressure to. A good outcome here is that you never need us again.

What happens after fourteen days of support?

You are on your own, which is the point. You watched every line of the config go in and you own all of it. Nothing phones home to us, nothing expires, and nothing stops working because you stopped paying.

The setup takes two hours. Not knowing has already cost you longer.

Pick a time. Bring your real work. Leave with it running.

Refund at the 1 hour mark · Recording is yours · No subscription attached