Tell us the chore.
A short interview, in plain language. What the chore is, when it happens, what counts as done. If you can explain it to a new assistant, you can explain it here.
You keep the craft.
We take the chores.
Chore-o-matic builds small, autonomous agents — each one pointed at the tedious part of your work, so you stay on the part you love.
§ 01 — How it works
You talk. We build. It works.
No code, no forms, no flowcharts to maintain. You describe the chore once, and a working agent comes back.
We build your agent.
Your answers become a blueprint written in plain words. You read it, you approve it, and we build the agent to match. Nothing to install, nothing to maintain.
You put it to work.
Your agent runs on its own, on schedule, and handles the chore. Check in whenever you like — anything unusual comes back to you.
§ 02 — How the agents operate
Inputs come in. Judgment stays bounded. Actions go out.
A chore-agent listens through the channels you choose, keeps context in its operating memory, reasons inside its written boundaries, then uses approved tools to do the tedious part. Anything odd comes back to you.
§ 03 — How agents get things done
Plugged into the tools you already use.
Agents don't work in a vacuum — they read, write, and tidy up inside the same tools you do.
No. 03-ATalks with your clients where they already are. Answers the routine messages, keeps every thread moving, and surfaces the one that actually needs you.
No. 03-BGoogle Calendar
Reads your week and puts new events on it. Confirmations land on the calendar before the back-and-forth reaches your inbox.
No. 03-CGoogle Sheets
Keeps the running record. Every reply, count, and confirmation lands on the sheet as it happens — quietly true by morning.
No. 03-DSendGrid
Sends the mail you'd rather not type. Confirmations, chase-ups, the morning digest — written once, sent whenever they're due.
No. 03-EWebhook
The spare socket. An HTTP POST to any endpoint you name, so the rest of your stack hears the news too.
No. 03-F — reserved for yours
Your tool isn't here yet? It can be.
Tell us the tool and the chore around it. New integrations ship by request — not by roadmap theatrics.
§ 04 — Examples
Five chores, handled.
A few of the chores an agent takes on — the persona, the chore itself, and what “done” looks like. Concrete, so the shape is easy to borrow for your own.
01 · Real estate
Marta · solo residential letting agent
- The chore
- Every evening, confirm tomorrow's viewings with each prospect on WhatsApp, log confirmed or cancelled to her sheet, and — only with her approval — offer a freed slot to the next prospect.
- Done looks like
- She opens her calendar in the morning and every viewing on it has said yes.
02 · Healthcare
Priya · practice manager, physiotherapy clinic
- The chore
- The afternoon before, remind each of tomorrow's patients on WhatsApp, record who confirmed in a sheet, and flag reschedule requests to the front desk. Anything clinical goes straight to a human.
- Done looks like
- The front desk starts each day knowing which slots are confirmed and which are free to offer.
03 · E-commerce
Tomás · owner of a ceramics shop on Shopify
- The chore
- Answer “where is my order?” on WhatsApp by looking up the order and its tracking status, log each conversation, and email Tomás when something is actually wrong — a lost parcel, an angry customer.
- Done looks like
- He hears about the three orders that need him, not the thirty that don't.
04 · Retail back-office
Elena · back-office manager, three-store boutique chain
- The chore
- At closing, message each store lead on WhatsApp for the day's counts, append the replies to the sheet, and email a morning summary — who reported, who didn't, what's running low.
- Done looks like
- The chasing happens without Elena, and the morning email tells her only what needs a decision.
05 · Customer support
Diego · support lead at a small SaaS
- The chore
- Cover the support WhatsApp line after hours — collect the account email, what broke, and when it started; file a ticket to the helpdesk; email the on-call address when it looks like an outage; send a morning digest. Never promise fixes, refunds, or timelines.
- Done looks like
- Every overnight message becomes a well-formed ticket, and on-call gets woken only for the real thing.
Illustrative examples of the kind of chore an agent handles — real customer stories replace them after the pilot.
§ 05 — FAQ
Sensible questions, straight answers.
Straight answers to the questions people actually ask.
Is this a chatbot?
No. Chat is how the system gathers the chore. The output is a running agent with tools, schedules, boundaries, and status.
What happens if my chore is not in the catalog?
The system says so plainly and records the gap — then the studio takes it from here. That chore moves to service-mode; it never gets rejected.
Do I need to host anything?
No. Your agent runs on the hosted Chore-o-matic runtime. Export exists as an ownership guarantee, not a chore for you to finish.
Who owns the agent?
You do. You own the Chore Blueprint and everything built from it. The blueprint is the lasting source of truth; the code it generates is output you can regenerate any time.
What does it cost?
During the pilot it's simple: one agent, one chore, one price we agree up front. Formal pricing comes later, set from what the pilot actually shows.
Where do secrets go?
Never in the blueprint. Secrets go through managed connections — scoped to the minimum, encrypted at rest, and handed to your agent only when it runs.
§ 06 — Build your agent
What chore do you want to automate?
Say it plainly. The front door is a conversation about the repetitive work around your craft — not a form about frameworks. A short interview turns your answer into a blueprint you can read.
others started with: booking confirmations · morning dockets · approval nudges · log entries