Skip to content
Sam Jennings
Case Study · 04Royal LePage Wolstencroft2026

One signing engine. Two systems the brokerage runs on.

How I built a real estate brokerage its own e-signature platform, then ran onboarding and commission advances on it: self-hosted, Canadian-resident, and keeping its own records.

Client
Royal LePage Wolstencroft
Sector
Real estate brokerage
Timeline
Five days, then three
Stack
Next.js · Supabase · DocuSeal
The brief

Not a website. The thing the business runs on.

A brokerage brings on two very different kinds of people. Employees (administration, conveyancing, management) and Realtors, who are independent contractors. Each arrives with a stack of documents that has to be signed, countersigned, and filed somewhere it can be found again in five years.

Email was the system. Documents went out as attachments, came back signed in whatever state the signer managed, and were filed into the HR drive by hand. It worked the way manual processes work: fine for one hire at a time, and unable to answer “what is this person still waiting on?” without somebody going and looking.

The ask was a portal to keep track of it. What it needed was a signing platform with the brokerage’s own name on the infrastructure. These are employment records, and where they live and who holds the audit trail is part of the specification, not an afterthought. Building it that way is also why the second system on this page took three days.

The first system

Onboarding ran out of an inbox. Now it runs itself.

BeforeWhere a new hire stood lived in somebody's sent folder, a shared drive, and a spreadsheet.

AfterOne checklist per hire. Signatures arrive on their own, and the signed PDFs file themselves.

Illustrated. The portal holds live records, so no real screens are shown.

01

No single source of truth

Where a new hire stood lived in somebody's sent folder. Answering “what is this person still waiting on?” meant opening an inbox, a shared drive, and a spreadsheet, then guessing.

02

Two intakes treated as one

Employees and Realtors need different documents, different checklists, and different filing. The manual process ran them down the same track and corrected by hand afterwards.

03

Filing done by dragging

Signed PDFs were downloaded from email and dropped into the HR drive by hand. Naming drifted, folders diverged, and the occasional document simply never landed.

04

Rented custody of employment records

Off-the-shelf signing services charge per envelope forever and hold the signed record, and its audit trail, wherever the vendor chooses to. For employment files, that placement is not a detail.

The second system

Three days, because the engine was already there.

Agents at the brokerage can ask for an advance against the commission on a firm deal, and it is repaid out of that commission when the deal completes. The process was a workbook and a chain of emails: someone checks the deal, someone approves, paperwork gets signed, money goes out, and weeks later somebody has to remember to take it back.

By then the hard parts existed. Signing, countersigning, storing the signed record, and telling people when it was their turn were all running for onboarding. So the advances portal went from first commit to production in three days, and those days went on the part that was actually new: the rules about when money is allowed to move.

It did not touch a real deal for another six weeks, on purpose. The people who would use it sat down and ran one through from request to repayment, that dry run turned up five changes, and the first real deal went through after they were made.

BeforeA workbook, with the state of each advance kept in the notes column and in people's heads.

AfterEvery advance on one board, from request to repayment, and funding locked until the books show it.

Illustrated. The portal holds live records, so no real screens are shown.

01

No money moves until the books agree

An advance is only safe if it is recorded against the deal in the brokerage's accounting system, so it comes off the commission at completion. That entry is made by a person, in another system. So funding is locked until conveyance confirms it, with a name and a time on the confirmation. It is not a checklist item. The button does not exist until it is done. The dry run added the same lock on the way out: an advance cannot be closed until the interest is posted there too.

02

The cost is worked out in one place

The calculator an agent sees, the approval screen, and the ledger all read the same figure from the database. The legal ceiling on the cost of borrowing is written into that one calculation, so going over it is not something a screen can get wrong.

03

Decisions are a record, not a status

Every verification and approval is a new line with who, when, and why. Lines are never edited or removed; a correction is another line. One person never signs both sides of an agreement, and a signing link shows only to the person it is addressed to. Those rules live where the data lives, not just in the interface.

04

