The MaxShip Master Cadence

Why most operators only run one cadence

Most builders have a daily rhythm and call it operations. Daily is necessary and not sufficient. The captains who compound run five cadences in parallel — daily build, weekly review, monthly retrospective, quarterly strategy, yearly retrospective. Skip any of them and the work stops compounding. The Captain's Flywheel only spins because Cadence — the third C — closes every loop.

Below is how I actually run it. Not theory. The pattern that produced 3,000+ pages on HBOT Finder, the agency client work, MaxShip itself. Templates at the bottom of each section, downloadable, ready to drop into your Command Kit.

Daily — the build cadence

First 30 minutes — the morning scan

Before I ship anything, I orient. git pull across every active repo (mine + clients'), then a quick database scan for new messages, inquiries, orders. I gauge today's KPIs against yesterday's and against the rolling 7-day average. Then I open Linear and GitHub and lay down today's priorities.

The point isn't to absorb every detail. The point is to know the shape of the day before I start. A captain who skips this builds blind.

The build block

After the scan, I lock in. The minimum bar for a shipped day:

• A few PRs — small + frequent beats waiting for one big one
• Looking for code to delete as readily as code to add
• Improving a tool or pattern the team uses
• Adding or upgrading an automated cadence somewhere — the HBOT Finder nightly research job, a weekly review automation, that kind of thing
• Checking that the daily and weekly automation loops are still running clean

What to ship next

I decide using a triangle: bug reports / fires, team priorities, my own priorities. If two of those are quiet, I focus on the third. There's always a clear direction — what's blocking, what's important, what's interesting. Shipping with no direction is the failure mode I watch for.

Before noon vs. after

Mornings are the scan, the planning, the meetings if any. Afternoons are focused shipping. I try not to do meta-work after noon — that's when the build block matters most.

End-of-day ritual — the most important 15 minutes

I triple-check that Claude has logged everything onto Linear tickets — with rich detail, not just headlines. Every meaningful action gets a ticket number. Linear becomes the journal of the work done. Months later, I can ask "when did we add that, and why?" and there's a ticket with the answer. Without this discipline, the company has no memory.

Then I read tomorrow's plan, edit it before bed, close the laptop.

↓ Download the Daily template Drops into ~/command/cadence/daily/ in your Command Kit.

Weekly — content + captain's call

The captain's call

Standing agenda with Tati and Ellen, ~30 minutes. Four topics:

• Information / content — what can we ship this week?
• Products — what can we ship this week?
• What's intriguing us — the lateral thinking pulling on us
• System improvements — where is our own machine creaking?

If a topic doesn't fit one of these four, it's an async Linear comment — not a meeting topic.

Content cadence — three pieces in practice

Three pieces minimum across our channels each week. In practice that looks like taking a video and turning it into shorts, or taking an essay and turning it into a carousel. There are many idea-to-output paths and we have a lot of flexibility right now to try things. As analytics show what's working, we'll double down — and report back what's hitting and what's not.

Friday filming → following Wednesday's distribution. Always rolling.

The rolling pipeline

We're constantly adding to the main content database — the blog at /log. That's the source-of-truth pipeline. Blog content gets converted to YouTube + social. We watch what's being read, who's reading it, how often. (Reader analytics aren't built yet — that's coming.)

The weekly review (solo, end of week)

Five questions, written down:

1. What shipped? — list the actual artifacts
2. What didn't? — and why
3. What's blocked? — what needs unblocking
4. What surprised us? — the unexpected signal worth tracking
5. What rolls up to next week?

↓ Download the Weekly template Captain's call agenda + content production + weekly review.

Monthly — strategic checkpoint

Monthly is where I zoom out. Weekly handles the work; monthly handles whether the work is the right work.

Standard checklist: content retrospective (what landed, what flopped), security review (rotations, audits, access lists), financial scan (burn, MRR, vendor costs), system improvements (what should be automated that still isn't), and deeper one-on-ones than weekly allows.

The strategic question I ask monthly that weekly is too busy for: three weeks of the same friction is the system, not the day. What pattern is repeating that I haven't named yet? Naming it is the move.

↓ Download the Monthly template

Quarterly — the strategic muscle

Quarterly is where the captain does the work nobody else can do: set direction. There's a bit more high-level strategy here — what do we want to do this quarter? What are the big milestones we want to achieve annually? Are we tracking?

Three quarterly objectives, three key results each. Plus a kill-list — what we stop doing. The hardest move and the most important.

I also use the quarterly to do compensation + role conversations with the team. Pay, scope, growth — these need a slower rhythm than the weekly captain's call.

↓ Download the Quarterly template

Yearly — the 10-hour retrospective

This is the slowest cadence and the one most operators skip. Don't.

Annually I do a year-in-review on each venture. I usually end up with 10+ hours of conversation and voice notes, answering hundreds of questions: the wins, the losses, the learning points, the key partners, what worked for the business, what's not working, finance, the deep nuance.

Then I incorporate that into the strategy for the next year. The output is a finalized report formatted for AI consumption that becomes the input to next year's Claude conversations. This year's retrospective becomes next year's Command. That's the compound.

The yearly retrospective also produces the year's theme (one frame, not a goal — a direction) and the three big bets that would change the company shape if they hit.

↓ Download the Yearly template Includes the 10-hour interview question set.

How the cadences stack

Each cadence feeds the next. Daily ships are inputs to the weekly review. Four weekly reviews stack into a monthly retrospective. Three monthly retrospectives stack into a quarterly with real signal — not vibes. Four quarters become the yearly retrospective. Skip a cadence and the rollups become hollow.

Most operators only run two of the five (usually daily + weekly). The compounding lives in the slower ones.