> For the complete documentation index, see [llms.txt](https://help.getweddingos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getweddingos.com/sales/sending-a-proposal.md).

# Sending a Proposal

Proposals in WeddingOS are a combined package overview, inclusions list, and service agreement — all in one document. When a client signs, they're automatically moved to Booked and a signed PDF is saved to their Drive folder.

***

## Before you send

Make sure the following are in place:

* The lead has an **email address** on file
* At least one **package** is configured in Settings → Packages
* Your **payment schedule template** is set up in Settings → Payment Schedules

***

## Sending the proposal

1. Open the lead's profile and click **Send Proposal** in the top right
2. Select the **package** you're proposing — the price and payment schedule preview automatically
3. Click **Review & Send →**
4. Review and edit the details before it goes out:

| Field                     | Notes                                                                                          |
| ------------------------- | ---------------------------------------------------------------------------------------------- |
| **Total Investment**      | Defaults to the package price — edit this if you need a custom amount (e.g. a multi-day event) |
| **Client Name**           | Pre-filled from the lead record                                                                |
| **Partner / Fiancé Name** | Appears in the proposal header                                                                 |
| **Event Name**            | Auto-generates as "Smith/Jones Wedding" when a fiancé name is set — editable                   |
| **Wedding Date**          | Drives payment due dates — update if it's changed                                              |
| **Venue**                 | Appears in the proposal and contract                                                           |
| **Payment Schedule**      | Auto-calculated from your template — you can edit individual amounts and dates                 |

5. Click **Preview Proposal** to see exactly what the client will see
6. Click **Send Signing Link →** — the client receives an email with a button to review and sign

> If you change the Total Investment and click out of the field, the payment schedule recalculates automatically.

***

## What the client experiences

The client receives a branded email with a link to their proposal. On the signing page they can read the full package inclusions and service agreement, then type their name to sign electronically. No account or login required.

***

## After signing

When the client signs:

* Their status automatically moves to **Booked**
* A signed PDF is generated and saved to their Drive folder
* The client receives a confirmation email with the signed agreement attached
* You receive a notification that the contract has been signed

The proposal status card on their profile updates to show **Signed ✓** with a link to the PDF.

***

## Resending or copying the link

If a client hasn't signed and needs a reminder, open their profile and find the proposal status card. From there you can **resend the email** or **copy the signing link** directly. If the link has expired (30 days), WOS automatically generates a fresh one.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.getweddingos.com/sales/sending-a-proposal.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.