The founder's-week operating rhythm
You are the operating rhythm
A founder with a great EA doesn't just get tasks done — they get a rhythm: every day closes with a clear picture, every week opens with priorities, every meeting turns into tracked action items. This rhythm is what separates the $5/hr task-doer from the $10–12/hr (~₱580–700/hr) operator. It's also the thing AI can't fake, because it runs on judgment about what matters.
Three artifacts make up the rhythm: the daily EOD report, the weekly priorities doc, and meeting minutes that become action items. Master the shape of each.
The daily EOD report
The end-of-day report is your single most important recurring deliverable. It's how a founder sleeping in Chicago knows what happened during your Manila shift. The shape never changes:
- Done — completed today, with links where relevant
- In progress — what's mid-flight and when it lands
- Waiting — blocked on someone else (name them) or on the founder (be specific)
- Tomorrow — your top three for the next shift
- Flags — anything that smells like a problem, even if small
What a real EOD looks like
Count the judgment calls in that message: held flights instead of guessing, chased the SOW once without nagging, caught $14/seat/month walking out the door. Fifteen minutes of writing, and the founder starts their day already oriented.
The weekly priorities doc
Every Monday (your Sunday night, usually), open a running doc with three sections: the founder's top three priorities for the week (pull these from Friday's conversation or ask directly), what's on the calendar that serves each one, and open loops carried from last week. On Friday, close the loop: what moved, what didn't, what rolls over.
This doc quietly makes you the founder's memory. When Mike says in week 6 "whatever happened with that partnership intro?", you have the answer in ten seconds. That's chief-of-staff behavior at EA cost, and it's exactly what earns the expert-band rate.
Meeting minutes that turn into action
Raw transcription is worthless — Otter and Fireflies already do it free. Your value is the distillation. Within 24 hours of any meeting, ship a note with three parts:
Then the part most VAs skip: put every action item into the task tool (Asana, ClickUp, Notion — whatever the client runs) and chase them before the next meeting. Minutes nobody follows up on are decoration. Minutes with a chaser are an operating system.
Async etiquette holds it together
Working PH night shift means most of your communication is asynchronous. The rules: front-load context (never "quick question — you there?"; always the full question with what you already tried), batch non-urgent questions into one message instead of six pings, and state your response-time norms up front — for example, Slack answered within 30 minutes during your shift, email within two hours. Predictability is the currency. A founder who knows exactly when and how you'll respond stops checking on you.
Do this now
Write a full EOD report for this fictional shift: you cleared 12 emails, drafted 2 replies awaiting approval, rescheduled a dentist conflict, noticed the client's Canva subscription has two unused seats, and are still waiting on a contractor named Ben to send a quote he promised Tuesday. Use the five-section shape, keep it under 150 words, and include at least one flag with a suggested action. Save it in your portfolio doc next to your triage SOP. 15 minutes — and time yourself, because in the real job this happens at 6am after a nine-hour shift.
Tip: use your ← → arrow keys.