Create Accountor Login
Docs

What Your Client Sees

Part of the MountDev Ops Proposals documentation. Updated November 17, 2026

MountDev Ops Proposals documentation | Updated November 17, 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.

The Client's Page

The link in the email opens the proposal, exactly as that version was sent: your company's name, the title, number, version, who it was prepared for and by, the date, Valid until, every section, the Project Journey as a timeline with dates, the lines with their totals, any optional add-ons, the Payment Schedule (each payment, when it is due, and its amount; amounts follow the add-ons the client ticks), and your Notes, when the proposal has any, just before the Accept section. Links in the notes open in a new tab. It works on any phone or computer, with no sign-in, and without scripts.

Preview on a proposal's page (action proposals.preview) shows the same page in the workspace, with answering switched off, and prices only for people with the pricing permission.

Opening It

Each time the client opens the link it is recorded with their IP address and browser (the same device within half an hour counts once). The proposal's status becomes Viewed, its views and first and last viewed times update, and its owner gets an email the first time each version is opened.

Accepting or Declining

  • Accept Proposal: the client types their full name, email, and job title (all three are required), confirms their email with a code (below), ticks the box to sign electronically (when you ask for it) and the box to agree to your agreement wording, and chooses any add-ons. The add-ons are added to the totals and the payments as they tick them.
  • Decline Proposal: with their name, email, and job title, and a reason, if they like. Declining needs no code.

Confirming Their Email with a Code

Before Accept Proposal works, the client confirms the email they typed: Send Code emails a 6-digit code to that address (the one you sent the proposal to, or another one they type), and they type it on the page (action hooks link.code and link.verify).

  • A code works for 10 minutes and allows 5 tries. A new code replaces the old one.
  • At most one code every 30 seconds, and 5 an hour, for each proposal.
  • Only a hash of each code is kept, never the code itself.
  • The code email comes from your Proposals Settings From address, in Arial, says why it was sent ("You are receiving this because you are accepting proposal P-1001 from your company"), and has no links. It is in Recent Emails like any other.
  • The accepted answer's activity says the email was verified. A different address they typed is saved only after it is verified.
  • Without scripts, it is two steps: Send Code (the page comes back with what they typed), then Accept Proposal with the code.

Recorded with every answer, as a Response: the name, email, and title they typed, the time, their IP address and browser, the exact version (its record and fingerprint, checked against the document before anything is recorded), the add-ons chosen, the reason for declining, and the wording they agreed to. A response never changes.

Then:

  • The client gets a copy by email, linking back to their page, which now shows their answer. It goes out at once, at any hour, since it confirms what they just did (Email and Business Hours).
  • The page carries a stamp (see The Answer Stamp below).
  • The proposal's owner gets an email.
  • With CRM, when accepted: the client's CRM contact is updated with what they typed: their full name (and first and last name from it), their verified email, and their job title (Title). It is the proposal's contact, or the contact with the proposal's client email, or the contact with the email they typed; with none, a new contact is added on the proposal's CRM company. The proposal links to it, and the contact's history keeps the old values. If the contact cannot be changed (a field you made required, say), the acceptance still counts and the proposal's activity says why.
  • Webhooks and automations: each answer is an event: proposals.proposal.accepted or proposals.proposal.declined (Webhooks). The event's record is the client's Response, with the proposal it answers.
  • With CRM: the linked deal moves to its pipeline's first won stage (accepted) or lost stage (declined). If it cannot, the proposal's activity says why.
  • With Contracts: an accepted proposal starts a contract in the Contracts app. Start Contract (action proposals.contract.start) starts one by hand, such as when Contracts was added later.

Both can be turned off in Proposals Settings.

Payments and Invoices

When a client accepts, the payment schedule is fixed from that day: each payment's amount (with the add-ons chosen) and the day it is due. The proposal's page shows each one and how it was billed.

With the Invoices app, and the proposal linked to a CRM company, each payment becomes an invoice in Invoices on its day (the payment at acceptance right away), once, named after the proposal, such as "Payment 2 of 5". Then:

  • As a draft (at first): someone reviews and sends it in Invoices.
  • Charged automatically, when Charge Proposal Payments Automatically is on in Proposals Settings (on at first when Stripe is connected): the invoice is sent the day the payment is due (the first one the same day the client signs, dated that day) and Invoices charges it within moments to the client's saved bank account through your Stripe account, or their backup card if the bank refuses at once, the same way it charges any invoice. No waiting for a Friday or the 1st. It needs Live Billing on and Billing Active on for the client in Invoices; until then the draft waits, and the proposal's page says why. Without a saved bank account, the invoice is still sent and the client pays from it.

What happens when a client signs, with automatic charging on: their answer is recorded; the schedule is fixed from that day; within moments the first payment becomes an invoice dated that day, it is sent to the client's billing contacts, and Invoices charges their saved bank account (a bank account they added in the pop up is waited for, up to 30 minutes, until Stripe confirms it). Later payments are invoiced and charged the same way on their days.

