Lythe

Onboarding

Connect Slack, Jira/Linear, your dev tools, and PostHog, then run your first simulation.

Getting Fraser running takes three connections and a few minutes: link the tools your team works in, point it at your customer data, then run your first simulation from whichever interface you prefer.

1. Open Fraser and connect your workflow tools#

Sign in at fraser.lythe.ai and connect the integrations your product team already lives in:

  • Slack: where Fraser runs as a teammate and posts findings back to your channel.
  • Linear and Jira: where findings become tickets your PMs pick up.

These two are the core setup: an interface to talk to Fraser, and a backlog to send work to. See Slack, Teams & tickets for how findings are filed.

2. Add optional developer integrations#

If engineering wants Fraser closer to where they build, connect any of these, all optional:

  • Claude Code, Codex, Cursor: kick off and run simulations from your editor.
  • GitHub: pull product context and run flows against a branch.
  • MCP server: connect Fraser over the Model Context Protocol. With MCP you can deploy and run simulations from inside Claude Code, too.

Skip this step entirely if you only need the PM workflow.

3. Connect your customer data#

Personas get sharper when they're grounded in real customer behavior:

  • PostHog: connect it directly so personas learn from real product analytics, the events, funnels, and drop-off your actual users generate.
  • Other customer data: CRM records, call transcripts, support tickets, research notes, and more: contact sales to set up persona generation from your sources.

See Personas for how grounding works, and Authorization & limits for the rights and consents you're responsible for.

4. Run simulations from your preferred interface#

Once Fraser is connected where your team works, Slack, Microsoft Teams, or an editor via MCP, you're ready to run. Give it a target and a goal, and it drives the personas and reports back.

Next: the Quickstart walks through your first run end to end, and Simulations covers targets, goals, and scope.

Related#

Was this page helpful?