Notary software

NotarPartner, B2B software for notary offices

6 months

Initial phase, from architecture to a working templating core

Word + PDF

Legally binding output, compiled directly from the web editor

People on the alm team, embedded in NotarPartner's product team

Challenge

Every feature costs more

The existing notary software did its job, but it belonged to a technology generation in which every new feature costs more than it is worth.

A successor platform, not a patchwork

Rethink templating logic, editor and output paths without lowering the predecessor's standard for legally valid Word and PDF documents.

How it works

From editor to document

WYSIWYG editor
Handlebars template
Custom compiler
LibreOffice
Word & PDF

The notary team works in the web editor; the output is produced directly as legally binding documents.

Solution

Templating core

Custom Handlebars engine

Compiles content directly into Word and PDF, while a full TipTap editor remains available in the frontend.

LibreOffice in the backend

For Word generation, a deliberately pragmatic choice over proprietary solutions.

Playwright for the output paths

Where Word and PDF output is legally binding, behavior has to be reproducible.

Platform

Design system

Built alongside feature development, so the growing platform stays consistent.

Modern frontend

React, Next.js, Tailwind and Zustand for state management.

Supabase as backend

A faster development loop and clear REST interfaces.

Result

The core is in place; rollout is next.

In six months, the platform went from architecture to a working templating core. The notary team keeps working in the WYSIWYG editor, and the output is compiled directly into legally binding Word and PDF documents. alm and NotarPartner continue development together; the rollout is scheduled for the coming weeks.