All 18 modules
Firm

Proposals

An accepted proposal is already a description of an engagement, a price and a schedule. Retyping it into the system is a step that exists only because your tools do not talk to each other. Here acceptance is what creates the engagement.

Defining a service in the LedgerOS catalog, with its pricing shape and billing trigger.

What it does

  • Proposals and engagement letters built from your own service catalog
  • Signed on acceptance, with payment details taken at the same moment
  • Acceptance spawns the engagement and sets up the recurring invoice

How it works

Decide how you bill for something once

Each service carries its own shape — fixed fee, hourly, per unit, recurring — so a proposal is assembled from things the firm has already agreed on rather than priced from scratch by whoever happens to be writing it.

  • Pricing kinds and recurrence set per service
  • Scope and quantity captured on the line, not in a note
  • A starter library you can import and then edit as your own
Defining a service in the LedgerOS catalog, with its pricing shape and billing trigger.

They accept, and the work exists

The engagements get created, the recurring schedules start, and you get told exactly what was set up. The acceptance is signed, and you can take payment details in the same breath.

Questions

Is the engagement letter separate from the proposal?
They are separate templates and can be sent separately, but both run through the same signature flow and file back to the client.

Next: Organizers — Send the organizer once, then see who has actually filled it in.

Read on →

Ready to retire the stack?

One plan for the whole practice — $129 per seat, every Practice module included. Start your free trial today; migration support from your current tools comes standard.

Start your free trial →

14-day free trial · No credit card required · Cancel anytime