Sistava

What Should Your AI Do Overnight: A Real Duty List

Guide — — by Mahmoud Zalt

The overnight jobs worth handing to an AI Employee, the ones to keep for daylight, and how to build a night shift you can read in ten minutes.

Once you accept that AI can run unattended, the next question is a practical one. What do you actually put on the night shift? Most people either hand over nothing, because they do not know where to start, or hand over everything, because it feels exciting for a week and then produces reports nobody reads.

The right answer is narrower than you would guess. Overnight work is best at the jobs that take time but not judgment, and worst at the jobs that need a person to weigh something. Getting that split right is the whole difference between a morning that starts ahead and a morning spent cleaning up.

In Sistava each duty is its own scheduled job with its own instructions, its own approval boundary, and its own credit cap. That separation matters more than it sounds. It means you can pause the research job without touching the inbox job, and it means the morning record tells you clearly which duty worked and which one did not.

At a Glance

3 to 5
Overnight duties most solo businesses end up with
10 min
What a well built morning review should cost you
Draft, not send
Where every new duty should start
50/mo
Entry plan with credits included

What should your AI do overnight?

Six duties cover almost everyone. Sort the inbox into needs you, handled, and ignore. Draft follow ups for anything that has gone quiet. Research new leads or new arrivals so you meet them informed. Check the things that fail silently, like payments and errors. Scan for mentions, competitor moves, and news that touches you. Then write one summary that pulls all of it into a single page.

Notice what those have in common. Each one is work you would happily give a capable assistant on their second week, and none of them ends in a commitment. They produce a pile of prepared material, not a set of consequences, which is exactly what you want happening while nobody is awake to check it.

Benefits

Inbox triage

Sort overnight messages into needs you, already handled, and safe to ignore. The biggest single time saver for most owners.

Follow up drafts

Find every proposal, quote, or thread that has gone quiet past your threshold and write the nudge, ready for one click in the morning.

Lead and account research

Look up new enquiries and upcoming meetings so you walk in already knowing who they are and what they likely need.

Silent failure checks

Failed payments, broken links, stalled orders, error spikes. The things that cost real money precisely because nobody notices them.

Mentions and market scan

New reviews, brand mentions, competitor changes, and news in your niche, filtered down to what actually affects you.

The morning summary

One page that ties the night together: what happened, what needs you, what it skipped and why. This is the only thing you must read.

Which overnight duty should you hand over first?

Start with inbox triage, unless your inbox is genuinely calm. It is the duty with the clearest rules, the fastest payback, and the lowest risk, because sorting messages changes nothing about the world. You can be wrong about a sort and lose thirty seconds. You cannot be wrong about a sent message and lose thirty seconds.

If your bottleneck is sales rather than email, swap in the follow up drafting duty instead. Quiet proposals are the most expensive thing in most small businesses, and a draft sitting ready is what turns a good intention into a sent message. Still keep it draft only for the first fortnight, because tone is the thing most likely to be off early.

Whatever you choose, add the morning summary as your second duty rather than your fifth. Without it you end up checking three places to find out what happened, which recreates the exact chore you were trying to remove. One page, read with coffee, is the entire user experience of a night shift.

What should never be on the overnight list?

Anything that commits you. Sending a message to an unhappy customer, agreeing a price, accepting a project, spending money, publishing something public, or making any promise on your behalf. Those are not overnight jobs at any level of trust, because the cost of being wrong is not a wasted paragraph, it is a relationship or a bill.

Also keep off anything you cannot describe precisely. If you would struggle to explain the rule to a competent new hire, the Employee has no better chance at 3am with nobody to ask. Vague duties are how you get a night of confident output that is quietly wrong in a way you only notice a week later.

Comparison

DimensionTraditionalWith Sista
EmailSort, label, and draft replies for reviewSending anything to an upset or high value client
SalesFind quiet threads and write the follow upQuoting a price or agreeing to scope
MoneyFlag failed payments and unpaid invoicesIssuing refunds or paying anything
ContentDraft posts, notes, and outlinesPublishing anything to a public channel
CustomersResearch accounts and prepare briefing notesEnding, changing, or promising anything in a relationship

A worked example: the solo founder's four job night

Camille runs a small scheduling product for physiotherapy clinics from her flat in Montreal. She is the entire company: sales, support, product, and the person who notices when something breaks. Her problem was not the work itself, it was that everything arrived at once at 9am and she spent until lunch just working out what mattered.

