Online Demo Setup

Use the demo ZIP beside the complete package to install a polished staging demo on a real domain. The demo uses seeded data, sandbox gateway records, and safe credentials.

Server Install

1. Upload and extract revenuepilot-crm-v1.0.0-complete.zip on the server.
2. Point the domain document root to /public.
3. Create a MySQL database and database user.
4. Copy .env.example to .env and enter database, mail, queue, and app URL settings.
5. Set APP_URL to the clean hosted domain. Do not include /public; the domain document root must point to public/.
6. Run the installer or execute the deployment commands below.
7. Run the demo seed and operational health commands.

php artisan key:generate
php artisan migrate --force
php artisan db:seed --class=RoleAndPermissionSeeder
php artisan crm:demo-seed
php artisan storage:link
php artisan optimize:clear

Queue and Cron

Use a real queue worker and scheduler for staging. Local/demo installs may use QUEUE_CONNECTION=sync, but production-style demos should run queue and cron.

* * * * * cd /path/to/revenuepilot && php artisan schedule:run >> /dev/null 2>&1
php artisan queue:work --tries=3 --timeout=90

Realtime Chat With Reverb

Staff and portal thread updates broadcast through Laravel Reverb when Reverb credentials and the server process are configured. If Reverb is not running, keep marketplace wording at configuration-ready/polling fallback.

BROADCAST_CONNECTION=reverb
REVERB_HOST=your-demo-domain.com
REVERB_PORT=443
REVERB_SCHEME=https
php artisan reverb:start --host=0.0.0.0 --port=8080

Health Check Commands

php artisan crm:sync-support-mailboxes
php artisan crm:sync-accounting-providers
php artisan crm:run-recurring-billing
php artisan crm:sync-payment-gateways
php artisan crm:retry-payment-events
php artisan crm:portal-readiness-check

Safe Provider Modes

Keep payment live API calls, ads publishing/activation, accounting live sync, and mailbox live import disabled for the marketplace demo unless real provider evidence exists. QuickBooks/Xero, payment, ads, and mailbox credentials can be configured after purchase.

Demo Credentials

Interactive Guided Tour

After demo seeding, open /crm/demo-studio as the demo admin and launch the Full Product Tour. Demo Studio also includes Admin Setup, Sales Pipeline, Accounts & Portal, Revenue & Billing, Operations, Platform & Marketplace, and Portal Client tours.

1. Run the Full Product Tour once before capturing screenshots.
2. Run the Portal Client Tour after logging in with the seeded client credentials.
3. Run the Revenue & Billing Tour before invoice and payment gateway screenshots.
4. Use Pause Tour to hide the guided panel while keeping the current step saved.
5. Use Resume Tour or the floating paused-tour dock to continue from the saved step.
6. Use Start / Restart or Restart Current Tour to begin the selected tour again from step one.
7. Use Clear Tour Progress only for the tour panel state; it does not reset demo data.

Screenshot Capture

Use the root /screenshots folder inside the CRM app as the source of truth for marketplace and package screenshots. The public docs copy includes only a small referenced subset to keep inode usage low.

php artisan crm:demo-seed
php artisan revenuepilot:marketplace capture-screenshots

Set SCREENSHOT_BASE_URL, SCREENSHOT_OUTPUT_DIR, SCREENSHOT_ADMIN_EMAIL, SCREENSHOT_ADMIN_PASSWORD, SCREENSHOT_PORTAL_EMAIL, and SCREENSHOT_PORTAL_PASSWORD when capturing from a hosted staging demo.

Buyer Demo Path

1. Open Demo Studio and start the Full Product Tour.
2. Open the CRM dashboard and dark CRM shell.
3. Show lead, deal, proposal, contract, and campaign context.
4. Open project billing and approve billable time.
5. Create or review the invoice and payment session preview.
6. Open the portal-visible delivery note.
7. Reply to a support ticket from the client portal and review the admin thread.
8. Open System Health and confirm fresh command runs.

Dark and Light Theme QA

Capture both dark/night and light/day themes, then inspect dashboard, support tickets, invoices, payment gateways, delivery notes, portal pages, setup checklist, and System Health for readable text and sidebar alignment.