Internal Demo Environment Checklist

Use this sequence only in an authorized demo environment. It validates connected product surfaces without publishing credentials or treating demo records as production data.

Demo identity Use an administrator account created in the authorized demo environment. Documentation never publishes demo identities or credentials.

What To Show In A Sales Demo

Not just CRUDShow guided demo, CBT runtime, Ask LMS, automations, tutor citations, result corrections, certificate QR, and exports.

Protected data stays scopedShow role dashboards, student-owned notes, protected files, tenant/academy scoping, and public-safe certificate verification.

AI is controlledAI drafts content, explanations, reports, tutor answers, and automations, but staff confirms before publishing or changing official data.

Real operationsShow commerce, invoices, earnings, reports, interventions, automations, notifications, and activity logs.

Inspection Sequence

Public showcase: open /showcase. Inspect feature journey, KPI proof, safe demo credentials, and certificate verify CTA.
Login: open /login with an authorized demo account. Confirm the page says normal login writes logs and database notifications, not email.
Demo Studio: open /lms/demo-studio. Start Full Product Demo, then pause, refresh, and resume to prove persistence.
System dashboard: open /dashboard/system. Show page header, 4 primary KPIs, 2 charts, and attention queue.
Course builder: open a seeded course builder. Show wizard steps, readiness, curriculum, media, AI assist, and reviewer notes.
Lesson studio: show protected media, resources, preview locks, drip/prerequisite controls, completion diagnostics, and lesson AI aids.
Student runtime: switch to learner surfaces. Show dashboard, course hub, player modes, notes, bookmarks, resources, tutor, and certificate strip.
CBT assessments: show one-question exam UI, timer, Answered/Skipped/Unanswered/Marked counters, final review, result sheets, corrections, XLSX/PDF exports.
Assignments: show assignment builder, submission versions, protected files, rubric grading, feedback release, resubmission, and AI feedback draft.
AI Tutor: ask a source-backed question, inspect citations, save note/task, then open staff transcript console.
Certificates: show eligibility, issue history, PDF download, public QR verification, revoke/reissue states, and verification events.
Community: show course reviews, rating distribution, Q&A, discussion threads, solved/pinned flags, moderation, and AI reply draft.
Commerce: show coupons, bundles, checkout invoice, payment history, instructor earning ledger, and payout requests.
Reports + Ask LMS: ask “Which students are inactive?”, inspect chart/table answer, create an intervention card, export report.
Automations: preview assignment due reminder audience, inspect Kanban, run history, cooldown, and certificate auto-issue rule.
SaaS/API: inspect tenant packages, limits, health, AI usage, billing placeholder, API docs, and mobile auth tenant resolution.

Screenshot Proof

Showcase — Start with buyer-safe public proof.

Launch and resume guided demos from Demo Studio.

Assessments — Show assessments, papers, grading, and result tooling.

Reports — Ask LMS and report Kanban prove operational depth.

Developer Checks Before Packaging

Run php artisan test.
Run php artisan view:cache.
Open /lms/demo-studio/health.
Confirm every required route exists.
Confirm every demo anchor exists or has synthetic fallback.
Confirm every screenshot referenced in docs exists.
Confirm demo identities are isolated from production users and are not documented publicly.
Confirm public tours do not expose private learner grades, media, notes, or payments.