The 30-Day Program

LUCE's own council review named its absence of a master timeline as that course's single biggest structural flaw — 21 modules, each with its own "Week 1," none of them agreeing with each other about what a reader had already built by the time they reached it. LUCE_22_90Day_Program.md was written to fix that after the fact. COVER_09 is written to fix it before the fact: it is this course's execution spine, and every other module's Week-1 or Action-Plan section is subordinated to the single calendar below. If a date in this module ever disagrees with a date implied in COVER_01 through COVER_08, this module is the one to trust — and that disagreement should be reported as a defect, not silently resolved by the reader guessing.

Why 30 days and not 90. LUCE needed 90 days because e-commerce time-to-first-dollar runs months: sourcing, store build, ad iteration, and enough sales volume to read unit economics honestly all take real calendar time. COVER's TTFD research points the other way — compliant lead-gen arbitrage (Path 4, COVER_02) realistically produces a first paid lead-delivery within 1–2 weeks of a standing start, once the funnel and at least one buyer relationship are confirmed. That compresses the entire arc — diagnosis, build, first ad spend, first sale, first real economics read — into a window closer to 30 days than 90. Day 31 onward is deliberately out of scope here; it is COVER_08's month-2/3 scaling-or-quit framework, and this module ends with a formal handoff into it, not a fade-out.

Confidence labels used throughout: [Established] = documented in the cited module with direct sourcing. [Directional] = an industry-range estimate, cited in the source module, not independently audited. [Program-derived] = a sequencing or timing conclusion this module draws by combining other modules' facts — flag these if your own results diverge, since they're the parts most likely to need recalibration to your specific numbers.

---

#1. One-Page Version

---

#2. Pre-Day-1 Gate: The Eligibility Check Must Be Resolved First

Day 1 of this program does not start until COVER_01's eligibility check has a recorded answer. This is a hard sequencing rule, not a suggestion — a reader who is actually eligible for a US resident producer license has a materially better path available (COVER_02's Path 2, own-funnel licensed producer) and needs to know that before spending a dollar building the no-license funnel this program executes.

What "resolved" means, concretely (per COVER_01 §3.3, §9):

• Confirmed eligible ("gate open"): written or recorded confirmation from at least one state DOI or NIPR/AgentSync that your specific passport/visa/residency combination qualifies you for licensing. → Do not run this program. Divert to COVER_02's Path 2 build, using COVER_03–06 for the compliant funnel/compliance/economics layers but under a licensed-producer structure, with COVER_08 covering the graduation path.
• Confirmed or assumed ineligible ("gate closed"): either a clear "no" from 2–3 independent sources, or — per COVER_01's asymmetric-risk rule — unclear/non-responsive answers, which are treated as closed by default because the downside of wrongly assuming eligibility (building a funnel for a business you legally can't run) is worse than the downside of a conservative assumption. → Proceed with this program as written.

Go/No-Go checkpoint: Do you have a written eligibility conclusion — "open" or "closed" — with an evidence trail (who you contacted, when, what they said)? If no, stop here and run COVER_01's own Day 1–5 SOP before opening this document again. This checkpoint has no pivot state: it's binary, and guessing is explicitly against COVER_01's own stated rule.

---

#3. Week 1 (Days 1–7): Foundation — Compliance, Funnel, Buyers, Tracking

Week 1's job is to make Week 2's ad spend defensible: nothing gets spent until the funnel is certified, at least one buyer is lined up, and the compliance checklist is clear. This directly encodes COVER_03's "buyer vetting BEFORE ad spend" requirement and COVER_05's "compliance checklist complete, not retrofitted" requirement — both are hard gates in Week 1, not soft ones.

