AI builds the first versions. Automations keep journey current.

Custory starts with your real product context, then turns new signals from integrations into follow-up work on the right step.

Start from product context, not a blank canvas

Fetching data

Onboarding journey

Draft the journey from your product

Paste a URL, connect a repo, or link your docs. Custory AI turns what already exists into a structured journey draft.

#product-feedback2 new

Charlie10:24 AM

@Custory add this as feedback — users dropping off before payment

CustoryAPP10:24 AM

Got it — I created a journey insight for Payment step drop-off

Processing signals

Journey item created

Payment step drop-off · Sign Up

InsightOpportunity

Capture signals from team channels

Connect Slack or Discord and turn observations, feedback, and recurring issues into journey insights without copy-paste.

Use from any MCP-compatible tool

mcp · custory

>custory.list_journeys()

←[{ name: "Onboarding", stages: 4 }]

>custory.add_item({ step: "Payment", type: "friction", title: "Drop-off on mobile" })

←✓ Item added to journey

Use Custory in AI workflows

Expose journeys to AI tools through the Custory MCP server so agents can read, add, and update journey items as part of broader product workflows.

AI that drafts structure and works in context

Custory AI turns your website, repo, docs, and workspace context into a usable journey draft your team can refine, extend, and keep current without rebuilding from scratch.

Loading grid view...

AI assistant

Start a conversation

Choose one of the demo prompts or type your own message below.

Automations that turn signals into action

Custory automations do more than send alerts. They bring product signals into the journey, place them on the right step, and kick off the next action across your stack.

Trigger

Daily — 8:00 AM

Next run: Tomorrow at 8:00 AM

Weekly — Monday

GitHub PR merged

Item status changed

Choose a trigger

Run on a schedule or fire when something happens in Custory or GitHub. Triggers decide when the journey needs attention.

PostHogEvent volume

↓ 23%vs last 7 daysDrop detected

StripePayment failures

12failures today↑ Spike

Pull the signal

Pull data from PostHog or Stripe using purpose-built presets like funnel changes, top events, payment failures, or refund activity.

Automation running

Journey item

Checkout drop-off · Sign Up

Opportunity · High priority

ENG-1092 opened

Core Payments · High

#payments-team

Message sent

Update the journey and kick off work

Create a journey item on the exact step where the problem lives, open a Linear or Jira issue, and send a Slack message from the same automation.

Don't let customer signals die in dashboards

Without automation, a PostHog drop stays in a dashboard until someone notices it, discusses it, writes a ticket, and maps it back to the journey. That loop is slow and often breaks. Custory closes it automatically.

Every signal can lead somewhere useful

PostHog↓ 23% drop

Checkout funnel · Last 7 days

Pinned to journey

Checkout drop-off spike

Capture the signal in context

Turn the signal into a journey item tied to the exact customer moment.

Click me

Create follow-up work automatically

Open the issue in Linear or Jira without copy-pasting context across tools.

app.slack.com · #growth

#growth8 members

CustoryAPP2:18 PM

Quick update: PostHog flagged a change in onboarding, so I checked the journey.

Keep the team aligned

Notify the right people in Slack the moment the workflow runs.

Frequently asked questions

AI builds the first versions. Automations keep journey current.

Custory starts with your real product context, then turns new signals from integrations into follow-up work on the right step.