Proposals Settings
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.
Where to Find Them
Owners and admins find Proposals Settings (with the card Defaults for New Proposals) on Proposals' Settings page, the last item of Proposals' menu (action proposals.settings.get). The same page lists Proposals' modules and fields, with their icons, and Proposals' roles (Apps).
Settings
Change Settings (action proposals.settings.save):
- From address and From name: proposals, copies of answers, and notices come from this address. It must be one your workspace can send from. Proposals cannot be sent until it is set. Leaving it, the From name, or Prepared by empty clears it.
- Prepared by: shown on new proposals. Left empty, it is the person who starts the proposal.
- Proposal numbers start with and Next number: each new proposal takes the next number, 1001 at first. Leave the start empty to follow your Company Code on Settings, Numbering (ACMEP- with the code ACME), or P- while you have no code (Numbering). A start is a letter, then letters or digits, ending with a dash. A proposal is never numbered below Next number, nor with a number already used with its start, so none is used twice; a start another kind of record uses is refused. Clearing the start (action
proposals.settings.savewithclear) follows the Company Code again. When you change it, Existing Records offers Also update existing proposals; each keeps its old number, and its payment invoices are still made only once (Updating Existing Records). - Days a proposal is valid: 14 at first, counted from the day it is sent. Its Valid Until date is set when it is sent, and set again when a new version is sent. A company that never changed it follows the usual number.
- Days a link still opens after that: 60 at first. The client can read their proposal (and download its PDF) for this long after it expires.
- Percent paid at acceptance and How the rest is paid: your usual payment schedule for a proposal's one-time amount. At first, 50% at acceptance and the rest Split Over the Project Weeks: one payment for each week of the Project Journey, the last one at launch. Or At Launch (one payment), or At Milestones (one at each step marked as a milestone, and at launch). These are set parts of the price quoted, never billing for time. With no Project Journey or no one-time amount, everything is paid at acceptance. Amounts are worked out to the cent, and the last payment takes any rounding. A proposal can have its own schedule instead (Writing Proposals).
- Agreement wording: what the client agrees to when they accept. {company} becomes your client's company (or "my organization" when it has none). At first: "I agree to this proposal and I am authorized to accept it for {company}."
- Electronic signature consent: a second box the client ticks, to sign electronically. At first: "I agree to sign electronically and to receive this agreement and related records electronically. My typed name below is my signature and has the same effect as a handwritten one." Leave it empty to not ask.
- Timing note under the Project Journey: at first, "Dates assume approval within two business days of each review. If approval takes longer, later dates move by the same amount, and we confirm the new dates with you."
- The agreement, the consent, the timing note, your working days, and the payment schedule are saved with each version when it is sent, so changing them never changes what a client already saw or agreed to. Both wordings agreed to are kept with the client's answer.
- Make an invoice in Invoices for each payment on its day (on at first; needs the Invoices app, and the proposal linked to a CRM company): see Payments and Invoices.
- Charge Proposal Payments Automatically (on at first when your Stripe account is connected, off otherwise, until you choose): each payment is invoiced on its day, the first the day the client signs, and charged right away to the client's saved bank account (their backup card if the bank refuses). See Payments and Invoices.
- Move the CRM deal when a client answers (on at first).
- Start a contract when a proposal is accepted (on at first; needs the Contracts app).
- Remind clients who have not answered (off at first), When reminders go out (After sending at first, or On set weekdays until the proposal expires), and Business days after sending for each reminder (3, 7 at first) or Weekdays for reminders (Monday, Wednesday, and Friday at first; at most 12 for a proposal with no Valid Until date): see Reminders.
- Email a proposal's owner when it is opened or answered (on at first), or when the client asks for a new proposal after it expired. With it on, owners and admins are also emailed when a proposal is approved to send, or when an approved proposal could not be sent at its time (Approve and Schedule).
Work Requests
Open work requests each client may have (action proposals.settings.save) is how many requests one client may have open at once: 5 at first, from 1 to 50. A client at the limit reads "You have 5 open requests. Please wait for an answer before sending another." The kinds of work a client can ask for are set under Request Types (Work Requests).
Who Sees Prices
The Who Sees Prices card on the same page sets who sees prices and dollar amounts in every app: Owners and Admins (at first) or Owners Only. Members never see them, and your client always sees the prices on their own proposal. Only an owner changes it (action core.prices.save). With Owners Only, admins see proposals without prices, the same as members, even when they can bill in Invoices or Subscriptions. See Who Sees Prices.
Bringing in Settings
Proposals Settings from another system (action proposals.settings.import, owners and admins, from an import file): fills in the agreement wording, the signature consent, the timing note, and the payment schedule only where you never set them, the days a proposal is valid only while it is not set or still the 30 days proposals once started with, turns reminders on once, only while they are off, and sets when reminders go out (such as on Monday, Wednesday, and Friday until the proposal expires) only while you never chose a schedule or weekdays, so running it again changes nothing you set.
Proposal Emails
Proposal Emails (action proposals.emails.list) lists the emails Proposals sent or is about to send, and any that were not sent, with the reason. At the top, Reminders Coming Up shows each reminder about to go out, with Show Email (action proposals.reminders.preview).
