diff --git a/src/use-cases/_template.njk b/src/use-cases/_template.njk
new file mode 100644
index 0000000000..a4240e01d7
--- /dev/null
+++ b/src/use-cases/_template.njk
@@ -0,0 +1,102 @@
+---
+# ===================================================================
+# Use-case page TEMPLATE.
+#
+# This file is intentionally NOT rendered (permalink: false) and is
+# NOT included in the `use-case` collection. It exists as a copy-and-
+# rename starting point for new use-case pages.
+#
+# To create a new use-case page:
+# 1. Copy this file to `src/use-cases/.njk`
+# 2. Replace the placeholder values below
+# 3. Make sure `tags` keeps `use-case` so the page appears in the
+# `/use-cases/` hub grid
+#
+# The layout renders a pain-led narrative from the rich blocks below
+# (customerPain, outcomeFirst, whyItMatters, competition, comparison)
+# plus a sticky section nav. Every block is optional: a section only
+# renders when its block is present. Keep copy generic, with no
+# customer names and no attributed quotes.
+#
+# Icon names refer to files in src/_includes/components/icons/.
+# ===================================================================
+permalink: false
+eleventyExcludeFromCollections: true
+layout: use-case
+tags:
+ - use-case
+title: "[Use case title]"
+meta:
+ title: "[Use case title] | Use Cases | FlowFuse"
+ description: "[One-sentence summary of the use case. Placeholder.]"
+problem: "[The pain in one line. This is the hero sub-headline. Placeholder.]"
+
+# 01 -- Customer pain
+customerPain:
+ heading: "[One-line statement of the core pain.]"
+ intro:
+ - "[First framing paragraph.]"
+ - "[Second framing paragraph.]"
+ cards:
+ - icon: "clock"
+ title: "[Pain symptom.]"
+ detail: "[One or two sentences.]"
+ - icon: "clip-list"
+ title: "[Pain symptom.]"
+ detail: "[One or two sentences.]"
+
+# 02 -- Outcome first
+outcomeFirst:
+ heading: "[Reframe around the outcome the buyer defines.]"
+ intro: "[Why there is no one-size-fits-all answer.]"
+ dimensions:
+ - label: "Operational"
+ title: "[Outcome.]"
+ detail: "[One or two sentences.]"
+ - label: "Financial"
+ title: "[Outcome.]"
+ detail: "[One or two sentences.]"
+
+# 03 -- Why this is important
+whyItMatters:
+ heading: "[Why the gap compounds if left unaddressed.]"
+ intro: "[One framing sentence.]"
+ points:
+ - title: "[Reason.]"
+ detail: "[One or two sentences.]"
+ - title: "[Reason.]"
+ detail: "[One or two sentences.]"
+
+# 04 -- Why off-the-shelf / competition does not work
+competition:
+ heading: "[Why generic tools fit this operation poorly.]"
+ intro: "[One framing sentence.]"
+ traps:
+ - label: "Trap 01"
+ title: "[Trap.]"
+ detail: "[One or two sentences.]"
+ - label: "Trap 02"
+ title: "[Trap.]"
+ detail: "[One or two sentences.]"
+
+# 05 -- With / without FlowFuse
+comparison:
+ without:
+ - title: "[Status quo pain.]"
+ detail: "[One or two sentences.]"
+ with:
+ - title: "[FlowFuse capability.]"
+ detail: "[One or two sentences.]"
+
+# ---------------------------------------------------------------
+# Legacy minimal fall-back (still supported). If you only set these
+# and omit the rich blocks above, the layout renders a simple
+# gap / workflow / outcomes skeleton instead.
+# ---------------------------------------------------------------
+# gap:
+# - "[Paragraph.]"
+# workflow:
+# - "[Step.]"
+# outcomes:
+# - "[Outcome.]"
+---
diff --git a/src/use-cases/index.njk b/src/use-cases/index.njk
new file mode 100644
index 0000000000..c7dfb199ec
--- /dev/null
+++ b/src/use-cases/index.njk
@@ -0,0 +1,57 @@
+---
+layout: layouts/base.njk
+sitemapPriority: 0.8
+title: "Use Cases"
+meta:
+ title: "Use Cases | FlowFuse"
+ description: "Generic operational workflow patterns for industrial teams. Turn events into action with FlowFuse. Placeholder skeleton hub."
+---
+
+
+
+
+
+
Use cases
+
Turn industrial events into action
+
Operational workflow patterns that follow Event, Decision, Action. Explore how each one is operationalized with FlowFuse.