Layr DocsHow teams use Layr
The in-app workflow from connected sources to review, opportunities, Ask Layr, and specs.
Once a workspace has connected tools and included sources, Layr becomes the place your team reads, curates, and acts on product evidence. This page maps the main surfaces in the app and a typical week-to-week rhythm.
Roles matter
Not every surface is editable for every role. Owners and workspace admins manage setup; product managers and project managers curate and draft; engineering roles and viewers read context. See Key concepts for the role summary.
Main surfaces
Home
Home is your workspace pulse.
- Setup checklist — unfinished governance steps (connect tools, invite team, run first sync).
- Source freshness — whether included Slack channels, Jira projects, and other sources are up to date.
- Recent signals — latest customer and team evidence Layr ingested.
Admins see an Open integrations link when a source needs attention. Other roles see freshness status without manage controls.
Integrations (governance only)
Integrations is where owners and workspace admins connect Slack, Jira, Linear, Notion, and Intercom; refresh discoverable sources; choose what to include; and run sync.
This is a setup surface, not a daily PM workflow. Most product users never open it — they consume the evidence it enables.
Review
Review is the human gate between raw incoming signal and structured product memory.
Layr classifies new evidence against existing problems or creates candidates for your team to evaluate. Product-action roles — Owner, Workspace admin, Product manager, and Project manager — can promote, reject, snooze, merge, or split candidates so only trustworthy problems enter the graph.
Think of Review as quality control: Layr proposes structure; your team confirms it.
Opportunities
Opportunities are promoted, evidence-backed problems ranked for prioritization.
Each opportunity shows supporting signals, heat trends over time, comments, watchers, and links back to the original messages, tickets, or docs. This is where planning conversations should start — not in a blank doc or a screenshot thread.
All member roles can browse opportunities. Curation actions stay with product-action roles.
Ask Layr
Ask Layr answers product questions in natural language using your workspace's product memory — the graph of problems, evidence, features, and decisions Layr has built from included sources.
Every answer is designed to be traceable: you can inspect the reasoning and the underlying evidence, not just accept a plausible paragraph.
Ask Layr is available to all member roles except Viewer.
Specs
Specs turn a prioritized opportunity into an execution-ready draft.
Layr generates a structured spec grounded in the opportunity's evidence — problem statement, user need, supporting quotes, proposed outcome, and acceptance criteria. Product-action roles edit, regenerate, export markdown, and optionally publish one Jira issue, Linear issue, or Notion page through an explicit write action.
Specs are an editing task, not a blank page.
A typical rhythm
Connect one high-signal source
An admin connects Slack or Jira first — not every tool on day one. See Integrations.
Include sources deliberately
Enable a small set of channels or projects. Confirm the first sync.
Invite the people who curate
Add product managers and engineering leads with the right roles. See Invite your team.
Validate on Home and Ask
Ask a question you already know the answer to. Confirm citations look right before expanding scope.
Layr ingests and classifies
New messages and tickets flow into product memory. Strong matches link automatically; ambiguous signal becomes a review candidate.
PMs curate in Review
Promote real problems, reject noise, merge duplicates. This keeps opportunities trustworthy.
Prioritize in Opportunities
Compare heat, evidence depth, and recency. Use comments and watchers for async alignment.
Ask before every planning meeting
Use Ask Layr to pull context instead of rebuilding it from Slack search and Jira filters.
Draft specs from opportunities
When something is ready for engineering, seed a spec from the opportunity — evidence carries forward.
Keep sources fresh
Admins monitor Home freshness and re-sync when integrations fail or scopes change.
What success looks like
| Before Layr | With Layr |
|---|---|
| Planning starts with "what did we hear lately?" | Planning starts with ranked opportunities and citations |
| Specs reinvent context from memory | Specs inherit evidence from the opportunity |
| One PM is the human API for product knowledge | The workspace memory is shared and auditable |
| Tool connections are all-or-nothing | Source inclusion is explicit and least-privilege |