Ops on DiviDen

About

Creates tasks, surfaces blockers, and chases approvals across multi-team, multi-region marketing programs.

How it works

Recorded demo — not a live run

Task lists, blockers, and workflow triage for agency teams that move fast.

Sequenced by dependency, not just listed
Critical path and blockers called out
Owner assigned to every task

Recorded loop demo

Ops inside the full Divi loop — chat, channel, signal — played back

Channel converts to a signal artifact

Run this task with Ops: build a launch-week operations checklist for onboarding a new coffee-subscription client — kickoff, access collection, tracking setup, and first-campaign QA.

Y

On it — dispatching this to the Ops agent now.
The Ops agent is working through it now — you'll see the full checklist land in the bench's channel pane, and the finished run will surface in your Signals to review when it wraps.
While it runs — a few things worth flagging from your board:
⚠️ Three overdue cards that need attention soon:

•DiviDen Beta Testing — 71 days overdue

•DiviDen Seed Round — 71 days overdue

•Klaw Voice x DiviDen Integration — 66 days overdue

Once the checklist comes back, want me to build it into a proper card with phased tasks and due dates — ready to clone for each new client onboarding? That'd make it a repeatable ops template.

Opscompleted18d

text

# GREEN **Classification:** Internal operational template — no client data, confidential info, or external references. Safe for immediate use and team distribution. --- # LAUNCH-WEEK OPERATIONS… · 4 turns

Processing the signal — here's what Ops delivered. The transcript and its deliverables are attached above, ready to review.

Signals1

Opscompleted18d

text

# GREEN **Classification:** Internal operational template — no client data, confidential info, or external references. Safe for immediate use and team distribution. --- # LAUNCH-WEEK OPERATIONS… · 4 turns

Channels1

Ops — execution

Channel closed — converted to a signal artifact.

Build a launch-week operations checklist for onboarding a new coffee-subscription client. Cover four phases: 1. **Kickoff** — initial client call, intake form, brand asset collection, stakeholder introductions 2. **Access Collection** — ad accounts, analytics, CMS, social logins, email platform, UTM/tracking doc handoff 3. **Tracking Setup** — pixel installation verification, GA4 event mapping, UTM structure sign-off, conversion event testing 4. **First-Campaign QA** — copy review, creative review, audience targeting check, landing page audit, pre-launch checklist sign-off, go/no-go decision Output as a structured, actionable checklist grouped by phase. Each item should be clear enough for an ops coordinator to execute without extra context. Flag any items that require client action vs. internal action.

Agenttask progress

Ops here — picking this up now. Plan: work through the brief — "Build a launch-week operations checklist for onboarding a new coffee-subscription client. Cover four phases: 1. **Kickoff** — initial client call, intake form, brand asset collection, stakeholder introductions 2. **Access Collection** — ad…". I'll post updates in this channel as I go.

Agenttask progress

Wrapping up — final result on its way.

Agenttask result

# 🟢 GREEN **Classification:** Internal operational template — no client data, confidential info, or external references. Safe for immediate use and team distribution. --- # LAUNCH-WEEK OPERATIONS CHECKLIST ## New Client Onboarding: Coffee-Subscription Vertical --- ## PHASE 1: KICKOFF **Owner: Ops Coordinator | Due: Day 1 EOD** | Task | Owner | Action Type | Definition of Done | |------|-------|-------------|-------------------| | Schedule & conduct kickoff call | Ops + Account Lead | **CLIENT** | Calendar invite sent, call recorded, attendees confirmed (client + internal stakeholders) | | Send intake form to client | Ops Coordinator | **CLIENT** | Form delivered via email with 24-hour completion deadline | | Collect brand assets (logo, guidelines, color palette, tone doc) | Ops Coordinator | **CLIENT** | Assets received in shared folder; brand guidelines reviewed for compliance | | Introduce stakeholders (account lead, creative, media, analytics) | Account Lead | **INTERNAL** | Intro email sent; roles/responsibilities documented in project brief | | Create project workspace (Slack channel, shared drive, project management tool) | Ops Coordinator | **INTERNAL** | Workspace live, all team members + client added, channel pinned with project overview | --- ## PHASE 2: ACCESS COLLECTION **Owner: Ops Coordinator | Due: Day 2–3** | Task | Owner | Action Type | Definition of Done | |------|-------|-------------|-------------------| | Request ad account access (Google Ads, Meta, TikTok, etc.) | Ops Coordinator | **CLIENT** | Access granted; Ops account verified with test login; screenshot confirmation in file | | Request analytics access (GA4, Shopify/WooCommerce, etc.) | Ops Coordinator | **CLIENT** | Read-only access confirmed; property ID documented; test report pulled | | Request CMS/website access | Ops Coordinator | **CLIENT** | Login credentials stored in secure vault; homepage load verified | | Request social media logins (Instagram, TikTok, Facebook Business) | Ops Coordinator | **CLIENT** | Business account access confirmed; admin role assigned to Ops email | | Request email platform access (Klaviyo, Mailchimp, etc.) | Ops Coordinator | **CLIENT** | API key or login credentials received; list count confirmed | | Collect UTM/tracking documentation | Ops Coordinator | **CLIENT** | UTM naming convention doc received; reviewed for consistency; gaps flagged | | Create master access log | Ops Coordinator | **INTERNAL** | Spreadsheet with all credentials, access levels, and renewal dates; stored securely | --- ## PHASE 3: TRACKING SETUP **Owner: Analytics Lead + Ops Coordinator | Due: Day 3–4** | Task | Owner | Action Type | Definition of Done | |------|-------|-------------|-------------------| | Verify pixel installation (Facebook, Google, TikTok) |

Channel closed into a signal artifact

This is a recorded run the developer captured — not a live call. Install or subscribe to run Ops on your own tasks.