In private use · not yet generally available

Practice management for Canadian law firms

Everything below is one package. None of it is an add-on.

Notes. Tasks. Calendars. Undertakings. Deadlines. Documents. Time. Invoicing. Trust accounting. Minute books. A client portal. One set of records.

The deadline, the undertaking it came from, the document that discharges it, the time you spent and the invoice it lands on are one chain, because none of them is a second copy.

hello@kamenic.ca The firms we are talking to now are shaping what gets built next.

What it is

Normally four or more products, from four or more vendors.

Four subscriptions, four support desks, four places the same client's name is typed. And the integrations meant to join them become the thing you maintain: a sync that runs overnight, a field that quietly stops mapping, two vendors who each say it is the other one's end. Kamenic is the one database underneath all of it, so there is nothing to join.

All eleven are on from your first day, and not one of them is compulsory. Use the notebook and nothing else, if that is what your practice needs — the rest waits, costing you no attention, until the day you reach for it. And not one of them is the junior version of a product you would otherwise buy on its own.

NotesPinned to the matter, the party, or nothing at all.
TasksUrgent and important are two switches, not one list.
CalendarThe firm's, the matter's and yours, one grid.
UndertakingsGiven and received, each with its own state.
DeadlinesComputed from the event, showing the calculation.
DocumentsVariables, versions, comparison and redline in place.
TimeCaptured beside the work, not after it.
InvoicingPro forma, revisions, and what was actually billed.
Trust accountingDouble-entry, immutable, reconciled monthly.
Minute booksRegisters computed from the resolutions.
Client portalThe same record, with the parts they may see.
All of itOne package, nothing held back — and nothing you are made to use.

Where it lives

Your records stay in Canada. Your clients' documents stay in your own Microsoft 365.

Matters, time, ledgers and minute books are held on Canadian servers, in the Canada region — not for processing elsewhere, not for backup elsewhere, full stop.

Your clients' documents are different: the files stay in your firm's own Microsoft 365, where they already are, and we reach them with your permission. So that you can search inside them, Kamenic keeps an extracted copy of their text beside your matter, on the same Canadian servers. Switch that off and Kamenic purges what it holds.

Made to fit

Your practice, and the places you practise.

Legal software usually arrives with someone else's way of working already baked in, and the firm spends years bending around it. The things that differ most — firm to firm, and province to province — are the things Kamenic puts in your hands instead of guessing at. Set them once and every matter follows them.

Precedents
Twenty-three corporate documents to start from, each keyed to a jurisdiction. Your firm can replace any of them with its own; a lawyer can keep a personal version on top of that; either reverts to the one underneath in a click. If your version falls behind the firm's, Kamenic says so.
Templates
A template is a set of documents you apply to a matter in one go — your wording, your formatting, your order of operations. Fork one to try a change without touching the original.
Fields
Decide which fields your documents actually use. The matter supplies the content, so a name is typed once and lands everywhere it belongs.
Deadline rules
No two provinces count the same way. Kamenic ships rule sets as worked examples, marked unverified, and will not write a date from a rule your firm has not reviewed — it stops, names the rule, and records who accepted it. Authoring your own sets is in development.
Every firm has a way of doing things that took years to work out. Kamenic is built to take instruction from it.
14 Rue Principale — purchase2026-0418
AllNotesTasksCalendarDeadlinesUndertakings
Discharge of the vendor's mortgagedue 12 Sep

Undertaking given · to the vendor's lawyer

Executed transfer, held pending closingreceived 2 Sep

Undertaking received · from the vendor's lawyer

Draft the statement of adjustmentsDo first

Task · urgent and important

Registration deadline30 Sep

Deadline · 30 days from closing, 31 Aug

An illustration, not a real firm's matter. Every row carries a shape and a word as well as a colour — an undertaking given and one received are never told apart by hue alone.

Notes, tasks and dates

One notebook per matter — and one that holds all of them.

Everything that happens on a matter lands in one merged stream. Narrow it to notes, tasks, the calendar, deadlines, or undertakings — the records do not move, your view does.

Undertakings are first-class, given and received, each with its own state and its own discharge. Deadlines are computed from the event that triggers them and show the calculation and the rule they came from, so a date can be checked rather than trusted.

Open it on a single matter, or open the one that gathers everything you have written across every file you touch — each note still carrying the matter it belongs to. You have a personal notebook that belongs to no matter at all, and the firm has one of its own.

Documents

Drafted, versioned and compared where you practise.

Variables come from the matter, not from a merge field you filled in twice. Change the purchase price and every document that quotes it says so.

Every version is kept, none is overwritten, and comparing two of them — as a diff or as a redline — is a view, not an export to a different program and back.

Agreement of purchase and salev6 → v7

Clause 3.1 — purchase price

The Purchaser shall pay $412,000.00 $418,500.00 on closing.

Both figures are the matter's {{purchase_price}} variable, at v6 and at v7. Four other documents quote it.

v7 · 2 Sep · A. Bellv6 · 28 Aug · R. Shaw7 versions kept, none overwritten

An illustration, not a real firm's document.

Trust reconciliation 31 August
Statement balance$47,318.40

Typed from the 31 August statement. Kamenic cannot verify this figure.

Trust ledger$47,318.40

142 entries to 31 August, none editable since posting

Client ledgers$47,318.40

38 client ledgers, footed

Bank vs ledger$0.00
Ledger vs clients$0.00

An illustration, not a real firm's data. The amber line is the only permanently unverifiable figure in the accounting module — because a person reads it off a piece of paper, and the software will not pretend otherwise.

Time, invoices and trust

Every figure says what it rests on.

Time is captured beside the work that earned it. It becomes a pro forma you can argue with, then an invoice, then a receipt against the client's ledger — one chain, no re-keying, and the trust side is double-entry throughout.

The reconciliation is not a report the software writes about itself. It is the ledgers, footed, beside the one number a human had to type — labelled as such, every month, forever.

And it foots twice: the bank against the trust ledger, and the trust ledger against the sum of every client's ledger. A trust account can agree with the bank to the cent and still be wrong about whose money it is.

How it behaves

Rules the software holds itself to — not settings a firm turns on.

Never a bare number.

Every figure carries what it is made of and what it rests on. Where a figure depends on something the software genuinely cannot check, it says so, in a different colour, every time.

Reports foot to a control account and say so — including when they disagree.

A report that is out by $432.00 renders “out by $432.00” and still shows every row. Hiding a discrepancy removes the evidence you would need to find it.

Nothing is ever edited.

The database refuses to update or delete a posted ledger entry — for everyone, including the firm that owns it. A correction stands beside the entry it corrects.

Registers are computed, not maintained.

Ask who the directors were on a date three years ago and it recalculates the answer from the resolutions. There is no separate register to fall out of step.

It says what it does not know.

A refusal names its reason. So does a blank. An unadopted deadline rule will not produce a date, and it will tell you that is why.

In development

Named, so you can ask for the one you need.

These are being built, not shipped. If one of them is the thing you need, say so — it moves up the list.

Not available yet
  • iOS appThe notebook, time capture and matters on your phone — and saving an attachment to a matter straight from your mail.
  • Two-signer trust withdrawalsSignatories and countersigned requisitions, so a firm with more than one lawyer can commit a trust cheque under its own controls.
  • More than one officeOffices as a dimension across people, matters and trust accounts — because most firms that grow, grow this way.
  • Your own deadline rulesThe calculation and the refusal gate are built. Authoring your own rule sets, rather than working from ours, is next.
  • More holiday calendarsStatutory days are loaded data, and today Kamenic carries New Brunswick for 2026. Ask it to count business days past the end of what is loaded and it refuses rather than quietly skipping a holiday. Further provinces and years are loading, not building.
  • Practising in more than one provincePrecedents, rule sets and holidays are each already keyed to a jurisdiction. What is being built is the part that knows which one a given file belongs to, so the right set is chosen for you rather than by you.
  • Filing straight to the corporate registriesAnnual returns and changes filed from the minute book to the registry that wants them, instead of re-keyed into a second website.
  • Corporate structure chartsThe ownership of a group, drawn from the share transactions already recorded — parents, subsidiaries and who holds what.

Who it is for

A law practice — whatever its size, whatever its province, whatever the work.

Practice areas
Any of them. The eleven above are not a narrower proposition in one area of law than in another: a matter, a notebook, a trust ledger, a calendar and an invoice are the same shape whatever the file is about. What is specific to an area — precedents, rule sets — is data, the same way a second province is.
Firm size
One lawyer, or hundreds. The records are the same shape at either end — what changes is how much structure you switch on: roles for lawyers and for support staff, who may see which matter, and how work is assigned.
Where
Canada, Atlantic provinces first — and firms that practise in more than one, which is most of them. Precedents, rule sets and holidays are each keyed to a jurisdiction, so a second province is a set of data rather than a different product. Choosing the right set per file is on the list below.
Built by
A practising New Brunswick lawyer, for his own firm first. Nothing on this page describes a feature he would not have to use on Monday.

Status

Kamenic is in private use. We are not taking general sign-ups yet.

If you practise law in Canada and this sounds like the software you have been asking for, write to us. We will show you where it is up to, and we would like to hear what your practice needs — the early firms are the ones setting the order of what gets built.

hello@kamenic.ca