• Day 1. Build the COVER_06 financial tracking template (empty — eleven columns, ready to receive real numbers from Day 9 onward). Start the buyer-candidate list (final-expense/life IMOs, lead-buying networks — target 5+ candidates to contact). Choose a landing-page builder confirmed to support TrustedForm/Jornaya field injection (COVER_03 §4) — verify this before committing, not after building.
• Day 2. Send outreach to all buyer candidates. In parallel (this does not block buyer conversations), file LLC/entity paperwork — COVER_03 §6 estimates 3–7 business days of mostly-waiting processing time, so starting it Day 2 means it's likely resolved by the time it's needed for buyer contracting.
• Day 3. Build the landing page per COVER_03 §3's full anatomy; integrate the TrustedForm or Jornaya snippet as infrastructure, not an add-on.
• Day 4. Run COVER_05 §6's licensing self-audit checklist against your actual planned operation — yourself, any VAs, any planned chat/DM handling. Draft (or request from your leading buyer candidate) a lead-purchase agreement; check it against COVER_05 §8's checklist (lead definition, exclusivity terms, compliance representations, refund policy, payment terms).
• Day 5. Send the draft lead-purchase agreement to your top 1–2 buyer candidates for review. Test-submit the landing page yourself; confirm the TrustedForm/Jornaya certificate is generated and correctly captured before any real click is accepted — this cannot be retrofitted later (COVER_03 §2 failure mode).
• Day 6. Run COVER_05 §10's full pre-launch compliance checklist item by item against your actual funnel and documents — not a skim, a literal checklist pass. This is the single most important artifact in the whole program's first week.
• Day 7 — WEEK 1 CHECKPOINT.

Content-asset work (COVER_07) starts quietly in the background this week: a first pass at niche selection, run in parallel with the above, not sequentially after it. It produces no output that gates anything in Week 1 — it's there so Week 2–3's pillar-page drafting has a starting point.

---

#4. Week 2 (Days 8–14): First Ad Campaign Launch

A sequencing note that matters: COVER_04 calls its ad-launch sequence a "Week-1 Action Plan," because from the ad-ops module's own point of view, it's the first week of running ads. In this program's calendar that maps to Days 8–14 — this program's Week 2, not Week 1. Treat every "Week 1" reference inside COVER_04 as meaning "the first week of ad spend," and translate it to Days 8–14 here. This is exactly the kind of cross-module date drift LUCE got flagged for; naming it explicitly is the fix.

• Day 8. Pre-flight: reconfirm the landing page is live, certified, and independently test-submitted (COVER_04 §12 step 1). In Meta Ads Manager, begin campaign creation and let the platform tell you whether Special Ad Category applies — don't assume. Decide format: click-to-landing-page for this first campaign, not native lead-ad, so the CPL read stays clean. Write exactly two creative concepts, each built around a distinct real trigger event (COVER_04 §4).
• Day 9. Build a single, consolidated ad set — not several narrow ones — sized to the learning-phase-clearing budget derived in COVER_04 §5. Pull that number from COVER_04 directly rather than using any figure repeated here from memory; it's computed from 50 optimization-events/week against your assumed CPL, and if your real CPL comes in worse than COVER_04's cited range, the true floor is higher than the number you started with. If the full floor isn't fundable, apply COVER_04 §5.2's documented remedy — consolidate ad sets, or optimize for a higher-volume, earlier-funnel event (lead-form-start rather than full completion) — rather than under-funding a full-completion test. Launch both creatives inside the one ad set. This is Day 1 of ad spend.
• Days 10–13. Do not touch the ad set — COVER_04 §12 step 8 specifies a minimum 3–4 day hands-off period, ideally through the full ~50-event/7-day window, because every mid-learning edit risks restarting the clock. Use this window for buyer-side work: confirm delivery mechanics (webhook or spreadsheet handoff) with your committed buyer, and continue COVER_07 niche/keyword research in the background. As leads arrive and are certified, begin delivering them to your buyer on whatever batching cadence your agreement specifies (commonly weekly) — don't wait for the ad set to formally clear learning phase before delivering leads you've already sold; delivery and the learning-phase clock are independent.
• Day 14 — WEEK 2 CHECKPOINT: has the campaign cleared the learning-phase floor?

First invoice timing [Program-derived]: leads generated across Days 9–14, batched weekly per your buyer agreement, typically produce a first invoice around Day 14–15. Under net-7 to net-15 terms (COVER_06 §5), the corresponding payment is expected to land roughly Day 21–30 — which is exactly why the Week 3 and Day-30 checkpoints, not Week 2, are where payment and full economics get evaluated.

---

#5. Week 3 (Days 15–21): First Payment, First Real Read

