Skip to main content
Lane is organized around four surfaces — Agent, Plans, Signals, and Data — sitting on a shared data model. Once you understand what each surface is for and how the data flows underneath, the rest of the product makes sense. The value comes from the connection. The Agent knows what’s in your Plans. Plans pull from Signals. Signals are grounded in real Feedback from real Customers. Nothing lives in isolation — and that’s what makes Lane different from stitching together a chatbot, a doc tool, and a spreadsheet.

​
The four surfaces

​
Agent

The Agent is where you think with Lane. Open a canvas, type a question, and the Agent responds inline — pulling in real context from your workspace. @mention a Feature, Customer, or Signal mid-sentence and the Agent reads the actual data behind it, not just the name. The whole thing reads like a flowing document, not a chat window — you write with the Agent, not at it. The Agent also runs in the background, automatically processing new Feedback as it arrives — extracting Insights, classifying sentiment, and clustering related signal into Signals.

​
Plans

Plans are living product documents written with the Agent and grounded in real workspace data. Reference a Feature and the Plan knows its score, linked Customers, and Insights. Reference a Signal and the Plan knows the volume and revenue behind it. Plans are also where your team works together. PMs draft, engineers comment, stakeholders read — all in one source of truth that stays connected to the underlying data instead of going stale the moment it’s written. When a Plan is ready to ship, hand it to Cursor, Cursor Cloud, or Lovable directly, or push it through a Feature to your delivery tool.

​
Signals

Signals are the patterns the Agent finds across your customer Feedback. When multiple Insights point to the same underlying issue — “slow CSV export,” “missing SSO,” “PDF formatting bugs” — the Agent clusters them into a Signal, ranked by how much revenue and recency is behind it. Signals turn noise into the few things actually worth acting on. Signals are AI-maintained. You can rename or dismiss them, but they can’t be manually merged — the Agent keeps them clustered as new Feedback arrives.

​
Data

Data is the source of truth underneath everything else. It holds the objects every other surface reads from: Feedback, Features, Customers, Objectives, and Roadmaps. Read on for how these objects fit together.

​
The data model

The data in Lane sits in three buckets, each answering a different question.

​
Customer voice — what was said and by whom

Feedback, Insights, and Customers together answer “what are our customers telling us?” Feedback is the raw input — a Slack message, an Intercom conversation, a forwarded email, a sales call note. It’s what was said, unedited. Insights are the meaningful signal extracted from Feedback. A single piece of Feedback can produce multiple Insights — one customer message complaining about export speed and asking for SSO is two distinct Insights, each tagged with sentiment, type, and product area. Insights are the building blocks of Signals. Customers are who said it — Companies (the accounts you sell to) and Users (the contacts within them). Every Feedback is linked to a Customer, which is how Signals and Features inherit business context like ARR, tier, and account status.

​
What you build — work and how it’s organized

Features and Roadmaps together answer “what are we shipping?” Features are units of planned or potential product work. A Feature can be created by promoting a Signal, drafted by the Agent from a piece of Feedback, or added manually. However it’s created, a Feature always carries its supporting context — linked Insights, requesting Customers, total ARR, priority score, and the Objective it serves. Roadmaps are how you communicate Features over time. They’re not a separate planning layer — they’re a view of your Features, organized by timeline or theme. Because Roadmap items stay linked to their underlying Customers and Insights, the Roadmap always reflects the reasoning behind the work.

​
Why you build it — strategic anchor

Objectives answer “why does this matter?” Objectives are the strategic goals your team is working toward — quarterly Goals, or full OKRs with measurable Key Results. Features link to Objectives, which means every item on the Roadmap connects back to a business outcome, not a wishlist. Progress on an Objective updates automatically as its linked Features move forward.

​
Plans cut across everything

Plans don’t sit cleanly in one bucket. A single Plan can reference Features, Customers, Signals, and Objectives in the same document — pulling Customer voice, work, and strategy into one place. That’s what makes a Plan agent-ready: by the time it lands in Cursor or Lovable, the context is already attached.

​
The agentic loop

Lane’s data model has a direction. Customer voice becomes Signals. Signals become Plans. Plans become work that coding agents ship. And when something ships, Lane closes the loop — automatically notifying the Customers whose Feedback fed into it. 
Feedback  →  Signals  →  Plans  →  Coding Agent  →  Shipped  ↩  Customer
The Customer hears back, new Feedback comes in, and the cycle continues. The loop isn’t a workflow you run — it’s the system you operate in.

​
What’s next

Now that you understand how Lane is organized, you’re ready to set it up. Set up your workspace →