Feature Requests

Ability to archive agreements for two reasons: Reduce the dashboard clutter and to "unpublished the URL" for confidentiality reasons (prevent sharing once agreement is signed) Allow the option to disable/hide the ability for Agreements (proposals) to be downloadable or printable (PDF). (Buttons next to the proposal name at the top of the screen).

In Agreement template settings, there's a single toggle for "Automatically create projects and invoices." This is all-or-nothing — you either auto-create both, or neither. Some people use external tools for project management and don't want projects automatically created in Moxie. But they still want invoices to be created automatically when an agreement is signed. Another scenario: if you're booking client projects far in advance, you might not want a project created yet — only closer to the start date — but you still want the invoice generated immediately. Or sometimes people do want the project auto-created, but not the invoice. Right now, if you turn off the toggle to avoid auto-creating projects, you also lose the ability to auto-create invoices. Requested feature: Split this into two separate toggles: — Automatically create projects — Automatically create invoices Separating these toggles would make Moxie more adaptable to different workflows without forcing an all-or-nothing approach.

Would like to choose a default email from my templates for sending agreements (like we can for invoices under the Workspace Settings > App Preferences section)

When you embed a form in an agreement template, the styling options are extremely limited. You can add a border and adjust spacing around the form container itself, but you can't style the form's internal elements — things like the input field border colour, background colour, text colour, etc. Current workaround: There isn't really a practical workaround right now. A custom CSS panel is planned for agreement templates, which would help those who can code CSS — but there's no timeline on when that will be released. What's needed: Styling options for the actual form elements, similar to what's available in the form builder: • Input field border colour • Input field background colour • Input field text colour • Other basic styling controls The margin/padding issue: Also, the margin/padding behaviour on the embedded form container is backwards from standard web design. In the standard box model, margin sits outside the border and padding sits inside the border (between border and content). In Moxie, it appears to work the opposite way. Why this matters: Right now, when you apply a background colour to an agreement template, embedded forms start to blend in (not great from an accessibility pov) or look bland. You can't make them complement other styled elements in the agreement (like a coloured payment plan table). Having built-in styling options would let you inject brand personality and colour into forms, to fit in with the rest of the agreement template.

The ability to preview agreements and proposals so you can see them before sending them. Without needing to finalize it, grab a link, then paste the link in a browser, then go back to it and make it a draft again, etc. That's a lot of steps just to get a quick preview of the agreement to make sure it looks ok to send. (Especially since we have use V2 which is more complicated then V1)

The ability to add custom CSS to the agreements and other items in the dashboard.

Current behavior: When forms are embedded in an agreement template with "Merge client data" toggled on, the form data only maps to client custom fields — not to opportunity custom fields or contact custom fields, even when the agreement is linked to an opportunity. According to Moxie support: "The agreement only works one way, there's nothing in the agreement flows that update opportunity data. So it's only agreement → client and not agreement → opportunity." The inconsistency: If I send a form directly to a client and it has fields mapped to client custom fields, contact custom fields, and/or opportunity custom fields, all three types of fields will be mapped when the client submits the form. But if I embed that exact same form in an agreement and send it to the client, only the client custom fields get mapped — contact custom fields and opportunity custom fields don't. This creates an inconsistent experience depending on how the form is delivered. The issue: Forms embedded in agreements often capture information that's project-specific, not client-specific. This information should map to opportunity custom fields, but currently can't. Example: I have a form embedded in an agreement that asks clients to confirm the pages they want on their website. The package includes 8 pages, and the form asks them to list the names of those 8 pages. This is project-specific information — it's not relevant to the client record overall, so I want it mapped to an opportunity custom field. At the moment, that's not possible. Current workaround: To capture this data in opportunity custom fields, you have to either not embed the form in the agreement and send it separately instead (which creates extra steps and a less seamless client experience), manually copy the information from the embedded form submission to the opportunity custom field, or only use client custom fields as mapping keys in embedded forms (even when the data is project-specific and doesn't belong on the client record). None of these options are ideal. Requested feature: Allow embedded forms in agreements to map data to client custom fields, contact custom fields, AND opportunity custom fields when "Merge client data" is enabled and the agreement is linked to an opportunity — matching the behaviour of forms that are not embedded.

I want to add a client's address in the agreement for legal purposes. Similar to Docusign, there should be a text field in Agreements where clients can type in requested information.

Currently, the Agreement Styles section only provides styling options for: Title Style (H1) Heading Style (H2) Subheading Style (H3) Paragraph Style (P) When creating longer, more detailed agreements with multiple levels of hierarchy (like Terms & Conditions sections), there's no native way to style H4 headings. This forces users to either: just use bold paragraph text or manually add inline styles via HTML source code. Requested Feature: Add a fourth heading level option that would appear in the Styles panel alongside the existing Title, Heading, and Sub-heading options, allowing users to define font, size, weight, color, and line-height for H4 tags.

I like the Accept button that was added, but would love to have an optional decline button as well. I usually request a proposal response and having a quick button or feedback section would make it a lot easier for clients.