> ## Documentation Index > Fetch the complete documentation index at: https://docs.laneapp.co/llms.txt > Use this file to discover all available pages before exploring further. # Quick Start > Get Lane working for your team in under 30 minutes Lane works best when it knows your product, your customers, and what they're saying. This page walks you through getting those three layers in — so Lane has real context to work with from day one. You don't need to set everything up before getting value. Start with the minimum, see Lane work, then layer in the rest. ## Your first two minutes Create your workspace with your work email, and Lane's onboarding gets the basics in for you: 1. **Add your company website.** Lane reads it and drafts your product description, so it knows what you build before you've typed a word. 2. **Set your current priority.** What your team is focused on right now. Lane weighs everything against it. 3. **Bring in customer feedback.** Connect Slack or Intercom and choose how far back Lane should look, or upload a CSV. Or choose **I'll do it later**. You land in [Ask Lane](/agent) with a first answer already on its way. The steps below build on that. ## Get set up Four steps, about 15 minutes, to make Lane properly yours. Go to **Settings → Context** and tell Lane about your world: * **Your company**: what you've built and who you compete with (Lane drafts the product description from your website) * **Priorities**: what you're focused on right now * **Not now**: what you've decided not to pursue, so Lane doesn't keep suggesting it * **Customers**: the tiers that matter most, the status that means an account is at risk, and any accounts to watch Context grounds every answer Lane gives and shapes which Signals get flagged and which Opportunities Lane brings you. Two minutes here makes everything sharper, even before much feedback flows in. See [Context](/context). Your workspace starts with a set of common Product Areas, like Onboarding, Billing and Integrations. Open **Settings → Product areas** and make them yours: rename them, remove the ones that don't fit, and add the parts of your product that are missing. The descriptions matter most: they're what lets Lane route incoming feedback to the right area. Editing a description to match how your team talks sharpens routing more than adding more areas. See [Product Areas](/product-areas). Add 5–10 of your top accounts so prioritization has real business weight from the start. * **Manually** — use the **+** next to **Customers** in the sidebar * **Via CSV** — bulk import under **Settings → Import** * **Via CRM** — sync your full list from [HubSpot](/hubspot), [Salesforce](/salesforce) or [Attio](/attio) under **Settings → Integrations** For each, fill in company name, domain, revenue, and tier. That's the difference between *"5 customers asked for this"* and *"5 Enterprise customers totaling \$480K ARR asked for this."* See [Customers](/customers). Get real customer [feedback](/insights) into the workspace so Lane has something to reason over: * **Add it manually** — open **Signals**, switch to the **Feedback** tab and use **Add Feedback** for a few recent customer messages * **Connect a source** — [Slack](/slack), [Intercom](/intercom) or [Zendesk](/zendesk) under **Settings → Integrations**; let Lane watch for feedback, or flag it by hand Once feedback is in, Lane extracts the insights, classifies them, and clusters related ones into [Signals](/signals) automatically. That's enough to make Lane useful. [Ask Lane](/agent) something like *"what are our Enterprise customers asking for?"* and you'll get a real answer grounded in real data. ## Make it richer Optional layers that turn a working workspace into a complete one — add them as you need them. **Connect more feedback sources.** The more sources, the richer Lane gets — each feeds the same pipeline. | Source | Best for | | :- | :- | | **[Slack](/slack)** | Feedback from internal and shared channels | | **[Intercom](/intercom)** | Support conversations | | **[Zendesk](/zendesk)** | Support tickets | | **[Chrome Extension](/chrome-extension)** | Capturing while browsing any web tool | | **[Email Forwarding](/email)** | Forwarding customer emails directly | | **[HubSpot](/hubspot) / [Salesforce](/salesforce) / [Attio](/attio)** | Customer data and CRM conversations | | **[CSV Import](/import)** | Historical feedback in bulk | | **[Zapier](/zapier)** | Any other tool | **Sync your full customer list.** If you only added your top accounts, connect [HubSpot](/hubspot), Salesforce or Attio, or import the rest via [CSV](/import), so every piece of feedback gets customer context automatically. **Set up an automation.** Start from a template so a weekly summary of what's rising in your feedback lands in Slack or email. See [Automations](/automation). **Connect your delivery tools.** Send [Signals](/signals) and [Docs](/docs) to [Linear](/linear), [Jira](/jira), [Asana](/asana) or [Notion](/notion) to kick off engineering. On Linear and Notion, let status flow back, so shipping there closes the loop with customers. **Invite your team.** Once the workspace has data and you can show what Lane does, invite the rest of your team from **Settings → Members**. Inviting people to an empty Lane usually loses them — set up first, invite second. **Connect MCP.** If your team uses Claude, [Cursor](/cursor), or any MCP-compatible tool, connect it to Lane so it can read your product context directly. See [MCP Server](/mcp-server). **Revisit Context.** When your priorities shift or a new competitor matters, update **Settings → Context** so Lane's answers and Opportunities stay sharp. ## What good looks like Here's the steady state you're building toward. Feedback flows in automatically from every source your team touches. Lane processes it as it arrives — extracting insights, classifying sentiment, routing to product areas, and grouping related insights into Signals — and recommends Opportunities, the product bets most worth your focus. You review them weekly, ranked by revenue, demand and momentum, and an automation brings the summary to you. When something is worth acting on, you accept it and send it to your delivery tool, or turn it into a Doc grounded in the real customers and feedback behind it. You ship, and the customers who asked hear back when it lands. Lane knows what you're building, who it's for, and what you care about right now — and reasons over fresh feedback through that lens. The system runs in the background; you stay in the parts that need judgment. ## What's next * [**Feedback**](/insights) — how feedback is captured and processed * [**Signals**](/signals) — how patterns are detected and prioritized * [**Opportunities**](/opportunities) — the product bets Lane recommends, based on your priorities and customers * [**Closing the loop**](/close-the-feedback-loop) — how Lane keeps customers in the loop automatically This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.