⌂ Index1 · Master Proof2 · SIGNAL Hub3 · Setup4 · Content Library5 · Launch Sched.6 · Analysis7 · Readiness Audit8 · Playbook9 · Contingency
🔒 Proprietary & Confidential — Internal Only — pre-launch playbook, nothing here is live yet

Companion to all seven other documents

Operating Playbook

How this gets recognized on sight, what actually posts every day, the exact sequence to flip it live, and how we'll know it's proven enough to clone. The document that turns strategy into a program you can run.

← Back to the Index

Contents

  1. Brand recognition system
  2. The content roster — every form, one table
  3. Storyboards for the new formats
  4. The daily rhythm — steady state
  5. Plan of action — path to live
  6. Monitoring — what "working" looks like
  7. Clone-readiness criteria

01

Brand recognition system

Voice and vocabulary are already defined in the SIGNAL Hub. This is the layer underneath that: the specific, repeatable mechanics that make someone recognize a Vivere post before they've read a word of it — on any platform, scrolling fast, sound off.

Color tells you what franchise you're looking at

Every card family already has a distinct gradient. Formalizing it as a rule: the color is the label. A viewer who's seen three Signal Check cards will recognize the fourth by its navy-and-amber palette alone, before reading the headline.

Before/After
navy #162340
The Proof
indigo #3a2f6b
The Tip
teal #0f5b52
The Wink
violet #5a2f6b
Signal Check
navy/amber #4a3410
County Report
gold #e8b04b — new

County Report is proposed here for the first time: gold, matching Master Proof's own hero treatment for "the flagship," so the investigation reads as the most serious, highest-stakes content in the library the instant it appears — distinct from SIGNAL's warmer, mascot-fronted palette.

Beam's pose is a semantic signal, not a random pick

PoseMeansUse it for
Standby"Always running, nothing urgent"Evergreen posts, Epilogue-era content, reposted best-performers
Broadcasting"Big reveal, full send"Launches, Act IV content, the County Report drop, milestone announcements
Building"Work in progress, behind the scenes"Act III prep content, "Build With Me," process/how-it's-made posts
Icon"This is us" — identity onlyAvatars, favicons, never used as a content illustration itself
The rule this implies: if a post uses the Broadcasting pose, it needs to actually be a big-send moment. Using the full-send pose for routine content burns the signal — the whole point of a semantic system is that it stops meaning something the moment it's used carelessly.

Verbal anchors — say the same things on purpose

Consistency checklist (already scoped in Setup Guide, restated as a gate)

Same handle everywhere: @vivereweb, same display name, same avatar (Beam icon pose)
Same bio core line on every platform (Setup Guide's paste-ready copy)
Every video ends on the same sign-off line, spoken or captioned
Every card uses its franchise's assigned color — no off-palette one-offs
County Report content never borrows Beam's mascot warmth — gold and serious, on purpose (see the Readiness Audit's brand-architecture section)

02

The content roster — every form, one table

Everything that exists or has been proposed, in one place, so "all forms of content" has an actual inventory instead of being scattered across the rest of this package.

FormFranchiseStatusCadence
Static cardsBefore/After, The Proof, The Tip, The Wink1 example each, built2–3×/week
Trivia cardsSignal Check3 Q/A pairs builtWeekly pair (Wed/Thu)
ShortsSite Teardown, SIGNAL in Action, You Own ItScripted, not filmed1×/week once filming starts
Long-form"Build With Me"Concept onlyFeeds shorts; own cadence TBD
InvestigationCounty Report (new)Proposed, unscopedChapters/findings, monthly; full report quarterly
NewsletterFree web-dev tips list (new)ProposedWeekly, Monday AM
TestimonialsClient spotlight (new)Proposed, format belowBi-weekly, as clients agree
Interactive toolInstant site audit (new)ProposedOne build; content is ongoing "results" posts
ReferralAsk + reward (new)Proposed, structure belowEmbedded monthly, not a separate post type
Framework courseLonger-term productProposed, out of daily scopeNot part of this playbook's cadence

03

Storyboards for the new formats

The three existing shorts already have full shot lists in the SIGNAL Hub — not repeated here. These are the formats the Readiness Audit proposed that don't have a shape yet.

County Report — the investigation, on camera

BeatWhat's on screen
Hook (0–3s)The single most surprising number, stated cold — e.g. "Half the businesses in this county don't show up on Google. Here's the proof." Gold on-screen text, no mascot.
The method (3–15s)Screen-recorded proof of the actual audit process — real searches, real sites loading slow, real HTTPS warnings. This is the "sourcing standard" made visible, which doubles as the credibility pitch.
The finding (15–40s)The data, presented plainly — a simple on-screen chart or count, voiceover explaining what it means for a local business owner specifically.
The closeNo hard sell. "Full report and methodology at the link — including whether your business is on the list." Sign-off line, gold end card.
Deliberately mascot-free per the recognition rules above — this is where SOL-grade seriousness has to hold, since it's simultaneously the flagship pillar investigation and a business-development asset.

Video testimonial — the repeatable interview

Four questions, always the same order, 60–90 seconds total, shot in the client's own space (not a studio — the real business is the credibility):

  1. "What was the site like before?" (let them describe the pain in their own words)
  2. "What actually changed?" (the concrete before/after — pairs naturally with a Before/After card cut in)
  3. "Did it change anything for the business?" (results, even soft ones — more calls, better reviews, pride in sending the link)
  4. "What would you tell someone who's on the fence?" (the natural, unscripted pull-quote — this is usually the clip that gets used as the hook)

