01
Curated team feeds
The people whose judgment your organisation already trusts — a partner, a head of compliance, a knowledge lead — hand-pick what matters into a shared feed with a line on why. Everyone in that team sees it, flagged as curated.
Lexstream Enterprise
Even Pros need help.
Enterprise gives you the Team you need.
Everything in Pro, for every person in your organisation — plus the layer that turns one lawyer’s reading into something the whole team knows: curated team feeds, discussion on the item itself, a workspace carrying your name, and the numbers to prove it is being used.
Trusted by
What Enterprise adds
Eight ways Enterprise helps your Team.
Pro is a tool for one person. Everything below exists because a second person got involved — and none of it can be simulated by buying more Pro seats.
02
Discussion on the item, not around it
Notes, replies, @mentions and reactions sit on the development itself, where the next person to open it will find them. The alternative is a forwarded link and a thread nobody can search six months later.
03
They find out the same day
An @mention or a new curation raises a notification the moment it lands. Nobody has to remember to check a shared folder, and nobody researches the same development twice without finding out.
04
A workspace with your name on it
Your logo and a short pinned note from leadership on every member’s home screen. It reads as your organisation’s system rather than another subscription somebody expensed.
05
New joiners arrive configured
Set the topics and jurisdiction once per team, and anyone you invite into it starts with a relevant briefing on their first morning — no onboarding wizard, no blank feed, no “which of the 27 do I pick”.
06
Shared team streams
Saved searches every member gets automatically — the client names, matter names and regulations your organisation is actually tracking this quarter. Set centrally, updated centrally.
07
Analytics your admin can act on
Seats used, active against dormant members, reading over time per team, and what people actually read against what the team was configured to follow. The gap between those two is usually the most useful thing on the screen.
08
Administration that is genuinely yours
Invite, assign a team, promote to admin, remove. Access is recomputed on every request, so adding or removing somebody takes effect on their next action — no waiting, no re-login, no support ticket to us.
For whoever signs the invoice
You can see whether it worked.
Most information subscriptions are impossible to evaluate. You pay, people say it is useful, and at renewal you have a feeling instead of a number. Your admin panel answers it directly: how many of the seats you bought are being used, by whom, and on what.
Dormant seats are named as dormant, so you can move this licence to someone else or take note for your teams’ evaluations.
The comparison worth having is the last one: what each team was configured to follow, against what its members actually read. When those diverge, the configuration is usually wrong, and it takes a minute to fix.
Reading is reported per team and above, never as one person’s reading list. What is visible per member is account state — active or dormant — and nothing else.
Side by side
Where the line actually falls.
Free and Pro are self-serve, priced and published. Enterprise starts where a second person needs to see what the first one found.
| Feature | Free | Pro | Enterprise |
|---|---|---|---|
| Reading | |||
| News, blogs and commentary | |||
| Filter by topic, jurisdiction and date | |||
| Case law, legislation, regulatory, competition and procurement | — | ||
| Semantic search over case law and legislation | — | ||
| Saved articles and custom streams | — | ||
| Daily and weekly email briefings | — | ||
| Audio briefing | — | ||
| Working together | |||
| Curated team feeds — “Save to Team” | — | — | |
| Team notes, replies, @mentions and reactions | — | — | |
| Curated for You home view | — | — | |
| Notifications for mentions and new curations | — | — | |
| Share to Microsoft Teams | — | — | |
| Running it | |||
| Multiple seats under one agreement | — | — | |
| Your logo and a pinned note on every home screen | — | — | |
| Teams with their own default topics and jurisdiction | — | — | |
| Shared team streams, set centrally | — | — | |
| Organisation analytics | — | — | |
| Buying it | |||
| Published price | — | ||
| Self-serve checkout | — | ||
| Trial without a card | n/a | 14 days | 30 days |
| Named contact, agreement and invoicing | — | — | |
Nothing in this table is a roadmap item — every row is something the product does today.
Getting there
Configured before anyone logs in.
The usual failure of a team subscription is that everybody gets a login and nobody gets a reason to return. We build the workspace first, so the first screen your people see is already about their work.
01Together
We build the workspace with you
One call to map your teams onto topics and jurisdictions, then we set it up: branding, teams, the searches you are actually tracking, and who has the standing to curate for others.
Teams
CorporateM&A · Competition
DisputesLitigation · Arbitration
EmploymentEmployment · Data
02Day one
Your people arrive to something relevant
You invite them into a team and they land on a briefing already scoped to that team’s work, under your logo, with your note at the top. No wizard, no empty state.
Seats
03Ongoing
You watch it land, we stay on the call
Thirty days, no card, the complete product. Your admin panel shows who is using it while the trial runs, and a named contact on our side works the gaps rather than waiting for a renewal date.
Reads per week
Diligence
Written for the person who reviews vendors.
Our buyers are the most diligence-literate buyers alive. So this section states only what we can show you today — every line below is something we can evidence, not something we intend.
Your data is in the EU
The application, the database and the backups all run in Ireland — a single EU region for hosting, storage and recovery.
Tenant isolation is tested, not asserted
No request can widen its own scope: an organisation identifier supplied by a client is never what selects the data. The cross-organisation denial cases are part of the test suite that runs before a release.
No user data reaches an AI provider
Classification and summarisation send published source text and nothing else — no account data, no identifier, no reading history. Personalisation is computed inside our own database and never leaves it.
Every subprocessor is published
A public register naming each third party we use, what personal data it processes and where — kept current rather than produced on request.
Read the registerA bad day costs minutes, not a day
Backups run continuously rather than once a night, and the data can be put back exactly as it stood at a chosen moment — so what is ever at risk is minutes of work.
Deletion actually deletes
A member’s erasure cascades across their account and content, and each erasure is recorded in an audit trail that stores a hash rather than re-introducing the email it just removed.
Privacy noticeBy organisation
Whose teams already work this way.
Law firmsEvery practice group on one thread, partners curating for their teams.Read Financial institutionsLegal and compliance reading the same supervisory change on the same day.Read Data protectionDPOs and privacy counsel tracking enforcement across jurisdictions together.Read Public affairsA dossier followed by a team rather than remembered by one person.Read Public sectorDepartments configured separately under one organisation.Read UniversitiesFaculties and research groups with their own topics and shared reading.Read
Questions
The ones procurement asks.
How much is Enterprise?
It depends on seats and what the agreement includes, and we do not publish a rate. There is no self-serve Enterprise checkout by design: we set the workspace up with you, and finance handles the agreement separately. A demo is the fastest way to a number.
Do you train AI on our reading, or on anything we write?
No. What goes to an AI provider is published source material — a judgment, a regulator decision, a news article. Your notes, your curation, your searches as an identified user and your reading history are not sent, and nothing we send carries a user identifier. Personalisation is computed inside our own database.
What happens when the 30-day trial ends?
Access reverts and nothing is deleted. Your teams, curation, notes and configuration stay exactly as they were, so converting later picks up where the trial stopped. Anyone who also holds a personal Pro subscription keeps it — the two never collide, because access is always the higher of the two.
Can someone belong to two organisations at once?
Not today — one person, one organisation. It matters for counsel who sit inside a client, and for anyone who moves between two entities you administer; tell us and we will work around it during setup rather than after.
Who can curate for a team?
Administrators always, plus anyone you grant the curator role — and a curator can publish into any team in your organisation, not only their own. That is deliberate: the person with the best judgment about a development is often not in the team that needs it.
Do you replace our compliance or matter management system?
No, and you should be suspicious of anyone who says yes. This sits upstream of those: it is how your organisation finds out something changed, not where it records what it did about it.
Are mobile notifications available to everyone on the team?
Push notifications are iOS-only at the moment; there is no Android or web push yet. In-app notifications and email briefings reach everyone regardless of device.
One organisation.
One shared brief.
Thirty days, no card, the complete product — with the workspace configured for your teams before your people ever log in.
Book a demo
Or write to us at info@lexstream.io — a real person answers.