Help until you don't need it.
Pick the sentence that sounds like you. That's the whole menu.
Not sure? Start with the Readiness Check. It's free, it takes 30 minutes, and the answer might be "not yet."
Door one
Show me.
You've heard the idea: a machine does the typing, checks its own work, and your team sees the result on the board. You want to watch it happen once before deciding anything.
Readiness Check
An honest answer to one question: is your project ready for this?
- You leave with
- A one-page note. Ready, not yet, or not a fit, and why.
- Takes
- Thirty minutes. Free.
- Good if
- You'd rather hear "not yet" now than after a month.
Workshop
Half a day. Everyone in the room writes one plan a machine can check.
- You leave with
- One small task, proven, by your own team.
- Takes
- Half a day, up to eight people.
- Good if
- You want the team to feel it, not just hear about it.
Office Hours
Bring what's stuck. Leave unstuck.
- You leave with
- An answer, or the name of the person who has it.
- Takes
- Thirty minutes, weekly, open to anyone.
- Good if
- You've started on your own and hit one wall.
The natural next step is Do it with me.
Talk to usDoor two
Do it with me.
You have a real piece of work and a team that will own it afterward. You want the first time to go well, and the second time to not need us.
First Plan
We write your first plan with you, so you can write the next one alone.
- You leave with
- One plan, run and proven, and the habit of writing checks first.
- Takes
- One week, a few hours of your time.
- Good if
- You have one clear task and one person who'll own it.
Pairing
Your keyboard. Our second pair of eyes.
- You leave with
- Fewer wasted runs, and the reasons why each one was wasted.
- Takes
- Two hours a week, for as long as it helps.
- Good if
- You learn by doing and want someone to catch the small things.
Pilot
One team, one quarter, measured. You decide at the end, with numbers.
- You leave with
- A short report: what it cost, what it saved, what to change.
- Takes
- Twelve weeks, one team.
- Good if
- Someone above you needs proof before a wider rollout.
From here, people continue alone or move to Stay with me.
Talk to usDoor three
Do it for me.
You know what you want built. You don't want to learn a new way of working to get it. You scope. We do the rest and hand it back with proof.
Plan Writing
Your intent, written as checks a machine can run.
- You leave with
- A plan you can read, agree to, and hand to anyone.
- Takes
- Two to five days per plan.
- Good if
- You can describe the outcome but not the checks.
Run Desk
Send the goal. Get back the proven work.
- You leave with
- The finished change, the proof, and the record of what was checked.
- Takes
- Agreed per piece of work, up front.
- Good if
- You want the outcome more than the method.
Done For You
A whole initiative, scoped with you, delivered in proven pieces.
- You leave with
- Working software and a board that already shows what landed.
- Takes
- Weeks to months. Scoped together first.
- Good if
- You have the goal and the budget, not the hands.
Nothing here happens without your sign-off. You see each piece before it counts.
Talk to usDoor four
Stay with me.
It's working. You want it to keep working, and you want someone who already knows your setup when something surprises you.
Standing Review
Every plan read by us before it spends a penny.
- You leave with
- Fewer bad runs. Each plan comes back with notes within a day.
- Takes
- Ongoing. Billed monthly.
- Good if
- You write plans often and want a second reader every time.
Retainer
We're there when a run surprises you.
- You leave with
- A named person, a reply within a working day, and a monthly check-in.
- Takes
- Ongoing. Cancel any month.
- Good if
- Downtime costs more than the fee.
Partner
Your way of working, our long attention.
- You leave with
- A playbook written for your team, kept up to date as you change.
- Takes
- Yearly.
- Good if
- Several teams use this and you want them to do it the same way.
The goal is still that you need us less each quarter.
Talk to usIn plain terms
What we don't do
- We don't do your thinking. Deciding what to build is yours, and it still takes real time.
- We don't promise speed. The gain comes from work happening while you're busy, not from the machine being quick.
- We don't touch your code without you. Nothing is written, committed, or published until you say so.
- We don't keep you dependent. Every service is designed to make the next one unnecessary.
The words we use
Said plainly
On this page and in the room we use six plain words. The docs use the others.
| We say | Others might say |
|---|---|
| The plan | PRD, spec |
| A check | acceptance criterion, hint |
| The work | run, loop |
| Proven | verified, passed |
| The machine | agent, provider |
| Shows up on your board | sync, publish |
One line
Checked before it counts. Shared after it's checked. Still yours.
Tell us which door sounds like you. We'll tell you if it's the right one.