Frequently Asked Questions

The research intelligence side of Lapis. You brief it on a program, and autonomous researchers called Scouts read the public record continuously and tell you what changed. Every finding arrives with its evidence attached.

A keyword alert only fires when someone happens to use your words. Lumen scores each record against your technology, your roadmap, and your claim position, so it catches the filing that describes the same mechanism in different language.

Six streams, read as one evidence layer: patents and published applications, research literature, grants, clinical trials, regulatory activity, and company movement. No source is read in isolation, because none of them are conclusive in isolation.

Only what survives. Almost everything fails the relevance test against your program, and that rejection is the work. Of a typical week of public output, roughly 0.003% reaches a decision brief.

It covers the continuous reading an in-house analyst would do, without the hire, and unlike a commissioned report it does not start ageing the day it lands. What to do about a finding stays your team's call.

Yes. Scouts run inside a Project, so findings, documents, and collaborators all sit in the same place.

Create a Project, brief your first Scout, and findings start landing on your Dashboard on its first scan.

An autonomous researcher assigned to one program. You give it an objective, the entities that matter, which sources and patent offices to read, and how often to run.

You describe what you are protecting and what would matter if someone else moved on it. Everything the system judges later is judged against that brief, so you are not maintaining a keyword list.

The project it protects, the key entities and terms, the sources and patent offices to read, the scan schedule, and any named organizations you want watched.

Overlapping mechanisms, emerging methods, freedom to operate, named organizations, clinical and regulatory activity, and competitor movement. All six are included on every plan.

Yes. A Scout can run sub-scouts, each carrying part of the objective, and their results roll up into the same findings feed.

On the schedule you set, as often as every day. You can also start a run manually, and a run keeps going if you navigate away from the page.

Yes. Edit the brief, its sources, or its schedule at any time. Changes take effect on the next scan, and findings already surfaced stay where they are.

Yes, from the Scout's overview. A paused Scout keeps its run history and everything it has already surfaced.

Its overview shows which sources are live and how much of the perimeter is being watched. The run history logs records read, how many earned deep analysis, and how many were surfaced.

A record, or a set of records, that cleared the relevance threshold for your program, together with the reason it was surfaced and the evidence underneath it.

Every finding carries the trail that produced it: when the record was ingested, what it was screened against, what it was cross-referenced to, and the moment it was escalated. Nothing arrives as a verdict you have to take on trust.

Yes. Every finding links out to the source record at the office or publisher that published it.

Technical overlap, intent, evidence quality, and proximity to your protected core are scored separately, then weighed. Below the threshold the entity stays on watch and nobody is interrupted.

Yes. Tell the Scout whether a finding was useful, and that feedback sharpens what it surfaces next.

Usually because there was almost nothing. The run history shows records read against records surfaced, so a quiet week reads as genuinely quiet rather than as a system that stopped working.

That is the point. Weak records are linked back to the organization behind them, so a scattering of documents becomes one actor with a direction.

By week, by briefings or findings only, and by relevance, source, and time range.

What changed, the evidence it rests on, which part of the program it touches, how confident the system is, and what is worth doing about it.

On your schedule, as often as every day. Weekly is the common cadence.

Five risk axes, each either moved or flat against a stated baseline, with the findings that moved them cited underneath. A quiet week is allowed to read as quiet.

What the record is, who filed it, what it overlaps, and why that matters to your program specifically.

That is what it is built for. Briefs, charts, graphs, and coverage maps are ready to present, with no exports to chase and nothing to assemble by hand the night before.

Yes, through the same external collaborator controls as the rest of the workspace, scoped to a single Project.

USPTO, EPO, WIPO, CIPO, JPO, IP Australia, KIPO, CNIPA, UK IPO, and DPMA. Offices are selected per Scout.

Roughly 150,000 patents, 49,000 papers, 2,800 grants, 1,400 trials, and 860 regulatory events. About 204,000 new records in seven days.

Yes, on the Program plan and above.

Private and messy internal sources can be wired in on the Portfolio plan.

The perimeter is read continuously rather than in periodic sweeps, so movement surfaces while it is still evidence instead of after the announcement.

No. Patents are the largest stream by volume, but a filing on its own rarely settles anything. Literature, funding, trials, regulatory activity, and hiring are read alongside it.

Admins set up the organization first. Team members join through an emailed invite link. Sign up with Google, or with email and password.

Your team's private workspace in Lapis, home to every Project, Scout, and Finding.

