“Win more work. Move it faster. Deliver on time.”
SHANNON’S OPERATING PLAYBOOK 01 / SOURCE FIRST
Your outcome
Prepare the work.
Protect the claim.
Make recording easy.
You turn one weekly role theme into three useful YouTube episodes, then derive every short and social draft from those approved beats. You build the line. Patrick makes the consequential calls.
THE FACTORY STRIP
One role. Three episodes. Everything else.
Every downstream asset must point back to an approved episode beat.
- 01JD teardown12–15 min · promise in 20 secAutomate / Assist / Human
- 02System pathTalking head or generic demoHuman acknowledgment is visible
- 03Operator realityICP conversation or honest substitute8–12 questions
- 04Shorts6–10 · 20–45 secClaim in 2 seconds
- 05X + LinkedInFrom beats, never a topic millStaged for review
ROTATE THE CTAEngagement questionorRole-automation mapor$1,500 / 90-minute founder workshop
MODULE 0
The lock before the work
If the claim does not survive this section, it does not move down the line.
Your Company GPT plus operational agents in the customer’s existing stack—not a new dashboard.
Industrial and project-based companies in the US and Canada, with supported annual revenue over $10M. Buyer: C-suite, VP, or director.
20-min discovery → $3,500 Current State Assessment, credited to build → custom implementation from $35k / 90–120 days → Managed AI $5k/mo or Embedded AI Engineer $18–25k/mo.
FFactTrace it
IInferenceQualify it
PProposalFrame it
?Missing evidenceRemove or ask
YOUR WEEK
Five days. Five visible finishes.
Work in hour-ish blocks. End each block with a named draft, decision, or blocker.
- MON01
Lock the role
Choose and anonymize a public JD. Build Episode 1 and its automate / assist / human board.
FINISH: Packet + one X + one LinkedIn draft - TUE02
Sharpen the promise
Revise copy from the packet. Start the Episode 2 path in the tools the operator already uses.
FINISH: Approved beat structure + diagram draft - WED03
Package the idea
Finish the system path. Prepare thumbnail directions with a real still of Patrick.
FINISH: Ep2 packet + 2–3 thumb directions - THU04
Prepare the cut
Export Archify HTML + PNG. If footage exists, write the brief before opening the timeline.
FINISH: 8–12-node visual + edit brief - FRI05
Complete the package
Draft the answer-first description, mark short candidates, and return cuts with a punch list.
FINISH: Review-ready weekly package
WORK INSTRUCTIONS
Thirteen modules. One pass standard.
Learn in sequence. Copy travels with the packet from day one.
Lock + claim guard
Classify every claim. Facts trace; inferences qualify; proposals say “could”; missing evidence stops.
PASS · No unsupported certaintyWeekly factory
One role connects three long-forms. Every downstream asset has a source beat and approved CTA.
PASS · No orphan contentYour desk
One finish per block. Keep Patrick’s decision list. Bring one blocker and one next job.
PASS · Visible artifact every blockEpisode 1
Anonymize a public JD. Sort real tasks across automate, assist, and human.
PASS · Packet ready before Focus CEpisode 2
Draw intake → watchers → daily list → human acknowledgment → write-back.
PASS · HTML + 2400×1260 PNGEpisode 3
After a yes: research card, 8–12 operator questions, host packet, exact referral close.
PASS · No interview pitchCopy
Promise becomes headline. One beat becomes one X claim and one LinkedIn argument.
PASS · Packet-backed and scannableThumbnails
Use the live template, one visual idea, few words, and a real Patrick still.
PASS · Reads small; face is realLong-form edit
Brief first. Probe, transcribe, cut A-roll, overlays, then captions. Return a punch list.
PASS · 1920×1080 intentional cutShorts
Cut 6–10 self-contained claims. Open in two seconds. Keep each 20–45 seconds.
PASS · 1080×1920, context intactX + LinkedIn
Draft from beats. Flag weekday snipes with source, pillar, and Patrick’s right to comment.
PASS · Staged, never posted by youPerformance
Review topic, hook, format, and meaningful audience action. Change one variable.
PASS · Evidence before reactionFirst 10 days
Move one role from packet through package. Outbound stays closed until Patrick opens it.
PASS · Complete line, authority intactQUALITY AT A GLANCE
Make the difference obvious.
Specific beats broad. Human gates beat magic. Traceable beats impressive-sounding.
✓ GOOD
“The watcher could prepare a daily exception list for human review.”
Proposal is framed. Human review is explicit.“The risky part of automation is not the task. It’s the handoff nobody owns.”
One idea, traceable to an approved beat.“What would an agent need your approval to do every time?”
Invites operator reality, not a pitch.× DON’T
“This system cuts quoting time by 60%.”
No approved evidence. Remove it.“The agent handles the process end to end.”
Erases exceptions and the approval gate.TOOL BOUNDARIES
Use each tool for one clear job.
Tools support the line. They do not set policy or expand your authority.
Focus CRecordThe recorder
HyperframesMotion + thumbnail stillsNot a recorder
FALSupporting thumbnail artNever generate Patrick’s face
ArchifyEp2 diagrams + map carouselsHTML + 2400×1260 PNG
Diffusion StudioEditing when enabledWindows browser; Codex out
CodexGuest outreach draftingNot the cut; nothing sends
RELEASE GATE
Prep quality is the score.
Revenue is not your scorecard. A clean handoff is.