The 5 automations I actually run every week

<!-- AI-DRAFTED: review before publish -->

Most automation demos show you something impressive once and then quietly break by week three. The trigger fires, the API changes, the output lands in a channel you stopped checking, and you go back to doing the thing by hand. I have killed more clever automations than I have kept.

The ones that survive share a pattern. They run on a schedule, they produce something I actually read, and they stop short of any action that would embarrass me if it went wrong. Here are the five I run with Niyra every week, exactly as they fire, including the parts where I keep her on a short leash.

1. Monday 7am: the week-ahead brief

Every Monday at 7am I get a brief in WhatsApp before I open my laptop. Not a generic digest. It pulls from my Google Calendar, flags the three meetings that need prep, and pastes the last relevant email thread under each one so I am not searching for context at 8:55 for a 9:00 call.

The reason this works is memory, not scheduling. A cron job can send me my calendar. What it cannot do on its own is know that the "Sync with Ravi" on Thursday is the third rescheduled version of a conversation about a contract renewal, and that I promised him revised terms two weeks ago. Niyra knows because she has the structured memory behind it. Superseded facts are versioned, so when a meeting moves or a decision changes, the brief reflects the current state, not the version from a month ago.

The brief takes me about four minutes to read. That is the whole point. If a Monday brief takes fifteen minutes to get through, it is a second inbox, and I will start skipping it.

2. Daily 6pm: commitment sweep

This one I would not give up. At 6pm Niyra scans the day's activity across my inbox and any meetings I recorded, and pulls out two lists: promises I made, and promises made to me. Then she nudges me on the ones about to slip.

A real example from last month. I told a client on a Tuesday call I would send a scope document "by end of week." I forgot the moment the call ended. Thursday at 6pm Niyra flagged it: commitment made, no document sent, deadline in one day. I wrote it that evening. Without the nudge it slips to Monday, I look disorganized, and the client remembers.

The commitment tracking is the feature I underestimated most before I lived with it. Everyone thinks their memory is fine until they count how many small promises they drop in a normal week. Mine was around six. Not one of them was catastrophic on its own. Together they were the difference between someone who follows through and someone who mostly does.

3. Wednesday 8am: pipeline pull, read only

I run a lightweight pull every Wednesday that reads my deal-tracking sheet in Google Sheets and tells me which deals have not moved in seven days. It does not update anything. It does not email anyone. It hands me a list, and I decide who to chase.

I want to be precise about why this is read-only. Niyra can drive a browser and write to tools, and for plenty of tasks she does. But a stalled-deal list is exactly the kind of thing where a wrong assumption becomes an awkward message to a real person. So this automation stops at "here are the four deals that went quiet, and here is the last thing that happened on each." I do the reaching out. She does the noticing.

This is the approvals model working the way it should. Routine reads happen without asking. Anything consequential, sending, spending, booking, waits for me to say yes. I did not have to configure a rule for this specific case. The default is already "ask before it matters," and I only loosen it where I trust the pattern.

4. Thursday afternoon: meeting cleanup

I record most of my calls. On Thursday afternoon Niyra takes whatever I recorded that week and does two things: turns each one into structured notes with decisions and action items, and then converts my action items into tracked follow-ups that feed the Friday sweep.

The chain matters more than any single step. A meeting summary is nice. A meeting summary that automatically becomes commitments that automatically get checked on Friday is a loop that closes without me holding any of it in my head. Last week that loop caught an action item from a Tuesday partner call that I had genuinely forgotten by Thursday morning: "send them the Q3 numbers." It was in the notes, it became a follow-up, and it showed up in Friday's list. That is three separate moments where the ball could have dropped and did not.

5. Friday 4pm: the honest wrap

The last one is a habit as much as an automation. Friday at 4pm Niyra sends me a wrap of the week: commitments I closed, commitments still open going into next week, and anything on my calendar for the following Monday that needs a heads-up before I log off.

I use the Chief of Staff persona for this one because I want the tone flat and direct, not cheerful. "You closed six of nine commitments. Three carry over. Two of them are yours to the same client, which is the second week running." That last sentence is the useful one. It is a pattern I would not have seen from any single day.

What I learned building these

A few things I would tell anyone setting up their own.

Start with reads, not writes. Every automation on this list earned its way up. The pipeline pull could send the chase emails itself. I have not turned that on, and I may never, because the cost of a wrong send outweighs the ten seconds it saves me.

Pick one channel per automation and stick to it. My briefs go to WhatsApp because that is where I actually look on a phone. The heavier meeting notes go to the web app because I read those at a desk. Scattering outputs across channels is how good automations become invisible ones.

And give the recurring stuff a job you would notice if it stopped. The commitment sweep passes that test. I would feel its absence within a day. The clever monthly report I built and then ignored did not, which is why it is gone.

If you want to see where the line sits between what she handles and what she asks about, the oversight model is the thing to understand before you build anything. Get that right and the schedule takes care of itself.

FAQ

Do I need to write code or set up cron jobs myself? No. You describe the automation to Niyra in plain language ("brief me every Monday at 7am with my calendar and prep") and she schedules and runs it. You adjust it the same way, by telling her.

Which channels can automations deliver to? Any of hers: the web app, WhatsApp, Telegram, Discord, and voice including phone calls. I split mine between WhatsApp for quick briefs and the web app for anything I need to read carefully.

Can an automation take an action, or just report? Both, but consequential actions like sending a message, spending money, or booking wait for your approval by default. Routine reads and reports she handles and tells you about. You decide where to loosen that.

Where does she get the context for a brief? From durable memory and, if you opt in, the Life Index, which indexes your Gmail, Calendar, Docs, Sheets, and Drive. You can view, edit, or delete anything she knows at any time.

What does this cost to try? Standard is $49/month and Pro is $99/month, with a 15-day trial. You can see the full breakdown on the pricing page.