Handoff
handoff.
Deal-pack & e-signing platform · built for Australian dealerships

Every deal gets typed twice.
We're deleting the second time.

Handoff reads the contract of sale your DMS already prints, lifts the customer, vehicle and price out of it, and carries that deal through checklist, signing and reporting — without a single API call to Pentana or Auto-IT.

~70%
of the AU DMS market sits behind one vendor
0
API integrations needed before you can sign a deal
1
PDF in — every other document in the pack auto-fills
CONTRACT OF SALE — ERANET v4.2 customer.full_name vehicle.vin deal.price EXTRACTED — VERIFIED BY STAFF CUSTOMER J. Whitfield VEHICLE · VIN 6G1MK5 · WVWZZZ1JZ3W… PRICE $38,450 → populates 6 more documents in the pack
Zone-mapped extraction: fields are lifted from fixed positions on a known contract layout, staff verify the core fields once, and that single verified record fans out to every other document in the pack.
Why this shape

The gap isn't missing software — it's shallow integration

Pentana holds roughly 70% of the Australian DMS market, and the friction of integrating with it is now the subject of federal litigation (Titan DMS v Pentana). Existing deal-pack tools either aren't built for Australia or only ever get shallow, vendor-controlled access — duplicate entry survives even the "integrated" setups.

So Handoff asks for nothing. It reads what already comes out of the printer.

How it works

Reads the DMS. Owns the handoff. Competes with neither.

Four layers, one read-only relationship with the system that actually creates the compliant contract. Handoff never asks the DMS for write access — it reads a document the DMS already produces for printing.

CRM / leads e-GoodManners, Dealer Studio owns: the prospect HANDOFF ingestion signing audit trail owns: the handoff itself DMS Eranet / eraPower, Units / PMDS owns: transaction of record Reporting SalesLogs-style grid reads contract PDF (export/print — no API) optional pull / push — phase 3 push — nightly 6pm AEST + manual "refresh now"
The only inbound dependency is a printed or exported PDF from the DMS. Everything else — the CRM sync and the reporting push — is optional or one-way, and neither blocks the core signing workflow.

Not the CRM

Doesn't try to own the prospect relationship or lead pipeline. That stays exactly where it already lives.

Not the DMS

Doesn't generate the contract, touch inventory or accounting. The DMS remains the compliant transaction of record.

Not the leaderboard

Doesn't replace KPI or commission reporting — it feeds them clean, already-verified deal data instead.

Trust

Signing that holds up

A signature only ever saves inside an active, authenticated session — never pre-staged, never a reusable image applied later.