Skip to main content
Lane can read every piece of feedback you have, but it can’t guess your strategy. Context is where you tell it: what your product is, what your team is prioritizing, what you’ve decided not to do, and which customers matter most. It takes a few minutes, and it changes how Lane works everywhere: the answers you get from Ask Lane, the Opportunities Lane recommends, the Signals it flags, and what your automations pay attention to. Without it, Lane gives good general answers. With it, Lane gives answers that fit your business.

​
What Context changes

  • Opportunities. Lane weighs your Signals against your Priorities and the customers you care about to decide which product bets to recommend, marks the ones that fit with Matches priority, and leaves out anything you’ve said is Not now.
  • Signals. Signals from your priority customer tiers or at-risk accounts carry a Priority tier or At-risk customer badge, so they stand out in the list.
  • Ask Lane, Automations and AI apps. Answers, briefs and drafted Docs start from your product, your priorities and your competitors, and don’t recommend things you’ve ruled out. AI apps connected through the MCP server get the same picture.

​
What you set

Context lives in Settings → Context, in four sections. Your company
  • Product: what you build, who it’s for, and what it helps them do. If you added your website during onboarding, Lane has drafted this for you; check it reads the way your team would say it.
  • Competitors: who you compete with and how you’re different.
Priorities What should lead when two things are close: the initiatives, problems or customer segments your team is focused on right now. Anything tied to a high priority can move ahead of louder requests. Not now Things you’ve decided not to work on, like a mobile app or a rebuild you’ve ruled out. Lane won’t recommend them, so the same ideas don’t keep coming back. Customers
  • Priority tiers: up to two customer tiers that matter most to you, such as Enterprise.
  • Churn-risk status: the customer status that means an account is at risk.
  • Accounts to watch: specific accounts you want Lane to call out by name when they come up.
Save appears once you’ve changed something. Badges on your Signals update straight away; Opportunities reflect your changes the next time Lane looks for them.

​
Keeping it current

Context should move as your focus does. Update your Priorities when the quarter’s plan changes, add to Not now when you rule something out, and refresh your tiers and accounts to watch as your customer base shifts. A few minutes here keeps everything downstream sharp.

​
Best practices

  • Be specific about your product. “A billing platform for B2B SaaS finance teams” grounds Lane far better than “our app.”
  • Write Priorities as you’d explain them to a new teammate. “Anything blocking an enterprise rollout comes first, then reporting performance” tells Lane how to break a tie.
  • Use Not now generously. Every idea you rule out is one Lane stops recommending.

​
FAQs

Q: Why does Context matter so much?
A: It’s how Lane knows what “important” means for your team. It shapes which Opportunities Lane recommends, which Signals get flagged, and how Ask Lane and your automations answer. Q: How many tiers can I prioritize?
A: Up to two. Q: What does Not now do?
A: Lane won’t recommend anything that matches it, in Ask Lane, in automations or as an Opportunity. Q: What if I leave Context empty?
A: Lane still works, but its answers and recommendations are more generic, and Signals won’t carry badges for your key or at-risk accounts.