Pills. Studio.
For every legal task,
the solution that fits it.
Studio takes a legal task that costs you time, and settles it with whatever fits. Sometimes we have already built it: an automation or a skill from the catalogue. Sometimes we build it for you. Sometimes it already exists inside your own tools. And sometimes a product on the market is the better answer, in which case we say so.
Studio stands on its own. No diagnosis and no prior consulting engagement are required.
- A requestIntake · Qualification · Assignment · Tracking
- A contractGeneration · Approval · Signature · Renewal date
- A piece of knowledgeSource · Structure · Agent · Sourced answer
Three standalone offers.
None is a prerequisite.
Pills., Pills. Studio and Pills. Academy each stand on their own. They combine when that is useful, never out of obligation.
- ConsultingPills.
We improve how the legal system runs and performs: organisation, processes, data, steering.
The method - SolutionsPills. Studio
We bring technology to legal tasks, off the shelf or built for you.
- TransmissionPills. Academy
We pass on what we practise. Formats to learn, build and experiment.
Pills. Academy
Before adding a tool,
we look at what you already have.
Most legal departments already pay for bricks they never open. That is a starting point, not a rule: when what you have is not enough, we say so and we move on.
SharePoint · Teams · Power Automate · Copilot Studio · Power BI · Purview
Drive · Forms · Apps Script · AppSheet · Gemini · Looker Studio
The tools are not what interests us. What you can do with them is.
A request. A contract.
A piece of knowledge.
Three legal tasks Studio settles end to end. Depending on the case, the solution already exists or gets built.
The request comes in through a single door, reaches the right person, and its status can be read without asking for it.
The document is generated from your templates, follows the approval path you defined, and its renewal date is flagged before it passes.
What you already know becomes searchable. Every answer points back to the document it came from.
Two ways to get the solution
Neither one is the compulsory route to the other.
Automations that install inside your own tools, and skills that require no installation at all. The catalogue is published on pills.studio, one solution at a time.
Browse the cataloguepills.studio · opens in a new tab
When nothing available settles the task properly, we build the solution. It starts with a conversation about the task.
Describe a needOne automation.
Not a new tool.
Anonymised engagement, at a French subsidiary of an international healthcare group.
- Before75 minutes
per NDA, from request to filing
- Context20 to 40 NDAs / month
on Google Workspace, already deployed
- DecisionDo not add a CLM
the environment in place could carry the need
- BuildOne automation inside Google Workspace
triage, tiered approval, filing, renewal reminder
- After10 minutes
per NDA, on the same scope
on the processing time of an NDA
at this volume
No additional licence was required for this engagement.
A measurement from a single engagement, on a given scope and volume. It is not an average, not a typical result, not a guaranteed outcome, and not a ratio to reuse elsewhere.
The other documented engagements, with their measurements and their limits, are published in the open. See the case studies
The right tool is the one
the task justifies.
Three possible answers, settled task by task. None is better on principle, and two of them sell you nothing.
- Keep
What you have already settles the task properly. We leave it alone.
- Build
Nothing available settles the task. Studio brings the solution: an automation or a skill from the catalogue, or something built specifically.
- Buy
A product on the market objectively answers it better. We tell you so, even though we do not sell it.
No vendor commission. We resell nothing.
What we put in place
stays under your rules.
Depending on the solution, what Studio installs lives inside your tools or alongside them. Either way, the frame is set before, not after.
- When the solution installs inside your tools, it uses the identities and permissions you already have. We do not create another set.
- Where the architecture allows it, it stays under the governance already in place: logging, retention, classification.
- When the solution lives outside your tools, we say where it lives and what passes through it, before you decide.
- Depending on the use case, scoping runs with IT, the CISO or the DPO. We do not decide in their place.
The four questions
that come up every time.
Does Studio replace a CLM?+
Not on principle. Studio settles a contract task with whatever fits: a solution from the catalogue, something built for you, or what your environment already carries. When volumes, negotiation or reporting obligations go beyond all of that, a dedicated CLM remains the right call, and we say so.
Do we need to buy new licences?+
It depends on the solution. A skill requires nothing installed on your side. An automation often builds on bricks already included in the subscriptions you pay for. Some advanced features are billed separately. That point is settled before we start, not afterwards.
Who maintains what Studio puts in place?+
A solution from the catalogue is maintained by us. A solution built inside your environment belongs to you: we document it and hand it over, to you or to your IT team. We can stay on call, but that is never a condition.
Do we need a Pills. consulting engagement before working with Studio?+
No. Studio stands on its own: you can arrive with a specific task and leave with the solution, without any prior diagnosis. Pills. consulting answers a different question, the one about how the whole thing runs. The two combine when that is useful.
Pick a solution,
or talk about a task.
The available automations and skills, presented one by one on pills.studio.
Explore Pills. StudioOne hour to describe the task, look at what already exists and decide what needs building. No commitment, and no prior consulting engagement.