FCCIS
·
Partner Demo Mode

Founder presentation — guided walkthrough

Eight-step sequence with deep-links into the live app. Pilot-ready, demo-ready — no fabricated traction.

Demo sessionMeeting-ready
Snapshot — what the partner will see
Pulled from the same data layer as the rest of the dashboard.
Read-only
Active assets
3
Observations
3
Reports
0
Unread notifications
Capability status
Honest status across the operational stack. Hover the label on each row to deep-link into the live surface.
  • Supabase persistence
    Demo seed in use. Sign in to a firm to enable live persistence.
    Demo-ready
  • Remote inspection flow
    Token-gated remote sessions with evidence capture and replay.
    Operational
  • Report PDF generation
    Reports synthesize observations with inline Florida Building Code references.
    Operational
  • Client portal
    Token-gated review, comment, acknowledgement, and PDF download.
    Operational
  • Delivery log
    Report-delivery audit trail per recipient.
    Operational
  • Internal notifications
    Sign in for live unread count. Inbox link still works.
    Demo-ready
  • White-label ready
    Branding, plan, and partner badging wired through firm settings.
    Operational

Guided walkthrough

Run these eight panels in order. Each card carries the pitch, a short founder script, and live deep-links.

1
Market problem — the 4:1 efficiency trap
Field engineers spend roughly four hours on paperwork for every hour on site. That ratio is the wedge.
What to say

Inspection firms in Florida bill for site time but lose margin on report production. Engineers retype voice memos, paste photos, hand-format compliance language, and stall on revisions. FCCIS compresses that 4:1 ratio toward 1:1 without taking the engineer out of the loop.

  • Frame this as an operating-leverage story, not an AI story.
  • Keep numbers conservative — 4:1 is the published industry benchmark, not a claim we invented.
2
Field capture & remote inspection
Capture flows on-site (photos + voice + observations) and remote (live video walkthroughs with the property owner).
What to say

Show the field capture screen first — that is the engineer's primary input. Then open Remote Inspections to show the same evidence stream pulled from a video walkthrough. Same structured observations, two capture modes.

3
Evidence upload & media packet
Every observation is tied to media (photos, video frames, voice transcripts) and stored as an audit-grade packet.
What to say

Point out that each observation has a media trail attached — this is what makes the report defensible. The packet is the deliverable surface the client and any reviewing engineer can both inspect.

4
AI report generation with code references
Observations are synthesized into a draft report with inline Florida Building Code citations.
What to say

Open a report and call out the code references next to each finding. The AI is doing the boring work — pulling cited language and assembling the narrative. The engineer is still the author of record; we are explicit about that on the report itself.

  • Always say 'engineer-reviewed AI draft' — never 'AI-signed report'.
5
Engineer review — the human control layer
Every report passes through engineer review before it leaves the firm. That is the defensible boundary.
What to say

FCCIS is not a replacement for the PE — it is the production layer underneath the PE. The reviewer can edit, request revisions, or sign off. This is what makes the product sellable to a regulated firm.

6
Client portal handoff
Clients get a token-gated portal: review the report, leave comments, acknowledge the package, download the PDF.
What to say

Open the demo portal link in a new tab — this is what the property owner or developer actually sees. Note the comment thread, the acknowledgement, and the download. All gated by a single-use token, all logged.

  • Open the portal in a separate browser window before the meeting so it loads instantly.
7
Notifications & audit trail
Every portal event (comment, ack, download) writes an internal notification with an immutable trail.
What to say

Show the notifications inbox — the demo portal activity is already in there: a comment, an acknowledgement, and a report download. This is the audit trail that compliance officers ask about.

8
Business model & wedge strategy
Seats + per-report unit pricing today. White-label add-on unlocks partner distribution.
What to say

Two revenue motions. Direct: per-seat plus per-report unit pricing to inspection firms. Indirect: white-label add-on for partners who want to deliver FCCIS under their own brand. The white-label switch is already wired in settings — that is the partner upsell.

Presenter checklist
0 of 8 steps marked. Saved locally so you can tick items off as you run the meeting.
Pinned demo identifiers
Reference
Demo portal tokenx1_x9oliTrsGv48Wyi0IJeA6omss5IIXSQbSzuhePxM
Demo report id5c5f9aa8-da97-4b07-abb9-7704f6ba53f9
Demo remote session idabbaa771-ae76-4f03-a8f0-3d9e3e52b420

Seeded notification rows exist for the portal comment, acknowledgement, and report-download events tied to these ids. If the inbox shows zero unread, mark a notification unread from the inbox before the meeting.