If nothing can be billed (Invoices is not added, the proposal has no CRM company, or billing payments is off), the proposal's page says so for each payment.

Services on the Client's Subscription

With Subscriptions added, the proposal linked to a CRM company, and monthly or yearly lines on it, accepting starts those services on the client's subscription by itself (action subscriptions.services.add, see Adding Services to a Subscription):

  • Each monthly and yearly line, and each add-on the client chose, becomes an item on the client's subscription, at the proposal's price and quantity, with its product when the line came from one. Monthly lines go on the client's monthly subscription and yearly lines on their yearly one; a client without one gets a new one, named after their company.
  • Each item is linked to the proposal's website (or the website named on its line). A website the client's company does not have yet is added to CRM's Websites for them. A website another company has is never taken: nothing starts, and the proposal's page says why.
  • They start on the proposal's Services Start day, else the Project Journey's launch day (laid out from the day the client accepted), else the day the client accepted. A monthly service that starts after the 1st has its first month prorated: the next monthly run bills the days left in that month along with the month ahead.
  • Weekly lines are never a subscription: there are no weekly invoices. One-time lines are paid through the Payment Schedule above.
  • Nothing is emailed to the client, and the client's acceptance always stands.
  • On a proposal that names its website or its Services Start day, the client's page says it under the Investment: when the monthly and yearly services start (that day, launch day, or the day they accept), and that a first month starting after the 1st is prorated.

The proposal's page shows a Services card: what was started (the items added, the subscriptions, any new website, and the day they start), or why nothing could start yet, such as no CRM company linked or Subscriptions not added. Start Services (action proposals.services.start, for people who send proposals) starts them once that is fixed. Each line is added once, so choosing it again only adds what is missing, and an item someone deleted is never added back.

The Answer Stamp

Once a client answers, their page carries a stamp, like one pressed on paper: Accepted in blue or Declined in red, with the proposal number, the name of the person who answered, and the day. It sits at the top right of the proposal's heading (centered between the title and the details on a phone) and again beside the answer. Right after they answer, it is pressed onto the page; when they come back later, it is simply there. With reduced motion turned on in their device's settings, it only fades in briefly. The same stamp shows in your Preview of the answered version and on its PDF.

The time of the answer, on the page, the stamp, the PDF, and the emails, is in your company's time zone from Business Hours, with its short name (10:42 AM PDT).

An open proposal has no stamp, and neither does an expired, withdrawn, or replaced version: an expired one keeps its expired notice.

Adding a Bank Account While Accepting

When the company charges payments automatically, has Stripe connected in Invoices, and the proposal is linked to a CRM company with a payment due at acceptance, the client's page shows that payment in the Accept section. A client with no bank account saved can choose Add a Bank Account: a pop up on the same page, through your own Stripe account, connects their bank (most banks right away, when they sign in to them). A card is only ever the backup Invoices tries when a bank refuses, so the pop up asks for a bank account. What they typed in the form stays as it is, and they accept as usual. The payment at acceptance then waits a few minutes for Stripe to confirm the account before Invoices charges it. Without the pop up (or without scripts), accepting works the same and the client pays from the invoice.

The Client's PDF

Download PDF on the client's page prepares the PDF of that version, with Preparing on the button until it is ready. It has the Project Journey, the Payment Schedule, and the Notes too; each link in the notes can be clicked, with its address printed after its text. After they answer, it shows their answer, the add-ons chosen, and the stamp: at the top right of the first page and again with the answer.

When It Ends

  • A proposal is valid for the days in Proposals Settings (14 at first), counted from the day it is sent.
  • After the Valid Until day, the proposal is Expired: it can still be opened, read only, but not accepted or declined.
  • A link stops working when a newer version is sent, when the proposal is withdrawn, or 60 days after the Valid Until day. The page tells the client which, and to ask you for a new one.

Asking for a New Proposal

When the client opens an expired proposal, the whole proposal shows, read only, with a notice over it: your company's name, that the proposal has expired, an optional short message box, and Request a New Proposal (action hook link.renew). Read the Proposal fades the notice away; a button at the end of the page brings it back. It works without scripts too.

When they ask:

  • The proposal's activity says "New proposal requested by" their name and email, with their message.
  • With Projects, on the proposal's project (its Project field): a Completed or Cancelled project is reopened (In Progress) first, then the message goes in the project's Notes: who asked, for which project, the proposal number, when it expired, and their message. When you set a Project Chat in Projects Settings, the same message is posted there too.
  • Without a project, with Helpdesk: a ticket from the client opens in Helpdesk instead, so the request is not missed. No receipt goes to the client.
  • The proposal's owner (or, when it has no owner who can sign in, the project's manager) gets an email, when Email a proposal's owner is on in Proposals Settings.
  • The client sees: "Thanks, we'll send you an updated proposal." Nothing is emailed to them.
  • One request per proposal per day: asking again the same day only shows the thanks. They may ask again the next day.

Then send them a new version: Revise, update it, and send it.

Ask Us Anything

We’d love to hear from you!