• Day 15. Consolidated weekly review (see §7 below). Pull rolling 7-day CPL by ad set. If the ad set cleared learning phase in Week 2, this is the first week where CPL data exists at all — not yet the two-consecutive-week bar COVER_06 requires for a kill decision, but enough for a directional read and for cautious scaling if CPL is trending down week-over-week (COVER_04 §6 note).
• Day 16. Chase the first invoice: confirm the buyer received and logged it, and confirm the actual payment term in writing — COVER_06 §5 flags that a verbally-quoted net-15 has been known to become net-21 in practice for a new seller without a track record.
• Days 17–19. Continue running the ad set. If the Day 15 review called for a scale move, execute it in 20–30% increments only (COVER_04 §11 step 4) — never a large single jump, which risks re-triggering learning-phase instability. Continue COVER_07 pillar-page drafting: outline into a first full draft of sections, still no expectation of traffic.
• Day 20. Check whether the first payment has landed (plausible as early as Day 20–21 under net-7 terms from a Day-14–15 invoice).
• Day 21 — WEEK 3 CHECKPOINT.

---

#6. Week 4 (Days 22–30): Second Read, Diversification, Content, Handoff

• Day 22. Consolidated weekly review. Second real CPL-vs-resale read — this is the first point in the program where COVER_06's full evidentiary bar (two consecutive clean post-learning-phase weeks) can actually be satisfied, assuming Week 2 cleared learning phase on schedule. Check the financial tracking sheet's cash-position and days-of-runway columns (COVER_06 §7, columns 9–10) — this is the point where a cash-timing failure, as opposed to a margin failure, would first become visible if the net-15 float wasn't held as a standing reserve.
• Day 23. Start a second buyer conversation. This is not a reaction to a problem with buyer 1 — it's proactive concentration-risk reduction, per the logic COVER_08 develops fully; this program only starts the relationship, it doesn't need to close it by Day 30.
• Days 24–26. Continue ad ops per the Day 22 review's decision. Publish the first COVER_07 content piece (pillar page live). Set the expectation explicitly here, in writing, because it's the exact kind of premature-verdict mistake this program exists to prevent: COVER_07 is a multi-month asset. "Published and indexed" is Day 30 success for this piece — not traffic, not leads, not revenue. Judging the content path a failure at Day 30 because it hasn't produced income yet is judging it against Week 2's timeline instead of its own.
• Days 27–29. Buffer days. Catch up anything that slipped — second-buyer contract paperwork, a compliance re-check if anything about the funnel changed mid-month, full reconciliation of the financial tracking sheet for all four weeks so Day 30's numbers are real, not estimated.
• Day 30 — THE CHECKPOINT: formal handoff into COVER_08.

This is the program's single most consequential decision point, and every branch below uses COVER_06's actual kill-switch numbers — nothing new is invented here.

Day 31 and beyond belongs entirely to COVER_08. This program does not extend past this checkpoint.

---

#7. The One Consolidated Weekly Review

LUCE's audited flaw wasn't just a missing timeline — it was also four separate weekly rituals from four different modules running in parallel, each competing for the same hour of the operator's week. COVER_04's ad-ops cadence, COVER_06's financial review, and COVER_05's compliance check-in are consolidated here into one weekly session, not three.

