Publishing Pod Handoff

State of play

Status is as of my exit on September 1. Anything marked in flight has moved since; confirm current state with Hamza and Marenti before you act on it.

The system on one page

The five documents describe one system. Each tool has one job, and the boundaries are what keep it usable.

The chain: Slack surfaces it, ClickUp owns it, the CRM measures it, documentation remembers it.

Six rules that carry everything else

1. Owner plus deadline means it lives in ClickUp, or it does not exist. Every task leaves a meeting with a Who, a What, a definition of Done, and a When. Tasks are assigned to a person, never to the room.
2. Send every message to the smallest room that contains everyone required to act. That one sentence is the whole Slack system. The channel map is the lookup table for it.
3. Meetings do five jobs: allocate, commit, unblock, learn, develop people. Status transfer is not on the list. Status lives in ClickUp. If a meeting is needed to find out what is happening, the fix is ClickUp accuracy, not another meeting.
4. Every meeting output is a decision, a commitment, a blocker escalation, a documented learning, or individual development. A decision that is not a ClickUp task did not happen.
5. We are always testing, never randomly. Every test attacks the named biggest constraint. One primary constraint per company per week.
6. Accuracy, not activity. Update a ClickUp task when its status, owner, due date, blocker, or next action changes. Every active task is accurate by end of day. No update is required when nothing changed.

Each creator is an operating company

Roan, Ariel, and Justin are each treated as a business unit with its own offers and acquisition paths. Their funnels never become Slack channels or ClickUp folders. A webinar and a workshop that both book a call are two ways into one core offer, not two businesses. The $27 products are attraction offers whose job is to create a customer and walk them toward the core offer. Every delivery and production task carries three fields: Offer (what the task supports), Entry Path (how the prospect arrived), and Ascension Target (what this path is designed to create next).

Meeting cadence

Source: Pod Operating Rhythm v1.3, frozen, with one amendment made in this handoff: Friday runs as an async report or Loom by default (see "Live or async" below). Async by default, synchronous on purpose. Monthly we allocate, weekly we commit and inspect, daily we keep ClickUp accurate, and during launches we spike into short bursts. Tuesday through Thursday are meeting-free by default, and that is defended on purpose.

All three team members asked, unprompted, for fewer, shorter, better-prepared meetings (section 08). This cadence is the answer. Use ClickUp for daily visibility and exception huddles for unresolved blockers, not a standing daily call.

The rhythm at a glance

Standing live load: 45 minutes of weekly sync per person (Monday) plus a 20-to-25 minute 1:1. Friday is a report or Loom under five minutes. Launch weeks add five 10-minute standups. Exception huddles can land any day; they need a trigger, not a slot.

Live or async

The test for each ritual: does its output need a conversation to produce? Commitments, allocation decisions, structured debriefs, and 1:1s do. Inspection, status, and reporting do not. Live is reserved for the first group.

Meeting specs, condensed

Monthly Growth Review · 90 min · leadership, cap 7

• Pre-read frozen 24 hours before, read before arrival: scoreboard by creator and offer path (revenue, gross profit, cash collected, customers), input metrics with 6 to 12 week trends, fulfillment capacity, active launches, concluded experiments.
• Agenda: scoreboard exceptions only (10), company review Roan / Ariel / Justin with Health On Track / At Risk / Blocked (20), constraint review naming the portfolio constraint and each company constraint with evidence and cost (20), resource allocation (25), next-month commitments (15).
• Output: a written decision per creator and per major initiative, one of Continue, Increase, Fix, Pause, Stop, each with a named owner. No meeting ends without resource decisions.

Weekly Game Plan · Monday · 45 min

• Runs directly from the This Week view in ClickUp. Walk This Week, clear Overdue, milestone-check launches inside 21 days, confirm Health on each active campaign, confirm ad batch and design priorities.
• Select the one primary constraint per company being attacked this week: what evidence, what action, who owns it, when we decide, what result would change direction. Secondary constraints go to the backlog unless they threaten delivery.
• Output: every priority has one owner, one due date, a definition of done, a ClickUp task, and a success metric. Required question: which constraint is this week's work designed to remove?

Ship and Learn · Friday · async by default

• Each function rep posts an end-of-week report, a written [UPDATE] or a Loom under five minutes, in their team channel by 3pm CT: what shipped and what slipped, and why; ads in Analyzing with a scale, iterate, conclude, or kill recommendation; concluded experiments with the learning; design queue status; the next constraint.
• The pod lead posts the decisions the same day ([DECISION] in Slack, filed in ClickUp), updates the scorecards, and carries the named constraint into Monday.
• Go live only when a decision needs discussion. That is a 15-minute triggered huddle with the people involved, not a standing meeting. If Friday decisions keep needing a room, fold them into Monday rather than adding a standing Friday slot.

