Project Orientation

S2S CRM

30-second project scan

Working CRM. Launch not proven yet.

S2S CRM is close to replacing Jobber for Whistler Peak Cleaners. The app exists and key workflows are code-backed, but launch should wait until the live host, database, backup, session behavior, staff access, and final browser smoke are proven.

Project stage
Launch readiness
Main blocker
Launch-host proof
Business goal
Replace Jobber for daily operations
Docs health
7 docs need review

Best next agent request

Run the launch-host readiness pass.

Run the launch-host readiness pass: verify the deploy target and secrets, prove backup/restore, run read-only readiness checks, confirm session behavior, create approved staff access only after those gates, then complete the final real-browser smoke with representative Whistler data.

Do not delegate yet

Production writes or launch changes.

Do not run reset/import scripts against production.

Launch Gates

What has to become true before the next milestone

These are delegation checkpoints for a nontechnical project manager.

Gate 1

Target host and secrets

Confirm the deployment target, database project, branch, and required environment values.

Ask: identify the intended launch target.

Gate 2

Backup and rollback

Record backup proof, restore confidence, and a named rollback owner before any production write.

Ask: prove backup and rollback readiness.

Gate 3

Schema readiness

Confirm the launch database includes newer client-property and recurring-series structures.

Ask: run read-only readiness checks.

Gate 4

Session behavior

Verify production session secret, session table behavior, restart persistence, and staff login.

Ask: test launch-host login behavior.

Gate 5

Approved staff access

Create staff users only after target, backup, and session gates are confirmed.

Ask later: create approved access.

Gate 6

Final browser smoke

Run representative Whistler data through clients, properties, jobs, requests, recurring work, invoices, and CSV export.

Ask: prepare and run the smoke checklist.

Work Lanes

Where the office PM can point agents

Each lane turns project state into a safe, plain-language request.

Launch setup

Host, database, secrets, backup

Needs proof before launch decisions.

Ask an agent: Check the launch readiness docs and tell me which approval gate is next.

Avoid: Running production writes before target and backup confirmation.

Daily CRM workflows

Clients, properties, jobs, schedule, invoices

Code-backed and close to operational.

Ask an agent: Prepare the final smoke checklist for daily staff workflows.

Avoid: Assuming local or staging proof equals launch-host proof.

Jobber cutover

Final exports, rehearsal, cleanup, signoff

Still requires human review and forward-only discipline.

Ask an agent: Summarize the Jobber cutover plan and missing approvals.

Avoid: Treating the CSV import helper as a full migration system.

Validation

Checks, smoke evidence, admin tools hidden

Focused tests exist; browser launch proof remains manual.

Ask an agent: Run safe checks and report what still needs live-host evidence.

Avoid: Claiming launch approval from docs freshness alone.

Accounting

CSV/manual path or proven QuickBooks

CSV/manual is the safer soft-launch path.

Ask an agent: Compare launch paths for CSV/manual accounting vs QuickBooks.

Avoid: Enabling QuickBooks before real tenant sync is proven.

Agent Context

Evidence belongs below the scan

Useful for agents and audits; secondary for the office PM.

What exists

  • Launch as a trusted internal staff CRM plus public job-request form.
  • Keep the first launch practical: CRM-owned operating records, service properties for multi-location clients, in-app invoices, invoice CSV/manual accounting, and QuickBooks only if the real tenant flow is proven before cutover.

What is not proven

  • Production/staging launch-host DB/schema/session readiness is not proven.
  • The launch DB has not been proven to include the newer recurring-series and client-property schema changes.
  • Backup/restore proof and rollback owner are not recorded for cutover.
  • Jobber cutover rehearsal and final exports are still outstanding.

Source packet

  • Generated 2026-07-10 from the active Markdown packet.
  • Markdown remains the source of truth; this dashboard adds no execution authority.

Source Health

Files behind this dashboard

Missing active docs
0
Needs review
7
Old but quiet
0

Freshness check

  • Needs review: docs/current-state.md (2026-06-05)
  • Needs review: docs/next-steps.md (2026-06-02)
  • Needs review: docs/product-plan.md (2026-06-02)
  • Needs review: docs/design-direction.md (2026-06-02)
  • Needs review: docs/architecture.md (2026-06-05)
  • Needs review: docs/validation.md (2026-06-02)
  • Needs review: docs/session-brief.md (2026-06-02)
README.md

Repo overview, commands, and documentation entry point.

Found
docs/current-state.md

What exists now, what works, what is incomplete, and stale signals.

Needs review - reviewed 2026-06-05
docs/next-steps.md

Recently completed work, recommended next moves, and work to avoid.

Needs review - reviewed 2026-06-02
docs/product-plan.md

Product north star, current product shape, and roadmap posture.

Needs review - reviewed 2026-06-02
docs/design-direction.md

Experience principles, visual direction, and interface guardrails.

Needs review - reviewed 2026-06-02
docs/architecture.md

Stack, app structure, data model, boundaries, and technical assumptions.

Needs review - reviewed 2026-06-05
docs/validation.md

Validation commands, QA expectations, and evidence requirements.

Needs review - reviewed 2026-06-02
docs/session-brief.md

Compact restart context, immediate next move, caveats, and reminders.

Needs review - reviewed 2026-06-02