Every step happens once

A double click, a slow connection, a second person pressing the same button: none of them can send two sets of documents or record funding twice. With money involved, “it usually only fires once” is not good enough.

5
Days to the first
running system
3
Days to the second,
on the same engine
0
Per-signature fees,
now or ever
0
Signed documents
filed by hand

A signing platform isn’t a form tool. Its database is evidence, so it gets backed up like evidence, and no template is ever edited after somebody has signed it.

What I built

The full scope.

  • /
    A self-hosted signing engine
    DocuSeal in Docker behind Caddy on a Canadian VPS, with TLS, key-only SSH, a firewall, and automatic security updates. No per-signature fee, and the signed record never leaves infrastructure the brokerage controls. Both portals send their documents through it.
  • /
    The onboarding portal
    Invite-only. Every active hire with real progress, a checklist per document, and status per signer. Employees and Realtors run on separate tracks with their own document packs, chosen when the hire is created. The new hire gets one link: no account, no password, no attachments.
  • /
    The advances portal
    An agent sees the cost in dollars and requests from the same screen. Conveyance verifies the deal, an approver signs off, the agreements go out for signature, and the ledger follows the advance from funding to repayment. It works on a phone, because that is where agents are.
  • /
    Signature status that can't be faked
    Completed signatures arrive from the signing engine and are applied automatically. Signature items cannot be ticked off by hand at all. If the screen says it's signed, a real signature exists behind it.
  • /
    Filing and chasing, without a person
    Signed PDFs and their audit trails are filed into the brokerage's existing HR folder structure, in the naming it already used. A daily digest lists everything outstanding, quiet candidates get nudged, and each person in an advance is told when it is their turn.
  • /
    Evidence discipline
    Nightly off-box database dumps and weekly snapshots, because the signing database is the evidence. Templates are versioned and never edited in place once anyone has signed one.
Judgement calls

The part I refused to automate.

Before wiring a single real document into the onboarding system, I read the brokerage’s entire document pack end to end. Some of it wasn’t ready to be automated yet, and automation is very good at taking a document nobody has finished reviewing and putting it in front of a hundred people.

So the platform shipped complete in July, proven end to end on placeholder templates, with a standing rule written into the spec: no draft document becomes a live template until it has been through proper review. The rule held for three months. The reviewed pack went in during November, and the same tooling can send a revised document out to everyone who signed the old one. The machine was ready before the paperwork was, and that’s the right order. The reverse is how a brokerage ends up with two hundred signatures on a document it has to re-paper.

The advances agreements followed the same rule: the fields were mapped while the wording was still with the lawyers, and nothing went to an agent until it came back final.

Two other things stayed out on purpose. Anything collecting full payment card details never went near either portal. That’s a compliance regime I wasn’t going to drag a hiring tool into for the sake of tidiness. And files that are access-restricted by design stayed where their restrictions already worked.

Knowing what not to put through the system is most of what makes it safe to hand over.

Under the hood

Five moving parts. One surface.

For anyone who wants the wiring, this is the onboarding side. The advances portal is a second box beside the first, talking to the same signing engine.

Admincreates the hireNew hireone link, no loginTHE PORTALNext.js · Verceldashboard + progresstwo-track checklistscandidate hubsetup sheetinvite-only authPostgres + AuthSupabaseCanadian regionSIGNING ENGINEDocuSeal · self-hostedDocker + Caddy, TLSCanadian VPSnightly off-box dumpsFiling workercron, every 5 minutessigned PDF + audit trailHR systemexisting Drivefolder structureEmaildaily digest, nudgesexpiry alertscreate requestwebhook: signedrequest / data flowsignature event: the only way an item completes
The portal is the only surface anyone touches. Everything to the right of it (signing, filing, notifying) runs without a person in the loop.

Got a process that only works because somebody remembers?

Most businesses have one: onboarding, quoting, approvals, intake. Email carries it, a person chases it, and nobody can say where it stands without asking. That’s the kind of thing I build out.