The Weekly Engine Run Sheet

Monday evening: planning (60 minutes)

• ☐ Four ideas pulled from the running capture file.
• ☐ Each checked against the transformation sentence.
• ☐ Engine topic picked; skeleton written: the one person it helps, the promise, the three beats. Stop when the timer stops.

Tuesday: batch record (2-3 hours)

• ☐ This week's piece recorded, and next week's if energy allows (the second take is looser and better).
• ☐ Gear: the phone you own, phone on a stack of books, window light, lavalier mic. A microphone before a camera, a light before either.

Wednesday: edit (2 hours)

• ☐ Dead air cut, audio fixed, captions added. Perfection is the enemy of Thursday. Done ships.

Thursday: publish and distribute (90 minutes)

• ☐ Engine piece goes up.
• ☐ Two clips cut from the strongest moments.
• ☐ One post written from the skeleton.
• ☐ Newsletter version prepared.
• ☐ One community question queued.
• ☐ Every surface ends with the lead magnet call to action.

This is the distribution hour, and it is where most beginners stop early. Publishing is half the job; the hour spent cutting surfaces is often worth more than the two hours spent editing.

Friday: email and replies (60 minutes)

• ☐ Newsletter sent to the list.
• ☐ Every reply answered. Reply mail is relationship, market research, and deliverability in one.

Saturday or Sunday: analytics (30 minutes)

Five numbers, written down, not to obsess: to notice which engine pieces pull people onto the list, and make more of those.

The dead zone, planned for

For the first months the analytics row will show almost nothing; treat that stretch as tuition. Set process goals you control (publish sixteen pieces, ship the lead magnet, land one service client), not outcome goals you do not. If thirty solid pieces in a tight niche produce no list growth and no replies, the problem is usually the work, not the cadence: diagnose before you quit, and before you double down.