1:1s · weekly · 20 to 25 min

• The report owns the agenda. Standing prompts: what is harder than it should be, where do you need a decision from me, what are you learning, how is the workload actually feeling. Name one specific thing they did well and why it mattered.
• Cancel only by mutual agreement, and reschedule within the same or following week. Never a task-status review.

Daily · async · everyone

• No standing daily meeting and no mandatory daily Slack post. ClickUp is the daily written status system. Work runs from My Tasks; blockers are comments with the person who can unblock tagged.
• Slack posts only for a blocker, a decision, or coordination ClickUp cannot carry. Urgent blockers use [BLOCKER] with a 60-minute response bar inside coverage hours.
• Launch weeks: keep ClickUp accurate as usual, and add the 10-minute standup plus the launch owner's one daily [UPDATE] in the launch channel.

Launch After-Action Review · within 5 days of cart close

• Structure: what was the plan, what actually happened (numbers on the table), why the gaps, what we keep, change, or stop, which SOPs and templates get updated and who owns each.
• Required output, every AAR: 3 keep, 3 change, 3 stop. Every change and stop item becomes a ClickUp task with an owner and a due date before the AAR closes. Learnings filed, runbook updated, launch channel archived. "Great discussion" is not an output.

Creator cadence

• Weekly async report in the creator's comms channel: wins, the numbers that matter, and a needs-from-you list with deadlines. Anything in WAITING with Waiting on = Creator for 48 hours or more is surfaced in it.
• Monthly 30-minute call: performance, next month's plan, strategic asks. In a launch month it may be replaced only if launch touchpoints cover all three.

Three levels of constraint

Leadership allocates against portfolio and company constraints. The weekly team executes against company and launch constraints. Monday selects the one being attacked. Five "biggest" constraints means nothing is prioritized.

Operating rules

1. Agenda or cancel, for scheduled meetings. No agenda 24 hours out, no meeting. Pre-read incomplete 24 hours out, the owner completes it or cancels. Exception huddles use the triggering blocker as their agenda; launch standups use the four standing questions.
2. No required output, no meeting. If no decision, commitment, blocker escalation, learning, or individual development is required, cancel it.
3. Decisions land in ClickUp before the meeting ends. Owner, due date, definition of done. Slack gets the [DECISION] pointer.
4. Attendance follows the work. Required attendees own commitments, remove blockers, or make decisions that week. Others get the notes. Decision meetings cap at seven.
5. Tuesday to Thursday are meeting-free by default. The standing live meeting is Monday; Friday runs as an async report by default.
6. Every new recurring meeting needs a decision it produces and a sunset date. Reviewed monthly. The system should make meetings fewer over time.
7. No status readouts, ever. If a meeting is used to find out what is happening, fix ClickUp accuracy.
8. Every important topic gets a disposition. Decide now, assign a next action, defer to a specific date, or remove it. Every disposition has an owner. "We'll think about it" has neither.

Failure modes and guards

Slack

Source: Pod Slack Blueprint v3, approved. The old pattern was two channels per creator and everything else in one shared scroll. Decisions got made and lost, requests got seen and forgotten, and during simultaneous launches the noise multiplied. The fix is one map and one rule.

The short version

• 19 standing channels in four groups (18 if setters fold into sales), plus a temporary channel per live launch. Every channel has one job, one owner, and a pinned note saying what belongs in it.
• Slack is organized by company, function, and temporary initiative. Never per offer, per funnel, or per campaign.
• Top-level messages that create an obligation or record an outcome start with a label: [DECISION] [REQUEST] [BLOCKER] [UPDATE] [LEARNING].
• Sales announce themselves in #sales-feed. Slack shows the win; the CRM is the source of truth; ClickUp owns commitments.
• No history gets lost. Existing channels get renamed into the new map, never recreated.

The channel map

