# How to send a proposal

> Create a proposal for a client and site, add priced service lines, preview the honest investment summary, then send it. Sending is a three-step chain that ends in your explicit approval. The client accepts through a portal signing link, which forms a binding acceptance and stands up the contract.

URL: https://biloh.com.au/docs/how-to/send-a-proposal
Category: How-to guides | Audience: operator | Updated: 2026-08-05

To send a proposal in biloh you build it, preview it, and send it for acceptance. You can do every step by chat (ask your AI assistant) or in the web app — the steps are the same.

## 1. Create the proposal

Create a proposal against a **client** and one of their **sites**. If the client or site does not exist yet, create them first (or use the one-step onboarding composite). A new proposal starts in `draft`.

## 2. Add priced service lines

Add a line for each service you are quoting, with its price and — for recurring work — its cadence (weekly, monthly, a multi-visit program, or specific dates). Pricing is captured in integer cents and shown to the client as a clear investment.

Where one client has several premises, you can attach each line to the premises it covers and send a single document covering them all — see [one proposal, many sites](/docs/concepts/one-proposal-many-sites).

## 3. Preview the investment summary

Before sending, preview the **investment summary**. This is the same honest, frequency-aware figure the client will see on the signed agreement and the accept page — visits per year are placed on their true months, not evenly smeared. Previewing here means there are no surprises at acceptance.

## 4. Send it

Sending is deliberately a **three-step chain**, and nothing reaches the client until the last one:

1. **Stage** the send — this renders the PDF and resolves exactly who will be emailed, so you can check the recipient list before anything goes out.
2. **Confirm** it — this mints the client's signing token.
3. **Approve** it — this is the step that actually sends the branded email.

The staging step is worth using properly: it reports the resolved recipients up front, which is how you catch a proposal about to go to the wrong contact.

## 5. The client accepts

The client accepts through the **portal signing link** in the email, by typing their name to sign. Acceptance is captured as immutable legal evidence under the Electronic Transactions Act, and the accepted proposal stands up the contract and its schedule automatically.

Do not ask a client to reply to the email with acceptance wording — a reply is not the signing flow, and it will not stand the proposal up.

## 6. If you need to change it afterwards

A sent proposal is immutable. Supersede it with an amended copy instead — see [amending a proposal after you have sent it](/docs/how-to/amend-a-proposal-after-sending).

## Related

- [What is biloh?](/docs/getting-started/what-is-biloh)
- [One proposal, many sites](/docs/concepts/one-proposal-many-sites)
- [Amending a proposal after you have sent it](/docs/how-to/amend-a-proposal-after-sending)
- [Connecting biloh over MCP](/docs/reference/mcp-overview) — to do all of this by chat.