About

Why UpLift exists

A producer's working life at a carrier or agency is split across systems that do not talk to each other. UpLift joins the two halves.

The gap

Getting a producer contracted is one job: licences, appointments, E&O, agreements, background checks — usually tracked in email threads, a shared drive and somebody's spreadsheet. Measuring what that producer then writes is a different job, in a different system, owned by different people.

Nothing carries across the seam. The moment a producer is appointed, the record of how they got there stops being useful, and the record of what they produce starts from nothing. Ask a simple question — was this producer appointed in that state when that policy was written? — and answering it means opening two systems and trusting that both were kept current.

One producer, one record

UpLift is built as a single platform with two components. OnBoard runs contracting: checklists that adapt to a producer's type, states and lines of authority, with review steps on the items that carry compliance weight. Sales runs production: contests, live standings and rewards over imported sales data.

They are not two products bolted together. A producer is one record whether they are being contracted or being measured, and that record holds through the messy cases — a producer writing business through more than one agency keeps a single identity, with every sale still attributed to exactly one agency.

Built for carriers and agencies

UpLift's customers are insurance carriers and agencies. A customer may subscribe to either component or both, and the same producer may be affiliated with more than one of them — so every screen is scoped to the organisation viewing it. A carrier sees its own producers and its own numbers; an agency sees theirs. Producers themselves see only their own records.

Evidence, not assertions

Contracting is a compliance activity, so the system is built to be defensible rather than merely convenient. Task transitions are recorded in an append-only trail: who verified what, and when. Uploaded documents are versioned rather than overwritten, and nothing is deleted — a superseded E&O certificate stays on file, so the question of what was on record on a given date always has an answer.