> ## 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. ## Get set up Four steps, about 15 minutes. Go to **Settings → Context** and tell Lane about your world: * **Product** — what you've built, who it's for, what it helps them do * **Current priority** — what you're focused on right now * **Competitors** — who you're up against and how you differentiate Context grounds every answer Lane gives and drives which Signals surface for you. Two minutes here makes everything sharper, even before any feedback flows in. See [Context](/context). Open **Product Areas** from the sidebar (or **Settings → Product Areas**) and add the functional parts of your product — Onboarding, Billing, Integrations, Reporting. Three to five is enough to start. Add a one-line description to each — that's what lets Lane route incoming feedback to the right area accurately. See [Product Areas](/product-areas). Add 5–10 of your top accounts so prioritization has real business weight from the start. * **Manually** — add accounts from the **Customers** page * **Via CSV** — bulk import under **Settings → Import** * **Via CRM** — sync your full list from **Settings → Integrations → HubSpot** (or [Salesforce](/salesforce)) 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: * **Paste manually** — add a few recent customer messages from the **Feedback** page * **Connect [Slack](/slack)** — one-click setup under **Settings → Integrations → Slack**; flag messages with an emoji or let Lane watch a channel 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)** | 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) or Salesforce, or import the rest via [CSV](/import), so every piece of feedback gets customer context automatically. **Turn on Automation.** Enable **Detect Signals** so feedback is clustered for you, and **Surface what matters** so the Signals that fit your context rise to the top. See [Automation](/automation). **Connect your delivery tools.** Push [Plans](/docs) into [Linear](/linear), [Jira](/jira), [Asana](/asana), or [Notion](/notion) to kick off engineering — and, on Linear/Asana/Notion, let status flow back to close the loop. **Invite your team.** Once the workspace has data and you can show what Lane does, invite the rest of your team from **Billing** (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 priority shifts or a new competitor matters, update **Settings → Context** so surfacing and answers 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. You check Signals weekly to see what's emerging, ranked by revenue and demand. When a Signal is worth acting on, you turn it into a Plan grounded in the real customers and feedback behind it. You review the Plan, hand it to Cursor or push it into your delivery tool, and ship. 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 * [**Closing the loop**](/close-the-feedback-loop) — how Lane keeps customers in the loop automatically