Agency MIOSA / Robert Package
This document turns the plan into scheduled work for Robert and Roberto.
The goal is simple: every important task needs an owner, a time window, a clear output, and a place where completion is tracked.
If a task matters, it needs one of four homes:
If it is only sitting in chat, it is not being managed yet.
Every Robert / Roberto task should use this structure:
| Field | Meaning |
|---|---|
| Task | The actual work to complete. |
| Owner | Robert, Roberto, or shared. |
| Due Window | When it should be done. |
| Calendar Block | When the work should happen. |
| Output | What proves the task is complete. |
| Status | Not started, in progress, blocked, done. |
| Notes | Blockers, context, links, or decisions needed. |
| Task | Owner | Due Window | Calendar Block | Output | Status |
|---|---|---|---|---|---|
| Review Agency MIOSA alignment package | Robert | ASAP | Robert early morning or evening review | Robert replies with questions/approval | Not started |
| Finalize offer wording for this week | Robert + Roberto | This week | Robert / Roberto sync | Final wording for Solutions Call / Growth System Audit | Open |
| Decide Robert’s first 3 content posts | Robert + Roberto | This week | Robert early morning content block + sync review | 3 approved post concepts | Open |
| Create/send Robert content direction | Roberto | This week | Build/Create or Execute/Deliver block | Final Robert content direction package | In progress |
| Define who owns website edits | Robert + Roberto | This week | Sync / owner-map review | Named owner and next action | Open |
| Define who owns ads execution | Robert + Roberto | This week | Sync / owner-map review | Named owner and launch criteria | Open |
| Define who owns inbox/email follow-up | Robert + Roberto | This week | Sync / owner-map review | Named owner and follow-up workflow | Open |
| Build lead follow-up routine | Robert | This week | Robert morning sales block | Daily follow-up list and script use | Open |
| Package BetterStem proof safely | Roberto | This week | Build/Create block | Proof points approved for posts/calls | Open |
| Decide Len/girls support lane | Robert | This week | Robert sales/pipeline block | Clear role: outreach, appointment setting, support, or parked | Open |
| Decide Jay/media role | Robert + Roberto | This week | Sync after offer is clear | Include now or park | Open |
| Create weekly Robert / Roberto sync cadence | Robert + Roberto | This week | Calendar | Recurring sync block | Open |
Roberto’s work should be scheduled into the existing calendar rhythm:
| Block | Best Task Type |
|---|---|
| Startup Buffer | Review urgent messages, pick the day’s top priorities, clean handoff list. |
| Morning Ops/Admin | Owner map, calendar, pipeline, admin, coordination, follow-up architecture. |
| Build/Create | Docs, systems, BusinessOS, client assets, offers, pages, automation design. |
| Execute/Deliver | Finish/send deliverables, implementation, package exports, client-ready work. |
| Wrap/Plan | Close loops, update status, set next-day plan, decide what gets sent. |
Robert should build his calendar around earlier front-end movement:
| Block | Best Task Type |
|---|---|
| Early Morning | Post, story, DM replies, lead follow-up, relationship touches, quick filming. |
| Mid-Morning | Pipeline review, sales follow-up, prospect notes, Solutions Call booking. |
| Before Roberto Deep Build | Send clean decision/blocker list for Roberto. |
| Afternoon | Calls, filming, partner coordination, client relationship movement. |
| Evening | Review what moved, prepare tomorrow’s content/follow-up list. |
| Cadence | Owner | Task |
|---|---|---|
| Daily | Robert | Post or prepare one buyer-facing content piece. |
| Daily | Robert | Check DMs/comments/leads and move warm people to follow-up. |
| Daily | Robert | Send Roberto only the decisions/blockers that require backend input. |
| Daily | Roberto | Update build/delivery status and identify blockers. |
| 2-3x/week | Robert + Roberto | Quick sync on offer, leads, content, and delivery blockers. |
| Weekly | Robert + Roberto | Review pipeline, content, booked calls, client deliverables, and owner map. |
| Weekly | Roberto | Update Agency MIOSA operating docs and package changes. |
A task is not done because someone talked about it.
A task is done when one of these exists:
Once Robert confirms the rhythm, create actual calendar/task entries for: