The Clerk'r night-shift report for Danish firms  Read now →
How it works
Request → Delivery
From request to delivery.

An email comes in. Clerk'r files it on the matter, assigns the task, prepares the draft and keeps an eye on the deadline. You approve. Nothing leaves the firm without your click.

Gathered, Assigned, Prepared, ApprovedSee how→
Built with
Built inside a law firm. Not just near one.

Clerk'r was built with a leading Danish employment law firm, on their real matters.

About us→
NewsLaunch

Clerk'r is out of stealth

Today we're officially launching Clerk'r for everyone. For the past months, we've been building quietly alongside our first customers, starting inside Danish law firms, on real matters. Now we're ready to share it more widely.

Clerk'r
4 min read
The three founders behind Clerk'r on a rock ledge above a mountain lake
The three founders behind Clerk'r

One conversation became an obsession

Clerk'r began with a conversation about how different industries were using AI. For founders Patrick Kjærsgaard, Yaw Gyamfi and Niels Høgh Høiberg, legal work became the subject they kept coming back to.

What interested them was how much of a firm's value lives in the work it has already done. Years of advice, negotiations, documents and decisions create a body of knowledge that lawyers draw on every day. Helping them put that experience to work felt like something worth building.

The conversation turned into a prototype. Then the prototype found its way into a real law firm.

Before we knew it, we had an MVP being used on real matters. We were seeing early users report time savings of two to four hours a day, per lawyer. That was the turning point when we knew we were going all in.

Patrick KjærsgaardCo-founder and CEO

So we moved in

We built Clerk'r with a handful of law firms that became our first customers. During development, we even moved into their offices.

Working beside the people using the product gave us a much better understanding of what needed to happen between a client asking for help and a lawyer delivering advice. It also meant we could ask questions, test ideas and get feedback while the work was happening.

Our first focus was helping lawyers find and use the firm's existing knowledge. As we worked together, we began to see how much more we could help prepare around it.

The challenge was to improve service to clients while preserving the care and judgement behind it. That shaped the product far more than a list of features could.

From finding knowledge to preparing the work

Our first version helped lawyers find answers in their firm's own material. Working alongside them made us want to take that further: to help bring the context together and prepare the work that follows.

Today, Clerk'r connects the firm's matters, documents, templates and correspondence, helping lawyers research, review and draft using the knowledge their firm has already built.

Before it writes, it looks for relevant material on the matter and across the sources the lawyer is allowed to access. Previous advice, an agreed template or an earlier exchange with the client can all change what a useful answer looks like.

Asked in the matter: Clerk'r searches its documents, the firm's templates and the case's emails before it writes. Clerk'r, with example data

The starting point is the matter itself, with its history, documents and decisions.

Connecting the request to the work

A client request rarely arrives with everything neatly assembled. An email may contain new instructions, several attachments and a reference to something discussed weeks earlier. Someone has to understand the request, find the background and work out what needs to happen next.

That is where Clerk'r's orchestration layer comes in.

Consider a client asking for an employment agreement to be updated. The work might involve reviewing their comments, finding the current agreement, checking the firm's preferred clauses and preparing a revised draft with a covering response.

Clerk'r brings the relevant material together and prepares work for the lawyer to review. The lawyer can inspect the sources, adjust the draft and decide what happens next. Clerk'r never sends anything on its own.

Our ambition is to connect that process from the moment work enters the firm to the format in which it is delivered. Search, review and drafting become connected parts of the same assignment, with the matter's context carried through.

For the client, the value is practical: their lawyer has more of the preparation in place and more time to focus on the advice.

Two minutes on what Clerk'r does in a lawyer's day.

Every firm has its own way of working

Spending time inside law firms also taught us how much those differences matter.

Two firms practising the same area of law can approach a matter differently. Their templates, language, review habits and experience all shape the service clients come to them for.

Clerk'r is built to work with those differences. Firms can set instructions and preferences, and Clerk'r keeps track of corrections and feedback. Approving a draft, changing a suggestion or correcting where an email belongs helps shape how it handles similar work next time.

Drafts and plans wait for the lawyer. Every yes, change or no teaches Clerk'r something. Clerk'r, with example data

That memory is visible to the firm. Lawyers can see the instructions and observations it retains, and Clerk'r asks before saving recurring preferences to memory.

The goal is an assistant that becomes more useful as the firm works with it.

Built into the working day

Clerk'r works as an add-in for Word and Outlook, alongside Teams, SharePoint and the firm's case management system. Documents and matter information come from the systems where they already live.

  • Word
  • Outlook
  • Teams
  • SharePoint
  • + the firm's case management system

That connection matters as much as the AI itself. A useful draft needs the right context, and it needs to be available where the lawyer can review and use it.

Clerk'r shows the material behind its answers, so the lawyer can check the relevant passages and apply their own judgement.

Every suggestion shows what it rests on: the source, the quote, and why. Clerk'r, with example data

Ready for the next chapter

We're entering the market with a clear belief: a firm's experience should become easier to use with every matter it handles.

Better AI models will keep expanding what is possible. Our work is to turn that capability into something useful for legal teams, connected to their knowledge, their systems and the way they serve clients.

Clerk'r is out of stealth. Let's talk.

Get in touch

Tell us a little about your firm and what you'd like to talk about. We usually reply within one business day.

We only use your details to reply to you. Read our privacy policy.

Book a demo

See it on your own matters

We'd love to show you what Clerk'r can do with the work your firm actually runs. Book a demo and we'll walk through it on your own type of matters.

  • Launch
  • Legal AI
  • Company

About Clerk'r

Clerk'r is built with lawyers, for lawyers. It started in one law firm; today we build it for the whole industry. Built in Copenhagen, with data in the EU.

  1. 1Details
  2. 2Pick a time
  3. 3Booked
Esc closes

Tell us where to start

So the half hour is about your work, and not a sample matter.

30 minutes, online, with the people who built Clerk'r.

How many lawyers Optional