Sending and Withdrawing
Part of the MountDev Ops Proposals documentation. Updated November 19, 2026
MountDev Ops Proposals documentation | Updated November 19, 2026
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.
Sending
Send to Client on a proposal's page (action proposals.send, permission proposals.send):
- To: the client's email (filled in from the proposal), and an optional note for the email.
- The draft becomes this version, frozen exactly as sent, with a fingerprint (SHA-256) of the document. Any version sent before it is replaced, and its link stops working.
- A private link is made for this version. It needs no sign-in, it is signed so it cannot be guessed or changed, and it expires: it can be answered until the Valid Until day, and still opened for 60 more days (see Proposals Settings).
- The email waits one minute, then for your business hours: sent while you are closed, it goes out at your next opening, and the proposal says when (Email and Business Hours). Undo (action
proposals.send.undo) takes it back before it goes out: the version is a draft again, and anything it replaced comes back. Only the person who sent it can undo it. - To send, Proposals Settings needs a From address, and the proposal needs a title and a section or a line.
- Its Valid Until date is set when it is sent: the days in Proposals Settings (14 at first) from today. Whatever date the draft showed was only an estimate.
The email is laid out in your company's email template (Settings, Email): your header color and logo, the proposal's number and Valid Until date, and your company's details at the bottom. It states why it was sent, and its link carries UTM tags. Every Proposals email uses the template: the proposal, the client's copy of their answer, the code to confirm their email, and the notices to your team.
Approve and Schedule
The project manager of the project a proposal is for can approve it to be sent, without seeing its prices. Approve and Schedule on a proposal's page (action proposals.approve, permission proposals.approve) shows to:
- the Project manager of the project in the proposal's Project field (their address in the project's Project manager field), and
- owners and admins, who can also send it themselves.
A proposal with no project can be approved only by owners and admins.
Approving needs everything sending needs: the client's email address, a From address in Proposals Settings, a title, and a section or a line. If any is missing, nothing is approved and the message says what to add.
Once approved:
- The proposal shows Approved | Sends and the day and time, such as Approved | Sends Fri, Oct 9, 10:00 AM PDT, and an Approved and Scheduled card with who approved it and when. Its Approved by, Approved, and Scheduled to send fields are set, so its history keeps who approved it, and its activity says so too.
- It sends at your next opening from Business Hours, in your time zone, skipping your closed days and holidays. Approved while you are open, it sends five minutes later, so there is a moment to cancel the schedule; approved while you are closed, it sends when you open.
- Owners and admins (everyone who may send proposals) get an email saying it was approved and when it sends, within your business hours, and see it in Needs You Today. The email never has prices in it.
- Until it goes out, they can change its prices (or anything else in the draft), choose Send Now to send it right away the usual way, or choose Cancel Schedule (action
proposals.schedule.cancel). The person who approved it can cancel too. A cancelled proposal stays a draft and can be approved again. - At its time it is sent the usual way, with the person who approved it as its sender: the same email, a new private link, and valid for the days in Proposals Settings counted from the day it really goes. There is no minute to undo, since it could be cancelled until then. If your business hours changed so you are closed at that time, it waits for your next opening.
- If it cannot be sent then (the From address was cleared since, say), it stays a draft, the proposal says why, and owners and admins are told.
A new version of a proposal needs its own approval.
Withdrawing
Withdraw (action proposals.withdraw) takes back a proposal waiting on the client: its link stops working and it can no longer be accepted. The reason is for your records only. You can revise it and send it again.
Ready to Send
An AI agent can check a draft the way a person would and mark it Ready to Send for a person to confirm (action proposals.send.prepare, Work Requests). The mark shows as a pill on the proposal and as a card on Needs You Today for the people who may send. It never sends, schedules, or approves anything, any change to the draft clears it, and the person then uses Approve and Schedule or Send as themselves.
For AI Agents and API Keys
AI agents and API keys never send, undo, or withdraw a proposal, never start a contract from one, and never delete one. Those stay with people. An agent or a key with the access can start a proposal and write its draft (actions proposals.create and proposals.draft.save), so a connected system can prepare a draft for a person to review and send, and can mark it Ready to Send (proposals.send.prepare) once it is ready for a person to confirm. Without the pricing permission, a draft it writes takes its prices from your products and Price Lines, as it does for any person without that permission.
Neither an AI agent nor an API key can approve a proposal on its own (proposals.approve). An approval made through an assistant for a named person is theirs, with every check theirs, and shows as approved by them "via" the assistant.