Newsletter — structure, not just cadence

Three fixed sections every issue, so it's fast to produce and fast to read: one tip (the kind of thing already scripted for shorts, in text form), one number (a stat or finding, increasingly drawn from the County Report as it develops), one link (this week's short or card, driving back to the platform where the comments/engagement live).

Interactive tool — the "results" short

Not a demo reel. Screen-record a real local business's actual (anonymized or permissioned) audit result, with Beam in the Building pose reacting to the score as it loads — this is the one place the tool and the mascot meet, since the tool itself is serious/utilitarian but the reveal moment is where personality belongs.

04

The daily rhythm — steady state

Launch Schedule covers the first 4 weeks of getting started. This is what continues indefinitely after that — a repeatable weekly template, not a finite calendar. Same shape, every week, so producing it stops requiring a plan and starts requiring only execution.

Monday
Newsletter goes out (AM) + a Tip or Proof card (all tier-1 platforms, late morning). The week opens with the trust-builders.
Tuesday
The week's video — rotate: a Short, a testimonial, or a County Report clip once that's producing content. The heaviest lift of the week, so it gets its own day.
Wednesday
Signal Check — question. Comment-bait, posted evening for engagement while people are off work.
Thursday
Signal Check — answer. Same evening slot; reply to every guess from Wednesday before posting the reveal.
Friday
Light close: The Wink, or a testimonial spotlight, or — once it exists — a referral ask folded into the caption. Morning post, low-pressure tone into the weekend.
Saturday
Re-promote whichever asset performed best that week (manual until PULSE automates it). Pinterest gets an evergreen pin here too — lowest-effort, longest-tail platform.
Sunday
No post. Batch-prep day: film/edit next week's video, write the next newsletter, queue the week in Blotato. Protecting this day is what keeps the rhythm sustainable past week 4.
Overlays, not separate days: County Report chapters (monthly) and testimonial spotlights (bi-weekly) slot into the existing Tuesday video slot when they're ready — they don't add posting volume, they replace a Short that week. Daily posting means something posts every day, not that every content type posts every week.

05

Plan of action — path to live

Everything above is the steady-state design. This is the specific, ordered sequence to actually get there from today — synthesized from the Readiness Audit's punch list, reordered around one question: what has to be true before the switch flips to "live and posting on real accounts"?

Before anything posts publicly

  • Decide one brand or two (Readiness Audit §2)
  • Write the SOL sourcing/correction standard
  • Call an insurance broker re: media liability
  • Claim @vivereweb on all 8 platforms (Setup Guide)
  • Set up the 4 tier-1 accounts with paste-ready bios

Before the first scheduled week

  • Batch-film the 3 existing shorts
  • Build 2–4 more variations per card family
  • Generate Story/OG crops; export the animated Beam loop
  • Wire the 4 tier-1 channels into the existing n8n cross-post config

Before the daily rhythm goes fully automated

  • Load the steady-state week into Blotato as a repeating template
  • Set up UTM tracking + a lead-source field on the assessment form
  • Scope the County Report's first checkable question
  • Draft the newsletter's first 4 issues ahead, so week one isn't a scramble

Can wait until there's real traction

  • Interactive audit tool build
  • Referral program structure
  • Sponsor kit real numbers (Launch Schedule's draft stays a template)
  • Framework course/licensing — explicitly longer-term
The actual go/no-go: the first quadrant is the real gate. Everything in "before the first scheduled week" and beyond can happen in parallel with early posting — but publishing before the brand decision, sourcing standard, and insurance conversation happen is the one sequencing mistake worth avoiding on purpose.

06

Monitoring — what "working" looks like

A short weekly review, not a dashboard project. Five numbers, checked every Sunday during the batch-prep block already carved out above.

Reach
Views/impressions, all platforms, weekly total
Engagement
Comments + saves — Signal Check's actual job
List growth
Newsletter + free-tier signups, the owned asset
Leads
Assessment form fills, attributed by UTM once wired

A fifth number worth tracking manually from day one, before any tooling exists for it: which single post each week performed best — that's the one that gets re-promoted Saturday, and over a few months it's also the fastest way to learn what this specific audience actually responds to, faster than any of the strategic-analysis scenarios can predict in advance.

The bear-case check-in: Strategic Analysis's bear scenario (~$180/mo MRR, ~19 members) isn't a failure state — it's the signal to look at engagement and list growth specifically before touching content strategy. Low reach with high engagement means the content works and distribution doesn't; low engagement with decent reach means the reverse. Don't react to the revenue number alone.

07

Clone-readiness criteria

The whole point of running this on Vivere's own brand first (per Master Proof and the SIGNAL Hub's Clone Playbooks) is to prove it before selling it. Concrete criteria for "proven enough," rather than a gut call:

SignalThresholdWhy this one
Cadence held90 consecutive days of the daily rhythm, no gapsEvery document in this package agrees cadence — not quality spikes — is what actually predicts growth. Prove the system runs before claiming it's sellable.
A real case study existsAt least one County Report chapter published and cited/shared externallyThis is the credential no competitor can fake — but only once it's actually happened, not while it's still a plan.
The funnel convertsAt least one assessment-to-client conversion attributably sourced from SIGNAL contentProves the lead rail works, not just that content gets views.
Production time is knownThe cost-side model (Readiness Audit §4) is filled in with real hours, not estimatesYou can't price "clone this for a client" without knowing what it actually costs to run.

All four, not any one — a single viral post or one good month doesn't mean the system is proven, only that content can work. The clone pitch ("we built this ourselves — we'll build yours") is only as strong as the receipt behind it.