Jack Yen Content Plan — Maple v1

Date locked: 2026-05-19 Author: Maple (with social media team: Brand Guardian, Instagram Curator, TikTok Strategist, LinkedIn Content Creator, Trend Researcher) Source canvas folder: /Users/jackyen/workspace/jackyen-personal-brand/

How to use this folder

Read in this order:

1. 01_brand_voice.md — north-star voice spec. Read first. Every post checks against this before shipping.
2. 02_strategy_overview.md — the positioning thesis, platform allocation, conversion mechanic. The "why."
3. 03_landing_page_changes.md — what changed on jackyen-personal-brand/index.html and what still needs review.
4. day_01_origin_post.md — the ship-ready Day 1 post (LinkedIn primary, IG/TikTok adaptations included).
5. day_15_variance_story.md — the ship-ready Day 15 post (replaces the fake "month 4 crisis" from the old plan).
6. Platform calendars (read whichever you're shipping first):
   • linkedin_30day.md — 20 fully drafted LinkedIn posts, ready to copy/paste
   • instagram_30day.md — 30-day IG reel + carousel + story cadence
   • tiktok_30day.md — 20-post Mon-Fri TikTok schedule with hooks + scripts
7. 05_operator_os_revision.md — updated strategy after reviewing the actual workspace/products Jack has built. This supersedes the old equal-weight pillar plan.
8. 06_high_viewership_framework.md — higher-viewership storytelling framework based on creator pattern study plus the viral hook library, adapted to Jack's operator voice.
9. month_2_str_outline.md — Month 2 expands the FlexStay / repeatability lane. Outline only, full spec after Month 1 ships.
10. lead_magnets_and_newsletter.md — the standing-offer model: bi-weekly newsletter + platform-specific lead magnets.
11. competitor_scan.md — peer/competitor reference for who Jack is vs. who he isn't.

Locked facts (the receipts)

These appear verbatim in any content. Do not modify without explicit approval.

• 7 donut shops in DFW. Brand: Golden Glaze. GP/LP fund structure, Reg D 506(b). Targeting 10 by year-end.
• 20+ employees across Golden Glaze.
• Golden Glaze growth plan: planned $1M raise + centralized kitchen. Treat this as part of Golden Glaze, not a separate business.
• 11 STR/MTR units across Hawaii, DFW, Tampa. Insurance housing, displaced families, traveling employees. (Month 1: mentioned only in Day 1 LinkedIn origin. Month 2: full lane.)
• October 2024 — planned his way to a layoff. Walked out with six-figure severance.
• At time of layoff: 5 STRs already cashflowing + 12 months of savings stacked. Not a leap. A runway.
• 18 months in as of 2026-05.
• Built solo in 3 weeks with AI: Discord ops layer, daily reporting, automated investor reports, scheduling, inventory, cash control.
• Additional internal systems built: Golden Cash Control, Golden Sales Report, Golden KPI / ReviewIQ, FlexStay Ops, Golden Invest, content strategy sites, and deployment plumbing.
• Currently building: inventory management, guest messaging, tighter cross-business operating dashboards.
• $60K/yr in third-party software replaced so far. Growing.
• 13 years in tech, 6 companies, six-figure salary.
• Managed engineers on Slack/Teams for 13 years. New challenge = 20+ deskless workers across physical locations, many of whom do not read messages between shifts.
• No kids.
• Based: DFW.

Current calendar rule

04_30_day_calendar.md is the active plan as of 2026-05-19, but 05_operator_os_revision.md is the strategic lens for execution. The calendar should now be read as an Operator OS launch sequence, not three equal pillars:

1. Operator OS: the internal software/control layer Jack built across real businesses.
2. Golden Glaze rollup: the main operating lab and proof surface.
3. FlexStay repeatability: same operating pattern in a different business.
4. Golden Glaze capital plan: $1M raise + centralized kitchen, framed as operating proof and investor-readiness, not hype.

Selling premium/the wheel is a personal capital strategy. It can appear only as occasional context if Jack asks, but it is no longer an active content pillar and should not be counted as a business.

Older platform-specific files stay in source for reference, but do not override the current calendar.

The deep playbook files (playbook_days_01_10.md, playbook_days_11_20.md, playbook_days_21_30.md) are rendered on the live review site because they contain the turnkey captions, scripts, shot lists, and production notes Jack can use verbatim. When strategy notes and a playbook draft disagree, use the locked facts here and the active 30-day calendar as the source of truth, then keep the caption's voice/structure.

Use 06_high_viewership_framework.md as the packaging overlay before shipping any post: strengthen the first 2 seconds with an adapted viral hook, show proof on screen faster, and end with an unresolved next step that makes the viewer want the next update.

Status — what changed from the prior plan

• ❌ Killed: 30-day plan from 2026-05-12 that stopped at Day 21 and overused comment X and I'll send Y (14×).
• ❌ Killed: fake "month 4 almost killed us" angle (replaced with the real variance story).
• ❌ Killed: any "two kids" reference (Jack has none).
• ❌ Killed: stale inflated employee-count language. Canonical figure is 20+ employees.
• ❌ Killed: "Left corporate, built the way out" hero (replaced with operator-receipt headline on the landing page).
• ✅ Locked: $60K/yr SaaS replaced as the working claim across all platforms.
• ✅ Locked: bi-weekly newsletter "Receipts from the Back Office" as conversion home.
• ✅ Locked: standing-offer model (link in bio), no comment-keyword loops.
• ✅ Revised: Month 1 leads with Operator OS. Golden Glaze is the main lab, the $1M raise + centralized kitchen is the growth narrative, and FlexStay is repeatability proof.

Open questions for Jack

1. Pick a domain/subdomain for the newsletter landing page (suggest notes.jackyen.com or receipts.jackyen.com). Or use existing jackyen.com/notes.
2. Confirm newsletter platform (Substack / Beehiiv / Ghost / ConvertKit). Recommend Beehiiv for SMB-operator audience (better deliverability, no political baggage).
3. Confirm bio link aggregator (recommend none — direct link to landing page is on-brand).
4. Confirm posting will happen via native scheduling tools or a buffer/sprout — recommend manual posting Month 1 to feel the rhythm before automating.

Ship sequence

Week 1 priorities:

1. Ship Day 1 origin anchor across TikTok, IG Reel, and LinkedIn, with Operator OS as the payoff.
2. Capture Golden Ops, Cash Control, Sales Report, KPI, FlexStay Ops, and Golden Invest screen recordings with sensitive data redacted.
3. Set up or confirm newsletter landing page (one-page, one form, one promise).
4. Pre-record Days 6-10 on Sunday, but bias toward software/workflow artifacts over pure talking head.
5. Update IG/TikTok/LinkedIn bios to point at the standing offer.

Success bar — Month 1:

• 2-3 LinkedIn posts/week shipped, 5 with 5k+ impressions
• 5-7 TikToks/week shipped, 1 with 50k+ views, 500 newsletter signups
• 4-5 IG Reels/week + daily Stories shipped, 1k follower delta minimum
• Newsletter issue #1 sent by end of week 2
• Zero off-voice posts (the brand voice red-flag list catches them)

Don't chase follower count. Chase: number of times an operator DMs you about a specific module, workflow, or number you posted.

Strategy Overview

Positioning

Jack owns a sharper lane than the old plan captured:

the ex-software engineer building the operating system for real-world businesses he owns.

The proof is not just 7 shops, 11 rentals, or $60K/yr of software replaced. The proof is that the workspace already contains multiple live internal systems:

• Golden Ops for shop operations, Discord workflows, check-ins, issues, labor, inventory, media archive, cockpit, MCP/API.
• Golden Cash Control for opening counts, drops, reconciliation, deposit bags, pickups, bank deposits, variance, audit logs.
• Golden Sales Report for Toast ingestion, daily reporting, dashboards, and Discord summaries.
• Golden KPI / ReviewIQ for review tracking and store-level KPI snapshots.
• FlexStay Ops for Hostfully reservations, turnover jobs, vendor dispatch, maintenance, supply runs, Drive archive, dashboard, MCP.
• Golden Invest for investor-facing modeling and LP communication infrastructure.

That is the content moat. Jack is not just talking about AI. He is using AI to build the operating layer under physical businesses with payroll, vendors, guests, investors, cash handling, and 4am exceptions.

Competitive Map

Jack sits between all of them. The receipts are not abstract: 7 shops, 20+ employees, 11 STR/MTR units, GP/LP structure, planned $1M Golden Glaze raise + centralized kitchen, investor reporting, $60K/yr software replacement, and multiple deployed internal apps.

Current business-plan alignment: Jack has two operating businesses — Golden Glaze Donuts and FlexStay Housing. Golden Ops is internal Golden Glaze software, not a standalone SaaS company. Selling premium/the wheel is personal capital strategy, not a content pillar. Golden Glaze's planned $1M raise and centralized kitchen are part of the Golden Glaze growth story.

Core Content Promise

Old promise:

receipts from leaving corporate and building businesses.

New promise:

receipts from building the operating system behind real businesses.

This makes the audience come back for the next module, not just the next personal update.

Platform Allocation

Each platform has a distinct job. Do not raw cross-post.

TikTok — discovery through artifacts

• 5-7x/week
• 60% screen-record / workflow walkthrough
• 25% talking head explaining the decision
• 15% shop/property b-roll
• Lowercase only
• Best series: Operator OS Module, Before/After Workflow, What I Shipped This Week, Build vs Buy
• Conversion: pinned comment + bio link only when the post shows a real artifact

Instagram — visual receipts + save engine

• 4-5 Reels/week, 1 carousel/week, daily Stories
• Lowercase only
• Carousels are the moat: annotated screenshots, workflow maps, module cards, before/after process diagrams
• Stories are raw capture: shop floor, dashboards, code, Discord threads, deployment notes
• Conversion: link in bio → newsletter landing page

LinkedIn — operator/product essays

• 2-3/week Tue-Thu, 7-9am CT
• Proper case
• Longer essays for ex-tech operators, vertical SaaS founders, search/ETA people, and SMB operators
• Best angles: internal tools at sub-scale, what vertical SaaS misses, build-vs-buy decisions, owning the workflow
• Conversion: newsletter + internal tools stack lead magnet in Featured

Voice In One Paragraph

Jack sounds like an operator who codes because the workflow is broken, not a creator performing entrepreneurship. He speaks in numbers, decisions, and what broke this week. Tension comes from specifics: a cash variance, a missed check-in, a turnover job, a store health signal, a dashboard that looked good but nobody used. He explains software the way he'd explain it to a shop GM: plainly, with the labor cost attached. He never asks for follows, never preaches freedom, never claims AI changed his life. He shows the tool, the decision, the time saved, the mistake, and what still sucks.

Full voice spec in 01_brand_voice.md.

Conversion Mechanic — Standing Offer

The standing offer should now be tied to the Operator OS lane.

• One link in each bio → newsletter landing page
• Bi-weekly newsletter: "Receipts from the Back Office"
• Primary lead magnet: "The Operator OS Stack"
• Secondary lead magnet: "5 Metrics I Check Every Morning Across 7 Shops"
• LinkedIn artifact: "The Ex-Tech Operator's Internal Tools Stack"
• No comment-keyword loops.

Newsletter platform recommendation remains Beehiiv.

Current Month 1 = Operator OS Launch

The current 30-day plan should be executed with this weighting:

1. Operator OS — 50%: Golden Ops, Cash Control, Sales Report, KPI/ReviewIQ, FlexStay Ops, Golden Invest.
2. Golden Glaze Rollup + Capital Plan — 30%: 7-shop operations, staff, waste, cash, reviews, investor discipline, planned $1M raise, and centralized kitchen.
3. FlexStay Repeatability — 15%: proof that the same control loop works outside donut shops.
4. Capital discipline context — 5% max: only if it supports operating cash discipline. Do not turn wheel/premium into a series or pillar.

This does not require throwing out the calendar. It requires changing the lens: every strong post should either show a module, explain a workflow, or prove why the operating system had to exist.

What We Won't Do

• Chase follower count
• Run ads in Month 1
• Launch a course, cohort, or paid product
• Cross-post raw between platforms
• Use generic AI hashtags
• Make claims we cannot back with a number or artifact
• Show secrets, tokens, customer names, guest names, employee names, LP names, addresses, or private financials
• Let options content become the headline
• Let Golden Glaze's $1M raise sound like a solicitation, guarantee, or hype cycle
• Present Golden Ops as a public SaaS unless Jack decides to sell it

Month 1 Success Bar

Real KPIs to grade against:

• Posts shipped: 2-3 LinkedIn/week, 5-7 TikToks/week, 4-5 IG Reels/week, daily Stories
• Operator signal: 3+ DMs from operators asking about a specific module or workflow
• Builder/product signal: 2+ DMs from vertical SaaS founders or product people reacting to the workflow
• Capital/search signal: 1+ investor/search/ETA person asking about the operating system thesis
• Newsletter signups: 500+ only matters if replies reference real artifacts
• Reusable assets: 5+ module posts that can become the Operator OS landing page later

Don't grade on followers. Grade on whether the right people ask about the system.

Operator OS Revision

Status: supersedes the old equal-weight three-pillar plan. Reason: workspace review showed Jack has not just built content-worthy tools. He has built a real operating system across Golden Glaze and FlexStay.

Core Thesis

Jack's strongest content lane is:

ex-swe building the operating system for real-world businesses he owns.

This is stronger than "left corporate and bought donut shops" and stronger than "ai replaced my saas stack." The actual proof is the breadth of live systems:

• Golden Ops: Discord bot, check-ins, issues, SOP Q&A, prompt nudges, labor scheduling, inventory, media archive, store cockpit, ops web, MCP/API surface.
• Golden Cash Control: opening counts, drops, reconciliation, deposit bags, GM pickup, bank confirmation, variance, audit logs, RBAC.
• Golden Sales Report: Toast sales ingestion, daily pipeline, dashboard, same-day comparison, Discord report.
• Golden KPI / ReviewIQ: store-level Google review tracking, KPI snapshots, admin mapping.
• FlexStay Ops: Hostfully webhook intake, vendor dispatch, turnover jobs, maintenance logs, supply runs, recurring jobs, Drive media archive, dashboard, MCP.
• Golden Invest: investor-facing memo/modeler and LP update infrastructure.

That is not a side project. It is an operator-built internal software company wrapped around businesses that already exist.

Alignment with ai-business.jackyen.com: Jack has two operating businesses — Golden Glaze Donuts and FlexStay Housing. Golden Ops is internal software for Golden Glaze. Selling premium/the wheel is a personal capital strategy, not an active content pillar. Golden Glaze's planned $1M raise and centralized kitchen are part of the Golden Glaze growth story and should be treated as operating/investor-readiness proof, not a separate business.

New Pillar Weighting

1. Operator OS — 50%

The main lane. Show the modules, the workflow, the before/after, and the operating reason each thing exists.

Recurring series:

• Operator OS module: one system at a time.
• Before / after workflow: what the work looked like before software, then after.
• What I shipped this week: small product updates from real operating pain.
• Build vs buy: what stays SaaS, what gets replaced, and why.

Proof assets:

• Golden Ops cockpit
• Discord check-in flow
• inventory catalog / on-hand count flow
• cash variance dashboard
• sales report dashboard
• FlexStay turnover board
• vendor dispatch thread
• investor dashboard/modeler, with sensitive numbers redacted

2. Golden Glaze Rollup + Capital Plan — 30%

The main operating lab. Use the shops to give the software stakes.

Angles:

• 7 shops, 20+ deskless employees, 4am production floor
• GP/LP structure and investor reporting discipline
• planned $1M raise and centralized kitchen
• use-of-funds, kitchen capex, capacity planning, production transfer controls, waste, and investor-readiness
• labor, waste, cash variance, reviews, and store health
• what breaks when a tech person buys a blue-collar business

3. FlexStay / Repeatability Proof — 15%

Bring FlexStay in earlier. It proves the system is not donut-specific.

Angles:

• same operating pattern across properties: intake, dispatch, status, proof, exception
• Hostfully as source of truth, Discord as ops surface, Drive as evidence archive
• insurance housing and multi-market operations as a different workflow with the same OS pattern
• why the guest-message layer is different from shop ops but shares the same control loop

4. Capital Discipline Context — 5% max

This is not a pillar. Selling premium/the wheel is personal capital strategy, not an operating business. Use it only when it supports the operator story and Jack explicitly wants it in the content mix.

Use it when it supports:

• variance management
• cashflow discipline
• operating cash discipline
• process over picks

Do not let options content compete with Operator OS, Golden Glaze capital plan, or FlexStay proof.

New Content Promise

Old promise:

receipts from leaving corporate and building businesses.

New promise:

receipts from building the operating system behind real businesses.

That gives the audience a reason to come back weekly. They are not just watching Jack succeed. They are watching a live internal operating system get built in public, with the businesses as test environments.

Series Architecture

Series 1 — Operator OS Modules

One post per module. Repeatable format:

1. The operating problem.
2. The old workflow.
3. The smallest tool that fixed it.
4. The receipt: time saved, variance caught, task closed, or adoption proof.
5. What still sucks.

Initial module list:

• Daily check-ins
• Cash control
• Inventory on hand
• Sales report
• Review/KPI tracker
• Store cockpit
• Labor scheduling
• FlexStay turnover dispatch
• Maintenance log
• Investor reporting

Series 2 — Build vs Buy

This keeps the SaaS replacement story honest. The point is not "replace everything." The point is owning the workflow.

Format:

• bought: payroll, accounting, POS/payments, PMS core
• built: check-ins, exception routing, cash control, dashboards, investor views, vendor coordination
• reason: if being wrong is regulated or legally expensive, stay bought; if the workflow is specific and high-friction, build.

Series 3 — Two Businesses, Same Control Loop

Compare Golden Glaze and FlexStay without turning FlexStay into a separate content brand.

Examples:

• shop issue vs property issue
• daily check-in vs turnover proof
• cash variance vs cleaning/vendor variance
• store cockpit vs property board
• manager note vs guest message

Series 4 — Golden Glaze Capital Plan

Use the $1M raise + centralized kitchen as a concrete growth narrative.

Examples:

• why a 7-shop donut rollup needs centralized production
• the operating controls required before taking in expansion capital
• how production capacity, waste, transfers, and store compliance become investor reporting inputs
• what the central kitchen changes operationally for 7 shops scaling toward 10

Platform Changes

TikTok

Move from personality-led talking head to artifact-led video.

Target mix:

• 60% screen-record / workflow walkthrough
• 25% talking head explaining the decision
• 15% shop/property b-roll

Best recurring hooks:

• "this is the module that runs ___"
• "before this, the workflow was ___"
• "i built this because ___ kept breaking"
• "this saved me from checking ___ manually"

Instagram

Make carousels the moat:

• annotated screenshots
• workflow maps
• module cards
• before/after process diagrams
• weekly operator OS receipts

Stories should be raw capture: shop floor, dashboards, code, Discord threads, deployment notes.

LinkedIn

Lean harder into ex-SWE/operator essays:

• why internal tools beat generic SaaS at sub-scale
• what vertical SaaS misses about SMB operators
• what an operating company can build that a SaaS company cannot
• where AI actually changes the math: not code speed alone, but workflow ownership

LinkedIn should become the place where vertical SaaS founders, ex-tech operators, search/ETA people, and SMB operators understand the thesis.

What Changes In The 30-Day Plan

Keep the existing day order where possible, but reframe execution:

• Day 1 stays origin, but the payoff becomes "i built the operating system behind it."
• Day 2 becomes the first control-loop post: the 90-second morning operating surface.
• Day 3 is still the $60K stack, but it opens the Operator OS series.
• Day 8 becomes deskless workforce as the reason the OS had to be built.
• Day 9 becomes the adoption lesson: Discord is the front end because managers already live there.
• Day 11 becomes the morning cockpit carousel.
• Day 13 becomes build-vs-buy doctrine.
• Day 17 becomes issue routing from a manager note.
• Day 20 becomes cash forecast/control system.
• Day 22 investor reporting should include Golden Invest / LP infrastructure and the $1M raise/central kitchen readiness work, with sensitive details redacted.
• Day 23 tool stack reveal should include Golden Ops, FlexStay Ops, Cash Control, Sales Report, KPI/ReviewIQ.
• Day 27 should be "why not better SaaS?" with actual repo/workflow examples.
• Day 30 should recap the operating system, not just the content system.

Content Guardrails

• Do not show secrets, tokens, private keys, customer names, employee names, guest names, addresses, LP names, account numbers, or sensitive store financials.
• Redact before recording, not after editing if possible.
• Do not imply Golden Ops is a public SaaS product unless Jack decides to sell it.
• Do not imply the $1M raise is generally solicited, guaranteed, or open to unqualified investors.
• Do not overclaim replacement savings; use $60K/yr.
• Do not inflate employee count; use 20+.
• Do not make FlexStay look like a course/STR guru lane.
• Do not make options the headline.
• Do not count Golden Ops, the wheel, or the centralized kitchen as separate businesses.

New Success Bar

Month 1 should be graded less on views and more on audience quality:

• 3+ DMs from operators asking about a specific module.
• 2+ DMs from vertical SaaS founders / product people reacting to the workflow.
• 1+ investor/search/ETA person asking about the operating system thesis.
• 500+ newsletter signups remains useful, but only if the replies reference real artifacts.
• At least 5 reusable module posts that can become a landing page / lead magnet later.

The real win is not followers. It is proof that the Operator OS lane pulls the right people.

High-Viewership Storytelling Framework

Purpose: apply what works from high-performing creator/operator accounts without copying their voice. The goal is more retention, more saves, and more qualified DMs while keeping Jack's content grounded in real operating receipts.

Studied accounts: @raycfu, @lattes.and.leases, @linalikesmoney, @chida.rajan, @rroomfies.

What transfers to Jack: sharp numeric hooks, live-build tension, unresolved next steps, proof on screen, simple captions, and a clearer conversion path.

What does not transfer: guru energy, generic finance advice, "comment keyword" bait as the default, lifestyle flexing, and broad AI takes without a receipt.

1. Reusable Pattern Study

@raycfu pattern — "specific AI opportunity"

Observed shape: concrete tool/opportunity, dollarized outcome, quick list, direct CTA.

Reusable mechanic: use AI/business specificity, but anchor it to Jack's operating companies.

Jack version:

• "3 workflows inside a donut rollup where AI actually saves time."
• "the ai module i need before i can trust a $1m kitchen plan."
• "what i would automate before buying another shop."

Do not copy: "build and sell this for $5k/mo" style claims. Jack's proof is internal operations first.

@lattes.and.leases pattern — "portfolio build in public"

Observed shape: personal timeline, portfolio milestone, approachable real estate education, behind-the-scenes build.

Reusable mechanic: make the audience feel like they are watching the asset get built in real time.

Jack version:

• "we're trying to raise $1m for a central kitchen. here is what has to be true first."
• "7 donut shops sounds like a brand story. it's actually a production problem."
• "11 rentals taught me the same lesson as 7 donut shops: the handoff is where things break."

Do not copy: real estate education/course energy. FlexStay is repeatability proof, not a guru lane.

@linalikesmoney pattern — "soft personality + hard money"

Observed shape: casual persona, simple money framing, low-friction explanations, punchy captions.

Reusable mechanic: simplify without dumbing down. Explain the operating concept like a person, not a memo.

Jack version:

• "central kitchen = less chaos if the tracking is right. more chaos if it isn't."
• "i don't need ai to write captions. i need it to catch cash variance before i miss it."
• "the boring dashboard is the thing that lets me sleep."

Do not copy: cutesy finance identity or investment advice.

@chida.rajan pattern — "live development stakes"

Observed shape: young founder building a specific hospitality asset; narrative tension comes from progress, delays, money, and reveal moments.

Reusable mechanic: turn Golden Glaze's $1m raise + kitchen into a serialized build.

Jack version:

• "central kitchen update #1: the model is not ready until these numbers are clean."
• "the kitchen plan sounds like expansion. really it's a daily transfer-control problem."
• "before i send an investor deck, i need this weekly packet to stop lying to me."

Do not copy: hype-launch language. Jack should stay matter-of-fact.

@rroomfies pattern — "fast creator tempo + broad curiosity"

Observed shape: fast-moving hooks, casual language, trend-aware packaging, quick payoffs.

Reusable mechanic: shorten the first beat and make the visual change faster.

Jack version:

• first 2 seconds: number or tension
• next 5 seconds: visible proof
• next 20 seconds: what broke
• next 20 seconds: what changed
• last 5 seconds: next unresolved step

Do not copy: broad AI hype or lifestyle randomness.

2. Jack's Higher-Viewership Content Loop

Every strong post should follow this loop:

1. Numbered hook: one number, one asset, one clear stake.
2. Tension: what is broken, expensive, late, messy, or risky.
3. Receipt: show the actual dashboard, shop floor, packet, spreadsheet, message, or checklist.
4. Mechanism: explain the control loop: intake -> status -> proof -> exception.
5. Unresolved next step: what still has to be fixed, built, verified, or decided.
6. Soft conversion: "i'm documenting the operator os behind this" or newsletter link.

This is more watchable than a static strategy post because the viewer gets a reason to come back.

3. Reel Tempo Template

Use this as the default edit structure for TikTok and IG Reels.

0-2 sec — hard hook

Show a number or high-stakes phrase on screen.

Examples:

• "$1m raise"
• "7 donut shops"
• "11 rentals"
• "$60k/yr replaced"
• "central kitchen problem"
• "cash variance"
• "before 8am"

2-7 sec — tension

One sentence: what could go wrong.

Examples:

• "if the transfer logs are wrong, the central kitchen just moves the chaos upstream."
• "if the investor packet has stale numbers, the raise gets sloppy before it starts."
• "if guest issues and shop issues hit the same inbox, i miss the wrong thing."

7-25 sec — receipt

Show one real artifact:

• Golden Ops screen
• cash variance dashboard
• weekly packet
• central kitchen capacity model
• redacted investor packet
• FlexStay turnover board
• vendor/guest issue queue

25-45 sec — mechanism

Explain what the system does in plain English:

• "manager enters count"
• "bot compares it against expected"
• "variance gets flagged"
• "only the red row reaches me"

45-60 sec — unresolved next step

Close with what is not solved yet:

• "next step is payroll visibility."
• "next step is making this investor-safe."
• "next step is testing it across all 7 shops."
• "next step is seeing if managers actually use it."

4. Caption Template

Use this for IG and TikTok captions.

[repeat the hook]

[one sentence of context]

receipt:
- [number / artifact 1]
- [number / artifact 2]
- [operating consequence]

what i'm fixing next:
[one concrete next step]

[soft CTA if earned]

Example

we're trying to raise $1m for a central kitchen.

the easy version is a deck.
the real version is proving the shops can run with tighter controls.

receipt:
- 7 shops today
- 20+ employees
- $60k/yr in qsr software already replaced
- cash variance + inventory still need cleaner reporting

what i'm fixing next:
turning the kitchen plan into a weekly operating packet before it becomes investor material.

documenting the operator os behind it here.

5. Hook Bank

Golden Glaze + central kitchen

1. we're trying to raise $1m for a donut kitchen. before i send the deck, this has to be clean.
2. 7 shops is where a donut business stops being cute and starts needing systems.
3. the central kitchen sounds like a growth move. it's actually a controls problem.
4. if the transfer logs are wrong, the central kitchen just moves chaos upstream.
5. before i spend $1m, i need this dashboard to tell the truth.
6. the kitchen model is not about ovens. it's about waste, timing, and accountability.
7. every shop wants product on time. the system has to prove where it went.
8. centralized production only works if the reporting gets tighter.
9. the investor deck is the easy part. the operating packet is the hard part.
10. the $1m raise has to be backed by boring controls.

Operator OS

11. i don't need ai to write captions. i need it to catch cash variance before i miss it.
12. this is what 7 shops and 11 rentals look like before 8am.
13. the dashboard is boring because the work is not.
14. i built this because the existing tools made managers do extra work.
15. ai is cheap. adoption is the expensive part.
16. the bot is not the product. the exception is the product.
17. if a manager won't use it at 4am, it does not count.
18. the system only matters if it finds the red row before i do.
19. most dashboards fail because they ask the operator to hunt.
20. the operating system is just one question: what needs attention right now?

FlexStay

21. 11 rentals taught me the same lesson as 7 donut shops.
22. guest ops and shop ops break in the same place: handoffs.
23. a turnover board is just a production schedule with beds instead of donuts.
24. vendor follow-up is not a reminder problem. it's a proof problem.
25. the guest message is not the issue. the unresolved next action is.
26. the property looks calm until three handoffs fail at once.
27. insurance housing is not passive. it is operations with furniture.
28. the same control loop works: intake, status, proof, exception.
29. i don't need more messages. i need fewer unknowns.
30. every property needs one red row, not ten tabs.

Founder tension

31. i left tech and accidentally rebuilt the part of tech i needed.
32. 13 years managing engineers did not prepare me for a 4am kitchen floor.
33. the hard part was not buying the shops. it was making the work visible.
34. every business looks simple until the handoffs stack.
35. the numbers were fine. the operating visibility was not.
36. my old job had dashboards. my new businesses had screenshots and texts.
37. the first version was ugly. that is why it worked.
38. the system got better when i stopped trying to make it impressive.
39. what i thought was a software problem was actually an adoption problem.
40. the more physical the business, the less useful generic software gets.

Conversion / series hooks

41. central kitchen update #1: the model is not ready yet.
42. operator os build log: this week i fixed the wrong thing first.
43. receipts from the back office: one thing that worked, one thing that broke.
44. before this module, i checked this manually.
45. i thought this would save time. it actually caught a miss.
46. the next 30 days are about making the raise packet operationally true.
47. this is the boring system behind the public growth story.
48. i am documenting the control layer behind two operating businesses.
49. if this works, i should need fewer check-ins, not more.
50. this is the part of the business no one puts in the investor deck.

6. Viral Hook Library Adapted To Jack

The attached hook library is useful, but only after it gets filtered through Jack's actual receipts. Do not copy the generic phrasing. Use the structure, then swap in a real business object, real number, real constraint, or real operating consequence.

Voice filter before using any hook

Use:

• numbers: 7 shops, 11 rentals, 20+ employees, $60k/yr replaced, $1m raise, 3-week build
• objects: dashboard, cash log, transfer sheet, kitchen plan, vendor board, investor packet
• tension: growth vs. controls, software vs. adoption, investor story vs. operating truth
• payoff: show the thing, explain the decision, reveal the miss, document the next fix

Avoid:

• "dream result"
• "financial freedom"
• "not to flex"
• "slightly unethical hacks"
• fake certainty
• keyword-bait CTAs on every post
• broad AI hype without a real screen, number, or process

Template Families From The Hook Library

Use these as the new packaging layer for the existing 30-day calendar.

1. before / during / after

• source pattern: "this represents your x before, during, and after x."
• jack version: show an operating workflow before software, during rollout, and after adoption.
• examples:
  • this is our donut shop reporting before, during, and after the operator os.
  • this is what a $1m kitchen plan looks like before the controls are ready.
  • this is flexstay before, during, and after one clean turnover board.
  • this is what cash control looked like before i stopped trusting screenshots.
  • this is what investor reporting looks like before the business earns the deck.

2. exact amount / exact number

• source pattern: "here's exactly how much x you need to get y."
• jack version: make the number concrete and operational.
• examples:
  • here's exactly what had to be true before i could take a $1m kitchen raise seriously.
  • here are the 5 rows i check before i trust a donut shop's daily report.
  • here's the $60k/yr software stack i replaced before it became a bigger problem.
  • here are the 3 numbers that matter more than revenue in a 7-shop rollup.
  • here's how many handoffs it takes for a simple turnover to become expensive.

3. 60-second tutorial

• source pattern: "can you tell us how to x in 60 seconds?"
• jack version: fast screen-recorded walkthrough with one narrow workflow.
• examples:
  • 60 seconds: how i check 7 shops without opening 7 spreadsheets.
  • 60 seconds: how i spot a cash variance before it turns into a manager conversation.
  • 60 seconds: how i turn a guest message into a tracked next action.
  • 60 seconds: how a central kitchen transfer should flow through the system.
  • 60 seconds: how i decide if a dashboard is useful or just pretty.

4. starting-over scenario

• source pattern: "if i woke up with x tomorrow and wanted y by z, here's exactly what i would do."
• jack version: useful, not guru. make it about rebuilding a control loop.
• examples:
  • if i had to run 7 shops from zero reporting tomorrow, this is what i would build first.
  • if i had to rebuild flexstay ops from scratch, i would start with this board.
  • if i had to prep for a $1m raise in 30 days, i would not start with the deck.
  • if i had to replace $60k/yr in software again, i would build the exception view first.
  • if i had to buy another shop tomorrow, this is the first control i would check.

5. everyone says x, nobody shows y

• source pattern: "everyone tells you to x but nobody actually shows you how to do it."
• jack version: use it when the post genuinely shows the workflow.
• examples:
  • everyone says "use ai in your business." nobody shows the 4am manager workflow.
  • everyone says "centralize production." nobody shows the transfer-control problem.
  • everyone says "raise capital." nobody shows the operating packet behind the deck.
  • everyone says "buy boring businesses." nobody shows the boring part.
  • everyone says "build systems." nobody shows what happens when staff ignore them.

6. if you want / if you don't want

• source pattern: "if you want x, do y" or "if you want to end up x, skip this video."
• jack version: frame stakes without sounding like a coach.
• examples:
  • if you want a central kitchen to work, fix transfer proof before ovens.
  • if you don't want 7 shops turning into 7 different businesses, standardize the daily report.
  • if you want ai to matter, make it own one ugly workflow.
  • if you don't want a dashboard no one uses, test it with the person opening the shop.
  • if you want investor updates to be useful, build the operating packet first.

7. what x looks like when

• source pattern: "this is what x looks like when you're doing y."
• jack version: pair screen recording with shop/property reality.
• examples:
  • this is what 7 donut shops look like when the check-ins actually roll up.
  • this is what a turnover board looks like when every vendor update has a next action.
  • this is what cash control looks like when the system flags the exception first.
  • this is what a raise looks like before the numbers are polished.
  • this is what ai looks like when it has to survive a physical business.

8. first things to do right away

• source pattern: "when you get x, here are the # things you have to do right away."
• jack version: acquisition, new property, new module, new manager, new shop.
• examples:
  • when you buy a donut shop, these are the 5 controls i would check first.
  • when a new flexstay property goes live, these are the 4 handoffs i want visible.
  • when a cash variance shows up, these are the 3 things i check before asking anyone.
  • when a manager starts using the system, these are the 2 screens that matter.
  • when a central kitchen plan starts getting real, these are the controls to build first.

9. mistake / warning

• source pattern: "don't start x until you learn y."
• jack version: warn against scaling before proof.
• examples:
  • don't centralize production until the shop-level reporting tells the truth.
  • don't build another dashboard until you know who has to act on the red row.
  • don't raise on a growth story if the operating packet cannot defend it.
  • don't automate a broken handoff. make the miss visible first.
  • don't buy another shop until you know which reports you still do by hand.

10. tier list / ranking

• source pattern: "industry tier list for year."
• jack version: rank workflows, not people.
• examples:
  • donut shop controls tier list: what matters before a central kitchen.
  • ai workflows i would build again vs. never touch again.
  • flexstay handoffs ranked by how expensive they get when missed.
  • qsr dashboards ranked by whether a manager would actually use them.
  • investor packet sections ranked by how much operating truth they reveal.

11. cost breakdown

• source pattern: "i built this x for $y."
• jack version: connect build cost, avoided SaaS, and adoption cost.
• examples:
  • i replaced $60k/yr in qsr software. the expensive part was not the code.
  • i built this in 3 weeks. here is the part that still took operator judgment.
  • this dashboard cost less than the software it replaced, but only because the workflow was narrow.
  • the central kitchen will cost real money. this control layer costs attention first.
  • the cheapest software is the one staff actually use.

12. turned x into y

• source pattern: "i turned one x into # different y."
• jack version: show repurposing one operating truth across businesses/platforms.
• examples:
  • i turned one cash-control problem into 5 pieces of content.
  • i turned one turnover miss into a repeatable flexstay workflow.
  • i turned one manager check-in into an investor-reporting input.
  • i turned one kitchen planning question into a whole operating packet.
  • i turned one ugly spreadsheet into the screen i actually check every morning.

13. questions before action

• source pattern: "here are # questions i ask before x."
• jack version: decision filters for buying, raising, building, hiring, centralizing.
• examples:
  • 5 questions i ask before i build another ai workflow.
  • 7 questions i want answered before the central kitchen spend gets real.
  • 4 questions i ask before trusting a daily sales report.
  • 6 questions i ask before adding another flexstay unit.
  • 3 questions i ask before a number goes into the investor packet.

14. if i only had x days

• source pattern: "if i only had x time, this is exactly what i would do."
• jack version: use for 7-day build sprints and 30-day raise-readiness.
• examples:
  • if i only had 7 days to clean up shop reporting, i would do this first.
  • if i only had 30 days before investor conversations, this is what i would fix.
  • if i only had one weekend to improve flexstay ops, i would build this board.
  • if i only had one screen for 7 shops, it would show this.
  • if i only had one metric for central kitchen readiness, it would not be revenue.

15. save-you-time tutorial

• source pattern: "i'm going to save you x minutes with y tips."
• jack version: show an operator shortcut that removes hunting, follow-up, or duplicate checking.
• examples:
  • this saves me 20 minutes every morning because it tells me what is wrong first.
  • this saves a manager from sending 3 texts after close.
  • this saves me from opening every shop report just to find one missing number.
  • this saves the investor packet from becoming a storytelling exercise.
  • this saves flexstay ops from becoming a message archaeology project.

100 Adapted Hooks For The Calendar

Use these to rewrite the first line of existing captions and scripts. Keep the body from the turnkey playbooks unless the hook demands a matching first visual.

Golden Glaze / central kitchen

1. this is what a $1m donut kitchen plan looks like before the deck gets pretty.
2. everyone says centralize production. nobody shows the transfer sheet problem.
3. if i had 30 days before investor conversations, i would fix this before the pitch deck.
4. 7 shops is where donut ops stops being cute and starts needing controls.
5. here's exactly what i need to prove before spending $1m on a central kitchen.
6. don't centralize production until the daily reports tell the truth.
7. this is what 7 shops look like when one number is missing.
8. i thought the central kitchen was a growth project. it is a reporting project first.
9. here are 5 controls i want clean before the kitchen gets funded.
10. the kitchen plan is not about ovens. it is about waste, timing, and proof.
11. if the transfer logs are wrong, the central kitchen just moves chaos upstream.
12. here's the boring part behind a $1m raise.
13. before i send the investor deck, i need this weekly packet to work.
14. this is the same donut business before and after the control layer.
15. how many reports should it take to trust 7 shops? fewer than this.
16. the investor story is growth. the operator story is whether the rows tie out.
17. if you want to buy more shops, first make the existing shops comparable.
18. here are 3 ways a central kitchen can fail before the food leaves the building.
19. this is what production planning looks like when every shop wants product on time.
20. i would rather find the miss here than explain it later.

Operator OS / AI workflows

21. everyone says "use ai." nobody shows the workflow that has to survive 4am.
22. i replaced $60k/yr in software. the code was not the hard part.
23. this is what ai looks like when it has to work inside a physical business.
24. if a manager will not use it during a shift, the build does not count.
25. here's the only dashboard i care about: the one that tells me what needs attention.
26. i built this in 3 weeks because the old tools made operators hunt.
27. this is what 7 shops and 11 rentals look like before 8am.
28. don't automate a broken handoff. make the miss visible first.
29. here are the 4 screens i check before i trust the morning.
30. the bot is not the product. the exception is the product.
31. if i had to rebuild this from scratch, i would start with the red rows.
32. this saved time only after it started catching misses.
33. i do not need ai to sound smart. i need it to flag the thing i forgot.
34. this is why generic dashboards fail in boring businesses.
35. here's the difference between software adoption and software theater.
36. i turned one ugly spreadsheet into the screen i actually open.
37. if the system needs perfect users, it is not a system.
38. this is the part of the workflow no SaaS demo wants to show.
39. i built the first version ugly on purpose. then people used it.
40. 60 seconds: how i check what needs attention across both businesses.

FlexStay / housing ops

41. 11 rentals taught me the same lesson as 7 donut shops.
42. a turnover board is a production schedule with beds instead of donuts.
43. everyone thinks guest ops is messages. the real problem is next actions.
44. this is what flexstay looks like when every vendor update has an owner.
45. if i had to rebuild flexstay ops in one weekend, this is the first board.
46. don't add another property until the handoffs are visible.
47. here's how one guest message turns into three operational risks.
48. insurance housing is not passive. it is operations with furniture.
49. this saves me from digging through old messages to find the real status.
50. the property looks calm until the cleaning handoff breaks.
51. here are the 5 rows i want visible before same-day turnover.
52. the guest does not care about our process. they care if the next step happened.
53. this is the same control loop as donut ops: intake, status, proof, exception.
54. if a vendor update lives only in text, it is not a system.
55. i do not need more notifications. i need fewer unknowns.
56. here is what a clean turnover handoff should show in 60 seconds.
57. this is how flexstay becomes repeatable instead of reactive.
58. the missed message is rarely the real issue. the missing owner is.
59. here are 3 flexstay handoffs that get expensive when they disappear.
60. this board exists because memory is not a process.

Investor / raise / control

61. everyone says raise capital. nobody shows the operating packet behind it.
62. before this number goes into the deck, it has to survive the weekly packet.
63. if i were investing in this, these are the 5 controls i would ask about.
64. the pitch deck is the easy part. the proof packet is the hard part.
65. here are 3 questions i ask before a number becomes investor-facing.
66. i do not want prettier reporting. i want reporting that catches the miss.
67. this is what investor-readiness looks like before the narrative.
68. if the business cannot explain the variance, the deck should not hide it.
69. the raise is for growth. the content should show the controls.
70. here is the difference between a growth story and operating proof.
71. every investor update should answer this first: what changed and why?
72. if i only had one page for the packet, it would be this one.
73. this is the unsexy work before a $1m raise.
74. the best investor material is usually built for operators first.
75. here is what i want clean before anyone sees the forecast.
76. i would rather show the constraint than pretend it does not exist.
77. this is the part of the business that makes the growth story believable.
78. before i ask for capital, i want the operating rhythm tighter.
79. here are 4 ways reporting can make a rollup look better than it is.
80. the model only matters if the weekly operating truth backs it up.

Founder / operator tension

81. i left tech and ended up building the software my businesses needed.
82. 13 years in tech did not prepare me for 20+ deskless workers.
83. the hard part was not buying the shops. it was seeing the work clearly.
84. this is what corporate dashboards never taught me about physical businesses.
85. i thought i needed better software. i needed better handoffs.
86. if i had stayed in tech, i probably would have overbuilt this.
87. the first version worked because it did one ugly job.
88. this is what happens when a tech person buys a donut business and stops romanticizing it.
89. i do not want to build a startup. i want my businesses to stop leaking attention.
90. the more physical the business, the less useful generic software gets.
91. i learned more from one missed shop check-in than from a polished dashboard.
92. this is the business lesson i did not get from corporate tech.
93. everyone talks about leverage. this is the boring version.
94. i am not building ai for demos. i am building it for monday morning.
95. the best feature is the one that prevents a text thread.
96. this looks simple because the complicated part got pushed into the workflow.
97. i stopped asking "can ai do this?" and started asking "who acts on the answer?"
98. if it cannot survive real staff, real vendors, and real customers, it is not useful.
99. the business did not need another app. it needed one place to see the miss.
100. this is the part of building that makes the public story true.

How To Use This In The HTML

Modify existing post blocks by changing:

• first on-screen text
• first caption sentence
• first 2 seconds of the script

Do not rewrite every full caption from scratch. The hook should make the existing turnkey caption sharper, not erase the operating detail.

Recommended update sequence:

1. Pick the day's original topic.
2. Choose one family above.
3. Swap in the strongest adapted hook.
4. Make the first visual prove the hook within 2 seconds.
5. Keep the caption concrete and end with an artifact-based CTA.

7. 30-Day Overlay For Existing Playbook

Do not delete the existing playbook captions. Use this overlay to improve them.

Days 1-7

Make the first week about the origin plus the new kitchen stake:

• Day 1: origin, but end with "now the next test is a $1m kitchen plan."
• Day 2: 7-shop morning operating surface.
• Day 3: $60K software replacement.
• Day 4: shop floor proof, no lesson.
• Day 5: batch day with central kitchen visuals.
• Day 6: deal math becomes kitchen/use-of-funds discipline.
• Day 7: central kitchen tension.

Days 8-14

Make week 2 about the control loop:

• deskless workforce
• Discord as ops surface
• Receipts Friday
• cash variance
• FlexStay repeatability
• investor reporting discipline

Days 15-21

Make week 3 about investor-readiness:

• variance story
• raise packet
• central kitchen failure modes
• data room gaps
• before/after workflows

Days 22-30

Make week 4 about proof and conversion:

• investor reporting
• tool stack reveal
• receipts friday
• why not better SaaS
• raise/kitchen readiness snapshot
• 30-day recap with what operators asked about

8. Conversion Path

Primary CTA should be soft and artifact-based.

Use:

• "documenting the operator os behind this here."
• "the full breakdown goes in receipts from the back office."
• "i'm turning this into the weekly operating packet before it becomes investor material."
• "saving the before/after here as i build it."

Avoid:

• "dm me"
• "comment X"
• "follow for more"
• "get my free guide"
• "anyone can do this"

Exception: if a post has a concrete artifact that people will ask for, use one direct CTA:

• "comment 'packet' and i'll send the sanitized layout."
• "comment 'stack' and i'll send the module list."

Use that no more than once per week.

Current 30-Day Calendar

Window: Wednesday 2026-05-20 through Thursday 2026-06-18
Goal: launch the Operator OS lane, build the habit, and give TikTok the most shots at a breakout.
Primary platform: TikTok. Mirror 4-5 winners to IG Reels. LinkedIn gets 2-3 posts/week with a stronger setup.
Pillars: Operator OS, Golden Glaze rollup + $1M centralized-kitchen plan, FlexStay repeatability proof. Golden Ops is the center of gravity; selling premium/the wheel is personal capital context only, not an active content pillar.

Operating Rules

• Shoot vertical, 9:16, 45-75 seconds unless noted.
• Record clean files without TikTok watermark before posting anywhere.
• Every post needs one receipt: a number, screenshot, workflow map, shop/property moment, invoice, dashboard, or actual decision.
• No guru phrasing. No motivational CTA. No "you guys." Talk to one operator.
• Default CTA: link in bio / newsletter. Do not run comment-keyword loops.
• Batch on Sundays. Capture b-roll during normal ops, not staged.

Weekly Cadence

• TikTok: 5-7/week. Main discovery engine.
• Instagram: 4-5 Reels/week, 1 carousel/week, daily Stories from real operations.
• LinkedIn: 2-3/week. Text-first, numbers up front, no lowercase requirement.
• Newsletter: one issue on Day 14 and one draft by Day 28.

Asset Checklist

Capture these before Day 1-3:

• 10 clips: shop exterior, racks, fryer, glazing, POS screen with sensitive info blurred, delivery/table area, manager check-in, empty back office, laptop dashboard, early morning car.
• 8 screen recordings: Golden Ops cockpit, Discord check-in flow, scheduling view, inventory/on-hand count flow, cash control/reconciliation, Toast sales report, KPI/review tracker, investor dashboard/modeler.
• 4 FlexStay recordings: turnover board, vendor dispatch thread, maintenance log, reservation/property dashboard.
• 2 Golden Glaze capital-plan recordings: raise/use-of-funds working doc and central-kitchen capacity or equipment model with sensitive details hidden.
• 3 receipts: SaaS invoices canceled/replaced, acquisition spreadsheet excerpt, 13-week cash forecast excerpt.

Execution Lens

The day-by-day calendar below is still usable, but execute it as an Operator OS launch sequence.

• If a post can show a module, show the module.
• If a post can compare before/after workflow, show the workflow.
• If a post can include FlexStay as repeatability proof, include it without turning the post into STR guru content.
• Cut wheel/premium posts unless Jack explicitly asks for personal capital context.
• Golden Glaze raise/kitchen posts must stay factual: no solicitation, no hype, no return promises.
• Redact secrets, employee names, guest names, LP names, addresses, and private financials before recording.

Day 1 — Wed May 20 — Origin Anchor

Primary: TikTok 6:15am CT
Mirror: IG Reel 7:30pm CT
LinkedIn: text post 7:45am CT

Pillar: the rollup / Operator OS origin
Hook: "i left corporate with severance. 18 months later i own 7 donut shops."
Video beats: 13 years in tech -> planned layoff -> 7 shops -> 20+ employees -> 11 units -> Golden Ops built solo -> the operating system behind the businesses.
Visuals: talking head in car, quick cuts to shop b-roll and Golden Ops screen.
LinkedIn angle: not a quitting story; a runway story that ended with Jack building the software layer underneath the businesses. Mention severance, 5 rentals at exit, 12 months savings, then 18-month result.
CTA: "following along here. receipts only."

Day 2 — Thu May 21 — What 7 Shops Look Like

Primary: TikTok 7:30pm CT
Mirror: IG Reel next morning if retention is decent
LinkedIn: none

Pillar: Operator OS / Golden Glaze control loop
Hook: "running 7 donut shops before most people wake up. 90 seconds."
Video beats: show the operating surface: check-ins, sales, waste, labor, issues. Explain the control loop: signal -> exception -> owner attention. The goal is not more dashboards, it is fewer surprises.
Visuals: blurred Discord/Golden Ops scroll, shop b-roll, manager note screenshot with names hidden.
IG Story: one real behind-the-scenes frame from a shop.
CTA: link in bio for longer receipts.

Day 3 — Fri May 22 — The $60K Stack

Primary: TikTok 6:15am CT
Mirror: IG Reel + save as Highlight "ops stack"
LinkedIn: document carousel

Pillar: Operator OS / Golden Ops
Hook: "i replaced about $60k/year of qsr software in 3 weeks."
Video beats: what got replaced: scheduling, daily check-ins, inventory, cash control, investor reporting. Say this is not a SaaS demo; it is the operating system behind the shops. Say what you would not rebuild.
Visuals: invoice/category list, Golden Ops screen, code editor for 1 second, final dashboard.
LinkedIn carousel: 8 slides: SaaS line items -> why generic tools failed -> Discord as ops surface -> scheduling -> inventory -> cash control -> investor dashboards -> what not to build.
CTA: newsletter: "the stack breakdown goes out next week."

Day 4 — Sat May 23 — Light Receipt Day

Primary: IG Stories only
Secondary: TikTok optional if a clip from Friday hits

Pillar: the rollup
Story frames: 1 shop clip, 1 metric screenshot with sensitive info hidden, 1 short text note: "saturday is where donut shops tell the truth."
Prep: pull one acquisition spreadsheet screenshot for Day 5.
No LinkedIn.

Day 5 — Sun May 24 — Batch Day

Primary: no public post unless there is a strong organic clip
Work block: 90 minutes

Record: Days 6-10 TikToks in one sitting.
Shots needed: acquisition spreadsheet, wheel tracker, cash variance dashboard, scheduling flow, manager check-in flow.
Write: LinkedIn posts for Day 6 and Day 8.
Review: cut any clip that sounds like advice without a receipt.

Day 6 — Mon May 25 — Deal Math

Primary: TikTok 6:15am CT
Mirror: IG Reel
LinkedIn: text post 8:00am CT

Pillar: the rollup
Hook: "the spreadsheet i use before buying a donut shop."
Video beats: revenue, labor, COGS, rent, equipment risk, manager depth, cash payback. Show one bought vs one passed with numbers anonymized.
Visuals: spreadsheet with columns blurred where needed, shop exterior, note that acquisition glamour is mostly math.
LinkedIn angle: why passing on a bad shop is the highest-return deal you do.
CTA: none. Let the detail carry it.

Day 7 — Tue May 26 — Why Golden Glaze Needs a Central Kitchen

Primary: TikTok 7:30pm CT
Mirror: IG Reel if comments ask about shop scaling
LinkedIn: none

Pillar: Golden Glaze capital plan
Hook: "7 shops is where a donut business starts needing a production backbone."
Video beats: why store-level prep gets messy at 7 shops, what central production should standardize, what still has to stay local, and why the $1M raise has to be tied to controls, not vibes.
Visuals: blurred use-of-funds doc, production flow sketch, shop b-roll, inventory/waste dashboard.
Caption: "centralized production only works if the controls move with it."
CTA: newsletter link.

Day 8 — Wed May 27 — Managing 20+ Deskless Employees

Primary: TikTok 6:15am CT
Mirror: IG Reel
LinkedIn: text post 7:45am CT

Pillar: Operator OS / deskless workforce
Hook: "i managed engineers for 13 years. donut shops broke that playbook."
Video beats: engineers self-report; shop teams show work physically; dashboards only help when they capture exceptions. This is the reason the OS had to start in Discord instead of a polished dashboard.
Visuals: kitchen b-roll, manager check-in prompt, exception channel screenshot.
LinkedIn angle: don't force Slack habits onto deskless work. Build exception channels.
CTA: newsletter link.

Day 9 — Thu May 28 — The Bot I Was Embarrassed To Build

Primary: TikTok 7:30pm CT
Mirror: IG Reel
LinkedIn: none

Pillar: Operator OS / adoption
Hook: "the most useful software i built is a discord bot."
Video beats: explain why Discord won: managers already use phones, notifications work, zero migration, bot handles structure. Adoption beats polish.
Visuals: blurred bot prompts, daily digest, Drive folder routing.
IG Story: poll: "dashboard or bot?" then answer in next frame.
CTA: "build where the team already is."

Day 10 — Fri May 29 — Receipts Friday

Primary: TikTok 6:15am CT
Mirror: IG Reel
LinkedIn: short reflection post

Pillar: Operator OS weekly receipts
Hook: "3 receipts from this week running shops, software, and options."
Video beats: one shop metric, one Operator OS change, one cashflow/trade note. Keep each under 15 seconds.
Visuals: quick cuts; use the same template weekly.
LinkedIn angle: "The operating week in three numbers."
CTA: none.

Day 11 — Sat May 30 — Carousel: What I Check Every Morning

Primary: Instagram carousel
Secondary: TikTok optional VO-over-carousel
LinkedIn: none

Pillar: Operator OS cockpit
Carousel slides: title, sales vs 7-day avg, labor, waste, cash variance, open issues, missed check-ins, close.
Caption: "if a shop is healthy, i don't need a paragraph. i need exceptions."
Story: share carousel with one note: "this is the morning screen."
CTA: save this if you run physical ops.

Day 12 — Sun May 31 — Batch + Comments

Primary: no new feed post
Work block: 90 minutes

Tasks: reply to high-signal comments, save operator questions, record Days 13-17.
Capture: one options screen record, one cash variance example, one investor dashboard clip.
Write: newsletter issue #1 skeleton: "the stack i built because qsr saas was too expensive."

Day 13 — Mon Jun 1 — What I Would Not Build

Primary: TikTok 6:15am CT
Mirror: IG Reel
LinkedIn: text post

Pillar: Operator OS / build vs buy
Hook: "i replaced $60k of saas, but i would not rebuild these 3 things."
Video beats: payroll, accounting core, POS payments. Explain why regulated/high-risk systems stay bought and specific/friction-heavy workflows get built.
Visuals: category list, red/yellow/green build-vs-buy board.
LinkedIn angle: internal tools are leverage, not religion.
CTA: newsletter signup for stack breakdown.

Day 14 — Tue Jun 2 — Newsletter Issue #1

Primary: newsletter send
TikTok: 7:30pm CT teaser
IG: Story link

Pillar: Golden Ops
Newsletter title: "the $60k software bill i killed first."
Structure: the bill, the workflow, the smallest replacement, what still stays bought, mistake made.
TikTok hook: "i sent the full breakdown of the saas i replaced. here's the part people will disagree with."
CTA: link in bio.

Day 15 — Wed Jun 3 — Variance Story

Primary: LinkedIn 7:45am CT
TikTok: 6:15am CT
IG: carousel 7:30pm CT

Pillar: the rollup
Hook: "13 years of w-2. the variance broke me before the math did."
Video beats: W-2 predictability -> portfolio income shape -> generator/food cost/manager churn -> observability system.
Visuals: cash forecast excerpt, anomaly alert, dashboard.
LinkedIn: use the variance story draft, updated to 20+ employees / $60K where relevant.
CTA: none.

Day 16 — Thu Jun 4 — The $1M Raise Has To Prove This

Primary: TikTok 7:30pm CT
Mirror: IG Reel
LinkedIn: none

Pillar: Golden Glaze capital plan
Hook: "what the $1m raise actually has to prove before it gets spent."
Video beats: use-of-funds, kitchen capex, production capacity, transfer controls, waste visibility, and what data has to be clean before investor materials go out.
Visuals: redacted use-of-funds table, kitchen equipment list, capacity model, Golden Ops dashboard.
Caption: "raise prep is operating prep."
CTA: none.

Day 17 — Fri Jun 5 — Manager Voice Memo

Primary: TikTok 6:15am CT
Mirror: IG Reel
LinkedIn: short post if the clip is strong

Pillar: Operator OS / issue routing
Hook: "this 12-second manager note is why i built Golden Ops."
Video beats: play/recreate a sanitized manager note, show how it becomes an issue, explain the alert routing, then compare it to FlexStay maintenance/turnover routing if there is room.
Visuals: voice memo waveform or transcript, issue card, resolved state.
CTA: none.

Day 18 — Sat Jun 6 — Shop Walkthrough

Primary: IG Reel
Secondary: TikTok repost only if strong

Pillar: Operator OS / floor signal
Hook: "first 90 seconds inside one of my shops. what i actually notice."
Video beats: floor, racks, speed, cleanliness, manager confidence, exception board.
Visuals: first-person shop walkthrough.
Story: "saturday floor check" with 2 frames.
CTA: save for operators.

Day 19 — Sun Jun 7 — Batch + Analytics Review

Primary: no feed post
Work block: 2 hours

Review: top 5 posts by retention, shares, saves, comments from real operators.
Decision: pick one recurring series to double down on for week 4. Default if unclear: "Receipts Friday."
Record: Days 20-24.
Write: LinkedIn posts Day 20 and Day 22.

Day 20 — Mon Jun 8 — 13-Week Cash Forecast

Primary: TikTok 6:15am CT
Mirror: IG Reel
LinkedIn: document carousel

Pillar: Golden Glaze capital plan / control system
Hook: "the cash forecast that stopped me refreshing dashboards all day."
Video beats: why W-2 habits made variance stressful, what the forecast tracks, buffer rules, when to act.
Visuals: forecast excerpt, buffer rule note, dashboard.
LinkedIn carousel: 7 slides: variance -> forecast -> fixed costs -> payroll -> capex -> buffer -> decision rule.
CTA: newsletter link.

Day 21 — Tue Jun 9 — Central Kitchen Failure Modes

Primary: TikTok 7:30pm CT
Mirror: IG Reel
LinkedIn: none

Pillar: Golden Glaze capital plan
Hook: "central kitchens fail when transfers become invisible."
Video beats: what moves to central production, what each shop still owns, where waste hides, how stockouts happen, and which daily controls prevent the kitchen from becoming a black box.
Visuals: production flow map, transfer log mock, waste report, shop receiving checklist.
Caption: "the kitchen only works if the reporting gets tighter."
CTA: none.

Day 22 — Wed Jun 10 — Investor Reporting

Primary: LinkedIn 7:45am CT
TikTok: 6:15am CT
IG: Reel

Pillar: Operator OS / investor infrastructure
Hook: "the report matters less than whether it shows up on time."
Video beats: GP/LP structure, Golden Invest / investor dashboard, why quarterly reporting cadence builds trust, how automation reduces excuses. Redact sensitive LP and entity details.
Visuals: reporting flow, blurred PDF cover, calendar reminder.
LinkedIn angle: sub-scale GP reputation is built in boring reporting cadence.
CTA: none.

Day 23 — Thu Jun 11 — Tool Stack Screen Record

Primary: TikTok 7:30pm CT
Mirror: IG Reel
LinkedIn: none

Pillar: Operator OS / stack reveal
Hook: "my operator stack is uglier than people expect."
Video beats: Cursor/Claude, Discord, Google Drive, Golden Ops, Golden Cash Control, Sales Report, KPI/ReviewIQ, FlexStay Ops, Sheets/Notion where needed. Explain why ugly wins if it ships and gets adopted.
Visuals: rapid screen-record tour.
Caption: "pretty software is expensive if nobody uses it."
CTA: link in bio.

Day 24 — Fri Jun 12 — Receipts Friday #2

Primary: TikTok 6:15am CT
Mirror: IG Reel
LinkedIn: short post

Pillar: Operator OS weekly receipts
Hook: "3 numbers from this week."
Video beats: one shop result, one ops alert, one premium collected or trade decision.
Visuals: repeat Day 10 template for series recognition.
LinkedIn angle: "The operating week in three numbers, week 2."
CTA: none.

Day 25 — Sat Jun 13 — Founder Face / Quiet Day

Primary: IG Stories
Secondary: TikTok optional

Pillar: operator identity
Story frames: one shop check, one laptop/back-office clip, one sentence: "the work is mostly boring. that's why it works."
Prep: collect questions from comments for Day 26 Q&A.
No LinkedIn.

Day 26 — Sun Jun 14 — Q&A Batch

Primary: TikTok Q&A post if there is a strong question
Work block: 90 minutes

Prompt: answer one comment from an operator, not a generic follower.
Default hook: "someone asked why i don't just buy better saas."
Record: 3 short answer clips for week 5.
Plan: newsletter issue #2 outline from best-performing pillar.

Day 27 — Mon Jun 15 — Why Not Better SaaS?

Primary: TikTok 6:15am CT
Mirror: IG Reel
LinkedIn: text post

Pillar: Operator OS / build vs buy
Hook: "why didn't i just buy better qsr software?"
Video beats: median customer problem, deskless adoption, workflows too specific, cost vs speed, what still stays bought. Use actual examples from Golden Ops, Cash Control, Sales Report, KPI, and FlexStay Ops.
Visuals: old workflow map -> new bot/workflow.
LinkedIn angle: internal tools win when specificity is the moat.
CTA: newsletter link.

Day 28 — Tue Jun 16 — Raise + Kitchen Readiness Snapshot

Primary: TikTok 7:30pm CT
Mirror: IG Reel
LinkedIn: only if the investor-safe version is clean

Pillar: Golden Glaze capital plan
Hook: "where the $1m kitchen plan is ready, and where it is not."
Video beats: data room status, use-of-funds draft, equipment/capacity model, capex tracking plan, missing numbers, and next decisions.
Visuals: redacted readiness checklist, kitchen model, investor packet outline.
Caption: "no hype. just what is ready and what still needs work."
CTA: none.

Day 29 — Wed Jun 17 — The 20+ Employee Lesson

Primary: LinkedIn 7:45am CT
TikTok: 6:15am CT
IG: carousel

Pillar: Operator OS / consistency
Hook: "the hardest part of 20+ employees isn't management. it's consistency."
Video beats: one shop can hide issues; seven shops expose system gaps; consistency comes from prompts, checklists, and exception routing.
Visuals: checklists, store comparison, issue queue.
LinkedIn angle: multi-unit ops are a consistency business, not a hustle business.
CTA: none.

Day 30 — Thu Jun 18 — Month 1 Recap + Next Series

Primary: TikTok 7:30pm CT
Mirror: IG Reel
LinkedIn: recap post next morning if metrics are clean

Pillar: Operator OS recap
Hook: "30 days of posting receipts. here's what got real operators to dm me."
Video beats: top post, top operator question, most saved module, one surprise, what Operator OS series continues next month.
Visuals: analytics screenshots, comment screenshots with names hidden, content calendar check marks.
CTA: "next month i'm going deeper on the series that worked."

Week-by-Week Production Checklist

Week 1: ship origin, stack, deal math. Prove the lane.
Week 2: introduce premium and variance. Prove range without losing the operator center.
Week 3: investor reporting, forecast, manager note. Prove operating discipline.
Week 4: repeat the series, answer real comments, pick the winner for Month 2.

Repurposing Rules

• TikTok wins become IG Reels within 24 hours with clean export and new cover.
• LinkedIn gets the same idea only when there is enough context for a non-video reader.
• Carousels should come from dashboards, forecasts, or step-by-step systems. Do not make quote carousels.
• Stories are proof of work: shop floor, back office, trade notes, shipping queue.

Review Scorecard

Score every post before shipping:

• Does it contain a real number or artifact?
• Could another creator say this? If yes, rewrite.
• Does the hook name a specific thing, not a category?
• Is there one idea only?
• Is the CTA light or absent?
• Would Jack actually say this out loud?

If a post fails two checks, scrap it. Record a new one.

30-Day Playbook — Days 1-10

Window: Wed 2026-05-20 through Fri 2026-05-29 Pillars: Operator OS, Golden Glaze rollup, FlexStay repeatability proof, operator treasury Format: full production depth — script, b-roll, captions, production notes per day Status: internal review — for Jack only

Revision note: execute this batch through the Operator OS lens in 05_operator_os_revision.md. Golden Glaze is the main lab; software/workflow artifacts should be shown whenever possible. Wheel content is a smaller operator-treasury lane.

Day 1 — Wed May 20 — Origin Anchor

Pillar: the rollup / Operator OS origin Primary: TikTok 6:15am CT Mirror: IG Reel 7:30pm CT LinkedIn: text post 7:45am CT Hook: "i left corporate with severance. 18 months later i own 7 donut shops."

B-roll shot list

1. 0-3s — Hook frame: talking head in driver seat of car, dawn light through windshield, on-screen text "i left corporate with severance. 18 months later i own 7 donut shops." Phone on dash mount, 9:16, soft sodium streetlight.
2. 3-8s — Severance beat: cut to laptop closed on passenger seat, then quick cut to shop exterior pre-dawn with neon "Golden Glaze" sign just turning on.
3. 8-15s — Runway beat: screen-record overlay of 5 STR pin map (hawaii, dfw, tampa) zooming out, hide street addresses.
4. 15-25s — Result beat (rollup): rapid b-roll cuts — donut rack being loaded, fryer in motion, glazing wheel, POS screen with order info blurred, manager checking off a paper sheet. 5 cuts in 10 seconds.
5. 25-35s — Software receipt: screen-record of Golden Ops Discord daily digest message, then scheduler view, then inventory dashboard. Blur any names/dollar figures except total replaced figure if shown.
6. 35-45s — Deskless workforce beat: kitchen floor wide shot at 4am, then close-up of hands rolling dough. No faces.
7. 45-55s — Back to talking head in car: same setup, slightly different angle, deliver the close.
8. 55-60s — End card: lowercase text card on black: "receipts only. no motivational stuff."

TikTok caption + hashtags

13 years in tech. now i count donut trays at 4am and build the software myself. real numbers in bio.

#smbops #multiunitoperator #internaltools #donutshop #dfwsmallbusiness #buildlog #deskless

Instagram caption + hashtags

october 2024 i planned my way out of corporate. 18 months later — 7 donut shops, 11 rentals, 20+ employees on a kitchen floor at 4am, custom software i built solo in three weeks. $60k/yr in qsr saas replaced.

not a story about quitting your job. a story about what i'm building, with real numbers, as i go.

link in bio if you want the receipts every other week.

#multiunitoperator #smallbatchbakery #donutshop #smbbuilder #internaltools #dfwsmallbusiness #deskless #opsautomation

LinkedIn (proper case, ~280 words)

October 2024. 13 years in tech, six different companies, six-figure salary, full golden handcuffs. Every Sunday night I dreaded Monday and told myself it was just a season. I told myself that for five years.

Then I planned my way to a layoff.

Read the room — tech was deep in layoff cycles in 2024 — and let the timing work for me. Walked out with a six-figure severance. By that point I already had 5 short-term rentals cashflowing across Hawaii and DFW, and 12 months of savings stacked. Not a leap. A runway.

18 months in now.

11 STR/MTR units across Hawaii, DFW, and Tampa — more than doubled. Displaced families, traveling employees, insurance housing. Different lane than the Airbnb-bro content.

7 donut shops in DFW. GP/LP fund structure. 20+ employees on a kitchen floor at 4am. Running on custom software I built solo in three weeks — Discord ops layer, daily reporting, automated investor reports, scheduling. Now building inventory management and guest messaging too. Roughly $60K/yr of QSR SaaS replaced so far. Still growing.

Two physical-asset businesses. One operator. One laptop in the back office.

The hardest part wasn't the math. I managed engineers on Slack and Teams for 13 years. I'd never managed a deskless workforce — 20+ people on a kitchen floor at 4am who don't read messages between shifts. Different problem. Different tooling. None of the SMB SaaS in this category was built for it.

So I'm building it.

Following along here. No motivational stuff. Just receipts.

#smbtwitter #deskless #verticalsaas #etaforum #searchfund

Production notes

• Shoot location: driver seat of car, pre-dawn (5:30-6:00am pull-up at a shop), one take talking head + b-roll captured day-of in the shop.
• Lighting: dawn ambient only. Do not stage. The 4am light is the brand.
• Wardrobe: plain dark t-shirt or hoodie. No logo, no watch flex.
• Audio: lav mic. Ambient road/HVAC noise is fine and adds operator texture.
• Edit: hard cuts only, no transitions, no music under the talking head — only ambient/light pad under b-roll if needed.
• Retention bet: the line "i planned my way to a layoff" pays the first 3 seconds; the receipts list pays seconds 25-45.

Voice check

• Real numbers in every paragraph (Oct 2024 / 13 years / 5 STRs / 12 months / 11 units / 7 shops / 20+ / 3 weeks / $60K / 18 months)
• No banned phrases ("quit my 9-5", "financial freedom", "follow for more")
• Single CTA ("following along here. receipts only.")
• Operator POV — first-person reports, no "you should"
• No identity claims — artifacts label him, he doesn't label himself
• Tension before payoff (sunday night dread → planned layoff → 18-month result)

Day 2 — Thu May 21 — What 7 Shops Look Like

Pillar: the rollup Primary: TikTok 7:30pm CT Mirror: IG Reel next morning if retention is decent LinkedIn: none Hook: "running 7 donut shops before most people wake up. 90 seconds."

B-roll shot list

1. 0-3s — Hook frame: static shot of dark shop interior, only proofing-cabinet light on, on-screen text "running 7 donut shops before most people wake up. 90 seconds."
2. 3-10s — Operating surface: screen-record of Discord ops channel scroll with names/timestamps blurred — show structured post template, then 6am daily digest message.
3. 10-18s — Exception view: screen-record cut to Golden Ops dashboard, color-coded shop row strip (green green red green green green green) — hover-emphasize the red row.
4. 18-25s — Old workflow comparison: quick montage of generic Slack-style screen (could be a mockup or a 2024 personal Slack with content blurred), then jump back to the Discord ops view.
5. 25-35s — Shop floor reality: close-ups of greasy hands on a phone, manager swiping through the Discord channel between trays.
6. 35-45s — The "fewer surprises" payoff: wide of the operator (Jack) at a back-office laptop, calm, drinking coffee. Single screen. No multi-monitor.
7. 45-50s — End frame: black card with "exceptions, not dashboards."

TikTok caption + hashtags

running 7 shops on a phone before 6am. discord + a bot. fewer surprises is the whole product.

#smbops #multiunitoperator #qsr #deskless #internaltools #donutshop #dfwsmallbusiness

Instagram caption + hashtags

the operating surface for 7 shops is a discord server and a bot. managers post the open. the bot pushes a 6am digest. i read the exceptions, not the dashboard.

the gap between managing engineers on slack for 13 years and managing 20+ people on a kitchen floor at 4am was a tooling category nobody built. so i built it.

#smbops #multiunitoperator #internaltools #donutshop #dfwsmallbusiness #opsautomation #deskless #qsr

LinkedIn

Skip per calendar.

Production notes

• Shoot location: combination of shop interior pre-open (5:00-5:45am) + back-office laptop shot at home.
• Lighting: keep it dark. The vibe is "before most people are awake." Don't add fill light to the shop interior.
• Wardrobe: same as Day 1 for consistency — don't introduce new wardrobe yet.
• Audio: keep ambient kitchen sounds (mixer, exhaust hood) under the talking-head VO for texture.
• Edit: longer holds on the operating surface screen-record (3-5s each) so the viewer can read structure. Don't rush the receipt.
• Privacy: blur all employee names, shop addresses, and any dollar figures except the digest format. Re-watch frame-by-frame before export.
• Retention bet: the "i read the exceptions" line at ~15s is the retention pivot. Cut tight to it.

Voice check

• Real numbers (7 shops, 20+ employees, 13 years, 4am, 6am)
• No "you should", no motivational close
• One idea: exceptions over dashboards
• No identity label ("ops nerd", "builder", etc.)
• Receipt is the operating surface itself, shown on screen
• No CTA — calendar says "link in bio for longer receipts" — apply as pinned comment, not in the script

Day 3 — Fri May 22 — The $60K Stack

Pillar: Golden Ops Primary: TikTok 6:15am CT Mirror: IG Reel + save as Highlight "ops stack" LinkedIn: document carousel Hook: "i replaced about $60k/year of qsr software in 3 weeks."

B-roll shot list

1. 0-3s — Hook frame: talking head close-up at desk, on-screen text "$60k/yr of qsr saas. replaced in 3 weeks."
2. 3-10s — The stack visual: screen-record of a simple list (could be a Notion or Sheets doc) — left column "what got replaced", right column "what stays bought." Show 5 vs 3 categories. Hold 4s.
3. 10-18s — Scheduling receipt: screen-record of Golden Ops scheduler view — drag a shift, show conflict alert, resolve.
4. 18-26s — Daily check-in receipt: Discord ops channel — bot prompt, manager response, digest output.
5. 26-34s — Inventory + cash variance: quick cut to inventory count screen, then cash variance dashboard with shop name + amount masked.
6. 34-42s — Investor reporting receipt: screen-record of investor PDF cover (blur entity name + recipient), then back to the dashboard that auto-generates it.
7. 42-55s — The "stay bought" beat: talking head, list payroll / accounting / POS on screen as he says them.
8. 55-60s — Close frame: "i wasn't trying to make pretty software. i was trying to delete five logins." Text card on black.

TikTok caption + hashtags

5 logins → 1 stack. 3 weeks of build. $60k/yr of qsr saas off the books. what to build and what to leave bought.

#smbops #internaltools #qsr #multiunitoperator #buildlog #deskless #donutshop

Instagram caption + hashtags

$60k/yr in qsr saas, replaced in 3 weeks. five categories — scheduling, check-ins, inventory, cash variance, investor reporting.

what i did not touch — payroll, accounting, pos. anything regulated or expensive-to-be-wrong stays bought.

the build was fast because i'd been the user for a year first. that's the part the "internal tools" content skips.

#smbops #internaltools #qsr #multiunitoperator #buildlog #deskless #donutshop #opsautomation

LinkedIn (document carousel — 8 slides, proper case, 150-220 words in the caption)

Slide 1 (title): The $60K/yr Stack I Killed in 3 Weeks What got replaced, what stays bought, why.

Slide 2 (SaaS line items, redacted): What got cut: • Scheduling (deskless-unfriendly) • Daily check-ins (web app nobody opened) • Inventory counts (POS-based, store-level only) • Cash variance / till control (manual spreadsheet) • Investor reporting (3-tool stitch) $60K/yr combined.

Slide 3 (why generic tools failed): Every tool was built for a single-unit operator OR a 100+ unit chain. A 7-shop owner with deskless staff and a GP/LP fund structure on top is neither. The middle gap is where most rollup operators live.

Slide 4 (Discord as ops surface): Managers already had phones. Notifications already worked. Zero migration. The bot does the structure. The humans answer. Adoption on day 1 was 100% because nothing new had to be installed.

Slide 5 (scheduling): Old: web SaaS, email reminders, $X/employee/month. New: a Sheet, a Discord prompt, a conflict rule, a digest. Same outcome. 0 logins.

Slide 6 (inventory + cash control): Inventory: count → photo → bot → log. Reconciled against POS overnight. Cash variance: daily till count → bot → flagged if outside band. Both surfaced in the 6am digest, not a separate dashboard.

Slide 7 (investor reporting): GP/LP fund. Quarterly distributions. Investor expectations are clarity, not flash. Auto-generated PDF + Drive folder + DocuSend trail. The boring part is the reputation.

Slide 8 (what not to build): Payroll. Accounting core. POS + payments rail. Anything regulated or expensive-to-be-wrong stays bought. Internal tools are leverage, not religion.

Carousel caption:

$60K/yr of QSR SaaS, replaced in 3 weeks. 5 categories cut, 3 categories left alone, and the operating discipline behind which is which.

The build was fast because I'd been the user for a year before I wrote a line of code. The first version was uglier than anything I'd ever shipped at a tech company. The team didn't care. They cared that it worked at 4am on a phone with greasy hands.

Internal tools win when specificity is the moat. They lose the second you try to make them pretty.

#smbtwitter #deskless #verticalsaas #etaforum #searchfund

Production notes

• Shoot location: back-office desk at home with laptop visible — the receipt is the screen. Not a shop this time. Different texture for variety in week 1.
• Lighting: practical office light, slight key fill so the screen-record reads.
• Wardrobe: swap to a different plain tee than Day 1-2. Same operator energy, different day.
• Audio: lav mic, near-silent room. The "stay bought" beat is the LinkedIn-quotable line — record it twice and pick the cleaner take.
• Edit: hold each receipt screen-record 3-5s. Don't quick-cut the inventory/cash variance frames — viewers need to read the shape.
• Retention bet: the "i wasn't trying to make pretty software. i was trying to delete five logins." close is the share line. End on it without music.
• LinkedIn carousel format: export 1080×1080, dark background, single accent color, no stock imagery. Same template as Day 11 carousel for series recognition.

Voice check

• Real number ($60K/yr, 3 weeks, 7 shops, 20+ employees, 5 categories, 3 left alone)
• No banned phrases ("game-changer", "disrupting", "AI builder")
• No second-person motivation
• Show the replacement (5 SaaS categories named) — passes Voice Rule 4
• One CTA (LinkedIn: implicit newsletter teaser; TikTok/IG: none)
• Tension before payoff ("none of it fit" → "replaced 5 logins")

Day 4 — Sat May 23 — Light Receipt Day

Pillar: the rollup Primary: IG Stories only Secondary: TikTok optional repost if a Day 3 clip hit LinkedIn: none

Status: Light day per calendar — stories only, no shoot day. Capture during normal Saturday ops, do not stage.

IG Story frames (3 frames, captured live)

Frame 1 — Shop clip:

• 5-7 second vertical clip from a Saturday morning shop (fryer in motion, glazing wheel, or full rack being loaded).
• Caption overlay: "saturday."
• No music. Ambient kitchen audio only.

Frame 2 — Metric screenshot:

• Screenshot of the 6am Golden Ops daily digest with shop names + dollar amounts redacted.
• Caption overlay: "the 6am digest. exceptions, not dashboards."
• Link sticker → newsletter signup OR /receipts page.

Frame 3 — Text frame:

• Plain black background, lowercase white text:
• "saturday is where donut shops tell the truth."
• No CTA. Let it sit.

B-roll shot list

1. 0-3s — Hook frame: screen-record of the spreadsheet header row, on-screen text "the spreadsheet i use before buying a donut shop."
2. 3-12s — Bought shop column: scroll down the column, hold 1s on each load-bearing row (revenue, COGS, labor, rent, equipment, manager depth, cash payback). Numbers visible but cell colors muted.
3. 12-20s — Passed shop column: same scroll on the second column. Highlight the "seller is manager / no #2" row in red.
4. 20-30s — Side-by-side framing: zoom out to show both columns. Talking head cut-in: "the math on the second one was better. the operating reality was worse."
5. 30-40s — Shop exterior cuts: generic DFW shop exterior, parking lot, signage from a distance. No identifying signage on the "passed" shop — use a stock interior or daylight blur.
6. 40-50s — Equipment beat: close-up of a fryer dial, oil change log, manager-on-the-floor wide shot. Equipment age is the silent killer.
7. 50-60s — Close frame: talking head, plain delivery: "passing was the highest-return decision i made that quarter." End card: "acquisition glamour is mostly math."

TikTok caption + hashtags

the spreadsheet i open before buying a donut shop. 12 rows. one of them is "seller is the manager." that row killed a deal.

#smbtwitter #etaforum #searchfund #smbops #multiunitoperator #donutshop #dealflow

Instagram caption + hashtags

12 rows. that's the whole sanity check before i buy a shop. revenue, cogs, labor, rent, equipment, manager depth, cash payback.

one bought, one passed. the passed one had better math on paper. it also had a seller who was the manager, no #2, and a fryer past warranty. operating reality > paper math.

the highest-return decision i made that quarter was passing.

#smbtwitter #etaforum #searchfund #smbops #multiunitoperator #donutshop #dealflow #smallbusinessacquisition

LinkedIn (proper case, ~230 words)

The spreadsheet I open before buying a donut shop has 12 rows. Not a deal memo. A sanity check.

Revenue last 12 months. COGS as a percent. Labor as a percent. Rent and remaining lease term. Equipment age — fryer, proofer, hood — and what gets capex'd in year one. Manager depth, because if the seller is the manager, you're buying a job. Cash payback in months, and the same number assuming I have to hire a manager from day one.

Two shops in front of me last quarter. One I bought. One I passed.

The one I bought had an 18-month cash payback, an intact manager with 4 years tenure, a fryer with 2 years of life left.

The one I passed had an 11-month cash payback on paper — better. But the seller was the manager, there was no number-2, and the fryer was past warranty. The math was better. The operating reality was worse. The day I closed I would have inherited a hiring problem and a capex problem at the same time.

The highest-return decision I made that quarter was passing on the better-looking deal.

Acquisition glamour is mostly math. The math is mostly about what happens the morning after close, not the morning of.

#smbtwitter #etaforum #searchfund #dealflow #operatormindset

Production notes

• Shoot location: back-office desk, recorded yesterday in the batch.
• Asset prep: the acquisition spreadsheet screenshot was pulled Saturday (Day 4). Confirm all column blurs are still acceptable before exporting.
• Privacy: triple-check no broker name, no shop address, no street view. The deal math story is shareable; the deal counterparties are not.
• Edit: longer holds (4-5s) on each spreadsheet row. Viewers who care will pause and zoom; viewers who don't will scroll. Both groups are correct.
• Retention bet: the "seller was the manager" line at ~17s is the share trigger. Cut tight.
• No CTA per calendar. Let the detail carry it.

Voice check

• Real artifact (the spreadsheet itself, on screen)
• Specific numbers (12 rows, 18 months, 11 months, 4 years, 2 years)
• Operator POV — "i open", "i bought", "i passed"
• No advice ("you should never buy where the seller is the manager") — calendar voice rule
• Tension before payoff (better math → worse reality → passing was the right call)
• No CTA, no sign-off, no identity label

Day 7 — Tue May 26 — Wheel Reset

Pillar: selling premium Primary: TikTok 7:30pm CT Mirror: IG Reel if comments ask for trades LinkedIn: none Hook: "i lost mid-four-figures on options in 2022. then i flipped sides."

B-roll shot list

1. 0-3s — Hook frame: dark screen, on-screen text "lost mid-four-figures on options in 2022." Cut to talking head with text "then i flipped sides."
2. 3-12s — Buy-side losing montage: quick cuts — old brokerage P&L (heavily blurred, just enough to show red), then chart of an expired-worthless option.
3. 12-22s — Whiteboard payoff sketch: physical whiteboard or iPad. Draw a simple CSP payoff diagram. Label "premium collected", "strike", "assigned here". 8 seconds of drawing.
4. 22-32s — Current trade tracker: screen-record of the wheel tracker — name, strike, premium, status. Account number + total account value redacted. Hold 5s.
5. 32-42s — Assignment plan beat: brokerage screen showing covered call chain (blurred ticker), highlight the strike you'd sell. Cut to talking head: "the worst trade is one you can't hold through."
6. 42-50s — Close frame: black card with "process, not picks. not financial advice."

TikTok caption + hashtags

stopped buying options. started selling premium. boring on purpose. not financial advice.

#wheelstrategy #sellingpremium #optionseducation #cashflowinvesting #optionswheel #csp

Instagram caption + hashtags

lost mid-four-figures on options in 2022. then i flipped sides. selling premium is different — you're not predicting direction, you're getting paid to hold cash or the underlying.

current setup: cash-secured put on a name i'd actually own if assigned. strike 10% below current. wheel it if assigned.

the worst trade isn't a loss. it's one you can't hold through.

not financial advice. just the mechanism i actually use.

#wheelstrategy #sellingpremium #optionseducation #cashflowinvesting #optionswheel #csp #monthlyincome

LinkedIn

Skip per calendar.

Production notes

• Shoot location: back-office desk, recorded in Sunday batch.
• Compliance: "not financial advice" on-screen text in the lower third for the entire trade-screen segment. Caption disclaimer too. Cover yourself.
• Privacy: account number, total account value, and exact ticker stay redacted. Generic strike % and premium amount can show.
• Whiteboard: if shooting digital (iPad), use a single-color stylus on white background. Keep the diagram simple — 4 labels max.
• Edit: the whiteboard sketch (8 seconds, ~12-22s) is the retention payoff. Don't speed-ramp it. Let viewers absorb the payoff diagram.
• CTA per calendar: "longer trade notes in bio." Add as pinned comment, not on-screen.

Voice check

• Real number (10% below strike, 1 month duration)
• Operator POV — "i'm running", "i used to"
• Tension before payoff (lottery tickets → boring on purpose)
• "Not financial advice" present in caption + on-screen
• No identity claim ("i'm a trader") — describes the mechanism, not himself
• Avoids "passive income" — replaced with "getting paid to hold cash"

Day 8 — Wed May 27 — Managing 20+ Deskless Employees

Pillar: the rollup Primary: TikTok 6:15am CT Mirror: IG Reel LinkedIn: text post 7:45am CT Hook: "i managed engineers for 13 years. donut shops broke that playbook."

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "i managed engineers for 13 years. donut shops broke that playbook."
2. 3-10s — Engineer-stack reference: screen-record of an old Slack thread (personal Slack with content fully blurred) and a Jira board (mocked or blurred). 4 seconds combined.
3. 10-20s — Kitchen reality: wide shot of kitchen floor at 4am, then close-ups — flour-covered hands, the donut rack being loaded, a manager pointing at something off-camera.
4. 20-30s — Manager check-in receipt: screen-record of Discord bot prompt with the 3 structured questions, then a manager response thread.
5. 30-40s — Exception channel example: Discord channel pinged red, an issue card opens, a vendor is notified, status flips to "resolved." Show the routing.
6. 40-50s — The 30-second beat: stopwatch overlay on a phone in a kitchen scene — manager opens Discord, taps three answers, dismisses notification. 8 seconds of real-time interaction.
7. 50-60s — Close frame: talking head: "dashboards are great if your team types. exception channels are what works if your team doesn't." End card.

TikTok caption + hashtags

13 years managing engineers on slack. then 20+ people on a kitchen floor at 4am. the playbook didn't translate. exception channels did.

#smbops #multiunitoperator #deskless #qsr #internaltools #donutshop #opsmanagement

Instagram caption + hashtags

engineers self-report. shop staff don't text for a living. that's the whole gap between managing knowledge workers and managing 20+ deskless employees.

the fix wasn't more dashboards. it was exception channels — one discord channel per shop, one bot prompt per shift, three questions, 30 seconds, greasy hands.

dashboards are great if your team types.

#smbops #multiunitoperator #deskless #qsr #internaltools #donutshop #opsmanagement #frontline

LinkedIn (proper case, ~270 words)

I managed engineers on Slack and Teams for 13 years. The entire tech management stack assumes a team that types for a living — async standups, ticket queues, threaded conversations, Loom updates. People who self-report.

Then I bought donut shops.

Shop staff don't self-report. They show up at 4am, do the work physically, and the only log of what happened is the donut rack, the cash drawer, and one manager's memory. There's no Jira. There's no async standup. If a fryer broke at 5:15am, nobody's typing it up.

The instinct from the tech playbook is to fix that with dashboards. Build the right BI surface, the right rollups, the right charts, and the truth will surface.

That doesn't work for a deskless workforce. Dashboards reward people who already type. They punish people who don't.

What worked: exception channels. One Discord channel per shop. One bot prompt per shift. Three structured questions — did you open on time, did anyone miss the shift, did anything break. 30 seconds on a phone with greasy hands. The bot does the structure. The manager just answers.

Then route the exceptions. A red flag on shift open pings the right vendor. A missing person pings the schedule. A broken fryer opens an issue card. The dashboard exists, but only the operator (me) reads it. The team operates inside the bot.

Don't force Slack habits onto deskless work. Build for the medium your team already uses. Build the exception layer, not the reporting layer.

The tools are different. The respect for the team is the same.

#smbops #deskless #etaforum #smbtwitter #operatormindset

Production notes

• Shoot location: mixed — talking head from Sunday batch + kitchen b-roll captured during a real morning open this week.
• Privacy: all employee faces obscured (back-of-head, hands-only). Same for the manager response screenshot — names blurred.
• Lighting: kitchen scenes keep their natural fluorescent + dawn mix. Don't gel.
• Edit: the stopwatch overlay on the "30 seconds" beat is the strongest visual proof. Don't skip it.
• Retention bet: the line "engineers self-report. shop staff don't text for a living." is the share line. Lead the IG/TikTok cut with it.
• CTA per calendar: newsletter link in pinned comment.

Voice check

• Real numbers (13 years, 20+ employees, 4am, 5:15am fryer, 3 questions, 30 seconds)
• Tension before payoff (tech playbook broke → exception channels worked)
• Operator POV — "i managed", "i bought", first-person throughout
• No advice formula — describes what worked for him, reader extracts the lesson
• LinkedIn line "Don't force Slack habits onto deskless work" is a quotable but not a guru aphorism — it's the concrete operating principle
• No identity claim ("ops nerd", "builder")

Day 9 — Thu May 28 — The Bot I Was Embarrassed To Build

Pillar: Golden Ops Primary: TikTok 7:30pm CT Mirror: IG Reel LinkedIn: none Hook: "the most useful software i built is a discord bot."

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "the most useful software i built is a discord bot."
2. 3-10s — Embarrassment beat: quick cut to an old IDE screenshot of a real Cursor session, then back to talking head shrugging slightly.
3. 10-20s — Bot in action: screen-record sequence — slash command typed → bot prompt opens → three buttons + text input → manager response.
4. 20-30s — Daily digest routing: Discord ops channel → daily digest message appears → click into a flagged item → routed to issue thread.
5. 30-40s — Drive folder receipt: screen-record of the Drive folder structure — by shop, by date, by document type. Hold 4s so the structure reads.
6. 40-50s — Close frame: "ugly software in the medium your team already uses — that's the whole game." End on a static phone-on-counter shot in a real shop.

TikTok caption + hashtags

the most useful software i shipped in 18 months is a discord bot. not a web app. not a mobile app. a bot. ugly software in the medium your team already uses wins.

#smbops #internaltools #discordbot #deskless #qsr #donutshop #buildlog

Instagram caption + hashtags

the most useful piece of software i built is a discord bot. slash command. three buttons. a text input.

embarrassing for a month. then i got over it.

managers already had phones. notifications already worked. zero migration. the bot does the structure. the drive folder fills itself by shop and date. no second tool to install.

pretty software is expensive if nobody uses it.

#smbops #internaltools #discordbot #deskless #qsr #donutshop #buildlog #opsautomation

LinkedIn

Skip per calendar.

IG Story add-on

Frame 1: poll: "dashboard or bot?" — two emoji options. Frame 2: the next morning, share the result + screen-record of the bot doing the thing the dashboard would have done. Two-frame loop.

Production notes

• Shoot location: recorded Sunday batch. The Drive folder screen-record needs to be re-captured fresh today so the dates are current.
• Privacy: all manager names blurred. The Drive folder structure can show shop names if the shop is mid-photo-blur (visible but not identifying).
• Edit: the slash command → prompt → response sequence at 10-20s is the proof. Don't speed-ramp it. Real-time pacing.
• CTA per calendar: "build where the team already is." Use as the end-card line, not a separate CTA.
• Story timing: post the poll frame at lunch (12-1pm), reveal frame at 5pm same day for the loopback.

Voice check

• Real artifacts (slash command, three buttons, Drive folder structure)
• Operator POV — first-person embarrassment story
• Tension before payoff (embarrassed for a month → ugly wins)
• "pretty software is expensive if nobody uses it" is a load-bearing line — not motivational, just operational
• No identity claim ("indie hacker", "builder")
• One CTA (end-card line only)

Day 10 — Fri May 29 — Receipts Friday #1

Pillar: all three (the rollup + selling premium + Golden Ops) Primary: TikTok 6:15am CT Mirror: IG Reel LinkedIn: short reflection post Hook: "3 receipts from this week running shops, software, and options."

B-roll shot list

1. 0-3s — Hook frame: title card "RECEIPTS FRIDAY · 1/?" — lowercase, no exclamation. On-screen "3 receipts from this week."
2. 3-15s — Shop receipt: Golden Ops dashboard, week-over-week strip, hover-emphasize the sales-up-4% cell and waste-down cell. Hold each ~3s.
3. 15-25s — Ops receipt: screen-record of the Discord channel — show the OLD digest message (generic channel) → smash cut to NEW behavior (manager group ping). Side-by-side comparison frame.
4. 25-40s — Premium receipt: wheel tracker screen-record, blur account but show position closed at 60% + new CSP opened. 6-second hold.
5. 40-45s — Close frame: end card: "three numbers. one week. same format every friday."

TikTok caption + hashtags

3 receipts this week — shops, ops, premium. no commentary. same format every friday.

#receiptsfriday #smbops #multiunitoperator #internaltools #wheelstrategy #donutshop #buildlog

Instagram caption + hashtags

receipts friday · week 1.

shops — sales +4% wow across 7. waste -0.5pt. ops — late-open exceptions now ping the manager group directly. 3 lines of code. response time minutes → under one. premium — one csp closed at 60% max profit. cash rolled into a new position.

three numbers. one week. same format every friday.

#receiptsfriday #smbops #multiunitoperator #internaltools #wheelstrategy #donutshop #buildlog #opsautomation

LinkedIn (proper case, ~150 words)

The operating week in three numbers.

Shops: Sales up 4% week-over-week across 7 shops. Waste down half a point. Nothing dramatic — boring is the point.

Ops: Pushed a small change to the daily digest: late-open exceptions now ping the manager group directly instead of going to the general channel. Three lines of code. Cut response time from minutes to under one.

Premium: One cash-secured put closed early at 60% of max profit. Rolled the freed cash into a new CSP on a different name. Monthly target on track.

Three receipts. One week. Same format every Friday.

The big lesson from week one — the operating moves that compound aren't dramatic. They're the small routing change that saves three minutes per exception, the half-point of waste that returns to the bottom line, the trade closed early instead of held to expiration.

Posting these every Friday as a series.

#smbtwitter #operatormindset #receiptsfriday #etaforum

Production notes

• Template lock-in: this is the format for every Friday from here on. Day 24 (Receipts Friday #2) uses the same on-screen template, same 3-segment structure, same end card. Series recognition compounds.
• Shoot location: recorded Sunday batch.
• Privacy: dollar amounts on the premium tracker stay redacted; only the % of max profit shows.
• Edit: keep each segment tight to 15 seconds. If a segment runs long, cut it down — don't extend the others.
• Audio: no music. The dryness is the brand.
• End card consistency: save the "RECEIPTS FRIDAY · N/?" title card and end card as a CapCut template so future Fridays take 10 minutes to assemble.
• Pinned comment: "i write longer once every two weeks — link in bio. operator audience only."

Voice check

• Real numbers in every segment (+4% wow, -0.5pt waste, 3 lines of code, 60% max profit)
• No commentary, no motivational close — the format is the message
• Operator POV — "i pushed", "i closed"
• No CTA per calendar — just the series tag
• Tension absent on purpose — this is the steady-state proof-of-work format, not a tension-payoff post
• "boring is the point" passes the Earned vs Borrowed test — Jack has standing to say this after 18 months of physical-asset ops

Batch 1 summary

Posts shipping this batch:

• 5 TikTok feed posts (Days 1, 3, 6, 8, 10 — primary 6:15am slot)
• 3 TikTok evening posts (Days 2, 7, 9 — 7:30pm slot)
• 1 IG Stories-only day (Day 4) + 1 IG Stories add-on (Day 9 poll loop)
• 3 LinkedIn posts (Day 1 origin, Day 3 carousel, Day 6 deal math, Day 8 deskless management — actually 4 LinkedIn beats including Day 10 short reflection)
• 1 Sunday batch day (Day 5) — internal production only
• 1 series anchor launched (Receipts Friday — Day 10 sets the template)

Recurring series introduced:

• Receipts Friday — locked template, repeats Day 10, Day 17 candidate, Day 24, Day 30. Same on-screen format, same 3-segment structure, same end card.
• The $60K Stack series — Day 3 anchors it, Day 13 ("what i would not build") and Day 14 (newsletter issue #1) extend it.

Retention bets (the one line per post that has to land):

• Day 1: "i planned my way to a layoff."
• Day 2: "i read the exceptions. green shops are silent."
• Day 3: "i wasn't trying to make pretty software. i was trying to delete five logins."
• Day 6: "the seller was the manager. that row killed the deal."
• Day 7: "the worst trade is one you can't hold through."
• Day 8: "engineers self-report. shop staff don't text for a living."
• Day 9: "pretty software is expensive if nobody uses it."
• Day 10: "boring is the point."

What to watch for in batch 2 (Days 11-20):

• Day 11 carousel ("what i check every morning") needs the same template Day 3 carousel uses — keep visual continuity.
• Day 14 newsletter send — first long-form. Should be 1400-2000 words. Use the Day 3 stack post as the seed, expand with what wasn't said.
• Day 15 variance story — primary LinkedIn slot. Already drafted in day_15_variance_story.md. Verify numbers align with the $60K canonical figure.
• Day 17 manager voice memo — needs a sanitized real (or convincingly recreated) 12-second clip. Capture this during Days 11-16 ops.
• Day 20 cash forecast carousel — needs a clean 13-week forecast screenshot. Pull during Day 12 (Sun) batch.

Inconsistencies / flags for Jack:

1. SaaS replacement canonicalized — use $60K/yr throughout. Older higher estimates were incorrect.
2. Employee count canonicalized — use 20+ employees throughout. Older inflated references were incorrect.
3. Trade specifics on Day 7 — used "10% below current strike", "1 month duration", "cash-secured put on a name i'd actually own". These are voice-consistent placeholders. If Jack wants to use a real recent trade with redacted ticker, swap before shoot day.
4. Day 10 Receipts Friday numbers — "+4% WoW across 7 shops" and "waste -0.5pt" are illustrative for the template. Marked [number TK] in spirit — please verify against actual week-1 numbers before shoot. The premium "60% of max profit" and "monthly target on track" are placeholders for the actual closed CSP that week.
5. Day 6 deal math specifics — "18-month cash payback intact manager 2-year fryer life" vs "11-month cash payback seller-is-manager fryer past warranty" are illustrative numbers. If Jack has a real bought-vs-passed pair from the last 18 months, plug those in for credibility — current numbers pass the voice spec but aren't grounded receipts.

Format/voice notes carried through all 10 days:

• All TikTok + IG captions lowercase, contractions, no exclamations, no sign-off
• LinkedIn captions proper case, numbers up front, ≤300 words
• Em-dashes used for asides (no semicolons, no Oxford comma)
• One CTA max per post; most have zero
• Every day has at least one real artifact on screen (spreadsheet, dashboard, trade tracker, kitchen, Discord)
• No banned phrases triggered across all 10 days
• Receipts Friday template locked for Day 10 → Day 24 → Day 30 continuity

Ship batch 1 once Jack greenlights the canonical numbers (item 1 + 2 above).

30-Day Playbook — Days 11-20

Window: Sat 2026-05-30 through Mon 2026-06-08 Pillars: Operator OS, Golden Glaze rollup, FlexStay repeatability proof, operator treasury Format: full production depth — script, b-roll, captions, production notes per day Status: internal review — for Jack only

Revision note: execute this batch through the Operator OS lens in 05_operator_os_revision.md. Prioritize module receipts, workflow screenshots, and control-loop explanations over generic operator commentary.

Day 11 — Sat May 30 — Carousel: What I Check Every Morning

Pillar: Operator OS cockpit Primary: Instagram carousel (drop 8:30am CT) Secondary: TikTok optional VO-over-carousel (mid-afternoon) LinkedIn: none

Carousel slide-1 hook: "if a shop is healthy i don't need a paragraph. i need exceptions." TikTok VO hook (optional reel): "8 metrics. 7 shops. 90 seconds before coffee."

IG carousel slides (8 slides, 1080×1080, dark background, accent color)

Slide 1 (title card): The 8 Things I Check Every Morning Before Coffee 7 shops. 90 seconds. exceptions only.

Slide 2 (sales vs 7-day avg): sales vs trailing 7-day avg, per shop. not "are we up" — "is anything more than 8% off the trailing line." the trailing line is the real number. yesterday alone is noise.

Slide 3 (labor %): labor as a percent of revenue, per shop. target band: 22-28%. red flag outside that. above the band = shift wasn't cut when sales slowed. below = under-staffed open.

Slide 4 (waste): waste in trays per shop. target: under 4% of trays produced. above = production over-shot the morning, throw the recipe sheet at the manager.

Slide 5 (cash variance): last night's till count vs POS expected. band: ±$15. outside = call. this is the metric that catches drift before it's theft.

Slide 6 (open issues): unresolved items from the night before, per shop. equipment, supply, staffing, customer. zero is silent. one is a check-in. two+ is a phone call.

Slide 7 (missed check-ins): managers post the open. if a post is missing by 5:45am the bot pings me. two misses in a week = conversation. consistency is the product, not the heroics.

Slide 8 (the close): green shops are silent. red shops show up first. the system isn't dashboards. the system is exceptions. save this if you run physical ops.

Optional TikTok caption + hashtags

7 shops. 8 metrics. 90 seconds before coffee. green is silent. red shows up first.

#smbops #multiunitoperator #qsr #internaltools #deskless #donutshop #dfwsmallbusiness

Instagram caption (carousel post)

people ask what i actually look at in the morning. this is the screen.

8 metrics across 7 shops. 90 seconds. exceptions only. if a shop is healthy i don't need a paragraph — i need to know when consistency broke and which shop broke it.

the band rules matter more than the numbers themselves. ±$15 on cash variance, labor between 22-28%, waste under 4%, sales within 8% of the trailing line. outside the band, i call. inside the band, i drink coffee.

this is the morning screen. save it if you run physical ops.

#smbops #multiunitoperator #qsr #internaltools #donutshop #deskless #opsautomation

LinkedIn

Skip per calendar.

Production notes

• No talking head shoot required. Carousel is the deliverable.
• Design template: lock this carousel format for the series — same dark bg, same accent color, same font, same title bar. Future morning-screen content reuses this template.
• Numbers: use real band rules (22-28% labor, ±$15 cash, <4% waste, ±8% sales) — these are Jack's actual operating thresholds. Do not invent new numbers.
• Sensitive info: no shop names, no real dollar figures, no employee names on any slide.
• Optional TikTok shoot: 30 seconds, talking head, single take. Use carousel slides as on-screen overlay. Don't shoot if Day 10 Receipts Friday is still climbing — let that breathe.
• Saturday timing: drop carousel 8:30am CT — captures operators checking phones with morning coffee.

Voice check

• Real numbers (7 shops, 8 metrics, 22-28%, ±$15, <4%, ±8%)
• One idea: exceptions, not dashboards (consistent with Day 2)
• No motivational close
• Operator POV — first-person, no "you should"
• Save CTA only on slide 8, light and specific ("if you run physical ops")
• Voice consistent — "green is silent, red shows up first" is the carryable phrase

Day 12 — Sun May 31 — Batch + Comments

Pillar: none (work day) Primary: no new feed post Secondary: IG Story 1 frame if a real moment shows up LinkedIn: none

Status: Internal production day per calendar. No public-facing post unless an organic moment surfaces.

Work block — 90 minutes

Comment reply pass (20 min):

• Pull all comments from Days 6-11 (TikTok + IG).
• Reply only to comments from actual operators (look for: shop owner, multi-unit, F&B, QSR, real estate operator language; skip generic "love this" / emoji-only).
• Reply rules: lowercase, no emoji, no exclamation, 1-2 sentences max, no "thanks for watching."
• Save the 3 best operator questions to a Notes file recurring_q_and_a.md — these become Day 26 Q&A content.

Recording session — Days 13-17 TikToks (60 min):

Set up the back-office desk shoot in one block. Same wardrobe variation as the week, same lav mic, same lighting.

Record in this order to minimize reset cost:

1. Day 13 — What I Would Not Build: talking head + build-vs-buy board screen-record.
2. Day 15 — Variance Story: car shoot at dawn OR back-office; cash forecast screen-record.
3. Day 17 — Manager Voice Memo: back-office; sanitized waveform/transcript overlay.
4. Day 16 — One Trade, Full Walkthrough: trade tracker screen-record + whiteboard cut.
5. Day 14 — Newsletter teaser: record after newsletter is written, not before — needs the actual headline.

LinkedIn drafts (15 min):

Write Day 13 (internal tools win when specificity is the moat) and Day 15 (variance story, updated with 20+ employees / $60K) to first-draft state. Don't polish — polish during scheduled post window.

Newsletter issue #1 skeleton (15 min):

Title placeholder: "the $60k software bill i killed first."

Sections:

• The bill (which 5 SaaS, total annual, redacted)
• The workflow (Discord + bot + Sheets glue)
• The smallest replacement that worked (Day 1 of build, what I shipped before lunch)
• What still stays bought (payroll/accounting/POS — same as Day 13)
• Mistake I made (over-built the scheduler before I'd done a single shift swap manually)

IG Story frame (optional, single frame)

If a real ops moment shows up during Sunday work:

• One photo of the laptop with the editing timeline visible (no actual content readable).
• Caption overlay: "sunday is batch day."
• No CTA.

B-roll shot list

Capture-only during batch session:

1. Behind-the-camera/desk wide shot (phone-on-tripod + laptop on desk) — for future "how the shoots work" content.
2. 3-second clip of timeline scrub in the editor.
3. Voice memo of one operator question (will be used Day 26).

TikTok caption + hashtags

None — no public post today.

Instagram caption + hashtags

None — Stories optional only.

LinkedIn

None.

Production notes

• No shoot day for new public content. Sunday is reset day.
• Schedule discipline: if recording runs long, cut Day 16's whiteboard segment first — least critical, easiest to re-record Wednesday.
• Phone discipline: put phone in airplane mode during recording block. The shoots take 60 min if focused; 3 hours if not.
• End state: Days 13-17 in CapCut/editor with rough cuts. Final polish happens night-before each post.
• Failure mode: if energy is low, record only Days 13 and 15. The receipts-heavy days (16, 17) need real performance — better to push to Tuesday.

Voice check

• N/A — no public post.
• Internal note: reply pass on comments should follow the same voice rules as posts. Lowercase, no emoji, no exclamation, one operator-to-operator.

Day 13 — Mon Jun 1 — What I Would Not Build

Pillar: Golden Ops Primary: TikTok 6:15am CT Mirror: IG Reel 7:30pm CT LinkedIn: text post 8:00am CT Hook: "i replaced $60k of saas but i would not rebuild these 3 things."

B-roll shot list

1. 0-3s — Hook frame: talking head close-up, on-screen text "$60k cut. 3 things i'd never rebuild." Light receipt energy, not victory lap.
2. 3-10s — Red/yellow/green board: screen-record of a build-vs-buy board (Notion or Sheets):
   • Green column (built): Scheduling, Check-ins, Inventory, Cash Variance, Investor Reporting
   • Red column (stay bought): Payroll, Accounting, POS+Payments
   • Yellow column (still deciding): Marketing automation, Customer messaging
3. 10-18s — Payroll beat: screen-record of a Gusto-style payroll run screen (mockup or actual, with all PII blurred). Cut to a generic state-tax-rules page on screen with multiple state codes visible.
4. 18-26s — Accounting beat: QuickBooks chart of accounts screen, scroll through. Cut to a redacted P&L cover sheet.
5. 26-34s — POS beat: POS terminal at a shop counter (close-up, no customer faces). Cut to a card-present screen.
6. 34-45s — "Stay bought" close: talking head, list payroll / accounting / POS on screen as he says them.
7. 45-55s — End frame: text card "internal tools are leverage, not religion." Black background.

TikTok caption + hashtags

killed $60k of qsr saas. these 3 i'd never rebuild — payroll, accounting, pos+payments. if being wrong is expensive, stay bought.

#smbops #internaltools #buildvsbuy #multiunitoperator #qsr #donutshop #buildlog

Instagram caption + hashtags

i replaced $60k/yr of qsr saas in 3 weeks. the question i get most often is "what else are you going to cut?"

wrong question. better question: what would you never touch?

payroll — gusto handles 50-state compliance. one missed withholding rule eats two years of saas savings.

accounting — quickbooks chart of accounts is load-bearing for the gp/lp fund. auditors and lenders trust the format.

pos + payments — card-present, disputes, pci. if my custom till software dies on a saturday morning i don't have a business that morning.

internal tools are leverage, not religion. if being wrong is expensive, stay bought.

#smbops #internaltools #buildvsbuy #multiunitoperator #qsr #donutshop #opsautomation

LinkedIn (proper case, ~220 words)

I replaced about $60K/yr of QSR SaaS in 3 weeks. The most useful follow-up question isn't "what's next to kill" — it's "what would you never touch."

Three categories I'd never rebuild:

Payroll. Gusto handles 50-state withholding, new-hire reporting, EITC notices, garnishments, multi-state remote employees, and the dozen quarterly filings that come with them. The regulatory surface is huge and the cost of being wrong is two years of SaaS savings, gone in one fine. Stay bought.

Accounting core. Our chart of accounts is load-bearing for a GP/LP fund. Auditors read it. Lenders read it. LPs read it. QuickBooks has a 30-year head start on report formats that bankers already trust. Rebuilding the ledger to save $200/month is the most expensive trade I could make.

POS + payments. Card-present transactions, dispute handling, PCI compliance, network outages, chargeback timelines — none of it is a side project. If a custom till app goes down on a Saturday morning, I don't have a business that morning. The downside is operational, immediate, and unrecoverable.

The rule I use across the build-vs-buy decision: if being wrong is expensive, stay bought.

Internal tools are leverage when specificity is the moat. They are religion the moment you start rebuilding regulated systems to feel productive.

#smbtwitter #deskless #verticalsaas #etaforum #searchfund

Production notes

• Shoot location: back-office desk, same setup as Day 3 for visual continuity (this is the "build-vs-buy series" callback to The $60K Stack).
• Lighting: same as Day 3. Don't change the lighting between these two posts — viewers should recognize the location pair.
• Wardrobe: new tee, dark, no logo. Don't repeat Day 1-3 wardrobe.
• Audio: lav mic, near-silent room. The "stay bought" line is the share line — record it three times, pick the cleanest.
• Edit: screen-record holds at 3-5s on each of the build-vs-buy board, payroll, accounting, POS frames. Don't quick-cut these — viewers need to read the categories.
• Privacy: Gusto/QuickBooks/POS screens fully redacted. Use mockups if real screens leak any account identifier.
• Retention bet: the line "if being wrong is expensive, stay bought" at ~50s is the share quote. Hold a beat after it.

Voice check

• Real numbers ($60K, 3 categories, 50 states, 30-year head start)
• No banned phrases ("game-changer", "disrupting", "next-gen")
• Single CTA (implicit newsletter — Day 14 follows)
• Operator POV — first-person, no "you should"
• Tension before payoff (kills $60K of SaaS → but won't touch 3 things → because being wrong is expensive)
• One quotable: "internal tools are leverage, not religion"

Day 14 — Tue Jun 2 — Newsletter Issue #1

Pillar: Golden Ops Primary: Newsletter send (10:00am CT) Secondary: TikTok teaser (7:30pm CT) Tertiary: IG Story link 11:00am CT LinkedIn: Optional next-day text post if open rate exceeds 35%

Hook (newsletter): "the $60k software bill i killed first." Hook (TikTok teaser): "i sent the full breakdown of the saas i replaced. here's the part people will disagree with."

Newsletter structure (~1,400 words, plain-text-feel)

Subject line: "the $60k software bill i killed first" Preview text: "what got replaced, what stays bought, and the mistake i made building it"

Section 1 — the bill (200 words):

The five SaaS line items I replaced, what each one cost (banded, not exact), what category it served, and why the cost wasn't the reason I killed it. The fit was the reason.

Section 2 — the workflow (300 words):

The pre-build operating surface. What managers were actually doing, what I was actually doing, and the gap between the SaaS workflow and the floor workflow. The phrase to use: "the SaaS was built for a 100-unit chain or a 1-unit owner. The middle is where rollup operators live."

Section 3 — the smallest replacement that worked (300 words):

The first thing I shipped on day 1 of build week — a Discord bot that asked one question at shift open and logged the answer to a Sheet. Took 4 hours. Replaced the daily check-in SaaS that night. Managers liked it because nothing new to install. I liked it because I could iterate in 10-minute loops.

Section 4 — what still stays bought (250 words):

Same three categories as Day 13 (payroll, accounting core, POS+payments). Add a 4th tentative: marketing automation. Still on the fence. Currently using a basic tool but watching to see if the pattern of "specificity as moat" applies. If it does, that's a Month 2 build.

Section 5 — the mistake i made (250 words):

Over-built the scheduler in week 2. Tried to handle every shift-swap edge case before I'd done a single swap manually. Cut 60% of the feature set after the first week of real use. The lesson: build the smallest version that solves today's swap, not the swap that might happen next month.

Section 6 — closing (100 words):

What comes next. Brief mention of upcoming inventory rework. Newsletter cadence promise (every other week). Replies go directly to Jack's inbox. No automated drip.

CTA: "reply if you're in the build-vs-buy spot. happy to share specifics."

TikTok teaser (~30 sec)

Hook: "i sent the full breakdown of the saas i replaced. here's the part people will disagree with."

Script:

just sent the full breakdown out. five saas categories replaced, $60k a year off the books, three categories i wouldn't touch even if i could, and one mistake i made in week two that cost me half the feature set.

the part people will push back on isn't the speed. it's the prerequisite. i'd been the user inside the workflow for 12 months before i wrote a single line of code. that's the actual unlock — not the three-week build, but the year of running the business that came before it.

so when people say "build in public," what they usually mean is a brand exercise. what i did was different. i built because i'd been the user long enough to know which 80% of the features in every off-the-shelf tool were dead weight for our specific shape.

full breakdown in the newsletter. link in bio.

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "the full $60k breakdown — sent today."
2. 3-10s — Newsletter screenshot: quick screen-record of the newsletter draft scrolling — section headers visible, body text blurred. Hold on the "what still stays bought" header for 2s.
3. 10-18s — Build-in-public counter beat: talking head, on-screen text "i was the user for 12 months first." Hold this frame longer than feels comfortable.
4. 18-26s — The 80% line: cut to a screen-record of an off-the-shelf scheduling tool with the unused features highlighted (mock or real, with PII redacted).
5. 26-30s — End frame: "newsletter link in bio. reply if you're in the build-vs-buy spot."

TikTok caption + hashtags

$60k of qsr saas replaced. full breakdown out today. the part people will disagree with — i was the user for 12 months before i built anything.

#smbops #internaltools #buildlog #multiunitoperator #qsr #donutshop #opsautomation

Instagram caption + hashtags

newsletter issue 1 just went out — the $60k qsr saas bill i killed first.

what got replaced, what stays bought, the smallest version that worked, and the mistake i made over-building the scheduler before i'd done a single shift swap by hand.

the part most people will push back on — i was the user for 12 months before i wrote a line of code. the speed of the build wasn't the unlock. the depth of user research from running the business was the unlock.

link in bio if you want it.

#smbops #internaltools #buildlog #multiunitoperator #qsr #donutshop #opsautomation

LinkedIn (optional, next day if open rate >35%)

Newsletter issue 1 went out yesterday — the $60K/yr QSR SaaS bill I killed first.

The part operators are pushing back on isn't the cost savings or the speed. It's the prerequisite.

I was the user for 12 months before I wrote a line of code. That's the actual unlock. The speed of the build was a downstream effect of knowing which 80% of the features in the off-the-shelf tools were dead weight for our specific operating shape.

"Build in public" is mostly a brand exercise. "Build because you've been the user for 12 months and you know exactly what to cut" is the operating move.

If you're in the build-vs-buy spot at 3-15 units in a deskless category, reply to the newsletter directly. I read every one.

#smbtwitter #verticalsaas #deskless #etaforum

Production notes

• Newsletter send window: 10:00am CT — operators check email between morning push and lunch.
• Subject line A/B: if the platform supports it, test "the $60k software bill i killed first" vs "$60k of qsr saas. 3 weeks. here's what i killed and what i kept."
• TikTok timing: 7:30pm CT for the teaser — newsletter has had 9 hours to settle, evening discovery window catches operators on phones.
• Story link: drop the Story link sticker at 11:00am CT, 1 hour after newsletter send — captures the early open spike.
• LinkedIn discipline: wait 24 hours to see open rate. If <35%, skip the LinkedIn post — would just look like recycled content. If >35%, the post lands as receipts.
• Failure mode: if newsletter is late getting written, ship the TikTok teaser anyway and reschedule the newsletter for Wed AM with revised subject. Do not skip the newsletter — Day 28 needs a cadence reference.

Voice check

• Real numbers ($60K, 12 months, 80%, 4 hours, 3 weeks)
• One quotable per surface: newsletter ("the saas was built for a 100-unit chain or a 1-unit owner — the middle is where rollup operators live"), TikTok ("i was the user for 12 months first"), LinkedIn (same)
• No banned phrases ("ai-powered", "next-gen", "build in public" used only to counter-position)
• Single CTA per surface — newsletter signup on TikTok/IG, newsletter reply directly on LinkedIn
• Tension before payoff (saved $60K → but the prerequisite is uncomfortable → 12 months as user before any code)
• No motivational close

Day 15 — Wed Jun 3 — Variance Story

Pillar: the rollup Primary: LinkedIn 7:45am CT Secondary: TikTok 6:15am CT Tertiary: IG carousel 7:30pm CT Hook: "13 years of w-2. the variance broke me before the math did."

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "13 years of w-2. the variance broke me before the math did."
2. 3-10s — Predictability b-roll: quick montage of generic w-2 artifacts (paystub corner with all PII blurred, direct deposit confirmation, calendar with biweekly markers).
3. 10-18s — Variance reality: quick cuts — hood fire damage photo (if safe to show, otherwise text card "hood fire — march"), manager exit interview prep doc redacted, generator failure invoice.
4. 18-26s — Income shape: screen-record of a chart showing W-2 (flat line) vs rollup income (sawtooth). Don't show actual dollar amounts — show shape only.
5. 26-34s — Forecast intro: screen-record of 13-week cash forecast Sheet — column headers visible (week, fixed costs, payroll, capex buffer, decision flag), dollar amounts blurred.
6. 34-42s — March generator example: brief redacted invoice clip, then the forecast row showing the buffer that absorbed it.
7. 42-55s — "Survivable" close: talking head, list "variance is the cost. forecast makes it survivable."
8. 55-60s — End frame: text card "consistency is the product. variance is the cost." Black background.

TikTok caption + hashtags

the hardest part of leaving corporate wasn't the money. it was the variance. what fixed it — a 13-week cash forecast and buffer rules. variance is survivable now.

#smbops #multiunitoperator #cashflow #operatorlife #donutshop #dfwsmallbusiness #buildlog

Instagram (carousel — 7 slides, dark template matching Day 11)

Slide 1 (title): 13 Years of W-2 Broke My Nervous System the variance was the cost, not the math.

Slide 2 (the predictability trap): 13 years. same number every two weeks. my brain built a mental model around biweekly cash. that model didn't survive owning physical assets.

Slide 3 (the income shape): monthly: volatile. quarterly: okay. annual: fine. the math worked. the shape didn't. the nervous system reads the shape, not the math.

Slide 4 (the hood fire wednesday): march. hood fire at one shop. manager exits at another. same wednesday. before the forecast: panic call to the cpa. after the forecast: knew the buffer, swapped the manager, moved on.

Slide 5 (the 13-week forecast): every monday i open one sheet. columns: fixed costs, payroll, capex, buffer, decision flag. if buffer drops below the line, i act. above the line, i wait.

Slide 6 (the buffer rule): target buffer = 1.5× fixed monthly costs. green: buffer healthy. yellow: tighten capex. red: cut something this week. the rule is the calm, not the dashboard.

Slide 7 (close): bigger reserves just delay the panic. the forecast and the buffer rule make variance survivable. consistency is the product. variance is the cost.

LinkedIn (~280 words, proper case)

The hardest part of leaving corporate wasn't the money. It was the variance.

13 years of W-2 income. Same number every two weeks. You build a mental model of your life around that predictability. Then you own 7 donut shops, 11 STR/MTR units, and a wheel position book — and the income shape is different. Monthly is volatile, quarterly is okay, annual is fine. But the nervous system is wired for biweekly.

What fixed it wasn't bigger reserves. Bigger reserves just delay the panic.

What fixed it was a 13-week cash forecast I look at every Monday and a set of buffer rules so I know when to act vs when to wait.

Target buffer: 1.5× fixed monthly costs. Green: buffer healthy, hold the plan. Yellow: tighten capex this month. Red: cut something this week.

March: hood fire at one shop, manager exit at another, same Wednesday. Before the forecast existed — that would have been a panic call to my CPA. With the forecast — I already knew the month's shape, knew the buffer, swapped the manager, scheduled the repair, didn't open a single dashboard until Tuesday.

Consistency is the product. Variance is the cost. The forecast is what makes the variance survivable.

This is the part of leaving corporate that nobody warns you about. The math is the easy part. The nervous system is the hard part. And the only thing that fixes the nervous system is operating discipline — Monday forecast, buffer rules, written decisions instead of stress responses.

18 months in. The variance is the same. The reaction is different.

#smbtwitter #verticalsaas #multiunitoperator #searchfund #etaforum

Production notes

• Shoot location: back-office at home, slightly warmer lighting than Days 3/13 — this is the personal/reflective post, not the build-vs-buy post. Different texture.
• Wardrobe: plain hoodie instead of tee. Signals "Wednesday, deep work" tone vs Monday's "build energy."
• Audio: lav mic, slightly closer than Days 3/13. The story needs intimacy — feel like the operator is across the kitchen table.
• Edit: longer holds, fewer cuts. This isn't a receipt-stack post — it's a reflection post grounded in receipts. Pacing should feel slower than Days 1, 3, 13.
• Privacy: redact all paystub/invoice/forecast dollar amounts. Hood fire photo only if no identifying info (shop name, address, employees in frame).
• Carousel template: match Day 11 carousel design — same dark bg, accent color, font. The series is "operating discipline" — both posts live in that template family.
• LinkedIn timing: 7:45am CT to catch the LinkedIn corporate-tech morning scroll. Cross-post the carousel to LinkedIn 7:30pm CT same day if it lands on IG.
• Retention bet: "bigger reserves just delay the panic" at ~32s is the share line. Hold a beat.

Voice check

• Real numbers (13 years, biweekly, 7 shops, 11 units, 13-week forecast, 1.5×, March)
• No banned phrases ("financial freedom", "follow your dreams", "the universe")
• Operator POV — first-person, no "you should"
• Tension before payoff (variance broke me → but bigger reserves don't fix it → the forecast and buffer rules do)
• One quotable per surface — TikTok ("variance is survivable now"), IG ("consistency is the product. variance is the cost"), LinkedIn ("the math is the easy part. the nervous system is the hard part")
• No motivational close — close on operating discipline, not encouragement

Day 16 — Thu Jun 4 — One Trade, Full Walkthrough

Pillar: selling premium Primary: TikTok 7:30pm CT Mirror: IG Reel next morning LinkedIn: none Hook: "one wheel trade. ticker. strike. premium. assignment plan. no pick."

B-roll shot list

1. 0-3s — Hook frame: talking head close-up, on-screen text "one wheel trade. ticker. strike. premium. assignment plan. no pick."
2. 3-10s — Ticker selection: screen-record of a generic stock screener filtered to "would own at right price" criteria. Real ticker if comfortable — otherwise a sanitized placeholder ticker. Hold on the filter criteria, not the ticker name.
3. 10-18s — Strike + delta: screen-record of the options chain, cursor hovers on the 10%-below strike, shows delta ~0.25. Premium amount visible (sanitized if needed).
4. 18-26s — Premium math: quick whiteboard or on-screen calc — credit × occurrences/year × win rate, lands on an annualized return number. Show the math, don't claim a number.
5. 26-34s — Assignment plan: screen-record showing the next-band covered call setup. Explain on-screen: "if assigned, sell the call here."
6. 34-42s — Early close rule: stock chart with the 50-60% max profit close visualized — entry premium, current credit, close marker.
7. 42-50s — Exit triggers: quick on-screen list: earnings inside window, thesis change, trend break on volume.
8. 50-65s — Close frame: talking head, end card "not a pick. a process." Disclaimer text small in bottom: "not financial advice. educational only."

TikTok caption + hashtags

one wheel trade. ticker. strike. premium. assignment plan. early close rule. start to finish. process not picks. not financial advice.

#wheelstrategy #options #cashflow #sellingpremium #optionsincome #csp #coveredcall

Instagram caption + hashtags

one wheel trade. ticker. strike. premium. assignment plan. no pick.

ticker — a name i'd actually want to own. boring business, real earnings. if i can't honestly say "i want this at 10% below current" i don't sell the put.

strike — 10% below spot. delta around 0.25. 30-45 days out.

premium — sized so the annualized math works and so assignment doesn't blow up the portfolio.

assignment plan — own at target basis, sell the next-band covered call same window.

early close — 50-60% max profit, don't hold for the last 20%. gamma risk doesn't pay enough.

exit triggers — earnings in window, thesis change, trend break on volume.

not a pick. a process. not financial advice.

#wheelstrategy #sellingpremium #options #cashflow #optionsincome #csp #coveredcall

LinkedIn

Skip per calendar. Wheel content stays off LinkedIn until Day 22's investor angle.

Production notes

• Shoot location: back-office desk, brokerage screen on monitor (with all account info covered by tape or a custom overlay), talking head over the screen-record.
• Wardrobe: plain dark tee. Different shirt from Days 13/15. Same operator tone.
• Audio: lav mic. Trade explanations need clean audio — viewers will rewind.
• Edit: screen-record holds are critical here. 4-5s per frame on the options chain, the math, the assignment plan. Don't quick-cut a trade walkthrough.
• Privacy: account number, balance, P&L year-to-date, position sizes — all covered. The screen-record overlay should hide everything except the specific cell being discussed.
• Disclaimers: "not financial advice" on-screen as text from second 30 onward. Caption disclaimer always.
• Ticker discipline: if using a real ticker, pick one Jack has actually traded in the last 90 days and would publicly stand behind. If unsure, sanitize with a placeholder ticker (e.g., "XYZ") and explain the framework only.
• Retention bet: the "not a pick. a process." close is the share line — viewers reshare for the framework, not the ticker.

Voice check

• Real numbers (10% below, delta 0.25, 30-45 days, 50-60% max profit, last 20%)
• No banned phrases ("guaranteed income", "make X per month", "passive income")
• Single CTA (none — wheel content stays receipt-only)
• Operator POV — first-person, no "you should"
• Tension before payoff (one trade → but the trade isn't the point → the framework is the point)
• One quotable per surface — TikTok/IG ("not a pick. a process.")
• Disclaimers visible

Day 17 — Fri Jun 5 — Manager Voice Memo

Pillar: the rollup Primary: TikTok 6:15am CT Mirror: IG Reel 7:30pm CT LinkedIn: short post 8:30am CT only if clip is strong

Hook: "this 12-second manager voice memo is why i built golden ops."

B-roll shot list

1. 0-3s — Hook frame: static dark frame, voice memo waveform pulsing across the screen, on-screen text "12 seconds. 3 issues. midnight."
2. 3-12s — The voice memo simulated: play a sanitized re-recording of the voice memo (re-record with a friend or use voice synthesis if real audio identifies the manager) over the waveform. Subtitle in lowercase as it plays.
3. 12-20s — The midnight pain: quick cuts — phone screen at 11:47pm, laptop opening, multiple tabs, texts going out, clock cuts to 12:30am.
4. 20-30s — The gap explained: talking head close-up, on-screen text "voice memos are how managers talk. dashboards aren't."
5. 30-42s — Golden Ops parses it: screen-record of the bot — voice memo lands, transcribes, parses, opens 3 issue cards (equipment, supply, staffing). Routes each to a different channel.
6. 42-50s — The "i don't lose the texture" beat: talking head, on-screen text "managers stay fast. routing happens automatically."
7. 50-55s — End frame: text card "build where the team already is." Black background.

TikTok caption + hashtags

12-second voice memo. 3 issues. midnight. this is why i built golden ops — managers stay fast, the routing happens for me.

#smbops #internaltools #multiunitoperator #deskless #qsr #donutshop #opsautomation

Instagram caption + hashtags

tuesday night, 11:47pm. one of my managers sends a 12-second voice memo. fryer making the noise again, short two trays, can you ping the morning crew.

three issues. one voice memo. by the time i'd listened, parsed, opened the right tools, and texted the morning crew — 12:30am.

that's the gap. voice memos are how managers actually communicate — fast, three things at once, no typing. but they're terrible for routing.

golden ops takes the voice memo, transcribes it, parses three intents, opens three issue cards, routes each to the right channel.

i don't lose the texture of how managers communicate. i just don't have to be the router at midnight.

#smbops #internaltools #multiunitoperator #deskless #qsr #donutshop #opsautomation

LinkedIn (proper case, ~180 words, only if the TikTok hits >50% retention at 30s)

Tuesday night, 11:47pm. One of my donut shop managers sends a 12-second voice memo.

"Hey Jack, fryer's making the noise again, and we're short two trays for tomorrow's open, and I'm starting the close, can you ping the morning crew."

Three issues. One voice memo. By the time I'd listened, parsed, opened the right tools, and texted the morning crew — 12:30am.

That's the gap most operators don't solve for. Voice memos are how deskless managers actually communicate. They're fast, they capture three things at once, and they don't require typing on a phone with greasy hands. But they're terrible for routing — you can't filter a voicemail, you can't dashboard a voicemail, you can't search one at 6am.

Golden Ops takes the voice memo, transcribes it, parses the intents, opens issue cards, and routes them to the right channel.

The texture of how managers communicate doesn't change. I just stop being the router at midnight.

Build where the team already is. Build for the texture of their actual work, not the texture of yours.

#smbtwitter #deskless #verticalsaas #opsautomation

Production notes

• Shoot location: back-office desk for talking head; voice memo waveform/transcribe segment is screen-record only.
• Wardrobe: dark tee, different from Days 13/16. Maintain the variety.
• Audio: lav mic for the talking head. The simulated voice memo should be re-recorded by a friend with manager-like tone (not synthesized robot voice) — Jack should not voice it himself; it has to feel like a different person.
• Edit: the waveform pulsing for the voice memo segment is the visual hook. Lock it tight on the audio. Subtitle in lowercase as the memo plays — captions get 60% of the playthroughs.
• Privacy: no real manager voice. No real shop names in the voice memo. Equipment issue is generic ("fryer's making the noise"). Manager name not used.
• Retention bet: the cut from "12:30am" to "managers stay fast, routing happens automatically" at ~50s is the share trigger. Cut tight.
• LinkedIn gate: only post if TikTok retention at 30s exceeds 50%. The story is strong; the platform fit needs proof first.

Voice check

• Real numbers (11:47pm, 12 seconds, 3 issues, 12:30am, 6am)
• No banned phrases ("game-changer", "transformative", "ai-powered")
• Single CTA (none — let the story carry)
• Operator POV — first-person, no "you should"
• One quotable per surface — TikTok ("managers stay fast, the routing happens for me"), IG ("i just don't have to be the router at midnight"), LinkedIn ("build for the texture of their actual work, not the texture of yours")
• Tension before payoff (12-second voice memo → midnight router pain → bot parses it, routes it, i sleep)
• No motivational close

Day 18 — Sat Jun 6 — Shop Walkthrough

Pillar: the rollup Primary: IG Reel 9:00am CT Secondary: TikTok repost only if Reel >30% retention by noon LinkedIn: none Hook: "first 90 seconds inside one of my shops. what i actually notice."

B-roll shot list (first-person walking, vertical 9:16)

1. 0-5s — Hook frame: first-person POV walking up to a shop, on-screen text "first 90 seconds inside one of my shops. what i actually notice."
2. 5-15s — Floor cuts: cuts to ground-level shots — clean floor near fryer (positive), close-up of crumbs (slightly negative, name what it tells you), close-up of proofer door (slightly negative, same).
3. 15-25s — Rack scans: wide shot of full rack, then zoom on a specific gap, then a close-up of one over-produced flavor (specify in voiceover what overproduction tells you about waste).
4. 25-35s — Manager interaction: wide of the operator (Jack) walking in, manager nods without stopping, keeps glazing. No dialogue. Background sound only.
5. 35-45s — Exception board: close-up of a paper exception board on the wall — equipment status sticky notes, supply note, staffing note. Real or sanitized (no real names/dates).
6. 45-55s — Smooth shift cue: medium shots of motion — glazing wheel turning, fryer in motion, tray being loaded, register transaction completing. Pacing of the cuts should feel calm.
7. 55-60s — End frame: text card "smooth, not busy." Black background.

TikTok caption + hashtags (only if reposting)

what i look for in the first 90 seconds. floor, racks, manager confidence, exception board, speed. smooth not busy.

#smbops #multiunitoperator #qsr #donutshop #dfwsmallbusiness #shopwalkthrough

Instagram caption + hashtags

first 90 seconds of walking into one of my shops. not the inspection sheet — what an operator actually notices.

floor: crumbs near the fryer mean the night close was rushed. dough on the proofer door means the morning batch was rushed. neither is a fire, both tell me the shift pressure.

racks: waste lives in overproduction more than spoilage. you see it in the rack before the report shows it.

manager confidence: if they stop everything for me, i'm a guest. if they nod and keep moving, i'm part of the operation. option two.

exception board: paper, low-tech, on the wall. five seconds tells me what's open.

speed: smooth, not busy. you can feel both within 30 seconds.

#smbops #multiunitoperator #qsr #donutshop #dfwsmallbusiness #deskless #shopwalkthrough

LinkedIn

Skip per calendar.

Production notes

• Shoot location: one shop, full first-person walkthrough. Saturday morning, real ops, not staged.
• Approach: gimbal or phone-with-stabilizer. Don't use a static cam — the walking POV is the format.
• Wardrobe: standard operator look — dark tee or hoodie, no logo, no flex. Hands should appear naturally in the frame.
• Audio: ambient kitchen sound bed under the VO. Don't kill the ambient — it's part of the texture.
• VO: record VO separately at home, not on-site. Read like a quiet operator telling a single person what to notice — not an instructor.
• Privacy: no customer faces in frame, no employee faces unless explicit consent. Blur any visible employee names on the exception board.
• Edit: cuts should match the rhythm of walking — every 4-6 seconds. Don't over-edit. The format is a quiet, observational walkthrough, not a music-video shop tour.
• No music: ambient only. Music would break the operator-noticing tone.
• Retention bet: the "smooth, not busy" close is the share line for operators who've felt the difference.

Voice check

• Real operator details (proofer door, crumbs near fryer, exception board, manager nod)
• No banned phrases ("hustle", "grind", "behind the scenes")
• No motivational close — close on operator observation
• One idea: what an operator notices vs what an inspection sheet says
• One quotable: "smooth, not busy"
• No CTA — let the walkthrough breathe

Day 19 — Sun Jun 7 — Batch + Analytics Review

Pillar: none (work day) Primary: no new feed post Secondary: IG Story 1 frame if a real moment shows up LinkedIn: none

Status: Internal production + review day per calendar. Two-hour work block.

Work block — 2 hours

Analytics review (40 min):

Pull metrics for Days 1-18. Rank by:

1. Retention at 30s (TikTok) and average watch time (IG Reel). Top 5 only.
2. Saves + shares (IG). Top 5 by absolute count.
3. Comments from real operators — manually count, not platform metric. Tag each as: question / agreement / disagreement / story.
4. Newsletter open rate + reply rate for Day 14 issue #1.

Write findings to Agent-OpenClaw/working-context.md with timestamp. Note which pillar (rollup / premium / Golden Ops) is hitting hardest and which is dragging.

Series decision (15 min):

Pick one recurring series to double down on in week 4 (Days 21-27).

Default if data is unclear: "Receipts Friday" — already running, low production cost, audience knows the format.

Alternatives if data points there:

• "Build-vs-buy Mondays" (anchor: Day 3 + Day 13)
• "Variance Wednesday" (anchor: Day 15)
• "Operator Saturday walkthrough" (anchor: Day 18)

Recording session — Days 20-24 (50 min):

Set up back-office for Days 20, 22, 23, 24 (Days 21 and 16/17 callbacks will record midweek if needed):

1. Day 20 — 13-Week Cash Forecast: back-office, forecast Sheet screen-record + talking head.
2. Day 22 — Investor Reporting: back-office, investor PDF flow screen-record.
3. Day 23 — Tool Stack Screen Record: back-office, rapid tour of the actual stack.
4. Day 24 — Receipts Friday #2: lock the 3-segment template (same as Day 10). Just need numbers — record placeholder, swap in real numbers Thursday night.

LinkedIn drafts (15 min):

Day 20 (forecast carousel caption), Day 22 (investor reporting), Day 29 (20+ employees lesson) to rough-draft.

IG Story frame (optional, single frame)

If a real moment surfaces:

• Photo of the analytics review on screen (no specific numbers visible).
• Caption overlay: "week 3 review."
• No CTA.

TikTok caption + hashtags

None — no public post today.

Instagram caption + hashtags

None — Stories optional only.

LinkedIn

None.

Production notes

• Analytics discipline: don't optimize for vanity metrics. Optimize for "operator comments per post" and "retention at 30s." Vanity views without operator pickup is wrong-audience traffic.
• Decision lock: write the series decision in working-context.md with a one-sentence reason. Future weeks reference that decision — don't re-litigate it midweek.
• Recording efficiency: keep wardrobe consistent within the session — change shirts only for variety across days, not within a day's batch.
• Failure mode: if analytics review is depressing (rare but possible early in a 30-day push), the move is to ship Days 20-24 as-is and revisit cadence at Day 30. Don't pivot mid-month based on early data.
• End state: Days 20-24 in editor with rough cuts. Series decision logged. LinkedIn drafts at first-draft state.

Voice check

• N/A — no public post.
• Internal note: comment replies during this week use the same voice rules. Lowercase, no emoji, no "thanks for watching."

Day 20 — Mon Jun 8 — 13-Week Cash Forecast

Pillar: the rollup Primary: TikTok 6:15am CT Mirror: IG Reel 7:30pm CT LinkedIn: document carousel 8:00am CT Hook: "the cash forecast that stopped me from refreshing dashboards all day."

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "the cash forecast that stopped me refreshing dashboards all day."
2. 3-10s — The w-2 habit b-roll: phone screen showing repeated app launches (mocked, no real data), generic anxiety-cue cuts — clock, phone, clock, phone.
3. 10-18s — The forecast intro: screen-record of the actual 13-week forecast Sheet. Column headers visible: Week, Fixed Costs, Payroll, Capex, Buffer, Decision Flag. All dollar amounts redacted.
4. 18-26s — The buffer rule visualized: simple on-screen graphic — buffer line, 1.5× fixed costs line, decision flags (green/yellow/red) plotted across 13 weeks.
5. 26-34s — The Monday cadence: quick montage — coffee, laptop opens, Sheet opens, 20-min timer, decision flag set, laptop closes.
6. 34-42s — The "single yes/no question" beat: talking head, on-screen text "monday's question: act this week, or ride the plan?"
7. 42-55s — Close beat: talking head, list "green: do nothing. yellow: tighten capex. red: cut something this week."
8. 55-60s — End frame: text card "discipline isn't more dashboards. it's one rule." Black background.

TikTok caption + hashtags

13-week cash forecast. one sheet. monday cadence. 1.5x buffer rule. stopped me refreshing dashboards all day. discipline is one rule, not more dashboards.

#smbops #multiunitoperator #cashflow #operatorlife #donutshop #dfwsmallbusiness #financialdiscipline

Instagram caption + hashtags

the 13-week cash forecast that stopped me refreshing dashboards all day.

one sheet. five columns — fixed costs, payroll, capex, buffer, decision flag. updated every monday in 20 minutes.

buffer rule: if the buffer drops below 1.5× fixed monthly costs at any point in the forward 13 weeks, i act this week. above the line, i ride the plan.

the unlock isn't the forecast. it's the rule. monday is one yes/no question — act, or ride the plan. green: do nothing. yellow: tighten capex. red: cut something this week.

i refresh dashboards once a day now. not because i'm more disciplined. because the forecast already told me what to worry about.

#smbops #multiunitoperator #cashflow #operatorlife #donutshop #dfwsmallbusiness #opsautomation

LinkedIn (document carousel — 7 slides, dark template matching Days 11/15)

Slide 1 (title): The 13-Week Cash Forecast That Killed My Refresh Habit one sheet. one rule. 20 minutes a week.

Slide 2 (the W-2 anxiety transfer): W-2: refreshed brokerage 3× a day for no reason. post-corporate: refreshed business bank accounts the same way. anxiety as a habit. nothing changed each refresh.

Slide 3 (the forecast structure): 5 columns: Fixed Costs, Payroll, Capex, Buffer, Decision Flag. 13 weeks rolling. updated every Monday in 20 minutes. not a financial model. an operating tool.

Slide 4 (the buffer rule): Buffer target: 1.5× fixed monthly costs. Green: buffer healthy. ride the plan. Yellow: tighten capex this month. Red: cut something this week.

Slide 5 (the Monday cadence): coffee → laptop → forecast → 20 minutes → decision flag → close laptop. single yes/no question: act this week, or ride the plan. no refreshing dashboards until the question is answered.

Slide 6 (what the rule replaced): 3× daily bank app refresh: gone. "what if capex spikes" anxiety loop: gone. mid-week reactive cuts: gone. the forecast did the worrying so I didn't have to.

Slide 7 (close): discipline isn't more dashboards. it's one rule, one cadence, and the courage to ride the plan. the forecast tells me what to worry about — and what not to.

Carousel caption:

13 years of W-2 wired my brain to check accounts 3× a day for no reason. The first thing I had to rebuild after corporate wasn't the cash position — it was the cadence.

The 13-week rolling cash forecast and the 1.5× buffer rule replaced 90% of my financial anxiety. One sheet. 20 minutes every Monday. One yes/no question.

Save this if you're carrying a W-2 nervous system into operating cash you don't get every two weeks.

#smbtwitter #verticalsaas #multiunitoperator #etaforum #searchfund

Production notes

• Shoot location: back-office desk, same setup as Days 3, 13, 14. The "back-office series" is now a recognizable visual lane. Don't disrupt.
• Wardrobe: dark tee, different from Days 13, 14, 15, 16, 17. Light enough variation for "different day, same operator" energy.
• Audio: lav mic. The "discipline isn't more dashboards. it's one rule" close is the share line — record it twice, pick cleaner.
• Edit: the screen-record of the forecast Sheet needs to hold at least 5 seconds. Viewers will pause to read the columns. Don't rush.
• Privacy: every dollar amount redacted. Show the structure only.
• LinkedIn carousel design: match Day 11 + Day 15 carousels. Same dark bg, same accent, same font. Save the template for Day 27 (Why Not Better SaaS?) — likely the next carousel format candidate.
• Retention bet: the buffer-rule visualization at ~20s is the share frame. Hold a beat after the green/yellow/red flags appear on screen.
• Newsletter teaser: add a final-frame Story link sticker mid-morning to newsletter signup. Forecast content drives newsletter signups historically.

Voice check

• Real numbers (13 weeks, 5 columns, 20 minutes, 1.5×, 3× a day, 13 years)
• No banned phrases ("financial freedom", "stress-free", "passive cashflow")
• One quotable per surface — TikTok ("discipline is one rule, not more dashboards"), IG ("the forecast already told me what to worry about"), LinkedIn ("the forecast did the worrying so I didn't have to")
• Operator POV — first-person, no "you should"
• Single CTA (newsletter on IG/LinkedIn via Story link, none on TikTok)
• Tension before payoff (refreshed dashboards all day → buffer rule → discipline is one rule)
• No motivational close

Batch 2 production summary

Days covered: 11-20 (Sat May 30 → Mon Jun 8) Shoot days: 13, 15, 16, 17, 18, 20 (talking head + screen-record) Carousel days: 11, 15, 20 (matching dark template) Light/work days: 12, 19 (Sundays — no public feed posts) Newsletter day: 14 (issue #1) Series anchors locked:

• Morning-screen carousel (Day 11) → re-template for Month 2
• Variance Wednesday (Day 15) → analytics-tested for series candidate on Day 19
• 13-Week Cash Forecast (Day 20) → primary candidate to become Mondays series anchor for Month 2

Unresolved flags carried forward to Batch 3:

1. SaaS replacement canonicalized — use $60K/yr throughout. Older higher estimates were incorrect.
2. Employee count canonicalized — use 20+ employees throughout. Older inflated references were incorrect.
3. Day 16 real ticker — placeholder framework used. Swap to a real recent trade with redacted account info before shooting.
4. Day 20 buffer rule numbers — used 1.5× fixed monthly costs as the rule. Verify this is Jack's actual operating rule before publishing.
5. Day 17 voice memo casting — find a friend to re-record the manager voice memo. Do not use synthesis or Jack's voice.

No deviations from the calendar topic spine. Batch 3 (Days 21-30) ready to write next.

30-Day Playbook — Days 21-30

Window: Tue 2026-06-09 through Thu 2026-06-18 Pillars: Operator OS, Golden Glaze rollup, FlexStay repeatability proof, operator treasury Format: full production depth — script, b-roll, captions, production notes per day Status: internal review — for Jack only

Revision note: execute this batch through the Operator OS lens in 05_operator_os_revision.md. Day 23, Day 27, and Day 30 should explicitly show the broader workspace: Golden Ops, Cash Control, Sales Report, KPI/ReviewIQ, FlexStay Ops, and Golden Invest where safe.

Day 21 — Tue Jun 9 — Trade Mistake

Pillar: operator treasury Primary: TikTok 7:30pm CT Mirror: IG Reel next morning LinkedIn: none Hook: "the options loss that made me stop buying lottery tickets."

B-roll shot list

1. 0-3s — Hook frame: talking head close-up, on-screen text "the options loss that taught me to stop buying."
2. 3-10s — The mistake setup: mock or sanitized trade ticket — far OTM calls, small position, 2022 date. Strike and ticker blurred; structure visible.
3. 10-18s — The loss visualization: simple chart showing call price decay to zero. Then a second chart showing the underlying moving 6 weeks after expiration.
4. 18-26s — The wrong conclusion: talking head, on-screen text "the dangerous part wasn't the loss. it was wanting to size up."
5. 26-34s — The strategy flip: simple split-screen — left "buying premium: right about ticker, strike, AND timing" / right "selling premium: right about ticker, willing to be wrong about timing".
6. 34-45s — Current rule: talking head, on-screen text "puts i'd be happy assigned on. calls against shares i'd be happy to sell."
7. 45-55s — The "tuition" close: talking head, on-screen text "losing was tuition. selling premium is the process."
8. 55-60s — End frame: disclaimer card "not financial advice. educational only."

TikTok caption + hashtags

the options loss that made me stop buying lottery tickets. 2022 calls expired worthless. wrong conclusion was "size up". right conclusion was flip sides. not financial advice.

#options #wheelstrategy #sellingpremium #optionsincome #csp #tradingmistakes #optionstrading

Instagram caption + hashtags

2022. tech stock i was sure of. far out-of-the-money calls. small position, big leverage, conviction entry. classic mistake.

thesis was right. timing was wrong. underlying moved 6 weeks after my calls expired worthless. mid-four-figure loss.

the actual mistake wasn't the loss. it was the conclusion — that i needed to "play smarter" by sizing up next time.

i didn't size up. i stopped buying.

the flip — buying premium means i need to be right about ticker, strike, AND timing in a narrow window. selling premium means i need to be right about ticker and willing to be wrong about timing — assignment is fine if i wanted the shares anyway.

three years later, every trade is a put i'd be happy assigned on or a call against shares i'd be happy to sell.

losing was tuition. selling premium is the process. not financial advice.

#options #wheelstrategy #sellingpremium #optionsincome #csp #tradingmistakes #optionstrading

LinkedIn

Skip per calendar. Trade-mistake content stays platform-native to TikTok/IG.

Production notes

• Shoot location: back-office desk, brokerage screen with all account info covered. Same setup as Day 16 for visual continuity in the wheel series.
• Wardrobe: dark tee, different from Days 16 and 20.
• Audio: lav mic. The "losing was tuition" close is the share line — record it three times. The tone should be matter-of-fact, not regretful.
• Edit: the split-screen at 26-34s is the visual anchor — viewers will screenshot it. Make sure the framing is clean and the text reads on mobile.
• Privacy: no real ticker name. No real loss amount beyond "mid-four-figure." No screenshot of the actual 2022 trade — reconstruct visually only.
• Disclaimers: "not financial advice" on-screen from second 30. Caption always.
• Retention bet: the "wanting to size up" beat at ~22s is the retention pivot — it's the part viewers haven't heard before. Cut tight to it.
• Sequence note: Day 16 (one trade walkthrough) + Day 21 (trade mistake) + Day 28 (monthly premium snapshot) form the wheel-series triangle for Month 1. Tone progression: framework → counter-example → results.

Voice check

• Real numbers (2022, 6 weeks, mid-four-figure, 3 years later)
• No banned phrases ("guaranteed income", "trade like a pro", "make X per month")
• No motivational close — close on operating discipline ("losing was tuition. selling premium is the process.")
• Operator POV — first-person, no "you should"
• Single CTA (none)
• Tension before payoff (loss → wrong conclusion → flip sides → 3-year track record)
• One quotable: "losing was tuition. selling premium is the process."
• Disclaimers visible

Day 22 — Wed Jun 10 — Investor Reporting

Pillar: Golden Ops Primary: LinkedIn 7:45am CT Secondary: TikTok 6:15am CT Tertiary: IG Reel 7:30pm CT Hook: "the report matters less than whether it shows up on time."

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "the report matters less than whether it shows up on time."
2. 3-10s — The 15th calendar beat: screen-record of a calendar with the 15th marked, deadline reminder visible. Pull back to show the calendar is recurring quarterly.
3. 10-18s — Numbers pull: screen-record showing data extraction from quickbooks, square, stripe (mock or sanitized screens — no real numbers visible).
4. 18-26s — Standard sections assembled: scroll-through of a redacted investor PDF — section headers visible (occupancy, p&l, expense variance, capex, distributions), body text fully blurred.
5. 26-34s — The narrative section: screen-record of a Notion or Doc with a section header "Q1 narrative — by Jack" — body fully blurred. Hold on the header.
6. 34-42s — DocuSend trail: screen-record showing the send confirmation, recipient list redacted, delivery + open status visible.
7. 42-55s — The "boring cadence" beat: talking head, on-screen text "respect comes from showing up on the 15th. every time."
8. 55-60s — End frame: text card "sub-scale gp reputation is built in cadence." Black background.

TikTok caption + hashtags

the report matters less than whether it shows up on time. lps don't remember the irr. they remember which gps went silent after a bad quarter. cadence beats narrative.

#smbops #gpdiscipline #realestateops #fundops #operatorlife #donutshop #multiunitoperator

Instagram caption + hashtags

the report matters less than whether it shows up on time.

golden glaze is a gp/lp fund — accredited investors, quarterly distributions. every lp has been burned by a sub-scale operator who promised great returns and then went silent for two quarters.

what gets you respect from lps isn't the irr. it's the report showing up on the 15th of the month after the quarter closes. every quarter. no exceptions.

golden ops pulls the numbers from quickbooks, square, stripe. assembles the standard sections. exports a pdf. tracks the send.

the narrative section i still write by hand. that part should not be automated — investors need to hear me think, not the bot.

sub-scale gp reputation is built in the boring cadence, not the headline returns.

#smbops #gpdiscipline #realestateops #fundops #operatorlife #donutshop #multiunitoperator

LinkedIn (proper case, ~280 words)

The report matters less than whether it shows up on time.

Golden Glaze is a GP/LP structure. Accredited investors. Quarterly distributions. Every LP I've spoken to has at least one story about a sub-scale operator who promised great returns and then went silent for two quarters after a bad one. That's the failure mode investors are actually pattern-matching against — not your IRR.

What earns respect at this scale isn't the headline return. It's the report showing up on the 15th of the month after the quarter closes. Every quarter. Without an excuse.

Golden Ops handles the boring half of the workflow. It pulls quarter-end numbers from QuickBooks, Square, and Stripe. Assembles the standard sections — occupancy and sales per shop, consolidated P&L, expense variance, capex deployed, distribution math. Exports a PDF with consistent formatting and runs the DocuSend trail.

The narrative section I still write by hand. That part shouldn't be automated. LPs need to hear me think — what went right, what surprised me, what I'm watching for the next quarter, what I'd do differently. That's the relationship layer. The numbers are the contract; the narrative is the trust.

The automation just protects the cadence. So even in a quarter where one shop had a hood fire, a manager exited, and a unit needed a roof replacement — the report still goes out on the 15th. Because the formatting, exporting, and sending isn't on my critical path during the operational fire.

Sub-scale GP reputation is built in the boring cadence, not the headline returns.

If you're considering taking outside capital at 5-20 units in a physical-asset rollup, build the reporting cadence first. Then go raise.

#searchfund #etaforum #realestateops #fundops #verticalsaas

Production notes

• Shoot location: back-office desk, same setup as Days 3, 13, 14, 20. The "back-office series" continuity.
• Wardrobe: plain dark tee, different from previous week. Investor-themed posts should feel slightly more composed — no hoodie this time.
• Audio: lav mic. The "respect comes from showing up on the 15th" line is the share line — record twice, pick cleaner.
• Edit: screen-record holds at 4-5s on each redacted artifact (PDF scroll, calendar, DocuSend). LPs in the audience will watch frame-by-frame; non-LP operators just need the structure.
• Privacy: absolute. No LP names, no entity names, no real distribution amounts, no recipient list visible in the DocuSend screen. If any frame leaks an identifier, re-shoot.
• LinkedIn-first ordering: post LinkedIn first at 7:45am, TikTok at 6:15am CT (yes, before LinkedIn — TikTok's morning window matters more for that platform). IG Reel at 7:30pm CT after both have had time to settle.
• Retention bet: the "narrative is the trust" beat at ~36s on the talking head reads as quotable for LinkedIn — feature it on-screen as a text overlay during the TikTok/IG cut.

Voice check

• Real numbers (GP/LP, quarterly, 15th of month, 3 source systems, 5+ standard sections)
• No banned phrases ("crushing it", "10x returns", "investor opportunity")
• No motivational close — close on operating discipline ("cadence beats narrative", "reputation built in cadence")
• Operator POV — first-person, no "you should"
• Single CTA per surface — LinkedIn ("build the reporting cadence first, then go raise"), TikTok/IG (none)
• Tension before payoff (LPs have been burned → it's not the IRR → it's the cadence → automate the boring half)
• One quotable per surface — LinkedIn ("the numbers are the contract; the narrative is the trust"), TikTok/IG ("cadence beats narrative")

Day 23 — Thu Jun 11 — Tool Stack Screen Record

Pillar: Golden Ops Primary: TikTok 7:30pm CT Mirror: IG Reel next morning LinkedIn: none Hook: "my operator stack is uglier than people expect."

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "my operator stack is uglier than people expect."
2. 3-12s — Cursor: screen-record of Cursor open on a Golden Ops file (function names blurred or use a public-safe file). Hold 4s.
3. 12-20s — Claude: screen-record of a Claude conversation about architecture (prompt text blurred or use a public-safe example). Hold 4s.
4. 20-28s — Discord: screen-record of the Golden Ops Discord bot — daily digest message, shop check-in flow, issue card creation. Names blurred. Hold 6s.
5. 28-34s — Google Drive: screen-record of the Drive folder structure showing the storage layout. Folder names visible, file contents blurred.
6. 34-40s — Google Sheets: quick screen-record of a Sheet acting as a data layer — column headers visible, row content blurred.
7. 40-46s — Notion: screen-record of the investor document workspace — section headers visible, body blurred.
8. 46-52s — The "ugly stack" reveal: on-screen text overlay listing the stack: "Cursor + Claude + Discord + Drive + Sheets + Notion + a $20/mo VPS. that's it."
9. 52-60s — End frame: talking head, on-screen text "ugly + adopted beats pretty + unused."

TikTok caption + hashtags

the operator stack that replaced $60k of qsr saas. cursor, claude, discord, drive, sheets, notion, $20/mo vps. ugly + adopted beats pretty + unused every time.

#internaltools #smbops #aiops #claude #cursor #opsautomation #multiunitoperator #buildlog

Instagram caption + hashtags

my operator stack is uglier than people expect.

people see "$60k of qsr saas replaced in 3 weeks" and assume the result looks like a polished saas product. it doesn't. it looks like glue.

the actual stack — cursor for code. claude for architecture and boilerplate. discord as the front end because that's where my managers already live. google drive as storage. google sheets where postgres would be overkill. notion for investor docs.

golden ops itself sits on a $20/mo vps. nothing modern. nothing fancy.

the lesson — pretty software is expensive if nobody uses it. ugly software is cheap if the team adopts it on day one. ugly + adopted beats pretty + unused every single time.

the stack isn't a flex. it's a constraint. constraints made the build fast.

#internaltools #smbops #aiops #claude #cursor #opsautomation #multiunitoperator #buildlog

LinkedIn

Skip per calendar. Stack-reveal content stays platform-native to TikTok/IG.

Production notes

• Shoot location: back-office desk for the talking head intro/outro. Screen-record is the bulk of the video.
• Wardrobe: plain tee, varied from previous days but consistent operator energy.
• Audio: lav mic for talking head. Voiceover layered on the screen-record tour — pre-record the VO clean, then sync to the screen-record.
• Edit: the screen-record tour is the deliverable. Each tool gets 4-6 seconds. Don't quick-cut — viewers will pause to read the structure.
• Privacy: highest discipline. Every screen-record needs a redaction pass. Function names, prompt text, manager names, shop names, file contents, investor document text — all blurred or replaced with public-safe placeholders.
• Tool order: code → AI → comms → storage → structured data → docs. The order matches the flow of how a request travels through the stack.
• Pin in caption: "if you want the build breakdown, newsletter link in bio." Newsletter signups from stack-reveal posts historically high.
• Retention bet: the "ugly + adopted beats pretty + unused" close is the share line. Drop a 2-second pause before it for emphasis.

Voice check

• Real stack names (Cursor, Claude, Discord, Drive, Sheets, Notion, $20/mo VPS)
• No banned phrases ("ai-powered", "next-gen", "transformative")
• Operator POV — first-person, no "you should"
• One idea: ugly + adopted beats pretty + unused
• Single CTA (newsletter link via caption — light)
• Tension before payoff (people expect polish → it looks like glue → constraints made the build fast)
• One quotable: "ugly + adopted beats pretty + unused"

Day 24 — Fri Jun 12 — Receipts Friday #2

Pillar: all three Primary: TikTok 6:15am CT Mirror: IG Reel 7:30pm CT LinkedIn: short reflection post 8:30am CT Hook: "3 numbers from this week."

B-roll shot list (Receipts Friday template — same as Day 10)

1. 0-3s — Hook frame: talking head, on-screen text "3 receipts. week 2."
2. 3-18s — Segment 1: SHOP: screen-record of the WoW sales metric (redacted dollar value, percentage visible), then 3-second shop b-roll cut. On-screen number large during the screen-record.
3. 18-33s — Segment 2: SOFTWARE: screen-record of the Golden Ops change — could be a diff, a feature flag, a manager-facing UI change. On-screen text reads the one-line impact statement.
4. 33-45s — Segment 3: PREMIUM: screen-record of the trade summary (redacted account info, P&L percentage visible). On-screen text reads the close or assignment status.
5. 45-50s — End frame: text card "next friday: 3 more." Same template as Day 10.

TikTok caption + hashtags

week 2 receipts. one shop number, one software change, one trade closed. no commentary, just numbers.

#receiptsfriday #smbops #multiunitoperator #operatorlife #donutshop #wheelstrategy #buildlog

Instagram caption + hashtags

3 receipts. week 2.

shop: [TBD Thursday night — WoW sales movement, one specific shop note]

software: [TBD Thursday night — one shipped golden ops change, one-line impact]

premium: [TBD Thursday night — one wheel trade closed or assigned, redacted P&L]

three numbers. one operating week.

#receiptsfriday #smbops #multiunitoperator #operatorlife #donutshop #wheelstrategy #buildlog

LinkedIn (~150 words, proper case)

Week 2 of the 30-day publishing push. Same Friday format: three numbers from the operating week.

Shop: [TBD Thursday night — same as TikTok/IG.]

Software: [TBD Thursday night — one shipped Golden Ops change with one-line impact.]

Premium: [TBD Thursday night — one wheel trade closed or assigned, redacted result.]

The format is the point. Same three categories every Friday. Same three numbers. Same redaction discipline. The series is "Receipts Friday" — if you've been around for week 1, week 2 is the proof-of-cadence drop.

Operating discipline is a cadence problem before it's an insight problem. The receipts series is partly content, partly accountability mechanism — if I publish three real numbers every Friday, the operating week has to actually produce three real numbers.

Next Friday: 3 more.

#smbtwitter #verticalsaas #multiunitoperator #etaforum #operatorlife

Production notes

• Template lock: Receipts Friday format is now locked from Day 10. Same on-screen template, same 3-segment structure, same end card. Do not deviate — series recognition is the asset.
• Number capture deadline: Thursday night before recording. The 3 numbers must be real, redacted appropriately, and tied to actual operating events from the week. No placeholder numbers. If a category has no real number that week, replace with a different category (rare — typically there's always a shop, software, or trade event).
• Shoot location: rotate between back-office desk and one of the shop back-rooms for visual variety while keeping the template the same. Day 10 was back-office; Day 24 could be a shop back-room for week 2.
• Wardrobe: Friday-default — light hoodie or tee. Consistent with Day 10 wardrobe energy.
• Audio: lav mic. Keep the read tight — viewers want the numbers, not commentary.
• Edit: 15-second segments. Cut tight. The template only works if the pacing is consistent.
• Privacy: every dollar amount redacted. Percentages, deltas, and shapes visible.
• Series propagation: Day 30 month-1 recap closes the loop. After Day 30, the template becomes the Month 2 anchor.

Voice check

• Real numbers in every segment (week-over-week shape, software impact in hours/dollars saved, wheel trade close percentage)
• No banned phrases ("crushing it", "massive week", "killed it")
• No motivational close
• Operator POV — first-person, no "you should"
• Single CTA (none — let the format carry)
• Series consistency with Day 10 (same template, same segment order, same end card)
• One quotable: "three numbers. one operating week."

Day 25 — Sat Jun 13 — Founder Face / Quiet Day

Pillar: operator identity Primary: IG Stories (3 frames) Secondary: TikTok optional (only if Friday Receipts post is still climbing) LinkedIn: none

Status: Light day per calendar. No talking-head shoot. Stories captured live during normal Saturday ops.

Story frame plan

Frame 1 — Shop check (mid-morning, 10-11am):

• 5-second vertical clip of Jack walking through one shop's floor — first-person POV, hands visible interacting with a rack or speaking briefly with a manager (no audible dialogue).
• Caption overlay: "saturday floor check."
• No CTA. No music.

Frame 2 — Laptop / back-office (afternoon, 2-3pm):

• Still photo of the laptop on a back-office desk with the operating dashboard visible (numbers redacted, structure visible).
• Caption overlay: "boring work. the kind that compounds."
• No CTA.

Frame 3 — Text frame (evening, 7-8pm):

• Plain black background, lowercase white text.
• "the work is mostly boring. that's why it works."
• No CTA. Let it sit.

B-roll shot list

Capture-only — no scripted shoot:

1. 2-3 candid shop clips during the Saturday morning visit (floor, rack, manager interaction without dialogue).
2. 1 laptop / back-office still photo with redacted dashboard.
3. Prep for Day 26: screenshot or save the best 5 operator questions from comments on Days 11-24. Use a Notes file recurring_q_and_a.md. Pick 1-2 for the Day 26 answer.

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text reading the question — "someone asked why i didn't just buy better qsr software."
2. 3-10s — The 2024 evaluation beat: screen-record of 4 redacted SaaS landing pages or evaluation notes. Pricing pages blurred. Hold 4-5s.
3. 10-18s — The "median customer" frame: simple on-screen split — "median customer of platform A: single-unit operator" / "median customer of platform B: 100-unit chain." Show the gap.
4. 18-26s — The 7-shop deskless gp/lp middle beat: static text card "7 shops + deskless managers + gp/lp = middle-gap. neither category."
5. 26-34s — The "build specific" frame: screen-record cuts to actual Golden Ops surfaces — Discord daily digest, scheduler, investor report. Real surfaces, redacted.
6. 34-45s — Close frame: talking head, on-screen text "middle-gap operators: accept the misfit, or build specific."

TikTok caption + hashtags

q: why didn't you just buy better qsr saas? a: better exists for the median customer. doesn't exist for the middle. middle-gap operators build specific or pay the misfit.

#smbops #multiunitoperator #internaltools #buildlog #qsr #donutshop #deskless

Instagram caption + hashtags

someone asked why i didn't just buy better qsr software.

short answer — i tried. spent two months in 2024 evaluating four different multi-unit ops platforms. they all had the same problem.

they're built for either single-unit owners or 100-unit chains. a 7-shop deskless rollup with a gp/lp fund on top is neither category.

the customer profile they actually fit is the median customer — and the median customer isn't running a rollup.

better software exists for the median. it doesn't exist for the middle. so i didn't buy better — i built specific.

if you're in middle-gap territory: accept the misfit and pay for it, or build specific and own it. there isn't a third option that doesn't cost more time than building does.

#smbops #multiunitoperator #internaltools #buildlog #qsr #donutshop #deskless

LinkedIn

Skip Day 26. Bigger LinkedIn post lands on Day 27.

Production notes

• Q&A discipline: only post if the question (or the default fallback) is genuinely operator-level. Skipping is fine — Day 26 is optional content.
• Shoot location: back-office desk, lower-key lighting than Days 3/13/14 — Q&A days are conversational, not declarative.
• Wardrobe: plain tee, varied from week.
• Audio: lav mic. The conversational tone is the format — slightly slower delivery, slightly more pauses than the declarative posts.
• Edit: the question-on-screen at the start is the hook. The platform-comparison split at 10-18s is the share frame.
• Reserve clip cadence: batch the 2-3 reserve Q&A clips even if Day 26 doesn't ship publicly. Month 2 will need them.
• Newsletter discipline: outline only on Day 26. Final newsletter writes on Day 27 for Day 28 send. Don't draft both posts and newsletter in the same session — quality drops.

Voice check

• Real numbers (4 platforms, 2 months, 7 shops, deskless, GP/LP, 2024)
• No banned phrases ("better than the competition", "next-gen platform", "transformative")
• Operator POV — first-person, "i tried" "i built"
• One idea: middle-gap operators have to choose specificity or misfit
• No CTA — let the answer breathe
• One quotable: "build specific or pay the misfit"
• No motivational close

Day 27 — Mon Jun 15 — Why Not Better SaaS?

Pillar: Golden Ops Primary: TikTok 6:15am CT Mirror: IG Reel 7:30pm CT LinkedIn: text post 8:00am CT (highest priority) Hook: "why didn't i just buy better qsr software?"

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "why didn't i buy better qsr software?"
2. 3-12s — 2024 evaluation b-roll: screen-record of evaluation notes (Sheet with 4 platforms in rows, criteria in columns, ratings visible). Hold 4-5s — viewers will read.
3. 12-22s — Single-unit failure mode: quick split-screen — left "single-unit tool: pos + reporting." / right "needed: cross-unit scheduling, waste tracking, gp reporting." Mismatch visualized.
4. 22-32s — 100-unit failure mode: split-screen — left "100-unit tool: assumes corporate it, dedicated admins, training program." / right "i have one back-office laptop and 7 managers with phones."
5. 32-40s — The "middle gap" frame: static text card "3-15 units. deskless team. fund layer. nobody's median customer."
6. 40-50s — Adaptation cost beat: on-screen list — "training: 40h. configuration: 60h. workflow bending: ongoing. exit cost: data lock-in." Adaptation cost is the hidden bill.
7. 50-58s — The "specificity is the moat" close: talking head, on-screen text "internal tools win when specificity is the moat."
8. 58-65s — End frame: text card "buy the median. build the middle."

TikTok caption + hashtags

why didn't i buy better qsr saas? because better exists for the median, not the middle. 3-15 units + deskless + fund = nobody's median customer. internal tools win when specificity is the moat.

#smbops #internaltools #multiunitoperator #buildvsbuy #qsr #donutshop #buildlog

Instagram caption + hashtags

why didn't i buy better qsr software?

i did try. two months in 2024 evaluating multi-unit ops platforms. four serious candidates. all failed the same way.

the platforms are either built for single-unit owners (pos + reporting) or for 100-unit chains (corporate it, dedicated admins, training programs). their feature sets reflect their actual customer base.

the middle — 3 to 15 units, deskless team, owner-operator with a fund layer — isn't anyone's median customer. so the platform never gets shaped around your workflow. you adapt to theirs. that adaptation cost is the hidden bill nobody talks about.

i didn't build because i wanted to. i built because the cost of bending our workflow to fit the platform was higher than the cost of building specific.

internal tools win when specificity is the moat. if your operating shape isn't specific, buy. if it is, build — and build the smallest version that works, not the biggest version you can imagine.

#smbops #internaltools #multiunitoperator #buildvsbuy #qsr #donutshop #buildlog

LinkedIn (proper case, ~300 words — highest-priority post of the week)

"Why didn't you just buy better QSR software?"

I get this question more than any other from operators in the build-vs-buy spot. So this is the long-form answer.

I did try. Two months in 2024 evaluating multi-unit operations platforms. Four serious candidates. All failed the same way.

The platforms were built for one of two customer profiles. Single-unit owners — a person who owns one location and needs a POS with reporting on top. Or 100-unit chains — corporate operations, head of ops, full IT stack, six-figure software budget. Their feature sets reflected their actual customer base.

Single-unit tools couldn't handle multi-shop scheduling, cross-unit waste tracking, GP-level consolidated financial reporting. The data model assumed one location.

100-unit tools assumed I had corporate IT, dedicated workflow administrators, and team training programs. I have one back-office laptop and 7 deskless managers communicating on phones.

The middle — 3 to 15 units, deskless team, owner-operator with a fund layer on top — isn't anyone's median customer. So the platform never gets shaped around your workflow. You adapt to theirs. That adaptation cost is the hidden bill nobody mentions during the sales call.

Real numbers from one of the four evaluations: ~40 hours of training, ~60 hours of configuration, ongoing workflow-bending forever, and a data lock-in exit cost I didn't want to discover at year 3.

Building specific cost me 3 weeks of build time and roughly nothing in ongoing maintenance.

I didn't build because I wanted to. I built because the cost of bending our workflow to fit the platform was higher than the cost of building specific.

Internal tools win when specificity is the moat. If your operating shape isn't specific, buy. If it is, build — and build the smallest version that works, not the biggest version you can imagine.

#smbtwitter #verticalsaas #multiunitoperator #searchfund #etaforum

Production notes

• Shoot location: back-office desk. The Day 27 build-vs-buy series anchor.
• Wardrobe: dark tee. Lock the "build-vs-buy series" wardrobe — Days 3, 13, 27 should look like the same operator-philosophy thread.
• Audio: lav mic. The "specificity is the moat" close is the LinkedIn quote — record twice, pick cleaner.
• Edit: the split-screen single-unit vs 100-unit beats at 12-32s are the share frames. Make sure the on-screen text reads on mobile.
• Privacy: no real platform names in the b-roll (use blurred logos or generic mockups). The story isn't "platform X is bad" — it's "the category doesn't fit middle-gap operators."
• LinkedIn priority: this is the highest-stakes LinkedIn post of the week. Hold the 7-day window — schedule for 8:00am CT Monday to catch the corporate-tech-Monday-morning operator audience.
• Newsletter follow-up: the LinkedIn post links to Day 28 newsletter issue #2 implicitly. Don't write the link in the post — let the cadence speak.
• Retention bet: the "i didn't build because i wanted to. i built because the cost was higher to bend the workflow" beat at ~52s is the operator share line. Cut tight.

Voice check

• Real numbers (2 months, 4 platforms, 3-15 units, 7 shops, 40h training, 60h configuration, 3 weeks build)
• No banned phrases ("disrupting", "next-gen", "ai-first")
• Operator POV — first-person, no "you should" (LinkedIn uses "if your operating shape isn't specific, buy. if it is, build" as advisory but applies to the operator audience, not generic motivational)
• Single CTA per surface — LinkedIn has implicit newsletter follow-up via cadence; TikTok/IG none
• Tension before payoff (i tried → 4 platforms failed → middle-gap nobody's median → built because adaptation cost too high)
• One quotable per surface — TikTok/IG ("internal tools win when specificity is the moat"), LinkedIn (same + "i built because the cost of bending our workflow was higher than the cost of building specific")
• No motivational close

Day 28 — Tue Jun 16 — Monthly Premium Snapshot

Pillar: selling premium Primary: TikTok 7:30pm CT Mirror: IG Reel next morning LinkedIn: none unless numbers exceed monthly threshold (decide Thursday) Hook: "premium collected this month — and what i wouldn't touch."

B-roll shot list

1. 0-3s — Hook frame: talking head close-up, on-screen text "premium collected. month 1."
2. 3-12s — Total premium screen: screen-record of the trade tracker — total column visible (real number or sanitized band), other account info covered.
3. 12-22s — Trades summary: quick screen-record of the position log — opened / closed / assigned / rolled columns, redacted ticker names visible as placeholders.
4. 22-32s — Wins frame: on-screen list of win criteria — "right delta. closed at 50-60%. would own at the strike." 3 bullets, hold 4-5s.
5. 32-42s — Close calls beat: quick chart visualization — strike line, 5% buffer line, position close marker showing it came in close but didn't get assigned.
6. 42-50s — Tickers avoided beat: on-screen list — "earnings in window. low-liquidity chain. don't want to own at any price." 3 bullets, hold 4-5s.
7. 50-55s — End frame: disclaimer card "not financial advice. process not picks."

TikTok caption + hashtags

month 1 of wheel premium captured. real number. trades opened, closed, assigned. wins, close calls, tickers i wouldn't touch. process not picks. not financial advice.

#wheelstrategy #sellingpremium #options #cashflow #optionsincome #csp #monthlyreview

Instagram caption + hashtags

month 1 wheel premium snapshot.

[TOTAL] real premium captured this month — placeholder until day-of recording.

[TRADES] positions opened / closed / assigned / rolled. one-line summary each.

wins — names i'd be happy assigned on, captured at target delta, closed at 50-60% max profit.

close calls — 1-2 positions came inside 5% of strike. assignment plan was ready.

tickers i wouldn't touch — earnings inside window, low-liquidity chains, names i don't want to own at any price.

assignment risk going into next month — open positions still inside the window. plan set.

process, not picks. not financial advice.

#wheelstrategy #sellingpremium #options #cashflow #optionsincome #csp #monthlyreview

LinkedIn (optional — only if monthly premium clearly exceeds a "respectable but not flashy" band — decide Thursday)

Month 1 of publishing the wheel premium snapshot.

Total premium captured: [TBD — real number from brokerage].

Positions: [opened / closed / assigned / rolled — real summary].

The reason for posting this isn't to brag the numbers. It's to demonstrate that wheel premium isn't a magic income stream — it's a process with wins, close calls, and tickers that don't fit the framework.

Wins came from names I'd be happy assigned on, captured at target delta, closed at 50-60% max profit before gamma risk got expensive.

Close calls came from positions that came within 5% of strike. Assignment plan was ready. Didn't get assigned this time.

Tickers I wouldn't touch this month — names with earnings inside my expiration window, low-liquidity options chains, and a few names I don't want to own at any price.

The framework is repeatable. The numbers will vary. The discipline doesn't.

Process, not picks. Not financial advice.

#wheelstrategy #sellingpremium #options #optionsincome #etaforum

Production notes

• Number capture deadline: day-of recording (Tue morning before the 7:30pm post). Total premium must come from the brokerage statement or accurate position log. No estimates, no rounded-up numbers.
• Shoot location: back-office desk, same setup as Days 16 and 21. The wheel-series visual lane.
• Wardrobe: plain dark tee, different from previous wheel-series days. Maintain the variety while keeping the lane recognizable.
• Audio: lav mic. Read the numbers cleanly — viewers will rewind to verify they heard correctly.
• Edit: screen-record holds at 4-5s on each numerical artifact. Don't quick-cut a results post.
• Privacy: account number, balance, year-to-date P&L, position sizes — all covered. Only the metrics being discussed are exposed.
• Disclaimers: "not financial advice" on-screen from second 10. Caption always.
• LinkedIn gate: check Thursday whether to post LinkedIn. The threshold isn't a specific dollar amount — it's whether the monthly result reads as "real, repeatable, not flashy." If the numbers feel like a flex, skip LinkedIn. If they read as operator-discipline, post.
• Series triangulation: Day 16 (framework) + Day 21 (counter-example) + Day 28 (results) close the wheel-series triangle for Month 1.

Voice check

• Real numbers (total premium, position count, 50-60% max profit, 5% buffer)
• No banned phrases ("massive month", "crushed it", "passive cashflow")
• Operator POV — first-person, no "you should"
• Single CTA (none)
• Disclaimers visible
• Tension before payoff (here's the number → but here's the process → and here's what i wouldn't touch)
• One quotable: "process, not picks"
• LinkedIn gate prevents flex tone

Day 29 — Wed Jun 17 — The 20+ Employee Lesson

Pillar: the rollup Primary: LinkedIn 7:45am CT Secondary: TikTok 6:15am CT Tertiary: IG carousel 7:30pm CT Hook: "the hardest part of 20+ employees isn't management. it's consistency."

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "the hardest part of 20+ employees isn't management. it's consistency."
2. 3-10s — One shop hides: quick montage of a single shop running smoothly — fryer in motion, glazing wheel, manager confidently working the floor.
3. 10-20s — Seven shops expose: split-screen visualization — left "shop 1: 14-item checklist." right "shop 6: 9-item checklist." Below: "same recipe. different consistency."
4. 20-30s — Variance metrics: on-screen comparison — "waste: 3% vs 11%. labor: 24% vs 29%. cash variance: ±$8 vs ±$31." Don't mock these numbers; pull real cross-shop variance from the dashboard with shop identifiers blurred.
5. 30-40s — The fix beat 1: prompts: screen-record of the Golden Ops opening prompt — manager opens the channel, bot asks the standard questions, manager responds. No memory required.
6. 40-48s — The fix beat 2: checklists: screen-record of the closing checklist UI — same 9 items in every shop. Tick boxes, timestamps.
7. 48-55s — The fix beat 3: exception routing: quick screen-record of an equipment issue card opening, routing automatically to the vendor channel.
8. 55-60s — End frame: text card "consistency is the product. the system holds the line." Black background.

TikTok caption + hashtags

20+ employees across 7 shops. the hardest part isn't management — it's consistency. multi-unit ops is a consistency business, not a hustle business. prompts + checklists + exception routing hold the line.

#smbops #multiunitoperator #qsr #deskless #donutshop #consistency #opsautomation

Instagram (carousel — 7 slides, dark template matching Days 11, 15, 20)

Slide 1 (title): The Hardest Part of 20+ Employees Isn't Management. It's consistency.

Slide 2 (one shop hides): one shop can hide issues. a good manager covers for a bad system. you don't see the gaps until you scale.

Slide 3 (seven shops expose): shop 1: 14-item closing checklist. shop 6: 9-item closing checklist. same recipe. same supplier. same hours. different consistency.

Slide 4 (variance metrics): waste: 3% vs 11%. labor as % of revenue: 24% vs 29%. cash variance: ±$8 vs ±$31. that's the cost of inconsistency.

Slide 5 (the lesson): multi-unit operations are a consistency business. not a hustle business. the heroics that work for 1 shop break at 3.

Slide 6 (the fix): prompts: the bot asks. the manager doesn't have to remember. checklists: same 9 items in every shop, every day. exception routing: equipment, supply, staffing — auto-routed.

Slide 7 (close): consistency is the product. variance is the cost. the system holds the line when the human can't.

LinkedIn (proper case, ~300 words)

The hardest part of 20+ employees across 7 shops isn't management. It's consistency.

One shop can hide issues. A good manager covers for a bad system. You don't see the gaps until you have multiple shops trying to run the same playbook and you notice they're running seven different versions of it.

Seven shops expose system gaps that one shop never would. The manager at Shop 4 trains opening differently than the manager at Shop 2. The closing checklist at Shop 1 has 14 items; at Shop 6 it has 9. Waste runs 3% at one shop and 11% at another. Same recipe. Same supplier. Same hours. Different consistency.

The lesson took me a year to learn: multi-unit operations are a consistency business, not a hustle business. The heroics that work for one shop break at three. The energy that founded a great single-unit can't scale to 7 — energy doesn't transfer through documentation.

What fixes it isn't more management. It's three system primitives.

Prompts. The bot asks. The manager doesn't have to remember the morning check-in list — the system prompts it. Memory load drops to zero.

Checklists. The closing checklist is the same in every shop, every day. Tick boxes. Timestamps. If the checklist is shorter at one shop, the system flags it — not because shorter is wrong, but because divergence is a signal.

Exception routing. Equipment issues go to the vendor channel. Supply issues to the ops channel. Staffing issues to the scheduler. Automatic. The manager doesn't decide who to call — the system already routed it.

Consistency is the product. Variance is the cost. The system holds the line when the human can't.

That's the part of scaling deskless ops that nobody on LinkedIn writes about.

#smbtwitter #verticalsaas #multiunitoperator #deskless #searchfund #etaforum

Production notes

• Shoot location: back-office desk + supplementary shop b-roll. The lesson is operator-philosophy — feels right shot from the back office.
• Wardrobe: plain dark tee or button-down. Slightly more composed than Days 13/17 — LinkedIn-first content.
• Audio: lav mic. The "consistency is the product" close is the LinkedIn quote — record twice, pick cleaner.
• Edit: the variance-metrics frame at 20-30s is the share frame. Numbers must be readable on mobile.
• Privacy: shop identifiers blurred in all variance metrics. Manager names absent. Real numbers if possible (Jack's actual variance across shops); else use representative ranges.
• Carousel template: match Days 11, 15, 20. Same dark bg, accent color, font. This is the "operating discipline" series consolidated. Save the template — Month 2 will reference all four.
• LinkedIn timing: 7:45am CT. The 30-day push's highest-stakes operator-philosophy post on LinkedIn. Hold the slot.
• Retention bet: the "energy doesn't transfer through documentation" line in LinkedIn is the LP-and-operator share quote. Highlight as on-screen text in TikTok edit.

Voice check

• Real numbers (20+ employees, 7 shops, 14 vs 9 items, 3% vs 11% waste, 24% vs 29% labor, ±$8 vs ±$31 cash variance, 1 year learning curve)
• No banned phrases ("hustle culture", "boss mode", "grind")
• Operator POV — first-person, no "you should" (LinkedIn uses "the heroics that work for 1 shop break at 3" as observational, not advisory)
• One quotable per surface — TikTok ("consistency is the product. the system holds the line"), IG ("the system holds the line when the human can't"), LinkedIn (same + "energy doesn't transfer through documentation")
• Tension before payoff (one shop hides → seven shops expose → consistency is the product, not the dashboard)
• No motivational close
• One central idea: multi-unit ops is a consistency business

Day 30 — Thu Jun 18 — Month 1 Recap + Next Series

Pillar: all three Primary: TikTok 7:30pm CT Mirror: IG Reel next morning LinkedIn: recap post Friday morning 8:30am CT only if month-1 metrics are clean Hook: "30 days of receipts. here's what got real operators to dm me."

B-roll shot list

1. 0-3s — Hook frame: talking head, on-screen text "30 days of receipts. here's what landed."
2. 3-12s — Top post recap: screen-record of the top-performing post's first frame, with metrics overlaid (real numbers: views, retention at 30s, saves, comments from operators).
3. 12-22s — Top operator question: on-screen text of the question, attribution scrubbed. Hold 4-5s.
4. 22-32s — Most saved topic: quick screen-record of the carousel or post most operators saved.
5. 32-42s — One surprise: talking head, on-screen text reading the surprise (one sentence).
6. 42-55s — What continues: quick visual of the Receipts Friday template, then a teaser of the chosen series — could be a build-vs-buy graphic, a forecast graphic, or a wheel triangle.
7. 55-65s — Same lesson beat: talking head, on-screen text "the system holds the cadence. that's the same lesson 7 shops taught me."
8. 65-70s — End frame: text card "month 2 — same pillars. deeper, not wider." Black background.

TikTok caption + hashtags

30 days of publishing receipts. top post, top operator question, most saved, one surprise, what continues. month 2 goes deeper not wider. cadence is the product.

#receiptsfriday #smbops #multiunitoperator #operatorlife #donutshop #wheelstrategy #buildlog

Instagram caption + hashtags

30 days of publishing receipts. the recap.

top post: [TBD day-of — real top performer by retention + operator comments].

top operator question: [TBD day-of — the question that came up multiple times].

most saved topic: [TBD day-of — probably operating discipline].

one surprise: [TBD day-of — a post that didn't fit my prediction].

what continues: receipts friday becomes the month 2 anchor. one recurring series doubles down based on what real operators engaged with.

30 days is enough to know the lane. month 2 goes deeper, not wider. same three pillars. one chosen series. the cadence holds because the system holds it — not motivation, not heroics. exactly the lesson the operating side teaches every day.

#receiptsfriday #smbops #multiunitoperator #operatorlife #donutshop #wheelstrategy #buildlog

LinkedIn (~250 words, proper case, Friday next-morning post if metrics are clean)

30 days of publishing operating receipts. The recap.

Top post by retention: [TBD — real result]. Top operator question across the month: [TBD — real result]. Most-saved topic: [TBD — likely operating discipline]. One surprise: [TBD — honest read].

What I'm carrying forward into Month 2:

Same three pillars — the rollup (7 donut shops, multi-unit operations), selling premium (wheel strategy, monthly cashflow), Golden Ops (the internal tool stack I built solo).

Same Receipts Friday template — three numbers per week, one from each pillar. The series only works if the operating week actually produces three real numbers. That's the accountability mechanism the content creates.

One series goes deeper: [TBD based on Day 19 analytics — likely either build-vs-buy or operating discipline].

What I learned about publishing as an operator: the cadence is the product, not the individual post. The hard 30-day push proved I can hold the cadence under normal operating chaos — hood fires, manager exits, wheel positions getting tested. The system held the cadence because the system held the calendar.

Same lesson the operating side teaches every day at 20+ employees and 7 shops — consistency is the product. The heroics that work for one post break at thirty. Prompts, templates, batch days. The publishing system mirrors the operating system.

Month 2 starts Monday. Deeper, not wider.

#smbtwitter #verticalsaas #multiunitoperator #searchfund #etaforum

Production notes

• Day 30 timing: post the TikTok at 7:30pm CT Thursday. LinkedIn waits until Friday 8:30am CT for the operator-Friday-morning window.
• Number capture deadline: Wednesday evening (Day 29 close). Pull all analytics for Days 1-29. The Day 30 post itself is one of the dataset's posts — its metrics belong to Month 2 retrospective.
• Shoot location: back-office desk. Day 30 should feel like a deliberate close — same setup as the origin post (Day 1) for visual symmetry.
• Wardrobe: match Day 1's energy — operator close-up, plain dark wardrobe. Symmetry beats variety on the recap.
• Audio: lav mic. The "the system holds the cadence" close is the share line — record twice, pick cleaner.
• Edit: the recap segments are screen-record dominant. Each gets 4-5s. Don't quick-cut.
• Privacy: any operator comments shown in screenshots have names scrubbed. Real operators dm'd — protect them.
• LinkedIn gate: Friday morning post is optional. If Day 30 metrics by Friday 7am CT show clean retention and operator comments, ship the LinkedIn. If the metrics are mid, hold and ship a Day 31 (Monday) post instead.
• Month 2 setup: at end of Day 30 production, write Month 2 calendar based on Day 19 series decision + Day 30 retro. This is the bridge — do not skip.
• Retention bet: the "the system held the cadence because the system held the calendar" line at ~58s is the meta share line. Hold a beat after it. Operators reshare meta-discipline posts.

Voice check

• Real numbers (30 days, 3 pillars, 7 shops, 20+ employees, Receipts Friday cadence)
• No banned phrases ("crushed it", "lessons learned" if generic, "we did it" energy)
• Operator POV — first-person, no "you should"
• Single CTA per surface — implicit Month 2 continuation, no "follow for more"
• Tension before payoff (30 days done → real operator engagement → cadence is the product, not the individual post)
• One quotable per surface — TikTok ("cadence is the product"), IG ("the system holds the cadence because the system holds the calendar"), LinkedIn ("the publishing system mirrors the operating system")
• No motivational close — close on operating-philosophy parallel (publishing system = operating system)

Batch 3 production summary

Days covered: 21-30 (Tue Jun 9 → Thu Jun 18) Shoot days: 21, 22, 23, 24, 27, 28, 29, 30 (talking head + screen-record dominant) Carousel days: 29 (Operator Consistency — matching dark template from Days 11, 15, 20) Light/work days: 25 (Sat), 26 (Sun) — minimal public post, Q&A reserve recording Wheel-series triangle closed: Day 16 (framework) + Day 21 (mistake) + Day 28 (results) Build-vs-buy series anchored: Day 3 → Day 13 → Day 27 (Why Not Better SaaS?) Operating discipline carousels: Days 11, 15, 20, 29 → unified template family Month 2 transition: Day 30 recap + Month 2 calendar drafted

Cross-batch flag resolution required before publishing:

1. SaaS replacement canonicalized — use $60K/yr throughout. Older higher estimates were incorrect.
2. Employee count canonicalized — use 20+ employees throughout. Older inflated references were incorrect.
3. Day 21 trade mistake real details — 2022 tech stock placeholder used. Optional to swap to a real trade with redacted ticker. If using real, redact ticker name fully.
4. Day 22 LP audience guard — Investor reporting post should not mention real LP names, real distribution amounts, or real entity names. Sensitivity check before publishing.
5. Day 24 + Day 28 + Day 30 — placeholder numbers throughout. Real numbers must be captured day-of recording or Thursday-night-before for Receipts Friday and monthly snapshots.
6. Day 27 evaluation specifics — said "spent two months in 2024 evaluating 4 platforms." Verify accuracy before publishing — if it was 1 month or 3 platforms, correct the script.
7. Day 28 LinkedIn gate decision — post only if monthly premium reads as "real, repeatable, not flashy." Skip if numbers feel like a flex.
8. Day 30 LinkedIn gate decision — post Friday morning recap only if Day 30 retention and operator-comment counts by Friday 7am CT are clean. Otherwise, push to Monday.
9. Day 19 series decision — which series doubles down for Month 2 (Receipts Friday is the default anchor; secondary series chosen from analytics: build-vs-buy, variance Wednesday, wheel triangle, or operating discipline carousels). Required input from Day 19 analytics review.
10. Day 17 voice memo casting — need a friend voice for the simulated manager memo. Recording should not be Jack's voice or AI synthesis.

No deviations from the calendar topic spine across all 30 days. Full 30-day batch ready for production.

Jack Yen — Brand Voice Spec (FINAL)

Purpose: This is the standalone reference any drafter (agent or human) reads before writing a single word for Jack. If a post can't survive this checklist, it doesn't ship.

1. Brand Voice Statement (North Star)

Jack Yen writes like an operator who already did the thing and then built the control system underneath it. Not aspirational, not motivational — load-bearing. Every sentence carries weight from real receipts: 7 Golden Glaze donut shops in DFW, a planned $1M raise + centralized kitchen, 11 STR/MTR units across Hawaii/DFW/Tampa, 20+ employees across the shops, a six-figure tech career walked away from in October 2024 with severance and 12 months of runway already covered by cashflow. The voice is quiet, specific, and slightly tired — like someone who built Golden Ops, Cash Control, Sales Report, KPI tracking, FlexStay Ops, and investor infrastructure because the third-party tools did not fit. No hustle theatrics, no identity claims, no second-person pep talk. The artifact does the talking. Jack just narrates.

2. The 7 Voice Rules

1. Specificity floor. Numbers, dates, dollar amounts, unit counts, time windows. "7 shops," "11 units," "3 weeks," "October 2024," "$60K/yr," "4am floor." If a sentence could belong to any operator, rewrite it until it can only belong to Jack.

2. Operator POV only. Write from inside the business, not above it. "I had 20+ employees across shops and no scheduling tool that worked deskless" — not "Here's how to manage frontline teams."

3. No second-person motivation. No "you should," no "you need to," no "imagine if you." Jack reports what happened to him. Readers extract their own lesson.

4. Show the control loop. When mentioning the custom software, name the operating problem, the old workflow, the module built, and the receipt. Cost replaced matters, but workflow ownership is the deeper point. Generic "I built tools" is a violation.

5. Tension before payoff. Lead with the constraint, the failure, or the awkward truth. Resolution comes second, smaller, and only if earned. The 18-months-in number is a tension marker, not a victory lap.

6. No identity claims. Jack does not call himself an "AI builder," "founder," "solopreneur," "indie hacker," "vibe coder," or any label. The artifacts label him. He just describes what he did and what it replaced.

7. One CTA max, earned only. Most posts have zero CTA. If there is one, it's at the end, one line, and the post above it has already paid for the attention. No "follow for more," no "DM me," no "what do you think?"

3. Cross-Platform Consistency Map

What stays the same everywhere:

• Specificity floor (numbers always present)
• Operator POV
• No identity claims
• Tension-first structure
• No motivational second-person

What adapts per platform:

4. Platform Bios — FINAL VERSIONS

Instagram (lowercase, ≤150 chars)

7 donut shops. 11 rentals. $1m kitchen plan. building the operator os behind both. dfw.

(91 chars)

TikTok (lowercase, ≤80 chars)

7 donut shops. 11 rentals. building the operator os behind both.

(63 chars)

LinkedIn Headline (proper case, ≤220 chars)

Operator — Golden Glaze Donuts (7 Shops, DFW, $1M Kitchen Plan) + FlexStay Housing (11 STR/MTR Units) | Left a 13-Year Tech Career in October 2024 | Building the Internal Operating System Behind Both

(184 chars)

5. Casing Standard

• Instagram & TikTok: lowercase by default. Deliberate. Signals operator-not-marketer. The artifacts are loud; the voice is quiet.
• LinkedIn: proper case. Audience expects business norms. Lowercase on LinkedIn reads as performance, not restraint.
• Break the rule only when:
  • A specific proper noun requires it (Golden Glaze, DFW, Hawaii, Tampa, Discord)
  • A dollar figure or unit count is the load-bearing word and needs visual emphasis ($60K, 7, 11, 3 weeks)
  • Never break casing for hype. "REAL TALK" or "HUGE NEWS" is an instant kill.

6. Red Flag Phrases — Auto-Rewrite List

If a draft contains any of these, rewrite before shipping:

1. "I use AI to..." → name what was built, name what it replaced, name the cost
2. "You should..." / "You need to..." → switch to first-person report
3. "Imagine if..." → delete; replace with what actually happened
4. "AI builder" / "vibe coder" / "indie hacker" → delete the label, describe the artifact
5. "Hustle" / "grind" / "rise and grind" → delete; the 4am floor speaks for itself
6. "Passive income" → delete; STRs at 11 units are not passive
7. "Quit my 9-5" → use "left a 13-year tech career in October 2024"
8. "Building in public" → delete the label, just describe the build
9. "Game-changer" / "disrupting" / "revolutionary" → delete
10. "Follow for more" / "DM me" / "link in bio" → delete unless earned
11. "Anyone can do this" → false and off-voice; delete
12. "Living the dream" → delete; replace with the specific tradeoff (no kids, DFW, 4am)
13. "Side hustle" → these are not side hustles; they are the business
14. "Financial freedom" → delete; use cashflow numbers or runway months instead
15. "Let that sink in" → delete on sight

7. Earned vs Borrowed Topics Test

Jack rides (earned):

• Running 7 donut shops with a deskless workforce of 20+
• Golden Glaze's planned $1M raise and centralized kitchen, framed through operating controls, use-of-funds, production capacity, and investor-readiness
• The October 2024 layoff math (severance + 5 cashflowing STRs + 12 months savings)
• Insurance housing and displaced families as STR/MTR customers
• Building Golden Ops, Cash Control, Sales Report, KPI/ReviewIQ, FlexStay Ops, and investor infrastructure
• Replacing $60K/yr in third-party software
• 13 years managing engineers on Slack/Teams vs. now managing kitchen staff on the floor
• The current build: inventory management + guest messaging + tighter cross-business dashboards
• DFW operator life, GP/LP fund mechanics, the 18-months-in honesty
• Selling premium/the wheel only as personal capital context when Jack explicitly wants it; it is not an operating-business pillar.

Jack skips (borrowed):

• General AI commentary, model releases, prompt engineering tips
• Startup funding news, YC, VC takes
• Crypto, day trading, dropshipping, Amazon FBA
• Productivity systems, morning routines, dopamine detox
• Politics, hot takes on other founders
• "How to start a business with $0" content
• Generic real estate investing advice (he runs a specific niche: insurance housing)
• Anything that requires claiming an identity he hasn't earned in that specific lane

The test: Can Jack point to a receipt from the last 18 months that gives him standing to say this? If no — skip it.

8. Voice Examples — Bad → Better

Example 1

• Bad: "I use AI to run 7 donut shops from my phone."
• Better: "I bought 7 donut shops in DFW. The ops software for a deskless 4am workforce didn't fit. Built the first version in 3 weeks. Now the system runs check-ins, cash control, inventory, sales reports, and investor updates."

Example 2

• Bad: "Quit my 9-5 to chase my dreams. You can too!"
• Better: "October 2024. Took the severance. Walked from 13 years in tech. 5 STRs were already cashflowing. 12 months of runway in the bank. It wasn't brave — the math was done two years earlier."

Example 3

• Bad: "Building in public as an AI-powered solopreneur."
• Better: "Currently building inventory management and guest messaging. Same pattern as cash control and FlexStay dispatch: intake, status, proof, exception. The dashboard is the easy part."

Example 4

• Bad: "Managing employees is hard. Here's what I learned."
• Better: "13 years managing engineers on Slack. Then 20+ employees across donut shops, no laptops, no Slack. The hardest part of the transition wasn't the hours. It was that none of the tools I knew existed for this workforce."

Example 5

• Bad: "Real estate has been a game-changer for my financial freedom journey."
• Better: "11 STR/MTR units. Hawaii, DFW, Tampa. Most of the bookings are insurance housing — families displaced after a fire, a flood, a contractor who blew a deadline. Not vacation rentals. Not passive."

Example 6

• Bad: "Excited to share I'm building the next big thing in hospitality tech!"
• Better: "18 months in. Built the Discord ops console, cash control, sales reporting, KPI tracking, investor updates, FlexStay dispatch. Now on inventory + guest messaging. Not selling it. Just running my own businesses on it."

Example 7

• Bad: "AI is going to change everything. You need to learn it now."
• Better: "I'm not an engineer who became an operator. I'm an operator who couldn't find software that fit, so I wrote the control layer myself. The AI part is the cheapest input I have."

Example 8

• Bad: "Follow my journey as I scale to 8 figures!"
• Better: "7 donut shops. 11 rentals. 18 months in. DFW. No kids. That's the whole org chart."

Daily checklist before any post ships:

• At least one receipt (number, date, dollar, unit count)?
• First-person, no "you should"?
• No identity label?
• If software is mentioned — named the operating problem, workflow, module, and receipt?
• Tension before payoff?
• Casing correct for the platform?
• Zero red-flag phrases?
• CTA earned (or absent)?

If any box is unchecked, the post is not ready.

Lead Magnets + Newsletter System

Principle

Standing offer beats comment-keyword loops. One link in each bio → newsletter landing page → bi-weekly digest. No "DM me X" friction.

The reason this works for Jack specifically: his content is operator-receipts. People who care about operator-receipts want more receipts, not a free PDF. The newsletter is the receipts engine, and the core receipt is now the Operator OS being built behind real businesses.

The newsletter

Title: "Receipts from the Back Office"

Cadence: bi-weekly (every other Wednesday, 6am CT)

Length: 600-900 words per issue

Structure per issue (consistent template):

1. One decision I made or am making (with the math behind it)
2. One number from the businesses (specific, real, surprising)
3. One mistake or thing I got wrong (with what I changed)
4. What I'm shipping next (Operator OS build log / 30-second status update)

That's it. No long essays. No "5 tips" content. Just the format.

Platform recommendation: Beehiiv

• Why: built for operator/SMB audience, no political baggage, referral program works, deliverability is best-in-class right now
• Alternatives ranked: Ghost (good but more setup), ConvertKit (over-priced for the use case), Substack (audience expectation is essays, doesn't fit the format)

Launch issue (Issue #1) outline:

Decision: Why I built the cash-control workflow instead of buying another dashboard Number: The variance / missed-check-in / turnover signal that forced the module Mistake: I built the wrong dashboard before I built the control loop Shipping next: The next Operator OS module — inventory, guest messaging, or investor reporting

First 5 issues planned:

1. The planned-exit math (severance + STR runway + savings — full math)
2. The Operator OS stack — every module, what it replaced, and what still stays bought
3. The deskless workforce problem — why the front end had to be Discord
4. Two businesses, same control loop — shops vs. FlexStay operations
5. Sub-scale GP/LP mechanics — what a 7-shop fund actually needs from reporting

Newsletter landing page

One page. One form. One promise.

URL recommendation: notes.jackyen.com (subdomain) or jackyen.com/notes

Above the fold:

Receipts from the Back Office

Bi-weekly. One decision. One number. One mistake. From running 7 donut shops and 11 short-term rentals.

[Email field] [Subscribe button]

No spam. No upsells. Built by an operator who codes.

Below the fold (optional):

• 3 sample issue excerpts
• The newsletter archive (once 3+ issues exist)
• Link back to jackyen.com main site

Build effort: 2-3 hours. Do it before Day 1 ships.

Lead magnets (one per audience segment)

The newsletter is the conversion home. Lead magnets are the anchor that gets people to subscribe.

Lead magnet 1 — Operator OS audience (IG/TikTok primary)

Title: "The Operator OS Stack"

Format: Notion page or lightweight PDF

Contents:

• Golden Ops module map
• Cash Control module
• Sales Report module
• KPI / ReviewIQ module
• FlexStay Ops module
• Investor reporting module
• What stays bought and why
• What data must be redacted before showing publicly

Why it works: this is the artifact only Jack can show. It is not "AI tools I use." It is the actual operating system underneath two businesses.

Lead magnet 2 — SMB operator metrics audience

Title: "The 5 metrics I check every morning across 7 shops"

Format: Notion page (publicly viewable, but you have to sign up to access via the standing offer)

Contents:

• The 5 metrics (with definitions)
• What threshold triggers an alert
• How I built each one
• Screenshot of the actual morning dashboard view

Why it works: operators want to know what other operators measure. Specific. Tactical. Defensible — most creators publish "10 metrics every business owner should track" generic lists. This one is what Jack actually does at 6am.

Lead magnet 3 — LinkedIn operator/investor audience

Title: "The Ex-Tech Operator's Internal Tools Stack"

Format: 12-page PDF

Contents:

• The 6 internal tools I built and what each replaced
• The cost of the SaaS I would have bought instead ($60K/yr total)
• Build time per tool (3-week initial sprint + ongoing)
• What I'd build differently if starting over
• The 3 categories I'm still buying (and why)

Why it works: LinkedIn audience reads the artifact. PDFs work here because the format itself signals "professional / saveable / shareable." Not a PDF for IG.

Lead magnet 4 — STR audience (Month 2 only — not Month 1)

Title: "STR Portfolio Dashboard — what I track across 11 units in 3 markets"

Format: Notion page

Contents:

• Per-unit KPIs
• Cross-market view
• Anomaly rules
• The PM stack I'm using vs. building

Why it works: multi-market STR operators are searching for exactly this. Almost no public examples exist of a 3-market portfolio dashboard.

Standing offer rules

Where the offer appears:

• ✅ Bio (every platform, one link)
• ✅ Last slide of carousels — handle + one line, never CTA bait
• ✅ Pinned comment on TikTok — single sentence + link
• ✅ Featured section on LinkedIn — newsletter signup + lead magnet 2
• ✅ Stories link sticker (IG) — once a week, Thursday "build-in-public" story only

Where it does NOT appear:

• ❌ Comment CTAs ("comment X and I'll send Y")
• ❌ Every post caption
• ❌ DM auto-responses
• ❌ Any post that doesn't earn it

The earn rule: include the bio-link line in a caption ONLY when the post itself surfaces a specific artifact you can reference (e.g., "the dashboard I'm referring to — full breakdown in this issue: link in bio"). Otherwise leave it off.

Conversion targets — Month 1

• Newsletter signups: 500+ (across all sources)
• Issue #1 open rate: 45%+ (small list, high-intent — expect this)
• Operator OS Stack downloads: 300+
• 5-metric dashboard downloads: 200+
• LinkedIn internal tools PDF downloads: 200+

Don't bait. Don't run paid ads in Month 1. Let the standing offer compound naturally.

Conversion targets — Month 3 (after 6 issues)

• List size: 2,000+
• Open rate sustained: 40%+
• Issue-to-issue retention: 80%+ (not unsubscribing)
• Inbound DMs from real operators referencing newsletter content: 10/week

If the list is growing but the inbound DM signal is flat, the newsletter content is wrong. Recalibrate toward module-level receipts and workflow screenshots.

Competitor / Peer Scan — Reference

Purpose: know who Jack is vs. who he isn't. Use this to position content + identify what to NOT copy.

The lane Jack uniquely owns

"The ex-software engineer building the operating system for real-world businesses he owns."

No one else credibly claims all four:

1. Real SWE chops (13 years, 6 companies)
2. A 20+ person blue-collar / deskless operation he actually runs (not just invests in)
3. A multi-market real estate portfolio (not concentrated)
4. He builds the internal software himself: Golden Ops, Cash Control, Sales Report, KPI/ReviewIQ, FlexStay Ops, and investor infrastructure

Peer / competitor map

Codie Sanchez — Contrarian Thinking

• Lane: boring businesses / acquisition content
• Audience size: ~8M across platforms
• Steal: cash-flow language, naming verticals in hooks ("laundromats, car washes")
• Don't copy: mass-market boring-business guru positioning; the course funnel; drift toward financial-freedom framing
• Where Jack wins: he RUNS the operation. Codie talks about the category from the outside.

Nick Huber — @sweatystartup

• Lane: self-storage + service biz operator on X
• Steal: thread structure (in-the-weeds ops + one strong opinion); raised $7M off Twitter
• Don't copy: edgelord/contrarian-takes flywheel — Jack's voice is receipts, not provocation
• Where Jack wins: Nick doesn't have SWE chops or AI-internal-tool content. The build side is Jack's.

Pieter Levels — @levelsio

• Lane: solo builder, ships SaaS in public on X
• Steal: public revenue counters, public dashboards, "I built X in N hours" format
• Don't copy: the vibe-coded SaaS spray — Jack ships internal tools for his own ops, not public products
• Where Jack wins: Levels has no W-2 payroll, no deskless workforce, no insurance housing portfolio. Different stakes.

Greg Isenberg — Late Checkout

• Lane: AI startup ideas, idea-guy content on YT/X
• Steal: cohesive "playbook" framing, tight YT thumbnails
• Don't copy: idea-guy / list-of-startup-ideas content — Jack has the operator side Greg doesn't
• Where Jack wins: Jack ships. Greg pitches ideas. Operator-receipts > idea posts.

Sieva Kozinsky — Enduring Ventures

• Lane: SMB roll-ups, holdco content on LinkedIn
• Steal: LinkedIn long-form with org-chart receipts, hiring posts
• Don't copy: CEO-of-holdco voice — Jack is closer to the floor
• Where Jack wins: Sieva manages portfolio CEOs. Jack manages shifts. Different altitude.

Brent Beshore — Permanent Equity

• Lane: SMB PE thoughtful operator on LinkedIn / longform
• Steal: long-arc essays on culture and operating reality
• Don't copy: investor frame — Jack is operator+builder, a sharper niche
• Where Jack wins: Brent invests. Jack builds the dashboards Brent's portcos would buy.

Khe Hy — RadReads

• Lane: corporate escape / ex-finance creator
• Steal: newsletter+cohort funnel mechanics
• Don't copy: "Quit your job" content — exactly the language Jack's voice rules forbid
• Where Jack wins: Khe sells the escape. Jack shows the build after the escape.

AI dev creators (Theo Browne / Levi Notik / various)

• Lane: AI dev tooling content on YT/X
• Steal: live-build, "watch me ship" cadence
• Don't copy: they build for devs. Jack builds for donut shop GMs.
• Where Jack wins: B2B-to-blue-collar end-user audience is unique.

The hole in this map

Nobody owns "ex-SWE building the internal operating system for physical businesses he owns."

• Codie owns acquisition category content (no operator skin)
• Nick owns service-biz ops (no SWE/AI chops)
• Levels owns solo SaaS (no W-2 payroll)
• Greg owns ideas (no shipping)
• Sieva/Brent own holdco/PE altitude (no floor work)
• Khe owns the escape (no build-after)
• AI devs own dev tools (no blue-collar end user)

Jack sits between all of them. The receipts (7 shops, 11 rentals, planned $1M Golden Glaze raise + centralized kitchen, $60K/yr SaaS replaced, Golden Ops, Cash Control, Sales Report, KPI/ReviewIQ, FlexStay Ops, GP/LP fund) make the lane defensible — none of these creators can credibly claim all of those.

Emerging trends Jack can ride (only the on-voice ones)

1. Operator OS receipts — concrete teardowns of a module, the old workflow, the new workflow, and the operating signal it now catches.
2. Anti-vibe-coding backlash — counter-current to Levels-style spray. "I ship code that touches payroll, it has to work." Operator-stakes coding is an unfilled lane.
3. AI-for-deskless / blue-collar workers — almost all AI-for-SMB content targets agencies/knowledge workers. Donut shop floor + 20 hourly employees is the underrepresented end.
4. Control-loop-as-content — check-in screenshots, variance reports, inventory alerts, turnover boards, vendor dispatch threads. The "show your workflow" format reads as proof, not flex.
5. Holdco / multi-unit operator content on LinkedIn — Sieva, Brent, etc. The 7-shop + 11-unit multi-asset story is a LinkedIn-native hook the IG-first creators undershoot.

Content gaps Jack should own

1. "The Operator OS module I shipped this week, and the workflow it replaced." Weekly changelog format. Nobody is doing build-in-public for an offline business they actually run.
2. Build-vs-buy teardowns with real invoices and real constraints — "Here's what I built, here's what I kept bought, here's why being wrong would be expensive." Receipt-mode anti-SaaS.
3. AI for the 20+ employee shop floor — scheduling, shift-swap, daily ops reporting from a non-knowledge-worker workforce. Codie talks acquisition; nobody talks operating-system.
4. "What 13 years in tech actually teaches you about running donuts (and what it doesn't)" — honest crossover content. Most ex-corporate creators oversell tech transferability; Jack can be the honest one.
5. The cash-variance / inventory-alert genre — boring operator metrics as content primitives. Owns a vocabulary (labor %, variance, on-hand, baseline anomaly) that the IG creator crowd literally doesn't speak.

Sources (peer references)

• Codie Sanchez — Main Street Millionaire
• Nick Huber on X (@sweatystartup)
• Greg Isenberg on Pieter Levels' solo AI builds
• How Codie Sanchez turned 4 properties into $17.7M