ddkc://swarm

2026-07-22 · WEDNESDAY RELEASE · CO-FOUNDER BRIEF · ~8 MIN READ

What Dream Office Is
(Swarm Office)

A readable brief for Victor and Aria: what the office product is, what it is not, and why Wednesday becomes our permanent release day — starting with this post.

Product
Swarm Office
Working name
Dream Office
Brand
WeAreSwarm
Engine
Dream.OS

One-Sentence Answer

Dream Office (Swarm Office) reconnects inactive customers and follows up on leads — with every outbound message human-approved — while Dream.OS stays hidden as the engine.

Parent brand: WeAreSwarm. Core engine: Dream.OS. Foundation artifacts validate PASS. MVP is defined; live customer sends are still gated.

Who It Is For

Ordinary owner-operated and small-staff local businesses — dental offices, veterinarians, pharmacies, restaurants, contractors, professional services — that already have a customer or lead list, but no marketing operations team and no hours left to run follow-up by hand.

Primary problem: recoverable revenue dies in the list. Inactive customers never get reconnects. Inbound leads go unanswered. The owner knows the list has value and still cannot personally draft, review, send, and track at scale.

Promise: bring back customers you already have and follow up with leads you already earned — every message reviewed before send, every result tracked to revenue.

First Wedge

MVP workflow: customer reactivation + lead follow-up.

mvp loop
Import list
→ normalize / dedupe
→ classify inactive + lead follow-up
→ draft messages
→ human approve
→ send
→ track replies
→ attribute outcomes
→ report
  • No outbound without explicit human approval
  • No billing automation in MVP
  • No Dream.OS internals on the customer surface

What Customers See

Follow up with leads. Reconnect inactive customers. Confirm appointments. Prepare campaigns. Request reviews. Process routine admin. Track results and approvals.

They do not see agents, prompts, YAML, SSH, worktrees, repositories, or model providers. That separation is the product — not a temporary cover story.

Wednesday Release Doctrine

From today forward: Wednesday is the biggest shipping day. Every Wednesday the swarm ships one publicly readable, amazing closure — not vibes, not status-only chat.

A Wednesday release can be a product brief, a live page, a payable CTA, a deploy receipt, or a verified pilot gate. It must be consumable outside the fleet so co-founders (and later customers) can read it without opening a worktree.

“Wednesday ships something amazing — every week.”

Finish Today

  1. Publish this brief on DaDudeKC + WeAreSwarm (this post).
  2. Victor + Aria read it and lock naming: Dream Office vs Swarm Office for public use.
  3. Pick next Wednesday track in writing: Swarm Office MVP wedge vs Bot Lab first payment path.

Cash north star this phase remains Bot Lab first payment. This brief is product clarity for co-founders — not a second economic loop.

Open WeAreSwarm copy →

What This Is Not

  • Not a claim that Swarm Office is fully live-sending to customers
  • Not permission to blast without approval gates
  • Not a replacement for Bot Lab as this week’s cash offer