The Comms Dept

Productized done-for-you communications service. PCT becomes a church’s remote communications department. Live private beta, 6 paying. App in daily team use. No public offer page — Company OS is the source. Do not invent a marketing URL.

Current offer (August 2026)

  • $299/month — operate the comms department every week. Monday: Weekly Package (coming Sunday) + Sunday Review (last Sunday). 3 stage slots from Ministry Levels. Church DNA Document. Calendar synced. Loop: deliver → perform → review → adjust.
  • $1,999/month — everything in $299 plus custom measurement (“are people taking next steps?”). 80% common / 20% church-custom.
  • Annual: two months free on $299 is still the offer.
  • Profit share: 25% of The Comms Dept profits split evenly among the Executive 7. Attached only to The Comms Dept.

May $497 / $997 / $1,997 and the five named deliverables (Brand Voice Workshop, Story Database, Quarterly Promotion Calendar, Quarterly Story Campaign, Weekly Comms Package) are not the current offer. Story Database is dead. Quarterly story campaigns are dead. Bulletin as weekly output is not shipped (likely when The Comms Dept goes public). See 2026-marketing-spec as historical / non-governing.

Operating model

Paying is not the same as weekly operate. Onboarding is phased and machine-gated, not merely time-based.

High-level flow:

paid signup → Church DNA → setup → Ministry Levels / customer tasks → production kickoff → invisible buildout → first Monday unlock → steady state

Any open client task prevents production kickoff. Open tasks after levels are approved: customer-blocked. Levels approved, no open tasks, and no kickoff or first delivery: company-blocked.

All customer-facing output is human-reviewed before first visibility. First delivery unlocks the weekly package and the other production surfaces together, not piecemeal. After unlock, the church enters the recurring weekly production rhythm.

Canonical implementation: The-Comms-Dept/the-comms-dept/docs/onboarding.md in The Comms Dept codebase. If that document and current code disagree, code wins and the operational document should be corrected. That rule applies to the product repo, not to Company OS.

What’s in this folder

  • 2026-marketing-spec.mdhistorical / non-governing. May 2026 marketing spec. Kept as a record. Not current operating truth.

How this connects

  • Funnel role: still the upsell branch for churches that do not have someone to run communications week-to-week. Pitch language and email sequence in follow-up-sequence Part Three are the last written version, not line-by-line re-verified.
  • Platform: most clients also come through the Makeover / Nucleus path. The public Makeover page does not mention The Comms Dept.
  • Methodology source: the service operationalizes the 7-building-blocks.

Status

  • Live private beta: 6 paying.
  • App: in daily team use.
  • Marketing site: no public offer page. Company OS is the source.
  • Profit-share alignment: the executive 7 (teamsensitive) collectively receive 25% of The Comms Dept profits.
  • products — canonical product entry
  • priorities — August 2026 jobs
  • follow-up-sequence — the conversion path (last written version)
  • Implementation: The-Comms-Dept/the-comms-dept/docs/onboarding.md in The Comms Dept codebase