If it is not there on Tuesday, it is not a use case

Everybody has a list of AI use cases. Most of those lists are a brochure.

A use case is not "AI can write emails." That is a capability. A use case is a job that still exists next Tuesday, starts from a trigger you can name, and leaves something behind you can check without a philosophy debate.

If it fails any of those three, it is a demo. Demos are fun. They do not pay rent.

Recurs, trigger, artifact

It recurs. Once is a prompt. Weekly invoices, a Monday numbers pack, the inbox that refills overnight: those are jobs. If you will not run it again, do not hire for it.

It has a trigger. A clock, a deploy, a form, a Stripe event, a full inbox. "When I remember" is not a trigger. You are the trigger, which means you still have the job.

It produces a checkable artifact. A draft reminder. A sorted inbox with four replies waiting. A one-page numbers pack. A QA note with pass or fail. "Better strategy" is not an artifact. You cannot approve a vibe.

LangChain's State of AI Agents put customer service around 26.5% of deployments and research and data around 24.4%. Those two win because they recur, they have triggers, and the output is a ticket, a reply, or a sheet. Not a TED talk.

Eight lanes that already look like jobs

We put these on the Octopus landing because they survive the three tests. Name them like hires, not like features.

Invoices and collections. Weekdays at 9. Clerk pulls what is overdue, writes the reminder, stops before send. Artifact: drafts sitting in Needs you.

Inbox. Weekdays at 7. Mail sorts, answers the routine ones, flags the supplier. Artifact: a quieter inbox and a short pile of "this is actually you."

Weekly numbers. Mondays at 7. Same shape every week. Artifact: a page you can argue with, not a new chart type because the model felt creative.

Support. Continuous, with a cap. Mail drafts from the same few policies. Artifact: replies waiting for a tap. Anything new gets parked.

Meeting notes. On every call. Maker writes it up, files actions with owners. Artifact: notes plus three next steps, not a transcript nobody reads.

Competitor watch. Mondays at 7. Watch reads the pages you named and writes a brief. Artifact: what changed, with links. Not 400 pings.

Release QA. On every deploy. Watch clicks the paths you listed. Artifact: pass, fail, screenshot.

Outreach. Weekdays at 8. Scout fills the sheet you designed, drafts the first line, waits. Artifact: a list plus copy you still approve.

That is the catalog worth starting with. Everything else is a remix or a hobby.

When billing is the job, a reminder app is not enough.

Three filters before you add a ninth

Would this force a context switch to another job. If Clerk has to become a copywriter mid-invoice, you invented a second job and hid it. Split it. Give the copy to Maker. Leave Clerk on money.

Can they fetch the data without inventing it. If the number is not in Stripe, Sheets, or a page they can open, they will guess. Guessing is how you get a confident lie in a customer email. No fetch, no job.

Do the rules of job A poison job B. SEO wants long. Social wants short. Support wants the refund policy, not the brand pun. One generalist averages the rules and calls it strategy. Two teammates with one shared voice file do not.

Anthropic's 2026 State of AI Agents said 57% of agent work is already multi-stage, and only 16% is cross-functional. That tracks. Sequence inside one job is fine. Mixing jobs is how the rulebooks leak.

What you should not hand over

Strategy. Taste. First-time invention.

A teammate can assemble last week's numbers. It cannot decide you should enter a new market. It can draft in your voice file. It cannot tell you the joke is funny. It can write the tenth invoice reminder. It cannot invent the product.

Skip those and you will like the software. Hand them over and you will spend the week undoing confident paragraphs.

The test is rude on purpose. If you cannot write the job like you would to a new hire on day one, you do not have a use case. You have a wish.

Microsoft's 2025 Work Trend Index had 82% of leaders expecting digital labor in the next year or so. Cool. The ones who will not hate it are the ones who picked jobs with a Tuesday, a trigger, and a thing to check.

Hire Clerk, Mail, Maker, Scout, Watch. Put Chief on routing so the pile has an owner. $99 covers OSS models, a computer, and a board. Bring ChatGPT, Claude, or Grok if you already pay. No markup on the tokens. Approvals stay on. Keys in the vault. Own email per teammate. Dedicated workspace. We never train on your stuff. Seven days to get your money back if the jobs do not stick.

Business use is the same test, just with more lanes to count.