Create a Project, then deploy your first Scout. Findings start landing on your Dashboard right away.

The workspace where Lumen tracks a specific technology or program, with your documents, findings, and competitor data in one place.

Dashboard for the latest brief, Findings for what your Scouts found, Search for patent and literature lookup, and Map for landscape views.

Click "+ New", select "New Project", name it, and set its visibility.

Go to the Collaboration tab and click "Add Collaborator".

In "Add Collaborators", click "Add Entire Team".

Use the "External" tab in "Add Collaborators" and enter their email.

Find them in the Collaboration tab, open the three-dot menu, and select "Update Role".

Private is invite-only. Public is visible to your whole organization.

Organization roles apply account-wide. Project roles apply only within that Project.

Yes, under Project Settings, then Roles and Permissions.

The main log covers organization-level activity. The Project log covers only that Project's edits.

It becomes read-only. Unarchive at any time to restore full access.

Deletion is permanent and erases everything in the Project. It cannot be recovered.

DOCX, PDF, TXT, PNG, and JPG. Drag and drop several at once.

Click "+ New" and select "New Folder".

Click "+ New" and select "New Document".

Drag and drop in the sidebar, or use "Move to Folder" from a document's menu.

Archiving hides it but keeps it safe. Deleting is permanent and cannot be undone.

Words matches exact terms. Meaning understands intent and finds relevant results even when the wording differs. Live Offices searches patent office records directly.

Yes. Use Meaning mode and ask it the way you would ask a person.

The mode selector sits in the search bar.

The main tab is the synthesized answer. Sources shows the underlying patents and papers behind it, each with a relevancy score.

Lumen reads across sources and composes an answer rather than just matching keywords.

It refines your last search without making you start over.

Filters by patent office, jurisdiction, classification, assignee, status, or date range.

Check spelling, broaden your terms, or switch modes. Live Offices is best for names, Meaning is best for concepts.

Yes, searches are logged and visible to admins.

Look for white space on the Topographic and Positioning maps. It marks where nobody has filed, or where the field is still open.

Landscape views of the space around your program: where activity is dense, who is clustered together, and where nothing has been filed at all.

Activity tells you where a field is crowded. Empty space is where the next opening is, and it is the part a list of alerts will never show you.

Yes. The landscape is rebuilt from the same continuously read record the findings come from.

Click "+ Add Members" on the Team page. Paste emails, or upload a CSV for larger groups.

Select members on the Collaboration page and click "Create Group".

Select them, then choose "Add to Group" from the action menu.

Team is your organization's members. External Collaborators are outside partners, and only on the specific Projects you add them to.

Member views and edits what they are assigned. Trusted Contributor creates and manages. Admin manages users and permissions. Owner controls billing and the account.

Deactivating cuts off the whole organization. Removing only drops them from that one Project.

Account or Billing in settings. Owner access is required.

Yes, use "Version History" from the document's menu.

Organization access does not include Project access. Add them to each Project separately.

Confirm they were invited, that they accepted the email, and that their status shows "Active".

Unarchive it from Project Settings, then General Settings.

Use Support in the main menu to book a call, email us, or find us on Slack or LinkedIn.

Pilot is $500 a month, Program is $1,000 a month, and Portfolio is priced per portfolio.

Pilot is a low-commitment look at what Lapis finds in your space. Program is for teams running active programs and adds source requests and priority support. Portfolio covers unlimited programs, custom scout schedules, your private data sources, SSO, a security review, a DPA, and dedicated support.

Yes, on every plan, including Pilot.

Pilot and Program are scoped per program. Portfolio covers unlimited programs.

On your schedule, as often as every day, on every plan. Portfolio adds fully custom scout schedules.

Yes. Bring one program and the organizations you already worry about, and we will show you what the last ninety days of public record say about them.

HTTPS and TLS 1.2 in transit, and AES 256-bit encryption at rest.

Google SSO or email codes. You can restrict the workspace to approved sign-in methods only.

Yes, workspace access can be limited to your private network.

Audit logs track important workspace events over the last 3 months.

Multi-region hosting is available, so you can choose where your data lives.

Yes. You control which third-party apps can access your Lapis workspace, and you can restrict system-level privileges.

Both are available on the Portfolio plan.

Private Projects are invite-only. Public Projects are visible to your organization. External collaborators only ever see the Projects you add them to, and private teams can be created for work that should stay narrower still.