Channels are named for creators, not pods. A pod will eventually hold five creators, and nothing renames when Pod 2 exists. At two or more pods, craft rooms split by pod (#pod1-marketing), never by creator.

Rule zero: where does this message go?

Send the message to the smallest room that contains everyone required to act. When two rooms fit, prefer the creator or launch channel and drop a link in the team channel if the craft side should see it. "Required to act" is the operative phrase; people who merely find it interesting are not a reason to widen the room.

The launch bar

A launch earns its own channel only when at least two of these are true: two or more functions must coordinate; there is a hard launch or close date; coordination is needed daily; more than five people are actively contributing; failure creates material revenue or customer impact. Below the bar, it is a pinned thread in the creator channel and tasks in the folder's Ongoing list with the Campaign field set.

Message labels

Casual questions and banter need no label. The tag is for messages someone must act on or find later.

House rules, pinned in every channel

1. Threads or it didn't happen.
2. Decisions get sealed, then filed. The Slack message is the pointer; ClickUp, the SOP, or the brief is the truth.
3. Slack surfaces work; ClickUp owns it. Owner plus deadline means it exists in ClickUp or it doesn't exist.
4. @channel in #announcements only. @here only in launch channels during launch week.
5. DMs are for logistics and private matters. Praise in public, critique in private.
6. -comms means outsiders are present. Write like the creator is reading it. They are.
7. Response expectations: coverage hours 9:00am to 6:00pm CT, Monday to Friday. Urgent [BLOCKER] within 60 minutes. -comms same business day. Team and creator channels same day. Outside coverage, tag the launch owner; a blocked launch escalates launch owner, then growth lead, then director.
8. Wrong room? Friendly redirect. Answer, then point to the right channel.

The sales feed

One incoming webhook on #sales-feed, fed by each funnel's payment platform (Whop or Stripe via Zapier, GHL via workflow webhook). Format: $997 · paid in full · [offer] · Creator: Ariel · Closer: Sam · Setter: Dee · Today: $14,240. No card data, no customer emails, phones, or full names. Refunds and cancellations post automatically so the feed never reads better than reality. High-ticket posts individually; low-ticket runs in hourly digest during launches. The feed celebrates; the CRM reconciles.

Rollout

Rename, don't recreate: "Roan internal chat" becomes #creator-roan and "Roan comms" becomes #roan-comms, same for Ariel and Justin, so every message and member survives. The day-by-day build and announcement sequence is in section 06: Slack goes live for all three creators on Day 1, the announcement and training land on Day 3, and the Day-30 audit judges friction, not tidiness.

ClickUp and project management

Source: Pod OS ClickUp Blueprint (Aug 30) plus the Implementation Guide. ClickUp is one tool in the system, not the system. Shared craft lives in central queues, company strategy and campaign coordination live in creator folders, campaign work lives in a temporary launch list, and acquisition paths are fields, not folders. The whole standard gets proven on one company for 30 days before it touches anyone else.

The shape: one workspace, three spaces

Where work goes: clears the launch bar in section 04, a temporary campaign list; dated work below the bar stays in Ongoing with Campaign/Launch set. Repeats indefinitely, Ongoing. Shared craft with a standardized process, the Production queue that owns that workflow. A one-off idea with no committed date, Backlog & Ideas. Do not create a campaign list for every recurring activity.

The field model

Three fields describe the money model on every piece of delivery and production work. Offer is what the task directly supports. Entry Path is how the prospect enters (single-select; Multi-path when genuinely shared, never comma-separated). Ascension Target is what this path is designed to create next, and empty is a valid answer.

The Offers Registry in HQ holds one record per direct offer; acquisition paths are listed inside the record. Roan has exactly two records (the booked-call core offer and the $27 Blueprint), not three. A new path is born in the Registry first, then the CRM, then the ClickUp dropdown, with the same name in all three.

Other fields: Company/Creator, Campaign/Launch (matches the launch channel name), Workstream, Waiting on (Creator / On-Camera Partner / Vendor / Platform / Internal Dependency), Health (On Track / At Risk / Blocked, on the campaign anchor task and company level only, never per task), Constraint (lab tasks only), On-Camera Partner and Usage rights confirmed (partner content only), and Work Type on every task. Every execution task has exactly one assignee and a due date. The field registry has one owner; nobody else creates fields.

Statuses: local per queue, defined in the dictionary

The WAITING rule. WAITING means work cannot continue until a dependency clears, and the Waiting on field says whose court the ball is in. Waiting on = Creator is what the saved "Waiting on Influencer" view filters on, which is why reporting runs on fields, never on status names. Statuses are operating contracts: every one is defined in the status dictionary with what has to be true to leave it.

Work Type, on every task

Standard Task · Fix · Request · Blocker · Decision · Learning · Iteration · Experiment. This is how the system tells a fix from a decision from an experiment. A Fix goes to its workflow at the right priority, never the lab. A Decision goes to Issues & Decisions with owner, effective date, and what changes. A Learning cannot close without a next action or an explicit "no action required." An Experiment enters the lab only with a complete test card. Never auto-classify from keywords: a Slack [BLOCKER] is a prompt for a human to create the task, never a trigger that creates it.

One master task per unit of work

A launch milestone, an ad, a design request, and an experiment are different units of work. Each gets one master task in its home queue. Related work is connected by dependencies and relationships, never copied. A task lives its whole life in its home list; progress is a status change, never a list move. Templates or it's twice-work: launches, ad briefs, design requests, test cards, meeting agendas are all stamped, never rebuilt.

The launch runbook

A campaign that clears the launch bar in section 04 gets a temporary campaign list created from the Launch Runbook template and a launch channel with the same name; the list is archived after the debrief. Below the bar, the work runs as Ongoing tasks with Campaign/Launch set and a pinned thread in the creator channel. The template anchors on launch day (T-minus tasks land automatically, weekends skipped) and gets built during the pilot from a real campaign. Launch Day and Cart Close are Milestone tasks, so one calendar view filtered to milestones is the master launch calendar across every company.

The Ariel and Justin ClickUp task breakdowns in the bundle are two worked examples of this runbook: seven epics each, roles not people, every subtask with a definition of done and an L-minus date.

Testing: attack the constraint

We are always testing, but we never test randomly. Every test comes from the company's biggest current constraint. The sequence: identify the constraint, quantify its impact, form a hypothesis, run the smallest valid test that can produce a decision, measure the one primary metric, decide, apply the learning, choose the next test from the next constraint. If the constraint is a broken checkout or missing tracking, fix it first; do not invent an experiment to satisfy a testing quota.

Know which one you are doing. A Fix corrects something broken. An Iteration improves a known version from prior results (a v02 hook on a winning angle). An Experiment is a controlled comparison under uncertainty. A Learning is a signal that is not yet a test ("Tuesday sends seem to open better"). Only Experiments enter the Split Test Lab, and only with a complete test card: current constraint, baseline, estimated economic impact, hypothesis, the one variable changed, control, challenger, one primary metric, minimum sample or spend or duration, decision rule set before it runs, owner, decision date, next action if won, next action if lost. When several tests qualify, run the one that scores highest on Constraint Impact × Confidence × Ease, each 1 to 5. No scoring system beyond this.

Every active company must have either one active experiment or one documented constraint-removal action. Not several at once; attention splits and attribution muddies.

The Monday and Friday questions

Monday's answers are written into the week's agenda task before anyone builds. Friday's answers close it, and the named next constraint becomes Monday's starting point.

Five saved views carry the pilot

The weekly hygiene audit, 10 to 15 minutes, before Monday planning

• Tasks missing an owner, a due date, or a Work Type
• WAITING tasks missing Waiting on or a follow-up date; stale Waiting on values on tasks no longer waiting
• [REQUEST]s in Slack missing ClickUp links; commitments living in Slack with no task behind them
• [BLOCKER]s that waited past the 60-minute bar
• Decisions missing implementation links; learnings missing next actions; experiments running without a complete test card
• Partner videos missing rights confirmation or a related task
• Tasks nobody has touched in 14 days; channels approaching 90 days of silence; launch channels and campaign lists past their archive date
• Post the counts as one [UPDATE] in #team-ops. These numbers are the Day-30 audit's raw data

Automation: earn it in phases

Phase 1, the first 30 days, is manual: templates, required fields, manual status changes, manual Slack links, manual weekly reports. Phase 2 automates the obvious transitions (reminders, notifications, escalations, form-to-task, partner-upload updates) only after 10 to 20 real examples have run by hand. Phase 3, the reporting layer (Slack summaries, follow-up task creation, CRM integration, dashboards, API scripting), only after the workflow is proven. Automate state changes, routing, reminders, and required fields. Never automate judgment. Automating a bad process just lets you fail faster. This phasing governs ClickUp workflow automation only: the Day-1 sales feed, the design intake form, and every launch-required delivery, payment, tagging, and tracking automation are not deferred by it.

The Roan pilot: minimum build

1. Roan folder: hub doc, Ongoing, Backlog, stamped clean. Active work migrated in; the old mess archived, not reorganized.
2. One real campaign run as a campaign list. When it is done, the cleaned-up list becomes the Launch Runbook template. Reality first, template second.
3. Ads Engine: queue, statuses, ad-brief template, naming convention (cr0042_priceanchor_hook01_vid_roan_v01).
4. Design Studio: queue, request form, internal turnaround targets (Urgent 24h, Standard 2 to 3 business days, Build scoped), revision cap.
5. Split Test Lab: board and test card. Empty until the constraint review sends something in.
6. The five saved views, built and pinned.
7. Monday planning and Friday review as recurring agenda tasks with the constraint checklists, walked from the views.
8. Weekly hygiene audit, logged as done or not.
9. Partner Content Queue: the request template, one mobile upload page, one cloud folder, run with one partner. Starts immediately; partner video is a live bottleneck.

Out of scope for the pilot: dashboards, advanced automations, API scripting, influencer guest access in ClickUp, advanced reporting polish, any workflow not required for the active Roan campaign.

Pass criteria, four straight weeks: Monday planning ran from ClickUp views, and Friday's async review used those views with reports in by 3pm CT and the pod lead's decisions recorded the same day; the hygiene audit found fewer than five violations; every design request entered through the form; no private side lists; every experiment decision documented; the current constraint documented every week; every active test traceable to that constraint. The Implementation Guide extends this to the 12-metric Day-30 gate in section 06. Before rolling to Ariel and Justin, add task estimates or another capacity method for design, chosen in the pilot's final week from 30 days of real throughput.

Rollout: the 30-day pilot

Source: Implementation Guide (build) and Rollout Playbook (training). Slack renames go live for all three creators on Day 1 because they are renames of rooms that already exist. The full ClickUp workflow pilots with Roan only. Nothing builds before Day 0 sign-off, and nothing gets redesigned mid-pilot.

• Day 0Adura signs off on the map, the decision flags D1 to D8, owner names, and status defaults.
• Day 1Slack build, half a day: paid plan confirmed, channel creation restricted to admins, renames per the mapping, new channels, descriptions from the template, pins, #announcements set to admin-post-only, sales-feed webhook fired with a test sale, a test refund, and a digest batch.
• Day 2ClickUp build, one day: three spaces, HQ lists, Offers Registry populated (Roan: two records), Roan folder, PRODUCTION queues, fields, statuses, Design Studio form. Migrate Roan's live work into Ongoing and campaign lists. No automations, dashboards, or reporting.
• Day 3Leadership announces and trains: the announcement copy, the five-minute Loom script (word for word), and the acknowledgment checklist are in the Rollout Playbook sections 18 to 20. Before using the announcement and the Loom script, replace their rollout sentences (they describe Roan piloting the communication standard first) with: "The Slack standard applies to everyone now. Roan pilots the full ClickUp workflow for 30 calendar days; Ariel and Justin keep their existing task lists until the rollout gate passes." Every team member reacts ✅ by end of Day 3. Rollout Day 3 is Pilot Day 1. The pilot runs 30 calendar days and must include four complete, documented weekly cycles.
• Pilot days 1 to 14Friendly-redirect era. Answer, then redirect, every time. Hygiene audits on pilot days 7 and 14. Managers enforce per section 07.
• Pilot days 15 to 30Steady state. Audits on pilot days 21 and 28. Wrong-room work messages now get moved, not just answered.
• Pilot day 30Audit against the gate below. Pass: build the Ariel and Justin folders, brief their teams, clone the system. Fail: fix the named friction; recheck a failed point-in-time metric after two weeks, and a failed four-week criterion passes only once four consecutive compliant weeks are documented.

Decisions Adura needs to make before Day 1

The Day-30 gate

Rollout requires all twelve metrics above, all seven four-week criteria in section 05, a working capacity method (task estimates or a capacity field) for design and any other constrained team, and a finished pilot campaign: its AAR completed and its cleaned-up list saved as the Launch Runbook template. Record the evidence and the rollout decision in HQ Issues & Decisions. Fail any item and you fix that item, not the design: point-in-time metrics are rechecked after two weeks, four-week criteria need four consecutive compliant weeks. The audit judges friction, never aesthetics.

Leadership's job: make the system stick

This is the section I care most about. In week one, all three team members told me some version of the same thing: we have systems, we just don't work the systems. ClickUp existed. Slack existed. Work still slipped, because ownership and follow-through were inconsistent. A better design does not fix that on its own. Enforcement does.

The feedback loops

Manager enforcement standards

1. Model it first. Managers label every work post, seal every decision, and never let their own requests skip ClickUp. The team does what leadership does, not what leadership says.
2. Redirect every miss in your channels, warmly, within the day. Weeks 1 and 2: answer, then redirect ("Answered above. For next time this lives in #creator-roan"). Week 3 onward: move it, don't answer in place. The kindness stays; the shortcut stops working.
3. Bounce unlinked requests with the template, every time, including from other managers. The work starts when the ClickUp link exists.
4. Protect -comms discipline absolutely. Internal content in a -comms channel gets handled the same hour. Never redirect the creator; route it yourself.
5. Praise publicly in #kudos when someone routes, labels, or bounces correctly in the first two weeks. Reinforcement beats correction.
6. Route findings to the individual, never to the team as a new ritual. The hygiene audit produces direct conversations, not new meetings.

What Adura's part looks like

• Two minutes of public buy-in at the rollout announcement, so the team works the system instead of around it.
• His own requests carry labels and ClickUp links. His own decisions get filed. The team watches the founder more closely than anyone.
• Client communication moves off his phone and into the -comms channels, with an account owner named per creator. Until that happens, every creator relationship depends on Adura's availability.
• Decision rights written down: what the Director decides alone, what needs his yes. The Director 4R draft has the list to start from.

How you know it is working

The redirect count trends down week over week. Nobody asks "wait, what did we decide?" because a search for [DECISION] answers it. The hygiene audit finds fewer than five violations. Monday runs from the views instead of from memory. The calendar gets quieter, not busier. If any of those reverse, the answer is a direct conversation with a person, that day.

The team

From hour-long calls in week one: goals first, then how each person likes to be managed, then the gaps they see. Common threads across all three: nobody was clear on who owns what, tasks were assigned to the room, the numbers weren't visible enough to know what to optimize, and meetings were too many and too long. Weekly 1:1s with each of them were being set up when I left; make them standing in your first week.

Hiring pipeline, as of Aug 20

• Copywriter, hire #1. Brief out to a part-time copywriter I've worked with and trust (named in the week-one report). Status after Aug 21 unknown to me.
• Video editor and designer on trial tasks. Keep / pass reads were due the following week.
• Funnel builder. Intro call set up by Adura.
• Confirm where each of these landed before you open any new search. Hiring triggers are in the pod structure doc: contractors first, convert anyone sustaining 25 to 30+ hours a week for a month.

Work in flight

Everything here is as of September 1. Dates may have moved. The first thing to do with each item is confirm where it actually stands today.

Ariel: Personal Brand Playbook · launch Sep 7

• $27 six-module video workshop plus the Face Card Agent. Three order bumps ($17 / $17 / $9), a $67 to $97 Toolkit one-click upgrade. All content client-supplied and final.
• Scope: sales page, checkout with bumps, OTO, thank-you; member portal gated per SKU; instant zero-touch provisioning; refund → revoke; access email, 5 to 7 onboarding emails, 2 to 3 cart recovery, 2 to 3 Toolkit follow-up; pixel, GA4, UTM kit, KPI dashboard with day 0/7/14/30 cohorts.
• Targets to confirm: sales page CVR 5%+, bump attach 25%+, OTO take 10%+, AOV $40+, purchase-to-access under 2 minutes, refunds under 5%, 100% attributed.
• Plan: Plan Aug 21 to 26, Build Aug 26 to Sep 2, Wire Sep 2 to 4, freeze Sep 5, live Sep 7, 48-hour monitoring, day-3 KPI readout Sep 9. Seven epics with every subtask's definition of done are in the ClickUp task breakdown.
• Open at kickoff: platform stack (cart, portal, email) and the Toolkit price. Biggest risks: a stack decision dragging, agent-setup friction turning into refunds, entitlement mapping across 16 purchase paths.
• Traffic is Ariel's organic audience. Paid media and ad creative are a separate decision after the readout; do not activate the runbook's ad-batch tasks for this launch.
• Do now: confirm whether the launch went live on Sep 7 and whether an AAR happened. This is an evergreen offer with no cart close, so the launch window ends at the day-3 readout (Sep 9 in the brief) and the AAR is due within five days of it; schedule it if it has not happened. Get the day-3 numbers against the targets above. If the launch slipped, find where the build stalled and put an owner on it.

Justin: 10M Shares Playbook · kickoff Sep 3, launch Sep 24

• $27 pure-information front end (9 myths, 7 Share Triggers, The Cook Up, "What 9.9M shares bought"). Bumps $17 / $27 / $34 (50 Openers, Cook Up Tapes, Bundle). $197 First Month Written Pack upgrade, $97 downsell. Information at $27, implementation at $197.
• Plan: Plan Sep 3 to 9 (PM-led while the build team clears Ariel), Build Sep 9 to 17, Wire Sep 17 to 21, freeze Sep 22, live Thu Sep 24, readout Mon Sep 28. Same seven-epic structure.
• Open at kickoff: platform stack, downsell structure ($97 two-pay vs Month Prompt alone), whether the Bundle replaces or stacks with single bumps at checkout.
• Traffic is Justin's organic audience. Paid media is a separate decision after the readout; do not activate the runbook's ad-batch tasks for this launch.
• The initial launch window ends at the Sep 28 readout if the dates hold. End the daily standups there and hold the AAR within five days of it. If the launch moves, the launch owner records the revised window end.
• Copy state: two copywriter drafts (v1, v2) got copy-chief feedback on Aug 31; the approved direction is the rewrite plan; sales page v3 was written from it (angle: heresy plus receipts, working headline C1). A voice spec built from Justin's own transcripts is in the folder. Read it before anyone writes a line for him.
• Open items you inherit from me: the headline choice (v3 lists three finalists, one of them gated on a screenshot), the screenshot inventory for every celebrity repost named on the page, and confirmation of the current approved copy with Hamza. V3 stays a draft until those approvals are recorded.

Chris Jefferson · CRO real estate offer

Hamza was onboarding him when I left, scoped at one to two weeks. I built nothing for this and have no brief. Before it goes further, it needs the same shape as the other two: a project brief, a minimal interim ClickUp task list during the pilot (the runbook template does not exist until the Roan pilot campaign finishes), migrated after the gate passes, and a decision on whether it clears the launch bar. See section 11 on whether it should be running at all right now.

Roan: Performance Tracker · live Google Sheet

• Nine tabs: Dashboard, Daily, Rep Daily, Deals, Weekly Summary, Cohorts, Monthly Summary, Rep Report, Lists. Two revenue streams tracked separately: front-end (self-serve: tickets, bumps, upsells) and high-ticket (rep-closed). Headline KPI of the split is Front-End Spend Coverage: front-end cash divided by ad spend; over 100% means front-end cash covered the ad spend; other costs still apply.
• The Dashboard auto-diagnoses the biggest constraint per funnel (opt-in, show, schedule, call show, close rate vs editable targets) with a dollar-impact estimate. That output should feed the Monday constraint review directly.
• It is seeded with sample data. Marenti coordinates the cutover to real numbers: clear the synthetic inputs (yellow cells only, never formula cells), assign one owner each for Daily entry, Rep Daily entry (calls only), and Deals entry, and reconcile the first real reporting period against the payment platform. High-ticket deals are entered only on Deals, one row per closed deal, with a date typed in the installment Paid column when money lands (that drives the overdue chase list and the receivables forecast); Daily high-ticket totals and Rep Daily deal totals derive from it.
• After about a month of real data, recalibrate the CONFIG targets on the Lists tab. Never rerun the build script; it wipes all tabs.

Marketing Command Calendar

A static planning prototype: a one-page view of launches, live moments, sequences, gates, tests, and AARs across creators. Ariel and Justin milestone dates come from the briefs; owners, Health, readiness gates, and Roan's dates are illustrative. The ClickUp and Slack buttons are not connected. Use verified launch records for operating decisions until the sync is built, and do not build the sync until the manual pilot proves the process.

The week-one build list: what got built

The numbers the team asked for

In week one we were flying blind: no cohort view, no benchmarks, no fully-loaded cost per customer, and no clarity on what each person should be optimizing for. Ahmad and Hamza both asked for the same fix. Here is the framework; most of the plumbing is specced in the launch briefs and built in the Roan tracker.

Publish the benchmarks. Once the first real month of data is in, put a target next to every number above, per offer, and pin it where the team sees it. Ahmad asked for exactly this and he is right. Numbers get read before the meeting; the meeting is about what they mean.

Email cadence. The play I run elsewhere: four sends a day, each to a tight engagement segment (active, less active, opened in 30 days, clicked in 30 days, visited in 30 days), with auto-tagging so it runs itself and the same segments uploaded as custom audiences. The minimum here is three value emails a week between promos, built around the lead magnets. That protects deliverability and keeps us top of mind between launches.

My read: where I'd focus

This section is opinion. It is what I would do in your seat; take what is useful and leave the rest.

One creator, one offer, one funnel, until the checklist is proven

When I left there were three launches in motion (Ariel Sep 7, Justin Sep 24, Chris Jefferson onboarding), new offers being discussed, and a Roan pilot that had not started. Every one of those was a good idea on its own. My concern is that concurrent launches plus the pilot exceed the team's current capacity, and that every new client inherits a process that has not been proven yet. I would agree a priority order with Adura before adding work.

The business sells trust. A creator hands us an audience they spent years earning. If the delivery leaks (slow access, a refund that doesn't revoke, an email that lands in spam, a number nobody can find), the creator notices before we do, and reputation is the one asset that does not come back on the next launch. Onboarding more clients onto a leaky process does not scale the business; it scales the leak.

So: pick one creator and go all in. Solidify one offer and one funnel end to end. Get the checklist to the point where the team can execute it fast and at a high level without you in every thread. Then, and only then, expand. Use the result as the proof that wins the next creator. Prove, document, duplicate.

If it were completely up to me: Roan is the established business, so keep running it and maintain what already works there. It stays the process pilot for the ClickUp workflow because it is the most mature. Justin has the highest potential of the three, so nearly all of the growth effort would go to Justin, with Roan maintained rather than expanded. The team's creative and media firepower should sit behind one creator at a time. Choose, commit, and say it out loud so the team stops splitting itself.

Fix the leaky bucket before adding water

Concretely, before any new offer or new client: cohort revenue visible at day 0, 7, 14, 30 for the offers already live; instant delivery proven with a test-purchase matrix; refund and failed-payment handling proven; email segmented with a value cadence running; and one named constraint per company being attacked every week. The Pod OS gives you the rule: every active company has exactly one constraint being attacked. If you cannot name Roan's constraint and its number, you are not ready to add Ariel's, let alone a fourth.

Decision rights, and pushing decisions down

The team's loudest request was clarity: who owns what, and the freedom to own it. Adura has a very clear picture of how he wants things done. That is an asset when it is written down as a standard and a bottleneck when it lives as approvals routed through him. Your job is to turn approval-dependent work into documented standards the team can execute: get his standards into checklists and SOPs, then hold the team to the checklist instead of routing the work through him. Agree in week one what you decide alone and what needs his yes, and write it down. The Director 4R draft has a decision-rights section to start from. Leadership's role is to set the standard and enforce the system, not to be the only person who can approve a task.

What this looks like at 90 days

The Roan pilot has passed the gate. The launch runbook exists as a template because it was built from a real campaign. Ariel and Justin are stamped from it, both with a constraint named every Monday. The team reads its numbers before meetings and argues about what they mean instead of what they are. Then a new client signs, and the offer is live in 30 days because the machine has done it before.

Where everything lives

Everything this document depends on is linked below, or download all of it at once: Pod-Handoff-Bundle.zip (includes this document as a PDF: Pod-Handoff.pdf). One exception: the per-offer economics calculator from week one is not included.

Shareable web copies of the four operating documents also exist (Slack Blueprint, Implementation Guide, Rollout Playbook, Operating Rhythm); the PDFs in the bundle are the same content and travel better.

Your first 30 days

A suggested order. It follows the pilot timeline in section 06, with the people and in-flight work folded in. Rollout Day 3 is Pilot Day 1 and the pilot runs 30 calendar days, so the gate lands around week six in your seat, not on your 30th day.

Week 1: read, meet, decide

• Read this document, then the Rollout Playbook, then the Implementation Guide, then the Pod OS. Two hours total.
• Confirm the status of Ariel's launch, Justin's build, and Chris Jefferson. Name who owns each launch (section 09, first move). Schedule Ariel's AAR if it has not happened.
• Hour with each of Ahmad, Hamza, and Marenti, using section 08. Set standing weekly 1:1s.
• Sit with Adura: decisions D1 to D8 and Q1 to Q4, decision rights in writing, payroll and overhead numbers for the CAC model, and his two minutes of public buy-in at the announcement.
• Name the system owner (Marenti, as project manager, is the natural fit) and the Roan campaign that anchors the pilot.
• Write the three roles-and-responsibilities docs. It is the gap the whole team named first.
• Decide, and say out loud, which creator gets the team's focus (section 11).

Week 2: build and announce

• Day 0 sign-off. Day 1 Slack build. Day 2 ClickUp build. Day 3 announcement, Loom, acknowledgment checklist. The pilot clock starts on Day 3.
• First Monday Game Plan run from the This Week view, with one constraint named per company. First Friday reports or Looms in by 3pm CT, decisions posted the same day.
• Start the Partner Content Queue with one partner. Document every question they ask; each one is a defect in the brief.
• Redirect every wrong-room message, bounce every unlinked request, praise every correct one in #kudos.

Weeks 3 to 6: operate and hold

• Hygiene audits on pilot days 7, 14, 21, and 28, counts posted in #team-ops.
• Justin launch week if the date held: daily 10-minute standup, one [UPDATE] a day, standups end at the Sep 28 readout, AAR within 5 days of it with owned tasks.
• Real data into the Roan tracker; first Monday where the constraint comes from the sheet, not from memory.
• Pilot day 30: run the gate, which also requires the pilot campaign's AAR done and its list saved as the Launch Runbook template. Pass, then stamp Ariel and Justin. Fail: recheck a failed point-in-time metric after two weeks; a failed four-week criterion needs four consecutive compliant weeks.

Do not

• Do not redesign the system mid-pilot. Change it only at an audit, from evidence of friction.
• Do not add ClickUp workflow automations, ClickUp dashboards, or the calendar sync until the pilot has run 10 to 20 real examples by hand. The design intake form, the sales feed, and every launch-required delivery, payment, tagging, and tracking build stay in scope.
• Do not add a standing daily meeting. If you feel you need one, fix ClickUp accuracy.
• Do not rerun the Roan tracker build script. It wipes the sheet.
• Do not take on a new client until the Day-30 gate passes. That last one is my opinion; the rest are the standard.