When: Every Friday, once the funnel is live (starting Day 8's launch week). Before that, Week 1 has no ad data to review, so the first full session is Day 15 (retroactively covering the Day 9–14 launch).

Duration: 60–90 minutes.

What it covers, in order:

1. Pull rolling 7-day CPL by ad set (COVER_04 §11 step 1). Flag anything still learning-limited — no kill/scale call on those yet.
2. Apply COVER_06 §6's kill/scale table to any ad set with 2+ consecutive clean post-learning weeks. Log the decision and the specific number that drove it.
3. Spot-check a handful of this week's leads for correct, timestamped TrustedForm/Jornaya certification (COVER_04 §11 step 5; full procedure in COVER_05).
4. Reconcile actual resold price per lead against the CPL assumptions driving the kill/scale thresholds — if resale price has moved, the thresholds move with it.
5. Update the COVER_06 financial tracking sheet in full: leads generated, ad spend, realized CPL, leads sold, realized resale price, costs, contribution margin, cash position, days-of-runway.
6. If a scale decision was made in step 2, schedule its execution for the following Monday, in 20–30% increments — the budget move itself happens on its own trigger, not as a second mid-week ritual.

One session, one artifact updated (the tracking sheet), one set of decisions logged. If a week ever seems to need a second sitting, that's a signal the week had a genuine incident (see §8) — not a sign the cadence needs to become two rituals again.

---

#8. Failure-Week Playbook

Scenario 1 — the Day 4/Day 7 compliance self-audit reveals a licensing-boundary blocker. Something in the planned operation (a VA script, a chat-handling process) crosses into personally soliciting or negotiating a specific policy. Recovery: stop before any spend. Re-scope the crossing behavior out of the operation entirely — usually this means restricting all human-touch contact to pure logistics (confirming receipt, scheduling) and routing anything policy-specific back to the licensed buyer. Re-run the COVER_05 §6 self-audit before resuming Week 1.

Scenario 2 — buyer vetting fails to produce a committed buyer by Day 7. Outreach to 5+ candidates produces interest but no signed or verbal commitment. Recovery: do not launch ads on schedule. Widen the buyer-candidate list (broader FE/life IMOs, lead-marketplace forums), and consider offering a small, unpaid or heavily discounted sample batch to a promising candidate to convert interest into commitment faster. Push Week 2's launch back by the number of days this takes — a late launch with a real buyer beats an on-time launch with no buyer for the leads.

Scenario 3 — the ad account gets rejected or restricted. This can happen pre-launch (account review) or mid-flight (policy flag). Recovery: do not attempt to circumvent the restriction with a new account under a different name — that compounds the problem. Appeal through Meta's standard process, and in parallel, audit the ad copy and landing page against Special Ad Category and platform-policy requirements (COVER_04 §3, §8) for anything that may have triggered it. If the restriction looks likely to take more than a few days to resolve, this is grounds for the Day-30 "extend 2 weeks" branch, applied early rather than waited out silently.

Scenario 4 — the campaign fails to clear the learning-phase floor even at the COVER_04-derived budget. This means either the real CPL is meaningfully worse than the assumed range, or the funnel has a conversion problem upstream of the ad (weak creative-to-landing-page match, slow page load, broken form). Recovery: first isolate which it is — check landing-page conversion rate against ad click volume before assuming CPL is simply higher than expected. If it's a genuine CPL problem, apply COVER_04 §5.2's remedy 2 (optimize for a cheaper, higher-volume event) rather than raising budget blindly. If it's a funnel-conversion problem, fix the funnel before spending another dollar on traffic — more spend into a broken landing page just buys more untrustworthy data faster.

---

#9. KPI / Kill-Switch Table (Consolidated Operational Dashboard)

This is the first place all of the individual modules' thresholds appear together as one dashboard, rather than scattered across their own KPI tables.

---

#10. Self-Test

1. Your eligibility check with 2 state DOIs came back clearly "no," and a third never responded after a week. Per COVER_01's rule, what do you conclude, and why is that the correct call given the asymmetry of the risk?
2. On Day 5, your top buyer candidate hasn't responded to the draft lead-purchase agreement, and you have no other live conversations. What does the Week 1 checkpoint tell you to do, and why is launching ads on schedule anyway the wrong call even if the funnel and compliance checklist are otherwise ready?
3. By Day 14, your ad set has spent at the COVER_04-derived floor but logged only 30 of the ~50 needed learning-phase events. What is the correct action, and what is explicitly not permitted?
4. Explain why COVER_04's own "Week-1 Action Plan" maps to Days 8–14 of this program rather than Days 1–7, and why that remapping matters for avoiding LUCE's contradictory-Week-1 flaw.
5. Your Day 21 checkpoint shows a realized CPL of $38 against a $50 resale price. Is this a pass, pivot, or kill per this module's table — and what single action does COVER_06 explicitly forbid you from taking in response to a gray-zone number?
6. It's Day 26, your first COVER_07 content piece just went live, and it has generated zero traffic. Is this a signal the content path isn't working? Justify your answer using this module's stated expectation for COVER_07 at Day 30.
7. At Day 30, your ad set has been learning-limited on and off for three of the four weeks due to two separate ad-account review delays, and you have only 6 days of genuinely clean post-learning-phase data. Which Day-30 branch applies, and why is forcing a scale-or-kill verdict here a mistake even if the 6 days of data look good?
8. Your Day 22 review shows contribution margin positive every week on paper, but days-of-runway has been trending down since Day 15 and is now at 5 days. What does the KPI table require you to do, and why does a positive margin not override this requirement?
9. Name the one weekly ritual this program consolidates, and list at least four separate module-level rituals it replaces.
10. A new operator reads only COVER_04 and launches an ad set on Day 1 of their own calendar, without having run COVER_05's compliance checklist or lined up a buyer. What two Week 1 gates did they skip, and what is the concrete downside of skipping each one?

---

#11. Cross-References

• COVER_01 — Eligibility Diagnosis: the Pre-Day-1 gate in its entirety; this program does not start without COVER_01's written eligibility conclusion.
• COVER_02 — Five Paths Compared: determines which path this program even applies to (Path 4, compliant lead-gen arbitrage, by default if the eligibility gate is closed); also the return destination if Day 30's KILL branch triggers and Path 3 or Path 5 needs reconsidering.
• COVER_03 — Compliant Funnel Build: Week 1's landing page, TrustedForm/Jornaya integration, buyer vetting, and entity setup, in the exact day-by-day sequence this module inherits.
• COVER_04 — Paid Media Execution: Week 2's ad launch sequence and derived learning-phase budget (§5), and the weekly ad-ops components folded into this module's single consolidated review (§11).
• COVER_05 — Legal/Compliance Armor: Week 1's pre-launch compliance checklist (§10), which must be complete before Day 8's ad spend, not retrofitted after.
• COVER_06 — Unit Economics & Kill-Switches: every numeric threshold in this module's §6, §9, and §10 originates here — this module consolidates COVER_06's numbers into one dashboard rather than re-deriving them.
• COVER_07 — Content/SEO Asset: the background-track work started in Week 1 and carried through Day 30's first publish, with its own multi-month timeline explicitly protected from a premature Day-30 verdict.
• COVER_08 — Scale-or-Quit Framework: the explicit destination for every Day-30 branch; this program stops at Day 30 by design and hands off entirely, rather than attempting to cover month 2 and 3 itself.
• COVER_M1 — Mechanisms Depth-Layer: referenced implicitly wherever this module cites a specific psychological or structural mechanism (e.g., the asymmetric-risk logic behind the eligibility default, the reason a single-variable diagnosis beats averaging down); read COVER_M1 for the underlying reasoning, not just the operational rule.

---

#RESIDUALS

• This module's entire job was contradiction-prevention, and its biggest risk is the same one it exists to fix: if any cited module (COVER_04's derived budget, COVER_06's kill-switch numbers) is revised after this module is written, this document goes stale first and silently — there is no automated check tying these documents together. Re-verify the specific dollar figures against the live COVER_04/COVER_06 modules before running this program if any meaningful time has passed since publication.
• The 30-day window assumes a standing start with no pre-existing delays — an eligibility check that drags past a week, an entity filing that hits a state-specific snag, or an ad-account review that runs long all push the whole calendar right without breaking its internal logic; when that happens, shift every subsequent day/week label by the delay rather than compressing later steps to protect the Day-30 date. A Day-30 checkpoint reached with genuinely clean data on Day 34 is a better outcome than one forced prematurely on Day 30 with contaminated data.
• The single weekly review (§7) is the fix for LUCE's four-ritual flaw, but it is not automatically safe from re-fragmenting — the temptation to "just quickly check" the ad account mid-week, outside the Friday session, is exactly how four rituals get reborn one at a time. If a mid-week check becomes routine, it belongs in the Friday session's scope, not as a new standing ritual next to it.
• Nothing in this module substitutes for COVER_08's fuller month-2/3 quit doctrine. The Day-30 branches here are deliberately narrow and falsifiable, not a complete framework for when to walk away entirely — that fuller treatment, including the psychological cost of sunk-time reasoning, lives one module ahead.