Pilot Kit

Everything needed to invite and run the first pilots.

CCM is ready for a tiny warm cohort when the domain is live. This page keeps the invite, onboarding, dashboard, and feedback workflow in one place.

Open intake View dashboard preview Read pilot guide

Invite

Warm outreach message

I’m opening a small free design-partner pilot for Compliance Changelog Monitor. It watches important public pages like pricing, terms, policy, partner, regulatory, or docs pages and sends human-reviewed alerts when something meaningful changes.

If you’re interested, send a few public URLs your team checks manually or worries about missing. We’ll run source preflight first, then only monitor sources that are reliable enough to trust.

There’s no paid ask for the first pilots. I’m looking for signal quality, workflow feedback, and a better understanding of what would make this genuinely useful.

Onboarding

What happens after they say yes

  1. Send the intake link. Ask for name, work email, company, URLs, and the risks they care about.
  2. Confirm receipt. Use the admin queue and Telegram notification to confirm the source list arrived.
  3. Run source preflight. Mark each URL active, needs setup, held, or rejected before making promises.
  4. Send source-status note. Tell the pilot which URLs are covered, which are not, and why.
  5. Create the workspace view. Replace sample dashboard data only after there is real pilot state.
  6. Ask feedback after first readout. Keep feedback specific to source quality, usefulness, trust, and missed context.

Agent Operating Model

Who handles what

Pax

Maintain the site, admin queue, pilot docs, analytics checks, and launch ledger.

Kit

Review public copy, invite language, business risk, and red-team claims before outreach.

Rook

Review watcher reliability, source-preflight calls, and monitoring failure modes.

Pilot Answers

Plain answers to likely questions

How do I sign up?

Submit the intake form. There is no self-serve account step for the first pilots.

What do I get first?

A source-status note showing which submitted URLs can be monitored reliably.

When do I see a dashboard?

After preflight, once there are approved, held, and rejected sources to show.

Who sees my submission?

The operator team. Intake details are stored for manual preflight and can be deleted on request.