> ## Documentation Index > Fetch the complete documentation index at: https://assembly.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Proposal builder > Build multi-page proposals from reusable templates, let clients pick the services they want, and track each proposal until they accept or decline. > [!NOTE] > > **Template.** You can change anything about this app by describing it in its build chat. See [App templates](https://assembly.com/docs/building-new-apps/app-templates.md). Build slide-style proposals from your own templates and send them to a client or a whole company. Clients read the proposal in your client experience, pick the services they want, ask questions in comments, and accept or decline. You see when each proposal is sent, viewed, accepted, or declined. **Category:** Proposals · **Used by:** your team and your clients · **Works with:** CRM, Payments services ## Features * Multi-page proposals with a cover and content pages, built from ready-made pages such as **Introduction**, **Executive summary**, **About us**, **Scope of work**, **Deliverables**, **Service selection**, and **Next steps** * Content blocks for text, images, tables, charts, timelines, team, testimonials, terms, and calls to action * Reusable templates you can create, reorder, archive, and start new proposals from * Service selection blocks that list services and prices from your workspace, where the client picks one or any number * Five statuses: **Draft**, **Sent**, **Viewed**, **Accepted**, and **Rejected**, plus **Archived** * Comment threads on the whole proposal or on a single page, with replies and resolving * A view count and last-viewed date for each sent proposal * Search and filters by status and recipient, with sortable columns The app doesn't take payments, create invoices, or start subscriptions. A client's service choice is recorded on the proposal and sent to your team, but nothing is billed. To charge for the work, send an invoice once they accept. ## How to use it ### For your team > [accordion] Create a proposal > > 1. Open the app and click **Create proposal**. > 2. Under **Start from**, choose **Blank proposal** or one of your templates. > 3. Enter a **Title** and choose a **Recipient**. Both are required. Choosing a company sends the proposal to every client in it. Choosing a client sends it to that person only. > 4. Click **Create proposal**. The proposal opens as a draft in the editor. > [accordion] Build the proposal > > 1. Edit the cover, then add pages. Start from a blank page or a ready-made one such as **Scope of work** or **Service selection**. > 2. On each page, use the add content menu to add **Text**, **Image**, **Text + image**, **Two columns**, **Table**, **Chart**, **Service selection**, or a preset such as **Timeline**, **Team**, **Testimonial**, **Terms**, or **Call to action**. > 3. Reorder pages with **Move page up** and **Move page down**, change a page's **Background color**, or delete a page. > 4. Open **Details** to change the **Title** or **Recipient**. > > Changes save as you go. > [accordion] Offer services for the client to choose > > 1. Add a **Service selection** block to a page. > 2. In the **Services** panel, pick services from your workspace, or click **Create a service** and enter a **Name**, **Description**, **Price**, and **Cadence**. A service you create here is added to your workspace's services. > 3. Under what the client can pick, choose **One** or **Any**. **One** means the client has to pick a service before they can accept. **Any** is optional, so they can pick any number or none. > [accordion] Send a proposal > > Click **Send proposal**. Only drafts can be sent, and a proposal needs a recipient first. Once it's sent, the proposal is read-only. To make changes, duplicate it and send the copy. > [accordion] Track proposals > > The proposals list shows each proposal's **Status**, **Recipient**, and its **Created**, **Sent**, **Accepted**, and **Last activity** dates. Use search and **Filters** to narrow by status or recipient. Open a sent proposal and click **Details** to see how many times it was viewed and when it was last viewed, and, once accepted, the services the client **Selected**. > [accordion] Reply to comments > > Click **Comment** to open the proposal's comments. Clients can comment on the whole proposal or on a single page. Reply in a thread, or start a new one. Your team can resolve a thread once it's handled. Comments your team writes on a draft aren't shown to the client until the proposal is sent. > [accordion] Manage templates > > Click **Templates** to see your templates, then click **Create template**. You build a template the same way as a proposal, but a template can't be sent. Hold and drag a template to reorder it. From a template's actions you can duplicate, archive, restore, or delete it. Use **Show archived** to see archived templates. > [accordion] Duplicate, archive, or delete proposals > > From a proposal's actions, choose **Duplicate**, **Archive**, or **Delete**. A duplicate is a new draft. An archived proposal can't be responded to, and the client still sees it marked **Archived**. Deleting a proposal removes it for everyone. ### For your clients > [accordion] Review a proposal > > Clients see their proposals under **Proposals**, with each one marked **Awaiting your response**, **Accepted**, **Declined**, or **Archived**. Opening a proposal shows every page, and they can print it. > [accordion] Pick services > > In a service selection block, the client picks the services they want. If the block asks for one service, they need to pick one before they can accept. > [accordion] Ask a question > > Under **Questions and comments**, the client can ask a question or leave a comment, or comment on a single page. They can reply to your team's replies. > [accordion] Accept or reject > > The client clicks **Accept proposal** and confirms, or clicks **Reject** and can add an optional **Comment** to say why. They can respond once, while the proposal is waiting for their response. After that, the decision is final. Clients only see proposals sent to them or to their company. They never see drafts or templates. ## Notifications * **When you send a proposal**, the recipient, or every client in the recipient company, gets an email and an in-product notification. * **When a client first opens a proposal**, your team gets an in-product notification. * **When a client comments**, your team gets an in-product notification for every comment, and at most one email every five minutes. * **When your team comments on a sent proposal**, its clients are notified. * **When a client accepts or declines**, your team gets an email and an in-product notification, with the services they picked or the reason they gave. A client who accepts also gets a confirmation email. Team members with limited client access are only notified about clients they can see. To change who's notified or what the messages say, see [Configuring notifications](https://assembly.com/docs/building-new-apps/configuring-notifications.md). ## Set it up **1. Add the template** Click **Add App** in the Dashboard sidebar. Find **Proposal builder** under **Start from a template**, or scroll down to **Browse all apps** and pick the **Proposals** filter. **2. Try it as your team** The app lands in your sidebar as a draft. Create a test proposal, add a **Service selection** block, and send it to your test client. **3. Check the client side** In the builder's **Client view**, pick your test client, pick a service, leave a comment, and accept or reject the proposal. **4. Publish it** Publish the app with visibility set to **Hidden from all people**, or on plans with custom visibility, limited to your test client. Sign in as your test client to try it in the real client experience, then make it visible to the clients who should use it. See [Launching apps](https://assembly.com/docs/building-new-apps/launching-apps.md). ## Change it with the app builder This app is a template, so you can change anything about it by describing what you want. **1. Open the build chat** Open **Proposal builder** from your Dashboard sidebar, click its name at the top, then click **Switch to builder**. **2. Describe the change** Write what you want the way you'd ask a teammate. Say who it's for and where it shows up, such as the proposal editor or the client's proposal page. **3. Check the preview** The app builder makes the change and updates the preview. Switch between **Team view** and **Client view** to check both sides, and pick a client to see it as them. **4. Publish** Click **Publish** when you're happy. Until you do, your clients keep seeing the last published version. Changes people often make to this template: * "Add an expiry date to each proposal and stop clients from accepting after it" * "Ask the client to type their full name to sign before they accept" * "Remind the client by email if they haven't responded three days after I send a proposal" * "Let me edit a sent proposal and resend it instead of duplicating it" * "Show a running total of the services the client picked at the bottom of the proposal" * "Add a Landscape option to the paper orientation" See [Iterating on apps](https://assembly.com/docs/building-new-apps/iterating-on-apps.md) for how to describe changes well and how to go back to an earlier version. To rename the app, or change who can see it and how it notifies people, click its name at the top and choose **Rename app** or **Manage app**. ## Related > [card] [Sales pipeline tracker](https://assembly.com/docs/apps/sales-pipeline-tracker.md) > > Track open deals by stage, with value and owner > [card] [Client intake form](https://assembly.com/docs/apps/client-intake-form.md) > > Collect scope, goals, budget, and timeline from new clients [View this template on assembly.com](https://assembly.com/templates/proposal-builder) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.