Skip to content

handbook/sales: document the tailored demo process - #5651

Open
dgatti0213 wants to merge 1 commit into
mainfrom
handbook/tailored-demo-process
Open

handbook/sales: document the tailored demo process#5651
dgatti0213 wants to merge 1 commit into
mainfrom
handbook/tailored-demo-process

Conversation

@dgatti0213

@dgatti0213 dgatti0213 commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

What & why

Documents the tailored demo process in the Demo stage of the sales handbook — the model we proved on our first tailored build (a canal monitoring & control demo built for a water district from their own project plan).

A tailored demo is a real, working FlowFuse app built for a specific prospect's own use case, so the Demo walks the backend of their problem rather than a relatable stand-in. The goal is unchanged from any Demo — establish the fundamentals and the app delivery / code-sharing methods — but using the prospect's own use case softens the barrier of also having to decode an unfamiliar example.

Changes

  • sales/meetings/demo.md
    • New Tailored demos section: what it is, why (same goal, lower barrier), and the 5-step process — fill a PoV workbook into the customer's Google Drive folder (one App tab per app) → SE review → build in a dedicated customer team → host the tailored front end → demo = walk the backend. Includes the graduation path: a strong, broadly relevant tailored demo can be rolled into the public Demo Apps registry.
    • Renamed Setup - Before the DemoStandard demo environment, with a legacy / to-be-deprecated callout (superseded by tailored demos + Demo Apps).
  • sales/demo-apps.md
    • New Where Demo Apps come from section: tailored demos are the pipeline; Demo Apps are the ones we choose to publish.

Docs-only. Both pages verified rendering locally.

Add a "Tailored demos" section to the Demo stage covering the process
proven on the first tailored build: capture the customer's use case as a
PoV workbook (one App tab per app), review before building, build the app
in a dedicated customer team, host the tailored front end, and demo by
walking the backend. Cross-reference generic Demo Apps vs tailored demos.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CVTs4TWBz2sVJ3k55ZHUg8
@dgatti0213

Copy link
Copy Markdown
Contributor Author

🔎 What changed — pages to review

Live on the Netlify Deploy Preview once it finishes building. Direct links so you don't have to hunt:

Updated pages

Page Preview What changed
Demo /handbook/sales/meetings/demo/ New Tailored demos section (purpose + 5-step process + graduation path); renamed Setup - Before the DemoStandard demo environment with a legacy/to-be-deprecated callout
Demo Apps /handbook/sales/demo-apps/ New Where Demo Apps come from section — tailored demos are the pipeline; Demo Apps are the ones we publish

No new pages, no redirects. Docs-only.


ℹ️ The Dependabot warning on push (11 vulns on main) is pre-existing on the default branch — unrelated to this docs change.

@netlify

netlify Bot commented Aug 20, 2026

Copy link
Copy Markdown

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit f817b95
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a8709b42df9c20007194bb2
😎 Deploy Preview https://deploy-preview-5651--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 51 (🟢 up 1 from production)
Accessibility: 96 (no change from production)
Best Practices: 100 (no change from production)
SEO: 85 (🔴 down 7 from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@dgatti0213
dgatti0213 marked this pull request as ready for review August 20, 2026 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant