Getting Started

Lisa is AI product intelligence for teams that ship. She connects your Slack conversations, GitHub repositories, and Linear boards into a single living context — so you can stop being a human integration layer and start making the decisions only you can make.

This guide gets you from zero to your first structured plan in under ten minutes.

Why Lisa exists

Product teams don't lack tools. Slack, Linear, and GitHub are excellent at what they do. What's missing is the layer between them — the connective tissue that turns scattered conversations into structured plans.

Today, that layer is you. You copy Slack messages into tickets. You context-switch between your codebase and your project board. You spend hours writing PRDs that could be generated from a single conversation. Lisa handles everything below the line — the operational work — so you can focus on what's above it: strategy, tradeoffs, and decisions.

Here's what makes Lisa different from another dashboard:

• She's an active participant. Lisa doesn't wait for input. She analyzes your codebase, suggests improvements, and creates structured work from conversation.
• She's code-aware. Lisa clones and indexes your repositories. Issues she creates reference actual files, patterns, and APIs — not guesses.
• She produces structured output. Every issue ships with acceptance criteria, verification hints, and dependency tracking. No more tickets that get sent back.
• She's integration-first. Two-way sync with Linear and GitHub means your team works where they already work.

Step 1: Sign in

Head to Lisa and sign in with one of two options:

• Magic link — enter your email and click the link sent to your inbox. No account setup required, the link expires in 10 minutes.
• GitHub — sign in with your GitHub account. This is the fastest path if you already have GitHub access, since Lisa will use that connection to access your repositories later.

You can link both methods to the same account, so your team can sign in however they prefer.

Step 2: Run through the setup wizard

After signing in, the setup wizard walks you through six quick steps:

1. Confirm your profile — verify your name so Lisa knows who she's working with.
2. Create your organization — name your team's workspace. Lisa auto-generates a URL slug from the name.
3. Configure AI — set your model preferences. In BYOK (Bring Your Own Key) mode, you provide your own API keys for Anthropic, OpenAI, or Google and choose from models like Claude Sonnet 4.5, GPT-5.2, or Gemini 3 Pro. In SaaS mode, Lisa uses a default model and you're ready to go — no keys needed.
4. Connect integrations — link GitHub, Linear, and/or Slack via OAuth. Each one opens a quick authorization flow and redirects you back.
5. Select repositories — once GitHub is connected, pick which repos Lisa should have access to. She'll clone and analyze them when you start planning.
6. Done — you're in. Head to your org and start chatting.

Why GitHub is required

Lisa's biggest advantage is that she's code-aware — she doesn't just plan in the abstract, she references your actual codebase when creating issues, PRDs, and specs. To do that, she needs read access to your repositories.

If you're a PM and don't have a GitHub account, don't worry — you don't need to write code. Ask your engineering lead to add you as a read-only collaborator on the relevant repos. This gives Lisa the context she needs without changing your day-to-day workflow. Most startups at this stage are happy to grant this — it means better tickets and fewer back-and-forth cycles with engineering.

Step 3: Connect your stack

If you skipped any integrations during setup, you can always add them from Settings → Integrations:

• GitHub — required. Gives Lisa access to your codebase for code-aware planning, plus bidirectional issue sync with GitHub Issues.
• Linear — bidirectional issue sync. Create in Lisa, track in Linear. Update in Linear, see it in Lisa.
• Slack — Lisa monitors connected channels and automatically surfaces feature requests, bug reports, and decisions as structured issue suggestions in your Insights page.

You don't need all three to start. GitHub is required (it's your code context), but Linear and Slack integrations can be added whenever your team is ready.

Step 4: Start planning

Navigate to your org and start talking to Lisa. She knows your codebase, your projects, and your connected tools. Try:

• "I want to build a notification system" — Lisa will ask clarifying questions, then generate a full project with milestones, issues, and a PRD.
• "Create a PRD for user authentication" — she'll produce a structured document referencing your actual codebase architecture.
• "Break down this feature into issues" — Lisa generates issues with hierarchies, dependencies, acceptance criteria, and verification hints.
• "Start a discovery session for our new search feature" — a guided four-phase process that turns a vague idea into an executable plan.

For the most structured output, try a Discovery Session. It's Lisa's guided planning flow — four phases that take you from "we should build this" to a full breakdown with milestones and developer-ready tickets.

Who is Lisa for?

Lisa is built for PMs and technical founders at seed-to-Series-A startups — teams of 10 to 50 people who ship on GitHub, plan on Linear, and talk on Slack.

If you spend your days copying context between tools, writing tickets that engineers send back for clarity, or starting PRDs from a blank page — Lisa was built for exactly that.

What to explore next

• AI Chat — how to talk to Lisa and get the most out of every conversation.
• Discovery Sessions — Lisa's guided planning flow for turning ideas into structured work.
• Issues — how Lisa structures work items with hierarchies, dependencies, and acceptance criteria.
• Templates — customize Lisa's output to match your team's standards.
• GitHub Integration — deep dive into code-aware planning and issue sync.