diff --git a/fern/docs.yml b/fern/docs.yml
index 66bd90e8..e3e96cc8 100644
--- a/fern/docs.yml
+++ b/fern/docs.yml
@@ -159,6 +159,15 @@ navigation:
- page: How Vellum Drafts 50%+ of Docs with Promptless
path: ./docs/customer-stories/vellum.mdx
slug: vellum
+ - page: How Acme API Keeps Developer Docs in Sync
+ path: ./docs/customer-stories/acme-api.mdx
+ slug: acme-api
+ - page: How CloudNova Turns Support into Documentation
+ path: ./docs/customer-stories/cloudnova.mdx
+ slug: cloudnova
+ - page: How FinStack Maintains Compliance Docs at Scale
+ path: ./docs/customer-stories/finstack.mdx
+ slug: finstack
- section: Technical
icon: fa-regular fa-code
contents:
diff --git a/fern/docs/customer-stories/acme-api.mdx b/fern/docs/customer-stories/acme-api.mdx
new file mode 100644
index 00000000..e62a6bad
--- /dev/null
+++ b/fern/docs/customer-stories/acme-api.mdx
@@ -0,0 +1,24 @@
+---
+title: How Acme API keeps developer docs in sync automatically
+description: Acme API uses Promptless to ensure their API documentation stays current as their platform evolves.
+---
+
+[Acme API](https://acme-api.example.com) builds developer tools for payment processing. With hundreds of API endpoints and weekly releases, keeping docs accurate was a constant challenge.
+
+## Act I: The Docs Backlog
+
+FOOIFDOISFOIDF
+
+Acme's engineering team shipped changes fast. But docs always lagged behind. Developers would find outdated examples, and support tickets piled up.
+
+## Act II: Promptless in Action
+
+Promptless now monitors every PR and automatically drafts doc updates. When an endpoint changes, Promptless catches it and updates the relevant guides.
+
+- **Fewer support tickets:** Docs-related support tickets dropped by 70%.
+- **Fast turnaround:** API docs now update within hours of code changes.
+- **Zero busywork:** Engineers don't spend time on routine doc maintenance.
+
+
+We used to dread release weeks because of the docs backlog. Now Promptless handles it automatically—our developers can focus on building.
+
diff --git a/fern/docs/customer-stories/cloudnova.mdx b/fern/docs/customer-stories/cloudnova.mdx
new file mode 100644
index 00000000..c2aaa553
--- /dev/null
+++ b/fern/docs/customer-stories/cloudnova.mdx
@@ -0,0 +1,23 @@
+---
+title: How CloudNova turns support conversations into documentation
+description: CloudNova uses Promptless to transform Slack support threads into polished help articles.
+---
+
+[CloudNova](https://cloudnova.example.com) is a cloud infrastructure platform serving thousands of developers. Their support team kept answering the same questions in Slack.
+
+## The Challenge
+
+CloudNova had active Slack Connect channels with customers. Great questions got great answers—but those answers lived only in Slack threads, buried and unsearchable.
+
+## The Solution
+
+With Promptless, support engineers trigger doc updates from Slack. A quick @Promptless mention turns troubleshooting conversations into help center articles.
+
+**Results:**
+- 40% fewer repeat questions
+- Support contributes to docs without context switching
+- 35% increase in customer self-service
+
+
+Our best support content used to disappear into Slack history. Now it becomes documentation that helps everyone.
+
diff --git a/fern/docs/customer-stories/finstack.mdx b/fern/docs/customer-stories/finstack.mdx
new file mode 100644
index 00000000..14192a24
--- /dev/null
+++ b/fern/docs/customer-stories/finstack.mdx
@@ -0,0 +1,19 @@
+---
+title: How FinStack maintains compliance documentation at scale
+description: FinStack uses Promptless to keep security and compliance docs accurate across their regulated platform.
+---
+
+[FinStack](https://finstack.example.com) provides financial infrastructure for banks and fintechs. In their world, docs aren't just helpful—they're a regulatory requirement.
+
+Before Promptless, FinStack's compliance team spent weeks manually updating security docs after each release. Any gap between code and documentation meant audit risk.
+
+Now, Promptless monitors their codebase and flags docs that need compliance review. Security-related changes automatically trigger updates with full audit trails.
+
+**Results:**
+- **Docs stay current:** Compliance documentation updated within 24 hours
+- **Faster audits:** Audit preparation time reduced by 60%
+- **No gaps:** Zero documentation gaps in the last 3 audits
+
+
+Promptless gives us confidence that our docs match reality. That's essential when regulators come knocking.
+