She built four duties over six weeks, one at a time. Week one was inbox triage at 5am, report only. Week two added the failed payment and error check, because two clinics had churned that quarter over card failures she never saw. Week four added trial account research, so every new signup came with a short note about the clinic. Week six added the summary that ties the other three together.

Her rules were blunt. Nothing goes to a customer without her. Nothing touches billing. Anything mentioning cancellation, refund, or a competitor gets flagged rather than answered. She capped each duty separately so the research job, which is the expensive one, could not quietly eat the month's credits during a busy signup week.

The result was not dramatic and that is why it stuck. Her morning triage went from roughly ninety minutes to about ten. Two failed payments got caught in the first month, which paid for the whole thing several times over. The trial research changed how her first calls went, because she stopped opening with what does your clinic do and started with something specific.

TimeDutyWhat she finds at 8am
4:30amFailed payment and error checkOne card failure flagged, with the clinic name and the amount
5:00amInbox triageNineteen messages sorted, four marked as needing her
5:30amNew trial researchThree signups with a short note on each clinic
6:00amMorning summaryOne page covering all three, plus what it skipped and why

How many overnight duties is too many?

You have too many the moment you stop reading the morning summary. That is the real limit, and it arrives sooner than people expect. Three to five duties is where most solo businesses settle, because that is what fits into a ten minute review without turning your coffee into a second job.

Add duties one at a time and let each one run cleanly for a week before the next. If a duty produces output you skim past two mornings in a row, it is not earning its place, so either sharpen its instructions or switch it off. A short night shift you read is worth far more than a long one you trust blindly.

Building your overnight list

  1. Write down your first hour — For three days, note what you actually do between opening the laptop and starting real work. That list is your candidate pool, in your own words.
  2. Cross off anything that commits you — Sending to sensitive people, agreeing prices, spending money, publishing. Those stay in daylight regardless of how well the night shift performs.
  3. Pick the one with the clearest rules — Usually inbox triage, sometimes follow up drafting. Clear rules mean you can tell instantly whether a run was right or wrong.
  4. Add the morning summary second — One page that covers every duty. Without it you check three places, which is the chore you were trying to delete.
  5. Cap each duty separately — Research jobs cost more than sorting jobs. Separate caps mean one expensive duty cannot quietly consume the budget of the useful cheap ones.
  6. Add the next duty after a clean week — One at a time, each report only at first. If you cannot remember what a duty produced last week, do not add another one yet.

For the mechanics behind these duties, read how to make AI work while you sleep, and for the jobs that should start on an event rather than a clock, see how to get AI to work without being asked.

Frequently asked questions

FAQ

What is the single best first overnight duty?

Inbox triage, for most people. It has the clearest rules, it changes nothing in the world if it gets one wrong, and it removes the chore that sets the tone for the whole morning. If your inbox is quiet, drafting follow ups for quiet proposals is the better first pick, because that is usually where the unclaimed money is.

Should overnight duties run at the same time or spread out?

Spread them, and put the summary last. Running the checks first and the summary at the end means the summary can actually see what the other duties found. It also makes the record easier to read, because a failure lands in one duty rather than smearing across a single giant run.

How much does an overnight duty cost to run?

It depends on the duty rather than the hour. Sorting and drafting are cheap, research over many sources is the expensive one, and a nightly cadence multiplies whatever a single run costs by thirty. Plans include a credit allowance, and giving each duty its own cap is what keeps the expensive one honest.

Can an overnight duty use my own documents and tools?

Yes, and it should. A duty that can see your inbox, your customer records, and your own written material produces something specific to you rather than something generic. You grant access per tool, and anything not connected simply stays invisible to the night shift.

What if the overnight run finds something urgent at 3am?

It flags it rather than acting on it, and the flag is at the top of your morning summary. If a situation is genuinely too urgent to wait until 8am, that is a sign it belongs on an event trigger with a notification instead of on the overnight list, because the night shift is built for preparation rather than emergency response.

A good overnight list is short, boring, and impossible to give up. Gather, sort, check, draft, summarise, and stop there. Keep the sending, the spending, and the deciding for daylight and your own judgment, add one duty at a time, and measure the whole thing by a simple test: does your morning start ahead, and can you read the night in ten minutes?