Measure the weekly habit
Review completion and review minutes matter because the product is a weekly operating rhythm, not a passive database.
The paid question is behavior, not feature applause.
The wizard forces the week-one report to answer four subscription questions: did the agent complete the review, did the Money List surface real relationship work, did reviewed drafts/prep stay manual-use only, and did proof attach to more than one protected relationship?
Count reviewed work
Money List opportunities, approved-for-copy drafts, prep briefs, and logged outcomes show whether the Pro workflow created useful local work product.
Prove breadth safely
Relationships with attached missed-moment proof show whether the board protected more than one relationship while the approval wall blocked automation, sends, scraping, and CRM/MLS writes.
Step 02 / Adjust sample counts
Markdown report
Weekly Review Report
JSON report
Structured review data
Download/copy buttons run in the browser only. They do not submit, store, transmit, contact, publish, email, text, sync, track, or connect to any external system.
What Tim should look for
Pass/fail thresholds.
- Proceed narrow: weekly review completed, 3+ return sessions, 3+ reviewed drafts/prep briefs, proof attached to 2+ relationships, approval gates respected, and return intent is credible.
- Simplify: value is visible but onboarding is confusing, proof clusters on one relationship, or agents still ask why this is not their CRM; reduce week two to Today Board + Appointment Prep + one follow-up draft.
- Pause: demand centers on autopilot sending, scraping contacts, CRM/MLS writes, unsupported lead promises, fair-housing-risky language, or compliance shortcuts.
No-field design choice
Buttons only by default.
This artifact intentionally avoids forms, text inputs, textareas, and selects. The safest first exporter uses fictional/sample counts and browser-local state. If Tim later approves a real pilot, real data entry should still be gated by an approved data policy and human review.
AI may prepare
Draft, organize, summarize, score, route, remind.
AI may create local weekly reports, identify missing facts, summarize approved notes, draft review language, and prepare Markdown/JSON files for human review.
Human must approve
Every external or sensitive action.
Humans approve participants, data sources, facts, public claims, legal/compliance-sensitive statements, fair-housing-sensitive language, testimonials/endorsements, vendor/resource recommendations, sends, publishing, lead capture, paid ads, account creation, terms acceptance, CRM/MLS/system changes, and every external action.
No live pilot action.
- No recruiting, outreach, posting, publishing, scraping, email/SMS sending, lead capture, checkout/payment, account creation, terms acceptance, analytics, paid ads, or public launch.
- No private CRM/MLS/brokerage/lender/vendor/buyer/seller/transaction data.
- No CRM, MLS, calendar, email, SMS, ad platform, brokerage, lender, vendor, or transaction-system integration or writes.
- No legal, tax, lending, pricing, disclosure, contract, agency, fair-housing, endorsement, testimonial, advertising, or compliance-sensitive claims without human/professional review.
Next best improvement
Package week-one exports into a launch decision sheet.
After the wizard, the next artifact should convert one exported weekly report into a single launch-readiness scorecard for Tim: proceed, simplify, or pause — still local-only and draft-safe.