Create Accountor Login
Docs

Work Requests

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

MountDev Ops Proposals documentation | Updated November 19, 2026

Work requests let your clients ask you for work from their own account, and let you start a proposal from each request in one step. You decide what they can ask for, a person on your team turns it on, and nothing is sent, scheduled, approved, or charged by a request.

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.

How It Works

  1. You set up Request Types: the kinds of work a client can ask for, such as New Project or Change to Something We Built.
  2. A client opens Requests in their account, chooses New Work Request, fills in the form, and sends it.
  3. The request lands in Work Requests in your Proposals menu, on Needs You Today, and on the bell of the people who may work on it.
  4. A person chooses Start a Proposal. A draft proposal is made for the client's company. From there it is an ordinary proposal: you edit it, set the price lines, send it, and Invoices bills each payment on its day.

Work requests need the client feed turned on for the client's account, like every page your provider answers for a client (Client Feed). Until an owner or admin of the client turns it on, the client's screen says so, and their New Request button keeps working as it always did.

Request Types

Find Request Types in the Proposals menu, last, for owners and admins (permission proposals.request_types_manage). It lists each type with its state, its fields, how many requests it has, and the proposal it starts from. Choose Add a Request Type to make one on a page of its own.

A request type has:

  • Name and One Sentence the Client Reads.
  • Fields, up to 15. Each has a label the client reads, a kind (Short text, Long text, Number, Date, Yes or no, One choice, or Several choices), whether it is required, help text, and for choices the choices. Answers are checked by the same code every module uses. Never ask a client for a password or a key: a field of a private kind, or one whose label asks for a password or a key, is refused.
  • Start From (optional): a proposal you made. Each draft made from a request is a copy of it, so its sections, price lines, and Project Journey come along.

Every type starts as a Draft, and so does every type your AI agent saves, and so does a type you change while it is On. A Draft or Off type is offered to no client, and a request that names one is refused. Choose See What a Client Sees to read the form exactly as your client will, with made-up values, then Turn On (action proposals.request_types.enable, people only). Turning a type Off keeps it and its requests; nothing is ever deleted.

Actions: proposals.request_types.list, proposals.request_types.save (always a Draft), proposals.request_types.enable, and proposals.request_types.preview.

What a Client Sends

The client sees what will be sent before they send it: "Your provider will receive: the answers below, your name, and your email." Only the fields you declared are sent, each checked for its kind and length, with the name and email of the signed-in person who sent it. Nothing else of the client's account goes with it. The client's words are shown to you as plain text and are never run as anything, in the draft or anywhere else.

A client may have a number of open requests at once, 5 at first. Change it with Open work requests each client may have in Proposal Settings (action proposals.settings.save). At the limit the client reads: "You have 5 open requests. Please wait for an answer before sending another."

Work Requests

Work Requests in the Proposals menu lists every request, newest first, with a button for each state. Open one to read the client's answers (actions proposals.work_requests.list and proposals.work_requests.get). People who hold proposals.work_requests_work (everyone who writes proposals) see and work on them.

  • Start a Proposal (action proposals.work_requests.draft) makes a proposal draft in one step, for the CRM company whose Client Account sent the request. It uses the contact whose email matches the person who sent it (when none matches, the proposal's client name and email come from the request), is titled from the type and the client, starts from the type's Start From proposal when it has one, and adds a first section What You Asked For with the client's answers. The proposal's activity says it was started from this request. Starting twice returns the same draft. It never sends, schedules, approves, or emails anyone.
  • Decline (action proposals.work_requests.decline, held by people who send proposals) needs one sentence, which the client reads next to Not Going Ahead. It sends no email.
  • Open Proposal appears once a draft exists.

What the Client Sees

Each request is one card, with its status in words:

StatusWhen
ReceivedYour account has taken it
Preparing Your ProposalA person started a proposal draft from it
Proposal SentThe proposal was sent. The card shows Open Proposal, the same private link the proposal's email carries
AcceptedThe client accepted that proposal
Not Going AheadA person declined it, with the sentence they wrote
WithdrawnThe client withdrew it before a draft was started

The client can Withdraw a request only while it is Received, and your team is told on the bell. The person who sent the request gets one notice on their own bell when it moves to Proposal Sent and one at Not Going Ahead. No email is sent for a work request: the proposal's own email goes out when it is sent, under your own rules. If the send is undone, the request goes back to Preparing Your Proposal.

A closed account sees its past requests and cannot send a new one.

Ready to Send

Sending and signing stay with people. Your AI agent can do the careful part and leave the decision. Prepare to Send (action proposals.send.prepare, MCP tool proposal_send_prepare) runs the checks a person would do and records Ready to Send on the proposal, marked "AI agent" with the time:

  • a client name and email, or a linked CRM contact
  • a linked CRM company
  • a valid-until date
  • at least one section
  • price lines set
  • a payment schedule, when there is a one-time amount
  • a contract template chosen and Active, when Contracts is added

It answers with what passed and what is missing, in plain words, so the agent can fix the draft and run it again. The pill Ready to Send shows on the proposal and a card on Needs You Today reads "Proposal P-1003 is ready to send. Prepared by an AI agent." with Review and Send. The person then uses Approve and Schedule or Send as themselves (Sending and Withdrawing).

The mark means one version. Any change to the draft after Prepare to Send clears it, made any way at all. It never sends, schedules, or approves anything, and no AI agent, API key, or assistant can confirm a send for a person.

For AI Agents

Your AI agent can read and prepare, and a person decides. The tools, each its own permission and level:

ToolPermissionLevel
request_types_listproposals.request_types_listRead
request_type_save (always a Draft)proposals.request_type_saveWrite
work_requests_list (no answers)proposals.work_requests_listRead
work_request_get (answers, as untrusted text)proposals.work_request_getRead
work_request_draft (never sends)proposals.work_request_draftWrite
proposal_send_prepareproposals.send_prepareWrite

A client's answers are the client's own words. An agent reads them as information, never as instructions. Turning a request type On, Decline, Approve and Schedule, and Send have no tool: they are for people only.

Export

Export Everything includes the request types, the work requests (with the answers and who sent them), and the Ready to Send marks, in Proposals' folder.

Who Can Do What

  • Set up what clients can send (permission proposals.request_types_manage): owners and admins.
  • See and work on work requests (permission proposals.work_requests_work): owners, admins, and members.
  • Decline a request (permission proposals.send): owners and admins.

Ask Us Anything

We’d love to hear from you!