Underwritetenant/underwrite-demo
Role
Request a demo

Operator surfaces: queues, clocks, correspondence, billing.

Services

Three engagements, each with a written output

The software is the product. These are the engagements that get an operator onto it and keep the correspondence moving, and each one ends in a document you keep whether or not you continue.

Priced from scope. Nothing here is billed before it is delivered, which is a habit rather than an obligation on this side of the contract.

  1. 01

    Tenant implementation

    Provisioning, migration and the dry run that finds what your templates are missing.

    • A provisioned tenant with your brand, domain and generated document set
    • Migration of open cases with every clock reconciled to a start evidence document, or flagged
    • A dry run against your existing contract and disclosure templates, with a written list of missing terms
    Duration

    2 to 6 weeks, phased by state

    Detail
  2. 02

    Compliance review

    A written review of your procedures against the controls the platform enforces, run with your counsel in the room.

    • Control by control mapping of your current procedure to CROA 1679b through 1679e
    • Review of your disclosure delivery evidence and your cancellation window handling
    • Clock practice review: what starts a window, what extends it, what your records prove
    Duration

    3 weeks

    Detail
  3. 03

    Bureau correspondence operations

    Managed despatch and intake, so proof of despatch and proof of receipt exist without anyone remembering to file them.

    • Certified despatch with article numbers and acceptance scans attached to the case automatically
    • Intake and classification of written results against the item they answer
    • Escalation queue for any window that expires without a written result
    Duration

    Ongoing, monthly

    Detail

How an engagement is run

The same shape every time. The dry run comes before the migration, because migrating into a template that fails validation just moves the problem.

  1. scopeSeats, states, volume, and the system you are leaving. One call, thirty minutes.
  2. dry_runYour templates and a sample of your cases through the controls, in a sandbox tenant. Output is a written list of findings.
  3. provisionTenant, brand, calendars, seats, keys. Your generated document set is produced and reviewed.
  4. migrateOpen cases first, closed cases second. Any clock that cannot be reconciled to start evidence is flagged, never silently dated.
  5. cutoverA signed baseline export is taken on the day, before the first live write.
  6. reviewNinety days later, against the findings document from the dry run.
An empty meeting room with a long plain table, identical chairs and a wiped-clean whiteboard
The dry run session. Your counsel in the room is the part that makes it worth running.