Yes, AI can draft the sales proposal from the meeting notes, on your own template. When the salesperson promises a quote in a meeting noted in Granola, a Muzau agent fills in a copy of your template in Google Slides, with what the notes say and the prices from your catalog. The recap email that attaches the proposal as a PDF waits for your approval. Your edits in Google Slides go out with it.
At the end of the meeting, the customer asks for a quote and the salesperson promises: "I'll send you the proposal on Thursday." Back at the office, they have to reopen the last proposal they sent, change the name, find the prices, copy the need from their notes, proofread. Between two meetings, this work slips to the next day, then the day after.
Meanwhile, the customer's memory of the meeting fades. Judgment on the offer and the relationship stay with the salesperson; filling in the template and drafting the email that carries it is what the agent takes on.
You upload your sales proposal template, a PowerPoint file of 10 MB at most. Muzau converts it to Google Slides in your Google Drive, which must be connected. It suggests the places to put the customer's name, the date, their needs, the prices, the total, their phrases, their goals and the next step. You tick the ones to keep, once and for all. Without a template, you receive the quote request written out as text, to be priced.
When the salesperson promises a quote in a meeting taken down in Granola, the agent spots the promise along with the exact sentence that states it. It then fills in a copy of the template in Google Slides. Every value written must rest on a passage of the notes. Prices come only from your catalog, for a confirmed price with VAT filled in. A field left empty on a slide blocks sending until you complete it. It needs a note with a single participant from outside the company. For the rest, see the mistakes an AI makes when writing to your customers.
The meeting recap email attaches the proposal as a PDF and waits for you in "To approve". The proposal always goes through your approval, even if you have turned on sending recaps without review. You change a price or a sentence in Google Slides: the PDF is generated from the copy at the moment you click, and your edits go out with it. If the promise has a date, the reminder the salesperson gets the day before the deadline says the proposal is ready. For these reminders, see the promises made to a customer.
If the customer asks for a change after sending, "Prepare a new version", from the customer's row, copies the sent proposal and drafts a new email in "To approve". The PDFs already sent stay available, version by version. If the salesperson sends the proposal themselves from Gmail or Outlook, with the PDF or the Google Slides link, the prepared proposal is withdrawn and the customer's file opens. For this, Muzau must be watching that mailbox. If the customer does not reply, the follow-up works as after any recap: see the follow-up after a meeting.
A proposal sent after a meeting is not a brochure: it answers one specific conversation. The customer should find what they said in it, and see what they have to do next.
The email that carries it stays short. Its subject says what it contains, for example "Your proposal, following our meeting". The text recalls the request in one sentence, mentions the attachment and suggests a time to go through it together.
Before sending, reread the first page: another customer's name left over from an old document is spotted straight away. Send a PDF rather than an editable file: everyone reads the same document, and the version sent is the one you will find again.
Autonomous does not mean unchecked. You set the level of autonomy of every agent, its limits cannot be crossed, everything it does is recorded in a plain-language log, and one gesture stops it all.
For the tasks you don't have time for. You give the address of your website, then describe the work in your own words. Nothing to install.