Vexlo
Course content
The Weekly Cadence

The 90-Minute Monday Block

10 min read

Event-triggered workflows run themselves whenever leads and jobs arrive. Calendar-triggered ones need a home, and scattering them across the week recreates the remembering tax you came here to kill. The fix is one protected block: Monday morning, 90 minutes, same time every week, where every calendar-triggered workflow runs back to back.

Why one block beats five slots

Batching is not just tidiness. Every workflow in the block shares the same warm-up: the Brain is already open, the assistant conversation is already primed, and you are already in reviewing mode. Five separate slots pay five warm-up costs and offer five chances to be preempted by a ringing phone. One block pays once, and a 9:00-to-10:30 appointment with your own business is much harder to lose than five ten-minute intentions.

Monday morning is the default for a reason: the week's marketing should land early, follow-ups from last week are ripe, and the crew schedule needs to exist before the crew does. If your Mondays belong to customers, Tuesday works. What matters is that the block is recurring, protected, and treated like a client meeting, because it is one: the client is the business itself.

The block, minute by minute

Here is the structure, with our HVAC company's version in brackets. Yours will differ in content, not shape.

0:00 - 0:05   Brain check. First Monday of the month, run
              the full refresh. Other Mondays, glance at
              Right Now: still true?
0:05 - 0:35   Marketing batch. Run the Monday Marketing
              workflow: this week's email and social drafts,
              reviewed and scheduled. [Fall tune-up campaign]
0:35 - 0:55   Pipeline sweep. Quotes past 5 days trigger
              follow-up drafts. Invoices past 14 days
              trigger the Chaser ladder. Review, send.
0:55 - 1:15   Ops batch. Crew schedule drafted from the job
              list. Maintenance reminders (first Monday).
              Supplier emails as needed.
1:15 - 1:30   Review and log. Fill the week sheet: what ran,
              what escalated, minutes the block took. Note
              anything a workflow keeps getting wrong.

Ninety minutes is a budget, not a floor. Early weeks run long while the drafts need more fixing; by month two, owners report finishing in an hour, and the temptation is to fill the saved time with more workflows. Resist for now; Chapter 6 has a better use for it.

The week sheet

The last fifteen minutes produce the block's only artifact: a running log, one row per week.

Week of      Ran            Escalations  Minutes  Notes
2026-08-03   Mkt/Pipe/Ops   1 (quote)    80       Chaser tone
                                                   too stiff x2

Two minutes of logging, three payoffs: escalations get counted instead of vaguely remembered, recurring draft problems become visible patterns (the Chaser's tone has now been "too stiff" twice, so its skill file gets a voice rule), and in Chapter 6 this sheet becomes the evidence for the hours you got back. You cannot count what you did not write down.

Defending the block

The block dies the way all good habits die: one urgent Monday at a time. Two defenses work. First, shrink before you skip: a brutal Monday gets a 30-minute block covering marketing and pipeline only, never a zero. Second, the block survives your absence by design, since every workflow in it has a runbook. A vacation Monday means someone else runs the sheet, which is precisely the drill Chapter 6 turns into a permanent handover.

Try it now

Put the recurring 90-minute block in your calendar now, pick your slot, and build your own five-line version of the minute-by-minute structure from your audit's calendar-triggered workflows. Then create the week sheet, one header row, wherever you keep spreadsheets. Next Monday, run whatever exists of your system inside the block, even if that is one workflow and some manual work. The block comes first; the workflows move in as you build them.

Workflows, Not Prompts Quiz