Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions fern/docs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
24 changes: 24 additions & 0 deletions fern/docs/customer-stories/acme-api.mdx
Original file line number Diff line number Diff line change
@@ -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.

<Tip title="Sarah Chen, Head of Developer Experience, Acme API">
We used to dread release weeks because of the docs backlog. Now Promptless handles it automatically—our developers can focus on building.
</Tip>
23 changes: 23 additions & 0 deletions fern/docs/customer-stories/cloudnova.mdx
Original file line number Diff line number Diff line change
@@ -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

<Tip title="Marcus Rivera, Support Lead, CloudNova">
Our best support content used to disappear into Slack history. Now it becomes documentation that helps everyone.
</Tip>
19 changes: 19 additions & 0 deletions fern/docs/customer-stories/finstack.mdx
Original file line number Diff line number Diff line change
@@ -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

<Tip title="David Park, VP of Compliance, FinStack">
Promptless gives us confidence that our docs match reality. That's essential when regulators come knocking.
</Tip>