How it works

You say it once. The loop does the rest.

Every piece of work goes round six steps, from one sentence to proof you can check. You are in it twice: for the plan, and for the proof.

  1. 01You say itOne sentence
  2. 02Co-founder places itThe right lead
  3. 03Lead plans itYour yes
  4. 04Engines buildYour accounts
  5. 05You reviewYour look
  6. 06ReportsBrief, digest

Then the next request starts the loop again.

The loop, with an example

Follow one request all the way round.

Chat with Bob · Co-founderStep 01
Customers keep asking for invoices as PDFs. Sort it out this week.
On it. That's a Build job, and Support will tell customers when it ships. I'll bring you Sage's plan.
NEW CARDInvoices as PDFOwner: BuildDue Fri
Message Bob, or hold to talkHold

You seeYour words, saved as a card with an owner and a date.

Placed by Bob · Co-founderStep 02
Card from your messageInvoices as PDFCustomers can download an invoice as a PDF.
Bob checked what is in flightclear
Sage, Build lead, owns itplaced
Support tells customers when it shipsfollows
If the request is unclear, Bob asks you one question first.

You see"Invoices to Build. Support will tell customers when it ships."

Plan · from Sage, Build leadStep 03
Needs you Send invoices as PDF, ready Thursday
Problem
Customers cannot download an invoice.
Plan
A Download PDF button on every invoice.
Tools
CC-1 builds it. CX-2 writes the tests.
Cost
about $1.80, cap $3.00
Risk
Old invoice links keep working.
Rollback
Hide the button. Under a minute.

You seeA one-page plan with an estimate, and an Approve button.

Cards · BuildLive
Planned 0
Building 1
Invoices as PDFCC-1CX-2
Review 1
Login copy
Done 3
Signup fix
CC-1Claude Code, writing the PDF exportworking
CX-2Codex, writing the testsworking
This card$0.74 of $3.00 cap
Today$0.92 of $5.00 limit

You seeCards moving, sessions busy, and the money spent so far against your cap.

Review · Invoices as PDFStep 05
Planned›Building›Review›Done
Audit checked first: tests re-run, screenshots matchpassed
CC-1PDF export built, 3 screenshots attacheddone
CX-214 testspassed
$Spent on this card$1.62 of $3.00 cap

You seeThe proof, Audit's note, and two choices: keep it or send it back.

ReportsStep 06
5 of 6cards on track
$1.97spent of $5.00 limit
2tickets closed
  • Invoices as PDF kept. Audit checked the proof.$1.62
  • 2 customer tickets closed$0.03
  • Duplicate charge flagged on hosting$0.01

Then the next request starts the loop again.

You seeWhat moved, what is stuck, what it cost, and what needs you tomorrow.

Build work, at the right size

Small job, small crew. Big job, bigger one.

Sage picks how many hands a job needs, says why, and shows the cost before anything starts. You can always ask for less.

Small

One session

A single session takes a card from start to proof. Right for a bug fix, a copy change or a small feature.

Example estimate$0.40
Medium

A lead with helpers

One session leads and hands parts to helpers working side by side. Right for a feature that touches several places.

Example estimate$1.80
Big

A whole crew

Several sessions across different tools, each owning a stream, with Sage keeping them in step. Right for a launch or a rebuild.

Example estimate$6.50

Costed first. The estimate and the cap come with the plan.The cost shows against your daily limit while it runs.

Everything else

Some work is a habit. Set it once.

Marketing, operations, finance and support mostly run on rhythm. You set the rhythm and the leads keep it.

Scheduled tasks

The same job, on a timetable

Each run is logged with what it did and what it cost.

YouEvery Monday at 9, send me last week's spend.
Loops

Keep going until it is handled

A loop checks its own result. It stops when the goal is met, the budget runs out, or it needs you.

YouWork through the bugs mailbox until it is empty.
Inboxes and calendars

The admin, sorted

Leads go to Marketing, bug reports to Operations. Follow-ups land on the right lead's list.