Standing orders

Hand off the work
you keep meaning to do.

Write it once: "every Monday," "after every call," "whenever a build fails." Then it's done, again and again. You open sprwl to finished work, not an empty chat.

foundersconsultantsanyone with a recurring Monday

Write your first order

Your home screen is results

Three columns: what's done, what's waiting on you, and what's coming up. Chat only appears when you open an order to steer it.

The idea is that the home screen is an inbox of results, not a message thread.

— DONE —

✓ Competitor brief · Mon 07:00 · 4 changes found

✓ Call notes: Acme kickoff · 6 follow-ups filed

✓ Weekly metrics → Vellum

— WAITING ON YOU —

⏸ Investor update draft · send to 14 people?

⏸ Reply to Acme re: scope · approve wording

— COMING UP —

· Fri 16:00 · week-in-review for the team

· on next failed build · triage + summary

Orders people actually write

every Monday

Competitor brief

What changed on five competitors' sites, pricing and changelogs, in one page.

after every call

Notes + follow-ups

Clairvoyance call → summary in Vellum → tasks in Alacrity → draft emails waiting for your OK.

always current

Investor update

A living draft that collects metrics and wins all month. Sending is one approval.

on a failed build

Build triage

Finds the commit, summarizes the error, pings the owner in Cicero.

every weekday 8am

Morning brief

Your calendar, what changed overnight, and the one thing that's late.

per client, monthly

Client report

For agencies: each client's numbers and progress, drafted and ready to review.

Every run leaves a receipt

What it looked at: sources, files, conversations.
What it did: every step, with timestamps.
What it asked you, and what you said.
What it wrote, signed through Provenance.

One sentence, no "AI," "agent" or "chat": "Write it once, and it gets done every week."

Pairs well with agent seats: a seat is who does the work, a standing order is what it does on repeat.