Before you start
Lane is built around a connected flow: Feedback → Insights → Features → Objectives. The setup steps below follow that same order - so by the end, you’ll have a working system, not just a configured tool. You don’t need to complete every step on day one. Start with Steps 1–3 and you’ll already be getting value.Invite your team
Go to Settings → Members and invite team members by email.Think about who should be in Lane from day one — typically the people who capture feedback (CS, Sales), make product decisions (PM, founder), and need visibility (leadership). See the Members page for details on roles and seat management.
Configure your workspace
Three things worth setting up before anything else flows in:Product Areas Product Areas are how work gets categorized in Lane — they map to the functional parts of your product (e.g. Onboarding, Billing, Integrations, API). Go to Settings → Product Areas and add the areas that reflect your product’s structure. Adding a clear description to each one helps Lane’s AI Agent make better suggestions over time.Statuses Lane comes with default statuses for each object. If your team has a specific workflow, customize them under Settings → Fields → Status. Statuses are configured per object — so you can have separate workflows for Insights, Features, and Objectives.Tags Tags are flexible labels used across all objects for filtering and grouping. Set up your core tags early - themes, teams, priority levels - under Settings → Fields → Tags.
Bring in your customers
Customer context is what separates Lane from a basic feedback tool. Get your accounts in before feedback starts flowing so every Insight is automatically enriched with the right customer data.Sync via HubSpot Connect HubSpot under Settings → Integrations → HubSpot to sync your companies and contacts automatically.Add manually or import Add customers individually under Customers → New Customer, or bulk import via Settings → Import using a CSV.Either way, make sure each customer record has their company name, domain, revenue, and tier filled in. This is the data that makes prioritization meaningful downstream.
Connect your feedback sources
The more sources you connect, the richer your Lane workspace becomes - automatically.
You don’t need all of these on day one. Start with one - whichever source generates the most feedback for your team right now.Turn Themes into Features
| Source | Best for | Setup |
|---|---|---|
| Slack | Capturing feedback from internal conversations | Settings → Integrations → Slack |
| Intercom | Logging feedback from customer support tickets | Settings → Integrations → Intercom |
| HubSpot | Syncing customer data and CRM conversations | Settings → Integrations → HubSpot |
| Chrome Extension | Capturing feedback while browsing any web tool | Settings → Integrations → Chrome Extension |
| Forwarding customer emails directly into Lane | Settings → Integrations → Email | |
| CSV Import | Bringing in historical feedback in bulk | Settings → Import |
| Zapier | Connecting any other tool (Typeform, Zendesk, G2) | Settings → Integrations → Zapier |
Set your Objectives
Before feedback starts shaping your roadmap, give it somewhere to point. Define one or two Objectives that reflect what your team is working toward this quarter.Go to Objectives → New Objective and choose the type that fits your team:
- Goal — a simple outcome statement
- OKR — a structured objective with measurable Key Results
Connect your delivery tools (optional)
If your engineering team uses Linear or Jira, connect it to Lane so Features stay in sync across both tools.Go to Settings → Integrations and connect your delivery tool. Once connected, you can:
- Push Features from Lane into Linear or Jira to kick off engineering work
- Pull existing issues back into Lane to prioritize them alongside customer feedback
- Track delivery status in real time without switching tools
You’re set up
At this point you have:- Your team in Lane with the right configuration
- Customer data synced and ready
- Feedback sources connected and flowing
- Objectives defined to guide prioritization
What’s next
- Feedback Management — How to triage and process Insights as they come in
- Strategic Product Discovery — How to turn Themes into decisions
- Building Roadmaps — How to communicate what you’re building and why