Pills.
Approach · Legal Ops on Microsoft 365

Microsoft 365,
your Legal Ops base.

Most legal departments and legal professions already have, in their Microsoft 365, the infrastructure needed to build a CLM, a legal ticketing system, a compliance Q&A agent, an ExCom dashboard. No one activates it. Pills. builds on this existing stack. Not next to it. Not elsewhere.

What's already there

Four bricks,
already in your Microsoft 365.

SharePoint
Document management and metadata

Contract libraries, file workspaces, validation workflows, automatic versioning, granular access control.

Teams
Legal workspaces

Dedicated channels by file type, threads tied to a contract, Outlook integration, in-context document sharing.

Power Automate
Workflows and automation

Orchestration of incoming flows, automatic follow-ups, multi-level validations, e-signatures, notifications, archiving.

Copilot Studio
Smart assistants

Compliance Q&A, triage of incoming requests, document base queries in natural language, grounded on your sources.

What we build

Five use cases,
running on your stack.

Automatic tracking of contract deadlines. No new software, no document migration.

Automatic triage by type, assignment to an available lawyer, consolidated dashboard for the ExCom.

Covers recurring questions (GDPR, procurement policy, code of conduct). Each answer cites its source.

Drift tracking, D-1 data, shareable to the ExCom, drill-down on each metric.

Automatic retention rules compliant with legal obligations. Confidentiality labels applied to each document.

Dedicated SaaS vs. Microsoft 365

Why build
rather than buy yet another tool.

Topic
Licences
Dedicated SaaS
Additional licences (per user, per module)
Microsoft 365 stack
No licences added. You activate what's already paid for.
Topic
Data
Dedicated SaaS
Hosted at the vendor, under their control
Microsoft 365 stack
In your Microsoft 365, under your governance, your retention rules
Topic
Integration
Dedicated SaaS
Often partial, at extra cost
Microsoft 365 stack
Native with Outlook, Teams, SharePoint, Active Directory, your SSO
Topic
Configuration
Dedicated SaaS
Standard module fitted to everyone, not to you
Microsoft 365 stack
Built around your flows, your act types, your vocabulary
Topic
End of contract
Dedicated SaaS
Uncertain export, migration to redo
Microsoft 365 stack
Everything stays with you. Nothing to migrate.
Security and governance

The frame that reassures
your CISO and DPO.

DPIA and CISO already done

Your Microsoft 365 agreement already includes the compliance items (DPIA, certifications, EU hosting). A Legal Ops deployment fits within an existing frame, not a new full assessment.

Granular access control

Active Directory, MFA, Sensitivity Labels, Data Loss Prevention. Each user accesses only the documents that concern them, and an external auditor has nothing more.

Your data with you

Microsoft 365 hosted in Europe, audit logs available, configurable GDPR retention rules. Legal data does not leave your environment.

Frequently asked questions

The objections
we hear at every framing.

Are additional Microsoft 365 licences required for what Pills. builds?+

In the vast majority of cases, no. The M365 E3 or E5 licences already in place cover SharePoint, Teams, Power Automate (standard usage). For Copilot Studio or advanced Power BI, specific licences may be needed. We make this clear during the framing phase, based on your current contract.

What organisation size is needed for this to make sense?+

As soon as your organisation uses Microsoft 365 (which covers most organisations in France, Europe, the Middle East and Africa), the approach is relevant. A 3-person legal team can get as much out of it as a 50-person department. The tooling scales, the stack stays the same.

Does it fully replace a dedicated CLM SaaS (Ironclad, LinkSquares, DocuSign CLM)?+

For 80 to 90% of use cases of a mid-sized legal department or legal profession, yes. For very advanced cases (multi-party global contract negotiation, very specialised contract AI), a dedicated SaaS may make sense as a complement. We never start with "replace your SaaS" but with "identify what your existing stack can already do".

How long does it take to deploy a full CLM on Microsoft 365?+

Between 3 and 5 months for a structuring CLM (scope set in phase 1, co-build over 6 to 10 weeks, progressive rollout over 2 to 3 months, transfer). A narrower scope (e.g., NDA automation only) takes 6 to 8 weeks.

What if we already have a legal SaaS in place?+

We look at what it does well and what it doesn't. In some cases, we recommend keeping it and building on M365 what it doesn't address (internal ticketing, Q&A, ExCom dashboard). In others, progressive migration to M365 is more logical. The phase 1 framing settles this with data, not preferences.

Can your IT team maintain what's deployed after your exit?+

That's exactly the point. What's built on M365 sits on tools your IT team already masters: SharePoint, Power Automate, Power BI. The phase 4 documentary handover lets your IT team or internal champions take over without external dependency.

Get started

An audit
of what's already there.

One hour to identify what your Microsoft 365 can already do for your legal activity, and what's missing to cover your priorities. No commitment.

Book a meeting