> ## 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.

# From signal to shipped

> Take one Signal or Opportunity all the way to shipped work, and make sure the customers who asked hear back.

A [Signal](/signals) tells you *what* customers keep asking for, and an [Opportunity](/opportunities) is a product bet Lane recommends, weighed against your priorities and the customers who matter most. This playbook is what you do next: decide, get the work built, and close the loop with the customers behind it. One continuous thread from customer voice to shipped work, with Lane keeping every step in sync so nobody updates anything twice.

## 1. Start from what matters

Open the [Signals](/signals) list sorted by **Priority score** or **Trending**, or an [Opportunity](/opportunities) Lane has brought you. Each one already has what you need to decide: the feedback behind it, the customers asking, the revenue at stake and how fast it's growing.

If it isn't worth building now, leave it Open. On an Opportunity, choose **Not interested**, and if the whole topic is off the table, add it to **Not now** in [Context](/context) so Lane stops suggesting it. Save **Closed** for work that has shipped: closing is what tells customers.

## 2. Decide and hand off

When it's worth doing, there are two ways forward:

* **Straight to your tracker.** On a Signal, **Send to** [Linear](/linear), [Notion](/notion), [Jira](/jira) or [Asana](/asana). Lane creates the issue, page or task with a link back, and marks the Signal **Accepted**, which moves its feedback into progress.
* **Write it up first.** Choose **Create Doc**. **Use Lane** drafts a structured brief from the evidence, using a template you choose; **Write it myself** starts with the title and summary. Creating a Doc from an Opportunity accepts the Opportunity and its open Signals in one step. Refine the Doc with Lane, then send it to your tracker the same way.

Either way, the feedback behind the work comes along. In Linear, it arrives as customer requests, so engineers see who's waiting and the revenue behind them.

## 3. Let status flow back

In the [Linear](/linear) or [Notion](/notion) settings, turn on status sync and map the statuses that mean "in progress" and "shipped" to Lane's **Accepted** and **Closed**. From then on the Signal moves as the work moves, and Lane always reflects where delivery really is.

With Jira or Asana, move the Signal to Closed yourself when the work ships.

## 4. Ship, and let the loop close itself

When engineering marks the work done, the linked Signal becomes **Closed**, its feedback is marked done, and [closing the loop](/close-the-feedback-loop) fires: every customer behind that feedback is told in the place they asked, with a reply in their Slack thread or a note on their Intercom or Zendesk conversation.

Nobody has to remember to follow up. The customer who asked hears back, new feedback comes in, and the cycle continues.

## The whole thread

```text theme={null}
Signal or Opportunity  →  Accepted  →  Delivery tool  →  Closed  →  Customer notified
```

That's the loop end to end: the [proactive setup](/stay-ahead) brings the decision to you, and this playbook carries it to shipped and back to the customer.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.