Calendar And Work Rhythm

This is the working rhythm we should use so Robert understands when Roberto is building, when Roberto is in calls, and how Robert should structure his own calendar around the company.

All times below are Central Time.

Roberto’s Current Calendar Rhythm

Roberto’s calendar is already structured around recurring work blocks.

The purpose of these blocks is not to make the day look busy. The purpose is to protect deep build time, client work, admin time, delivery time, and planning time.

Time	Current Block	What This Means
6:30 AM - 8:30 AM	Startup Buffer	Wake up, reset, organize, review urgent messages, prepare for the day.
7:00 AM - 8:00 AM	Build Meeting	Early build alignment when scheduled.
8:30 AM - 12:30 PM	Morning Block: Ops & Admin	Admin, planning, messages, follow-up, coordination, business operations, and priority sorting.
10:00 AM - 10:15 AM	Roberto / Ben Daily Stand-up	Quick internal check-in.
10:00 AM - 11:00 AM	Clinic IQ Daily Connect	Client/company operating call when scheduled.
12:30 PM - 4:30 PM	Evening Block: Build & Create	Deep build work, documents, systems, client assets, platform work, and strategic creation.
4:30 PM - 8:30 PM	Night Block: Execute & Deliver	Delivery push, finishing work, implementation, client output, and send-ready assets.
8:30 PM - 11:30 PM	Dawn Block: Wrap & Plan	Close loops, review what moved, plan next day, package/send work.
11:30 PM - 6:30 AM	Sleep	Protected recovery block.

Some meetings overlap the larger work blocks. The large blocks are the default rhythm; meetings sit inside them when needed.

What Robert Should Understand

Roberto is not ignoring the company when he is unavailable.

He is usually in one of four modes:

building systems,
handling client/company calls,
coordinating operations,
or finishing deliverables.

That means Robert should not rely on scattered messages as the operating system.

Robert should put the work into clear buckets:

content ideas,
lead follow-up,
offer questions,
client opportunities,
urgent blockers,
decisions that need Roberto,
and items Robert can move without waiting.

Robert’s Advantage: Earlier Mornings

Robert gets up earlier than Roberto.

That should become an advantage, not a point of frustration.

Robert’s early morning should be used for front-end motion before Roberto is fully in the workday:

post or prepare content,
reply to warm leads,
review comments and DMs,
note client opportunities,
record quick voice notes or Looms,
send buyer questions into the pipeline,
identify what needs Roberto’s decision,
and organize the day’s sales/content priorities.

By the time Roberto gets into ops/admin and build blocks, Robert should already have the clean inputs ready.

Suggested Robert Calendar

This is not final. This is the structure Robert should build toward.

Time	Robert Focus	Output
Early morning	Content and relationship warm-up	Post, story, reply, DM follow-up, lead notes.
Mid-morning	Sales and pipeline movement	Who needs follow-up, who needs a Solutions Call, who needs a proposal.
Before Roberto’s deep build block	Decision handoff	Send only the decisions or blockers that require Roberto.
Afternoon	Calls, content, partner movement	Client conversations, relationship work, filming, checking on Len/girls/Jay if active.
Evening	Review and next-day prep	What moved, what is stuck, what Roberto needs to know tomorrow.

Robert / Roberto Sync Rule

Robert and Roberto should not need constant back-and-forth all day.

The better rhythm is:

Robert moves the front-end work early.
Robert sends a clean decision/blocker list before Roberto’s deeper build window.
Roberto protects build and delivery time.
Robert and Roberto sync on the few things that actually need both people.
Open items get assigned to an owner instead of staying in chat.

What Goes In The Shared Agenda

Every Robert / Roberto sync should answer:

What are we selling this week?
What content is going out?
Who is following up with leads?
What calls are booked?
What clients or opportunities need Roberto’s backend/system input?
What deliverables are due?
What is blocked?
What owner is assigned before the next sync?

Rule For Messages

If something is urgent, Robert can message directly.

If something is not urgent, it should be organized into the agenda, pipeline, or owner map.

That keeps Roberto out of scattered reactive work and keeps Robert clear on what he can move without waiting.