Vivere Internal — Readiness Audit

Fix these five first
The structural question — one brand or two?
Legal & liability blind spots
The missing cost side
Retention & member-experience gaps
Tactical gaps in what's already built
Opportunities — what to add, not just fix
Reconciling the monetization numbering
The full punch list, sequenced

Fix these five first

Everything else in this audit is real, but these five block or materially de-risk everything downstream of them. Read the rest when you have time; treat these as the ones worth a conversation this week. (This list is about risk and gaps. For genuinely new ideas nobody's proposed yet, skip to Opportunities. For what to actually do if any of these — or anything else — goes wrong, see the Contingency & Pivot Plan.)

Decide: one brand or two?

Beam/SIGNAL (friendly, marketing) and SOL (serious, investigative) are structurally different businesses sharing one package. Every downstream content, hiring, and legal decision depends on this being settled first.

Why first: content already being produced (this week's cards, trivia) is being built blind to the answer.

Talk to an insurance broker about media liability

"Investigative reporting" is a different risk class than a web-dev blog. General liability doesn't cover defamation or media claims — errors & omissions (media liability) coverage does.

Why first: this is the one item where the cost of being wrong (an uninsured claim) is existential, not just inconvenient.

Write a one-page sourcing standard before Act I

What counts as "sourced enough" to publish, who fact-checks, what triggers a correction. SOL's entire value proposition is credibility — the standard needs to exist before the first piece, not after the first complaint.

Why first: retrofitting editorial standards after a mistake is reputationally worse than not having published yet.

Model the actual cost side, not just revenue

Every scenario in Strategic Analysis is revenue-only. There's no line item for Joe's production hours, Mike's involvement, tool costs, or the migration cost off a hosted platform.

Why first: "$1,440/mo MRR" isn't a business decision until you know what it cost to get there.

Design what happens after someone subscribes

The funnel in every document stops at "they convert." No onboarding, no cancellation flow, no win-back. Retention — which Strategic Analysis itself calls the real lever — has zero described mechanism.

Why first: cheaper to design before Act III than to retrofit once the first cancellations start.

The structural question — one brand or two?

SIGNAL/Beam and SOL are bundled into one "Vivere Internal" package, but they're not the same business. Naming the difference plainly:

	SIGNAL / Beam	SOL
What it is	Vivere's own marketing content, to sell more web-dev clients	A paid investigative-journalism subscription — a media company
Monetization	Leads → contracts & retainers	Recurring subscriptions (membership)
Voice	Warm, mascot-fronted, "we build the signal, then broadcast it"	Serious, sourced, "teach people how to think, not what to think"
Content built so far	10 cards, 3 shorts scripts, a mascot with 4 poses	Zero pillar investigations chosen or written
Risk profile	Ordinary marketing/brand risk	Defamation, sourcing, correction-policy, media-liability risk

Both docs that touch this already flag it as open (Signal Hub: "Beam final pick — approve the beacon direction or swap the concept"; Master Proof: "does the investigative flagship use the SIGNAL mascot, or its own more serious visual identity?"). What hasn't been said plainly: this isn't a mascot styling question, it's a brand-architecture question.

Three real paths, not one

One brand, one voice. SOL folds into Vivere's own identity, Beam included. Simplest to run, but risks a friendly mascot undercutting an investigative piece's credibility the moment a reader sees both.
Two brands, shared infrastructure. SOL gets its own name, its own visual identity (no Beam), possibly its own handles — but still built on the same Cloudflare stack, same production workflow, same operator. Most credible for SOL, more overhead to run two content calendars.
SOL as a "Vivere presents" sub-brand. A middle path — SOL is visually distinct and mascot-free, but its footer/about page openly credits Vivere as the studio behind it (which is itself good marketing — "the same studio that built this also builds client sites").

A reasonable default if this isn't resolved soon: path three. It gets SOL the gravitas it needs without inventing an entirely separate operation, and it keeps the "we built this ourselves" sales story intact for the web-dev business. But this is a brand call, not a technical one — worth deciding on purpose rather than by default.

Legal & liability blind spots

None of the other documents in this package mention any of the following. Flagging them isn't legal advice — it's a list of what to bring to an actual attorney and insurance broker before either venture has real subscribers or sponsors.

Specific to SOL (investigative content)

Defamation & media liability exposure. Investigative claims about real businesses or people carry real legal exposure that a web-dev portfolio doesn't. Standard general liability insurance typically excludes media/publishing claims — errors & omissions (media liability) coverage is the relevant product, and it's usually not expensive at this scale, but it needs to exist before publishing, not after a demand letter.

No sourcing standard or correction policy. Nothing in Master Proof or Signal Hub describes what "sourced" means in practice (second-source rule? on-record requirement? right-of-reply before publishing?), who reviews a piece before it goes out, or what happens when something needs correcting after publication. This is both a legal and a credibility issue — for content whose entire pitch is trustworthiness, the process needs to be real and probably needs to be visible to readers.

Specific to the membership product

Subscription cancellation compliance. The FTC's "click-to-cancel" rule requires that canceling a subscription be at least as easy as starting one. None of the membership-tier documentation describes a cancellation flow, refund policy, or auto-renewal disclosure — all of which the platform decision (hosted vs. native) will need to satisfy either way.

Sales tax on digital subscriptions. A growing number of states tax digital subscriptions/SaaS. Worth a five-minute check with whoever handles Vivere's existing bookkeeping before pricing gets locked in.

Cross-cutting

Trademark exposure. "SIGNAL" and "PULSE" in particular are common names in tech and media. Nobody's run a trademark search on SIGNAL, PULSE, CAST, or SOL — worth a basic USPTO search before either becomes a public-facing brand people build loyalty around.

Sponsor disclosure. The draft sponsor kit in Launch Schedule describes rate tiers but not FTC endorsement-disclosure requirements (clear "#ad"/"sponsored" labeling) that apply the moment Rail 3 activates.

Mike Olmsted's role isn't documented anywhere in this package. CLAUDE.md names him as co-operator of Vivere Colorado LLC, but nothing here addresses his involvement in SOL/SIGNAL specifically, equity or revenue split, or whether content/IP produced for this venture is being assigned to the LLC or created personally. Worth settling on paper before there's real revenue to split or a dispute to have.

The missing cost side

Strategic Analysis models revenue in real depth — bear/base/bull scenarios, LTV, CAC, a 12-month horizon. There is no corresponding cost model anywhere in the package. Below is the shape one would take — deliberately left as an empty template, since filling it with guessed numbers would be worse than leaving it blank.

Cost category	What belongs here	Currently modeled?
Production time	Hours/week on SOL research & writing, valued at what that time is worth doing client work instead	Not modeled
SIGNAL content time	Hours/week on cards, trivia, shorts filming/editing	Not modeled
Tools & software	Membership platform fees, Stripe processing, any paid AI/automation tooling	Rates mentioned; not totaled
Platform migration	The eventual hosted→native Cloudflare paywall build, explicitly planned as a future project	Not modeled
Insurance & legal	Media liability coverage, any trademark/legal review	Not modeled (see Section 3)
Mike's time/compensation	Whatever his actual involvement ends up being	Not modeled

Why this matters more than another revenue scenario: "$1,440/mo MRR" (the base case in Strategic Analysis) sounds like a clear win in isolation. Whether it actually is depends entirely on what it cost in hours and dollars to get there — and right now there's no way to answer that question from anything in this package.

Retention & member-experience gaps

Every funnel diagram in this package ends at "they convert." Strategic Analysis itself says retention, not acquisition, is where subscription revenue actually compounds — but nothing describes what happens to a member after they subscribe.

Onboarding — undescribed

No welcome sequence for a new subscriber
No "here's how to get the most out of this" orientation
No described first-week experience at all

Churn — undescribed

No cancellation flow (also a compliance gap — see Section 3)
No exit survey to learn why people leave
No win-back sequence for lapsed members

Community — unaddressed

No comments, Discord, or member-to-member layer
For many 2026 membership products this is the actual retention driver, more than the content itself

Support — unaddressed

No plan for who answers billing/login questions
Thin at 20 members; real operational load at 200

The cheap fix: none of this needs to be built before Act I. It needs to be designed before Act III (when the paywall opens), so the first real subscriber doesn't hit a gap nobody thought about. A one-page "member lifecycle" sketch — welcome email, 30-day check-in, cancellation flow, win-back email — would close most of this in an afternoon.

Tactical gaps in what's already built

Specific to the Content Library and Launch Schedule built this session — smaller than the sections above, but worth a punch list of their own before real posting starts.

Only one example per card family. Before/After, The Proof, The Tip, and The Wink each have exactly one rendered card. By Week 3 of the Launch Schedule, the calendar is already reposting the same single asset — fine as a proof of concept, thin for a sustained calendar. Needs 3–5 real variations per family before Week 4.
Story and OG crops not generated. Content Library's own text flags this: every card wants a 1080×1920 Story crop and a 1200×630 OG crop alongside the 1080×1350 original. None exist yet.
The animated Beam loop isn't exported. It runs live on the Content Library page (CSS-only), which is great for review, but nobody has actually screen-recorded it into a video/GIF file — which is what's needed to use it as a real intro bumper in an edited short.
No thumbnail templates. The Setup Guide calls thumbnail CTR "the #1 Shorts/long-form ranking lever," but no thumbnail layout exists for the three shorts once they're filmed.
No caption/subtitle workflow. Signal Hub's own shorts spec requires on-screen captions always (sound-off default) — there's no described process for how captions get written, timed, or burned into the filmed video.
No music/audio licensing note. If any of the three shorts use background music, licensing (YouTube Audio Library, a paid library, etc.) hasn't been mentioned anywhere.

Opportunities — what to add, not just fix

Everything above is about risk and gaps in what already exists. This section is different: ideas nobody has proposed anywhere in this package yet, additive rather than corrective.

The flagship idea

A "State of [Delta/Montrose County] Small Business Web" investigative report. Pick a real, checkable question — how many local businesses have a website at all, how many load fast, how many are on HTTPS, how many actually rank on Google — go verify it directly, and publish it as a genuine SOL-grade investigation with real local data. This is the one idea that does double duty: it's real journalism (serious, sourced, credible — the exact bar SOL is trying to clear), it's a lead-gen machine (every business named without a site, or with a slow one, is a warm prospect), it's local-press bait (this is precisely the kind of story a county paper picks up and links to), and it's a natural sponsor magnet once it has reach. Nothing else planned does all four at once — and it's a strong candidate to literally be one of the "first 2–3 pillar investigations" that Master Proof and this package's own CLAUDE.md already flag as an open decision, so it doesn't have to be additional scope so much as a concrete answer to a question already on the list.

Five more, ranked by fit

Idea	Why it works	Priority
Interactive audit tool	Everything currently planned is one-way broadcast (shorts, cards, trivia). A free "is your site costing you customers" instant checker (speed, mobile score, HTTPS, basics) converts far better than a card, because the visitor gets a personalized result — and it's a live demo of the exact capability being sold.	High
A separate, low-commitment newsletter	SOL's membership is a real ask ($10–25/mo). There's nothing for a business owner who's curious but not ready to pay — a free "one web tip a month" list nurtures that middle group instead of losing them between "watched a Short" and "booked a call."	High
Video testimonials as a content type	Completely absent from the plan despite being one of the highest-converting formats for a service business. A 30-second client saying "here's what changed" outperforms a lot of what's currently scoped.	High
A referral program	The seasonal arc's Epilogue mentions "referral asks" in passing, but there's no actual structure — what does a referrer get? For a word-of-mouth local business this is usually the cheapest lead source available, and it's barely sketched.	Medium
Framework licensing or a paid course	The Master Framework already exists elsewhere in Vivere Internal. Licensing it, or teaching it as a cohort course, is a genuinely different and more scalable revenue line than one-to-one client work — nobody has proposed it yet.	Lower / longer-term

One more, cheap enough to just do: a public build log or changelog — not this internal one, an actual public-facing version. "Build in public" is proven in dev/indie-hacker circles specifically because watching progress creates its own anticipation and trust, and Vivere is already keeping this kind of log internally; making a version of it public costs almost nothing extra.

Reconciling the monetization numbering

This one's already fixed, not just flagged — worth explaining what was wrong and what changed, since it's a good example of the kind of drift that happens across a package written over multiple sessions.

Three documents each described SIGNAL's monetization, and they disagreed with each other on what "Rail 2" meant:

Document	Old scheme	Issue
Signal Hub (before this audit)	"Two rails" — Rail 1 = leads, Rail 2 = ad/sponsor	Its own table below the header already used a 3-tier priority scheme where ad/sponsor was "3," not "2" — the header contradicted its own table
Setup Guide	Three rails — Rail 1 = leads, Rail 2 = productized SIGNAL, Rail 3 = ad/sponsor	Internally consistent
Launch Schedule	Content→revenue map using "Rail 1 + Rail 2"	Already followed Setup Guide's 3-rail scheme, which made it disagree with Signal Hub's header

Fixed as part of this audit: Signal Hub's monetization header now reads "Three rails" and its stat boxes correctly show Rail 1 (leads), Rail 2 (productized SIGNAL — scaling), Rail 3 (ad/sponsor — on reach), matching Setup Guide and Launch Schedule exactly. The canonical version going forward, across every document: Rail 1 = leads, Rail 2 = productized SIGNAL-per-client, Rail 3 = ad/sponsor.

Note this doesn't touch Master Proof's revenue model — that document's "1 Membership MRR / 2 Sponsors / 3 Ads / 4 Client sales" ranking is deliberately a different framework, because SOL's membership business has different revenue mechanics than SIGNAL's lead-generation business. That's intentional, not an inconsistency — see Section 2 for why these are genuinely two different things.

The full punch list, sequenced

Everything above, fixes and additions both, in the order it's cheapest to do it.

When	Item	Section
Before any more content	Decide one brand or two (SOL vs. Beam/SIGNAL)	§2
Before any more content	Write the one-page sourcing/correction standard for SOL	§3
Before Act I (first investigations)	Call an insurance broker about media liability coverage	§3
Before Act I	Trademark search on SIGNAL / PULSE / SOL	§3
As Act I — this can be the pillar investigation	Scope and report the "State of [County] Small Business Web" investigation	§7
Start now, runs in parallel	Launch the free low-commitment web-dev newsletter	§7
Before filming the 3 shorts	Build 2–4 more variations per card family; generate Story/OG crops; export the animated loop; sketch a thumbnail template	§6
Before scaling any paid distribution	Build the interactive audit tool (site speed/HTTPS/mobile checker)	§7
Ongoing, starting with the next client	Start collecting video testimonials as a standing content type	§7
Before claiming this "profitable"	Build the cost-side model — time, tools, migration, insurance	§4
Once there's an initial happy-client base	Design and launch a referral program	§7
Before Act III (paywall opens)	Design the member lifecycle — onboarding, cancellation, win-back, support	§5
Before Act III	Settle Mike's role, split, and IP assignment on paper	§3
Before Rail 3 (sponsors) activates	Confirm FTC disclosure practice for sponsored content	§3
Ongoing	Re-verify sales-tax treatment of the membership once pricing is final	§3
Longer-term, post-launch	Evaluate framework licensing / a paid course as a scalable revenue line	§7

Contents

Fix these five first

Decide: one brand or two?

Talk to an insurance broker about media liability

Write a one-page sourcing standard before Act I

Model the actual cost side, not just revenue

Design what happens after someone subscribes

The structural question — one brand or two?

Three real paths, not one

Legal & liability blind spots

Specific to SOL (investigative content)

Specific to the membership product

Cross-cutting

The missing cost side

Retention & member-experience gaps

Onboarding — undescribed

Churn — undescribed

Community — unaddressed

Support — unaddressed

Tactical gaps in what's already built

Opportunities — what to add, not just fix

The flagship idea

Five more, ranked by fit

Reconciling the monetization numbering

The full punch list, sequenced