Monday client handoff

Send the clean link. Screen-share the private Hub.

Use this page before sending the demo package. It separates public client links from guided/protected Hub screens so the walkthrough feels polished and access stays intentional.

Email-ready package

Give the client one clear path instead of a pile of links.

Visual backup

Public screenshots PDF

https://askaires.com/sales-deck/useaires-front-end-current.pdf

Keep this as backup collateral. It was refreshed after the client-facing copy polish, so it now matches the public review path, Rising Hills preview, Contact launch intake, and live private-Hub walkthrough framing.

Safe to send

These links can go directly to a client before Monday.

Monday operator path

Use this sequence when you are running the demo.

1

Send the public review path

Email the Client Email Landing Page first. It gives the broker one clean prep path into Rising Hills, the Hub overview, and the product story without private credentials.

2

Sign in as the Rising Hills broker demo account

Use the role-specific Rising Hills broker-admin demo account, then open the Broker Dashboard Presenter Mode view before the call.

3

Confirm presenter cockpit

Open /admin/dashboard?client_id=client_rising_hills and confirm it shows Presenter Mode, Presenter Start Here, Client Demo Command Center, Post-Demo Follow-Up Pipeline, and the selected Rising Hills client context.

4

Walk the protected workflow live

Screen-share Broker Dashboard Presenter Mode, Command Center, Launch Wizard, Go-Live Handoff, Launch Artifact Vault, Security Review, Lead Inbox, Smart Lists, Registration, Agent Queue, Routing, and Proposal Builder in that order if time allows.

5

Close into first-launch scope

Ask for the first community/project, roster, listing links, routing rules, CRM/export needs, launch timeline, and support package.

Screen-share first

These screens are powerful, but they belong in a guided walkthrough.

Broker Dashboard Presenter Mode

/admin/dashboard?client_id=client_rising_hills

Presenter Mode top band, four first-show proof paths, Presenter Start Here cockpit, client demo launchpad, post-demo pipeline, lead health, stale follow-up, source quality, and agent accountability.

Launch Artifact Vault

/admin/artifacts?client_id=client_rising_hills

Protected proof archive for go-live approvals, broker handoff packets, CRM/import proof, access/security exports, follow-up logs, launch-intake exports, and support-ready operations artifacts.

Security Review

/admin/security?client_id=client_rising_hills

Production readiness proof for named access, live session checks, CSRF-protected writes, client isolation, agent boundaries, shared fallback phase-out, and formal review status.

Lead Inbox

/admin/leads?view=new

Lead routing, status, priority, assignee, AI insight, and action controls.

Client Settings

/admin/settings/clients

Branding, domains, plan tier, enabled modules, support package, and feature flags.

Fallback visuals

Keep these open so the call never depends on one tab.

Lead Hub screenshots PDF

https://askaires.com/sales-deck/aires-lead-hub-screenshots.pdf

Use as a sanitized Hub visual backup if protected auth slows down during the call. It now includes the Broker Dashboard Presenter Mode top band, Presenter Start Here cockpit, Command Center, Launch Wizard, Go-Live Handoff, Security Review, and Meeting Tracker.

Backend screenshots PDF

https://askaires.com/sales-deck/lead-hub-backend-current.pdf

Use when the broker wants to understand admin depth: Presenter Mode, presenter cockpit, dashboard command center, post-demo follow-up pipeline, meeting follow-up, routing, registration, exports, reporting, setup controls, and production-readiness proof.

Access rules

Keep credentials out of the first client email.

  • Do not put shared admin credentials in the client-facing demo email.
  • Screen-share protected Hub screens first so the client understands the workflow before touching credentials.
  • Use the dedicated broker-admin demo account when preparing the call.
  • For the Rising Hills client workspace, sign in with the dedicated Rising Hills broker-admin demo account when you need role-specific broker/admin access.
  • If direct access is needed, send credentials separately and rotate them after the review window.
  • Use role-specific access whenever possible: broker/admin for operations, agent login for agent portal only.
  • A signed-out 401, 403, or Hub login redirect is expected behavior for protected links.

Readiness boundary

Know exactly what is demo-ready, launch-ready, and scale-ready.

Demo-ready now

Safe to show Monday

  • Public Client Email Landing Page path, Monday Demo Link, Working Demo, Rising Hills site, Lead Hub overview, pricing, brief, optional Client Demo Guide, and screenshot PDFs.
  • Protected Hub screen-share for Broker Dashboard Presenter Mode, Command Center, Launch Wizard, Go-Live Handoff, Launch Artifact Vault, Security Review, inbox, Smart Lists, routing, registration, reports, agent queue, and client settings.
  • `pnpm demo:monday` and optional session-auth checks before the call.
First client launch

Harden for paid use

  • Create role-specific Hub users for the client and avoid shared credentials for client access.
  • Replace demo seed data with the client's real community, roster, listings, routing, and support package.
  • Confirm notification, export, CRM handoff, privacy, security review, and data-retention expectations in writing.
Multi-client scale

Protect the operating system

  • Keep client isolation, auth hardening, and secret-hygiene checks in the deploy path.
  • Move production CRM/API credentials into Worker secrets or the per-client secret reference flow.
  • Run live/session-based integration checks before unrelated brokerages share the same production deployment.

Before sending

Run the quick sanity pass.

  1. Run `pnpm demo:monday:private` from this machine and confirm public links, public PDFs/images, expected protected responses, TypeScript, build, secret hygiene, client-isolation checks, registration health, D1 health, signed-in Hub health, and session login smoke pass.
  2. Open the Client Email Landing Page and confirm it is still the required first client link, with Monday Demo Link as the primary action and Client Demo Guide as supporting detail.
  3. Open the Rising Hills public demo and Lead Hub overview in a normal browser tab.
  4. Sign into the Hub in a separate private/admin tab before the call starts using the Rising Hills broker-admin demo account.
  5. Open the Broker Dashboard Presenter Mode view and confirm the selected client is Rising Hills before screen-sharing private workflows.
  6. Open Security Review and confirm it shows live session checks, client isolation, agent boundary, shared fallback phase-out, and formal review status before using it as production-readiness proof.
  7. Keep screenshot PDFs open as fallback visuals if live auth or network conditions slow down.