Roadmap
Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Zapier Integration for Asana

Allow users to connect ManyRequests to Asana through Zapier so they can automatically create and update tasks. Core Functionality Trigger when a new request is created in ManyRequests → create a task in Asana Trigger when a request status changes → update the Asana task status Optional: when an Asana task is completed → update the ManyRequests request status

Regine Garcia 3 days ago

💡 Feature Request

Organization-Level Tax Exempt Setting

Add a setting at the organization level that allows admins to mark the entire organization as tax exempt. When enabled, all invoices generated under that organization will automatically have taxes removed or set to 0%. Include: A toggle in Organization Settings for “Tax Exempt” Optional field for tax exemption ID or certificate reference Automatic application to all future invoices No manual override needed per invoice This helps agencies working with non-profits or tax-exempt clients avoid adjusting tax settings manually every time.

Regine Garcia 7 days ago

💡 Feature Request

Completed

Restrict Team Members to Internal Comments Only

Add a permission setting that allows a team member to post internal comments only. This role should prevent them from posting any client-visible comments while still letting them collaborate internally on tasks and projects. This is useful for juniors, ops, QA, or contractors who need context and discussion access without the risk of commenting directly to clients. It reduces mistakes and gives agencies more control over client communication.

Regine Garcia 26 days ago

💡 Feature Request

Add “Mark as Refunded” status

Add a refund action on invoices/payments so an admin can mark a transaction as Refunded inside ManyRequests. Once marked, the refund should: Show a clear Refunded label/status in the relevant views (invoice, client billing history, transactions list). Be reflected in reporting by deducting the refunded amount from Revenue (net revenue), so revenue metrics and dashboards stay accurate.

Regine Garcia About 1 month ago

💡 Feature Request

MCP

It would be incredible if ManyRequests had an MCP setup. We currently use claude code and gemini with mcp connections to Notion, Webflow, Slack. This gives it great context of our clients and ongoing projects without having to explain it all. By having an MCP to ManyRequests it would complete the full team to clients interaction, and AI could auto update progress and flag issues.

Dylan Harrocks About 1 month ago

💡 Feature Request

Subscription Reporting Dashboard

Add a dedicated Subscription Reporting area that gives agencies visibility into subscription performance over time. Reports like: Active subscriptions - Count by plan, status (active, paused, canceled), and billing cadence Clients by plan - Client list per plan, plus totals and percentage split Average subscription duration - Average tenure (overall + by plan), including churned vs active breakdown Plan changes - Track upgrades/downgrades, plan switches, and frequency over time. Show before/after plan, date, client, and reason (optional note field) Churn and retention basics - Cancellations over time, reactivations, net subscription growth

Regine Garcia About 1 month ago

💡 Feature Request

Improved Slack Notification Settings

Right now ALL slack notifications go to the same channel and that can be incredibly overwhelming. It would be ideal if we could: Choose what notifications go where (ability to send different notifications to different channels) Reply to request comments directly via Slack (same for clients that use the integration if the agency decides to make the app public). Ability to control what information is shown on the notification itself (right now they’re pretty simple and seemt to cut off after a certain length, which defeats the purpose and still have to go to the portal to check vs just being able to see everything right in Slack).

Luis About 1 month ago

💡 Feature Request

Improve File Management and Upload Capabilities in Requests

The current file upload and management experience is slowing teams down during daily work. Basic file handling actions that are standard in most tools are missing, which leads to repetitive manual work and higher risk of errors. What’s currently missing: Uploading folders with multiple files at once Uploading a .zip file and extracting it directly in the platform Selecting multiple files for bulk deletion Moving files between folders Warning or indicator when uploading files with duplicate names These limitations add unnecessary friction when handling large or structured client files. Improving this would significantly reduce time spent on file management and help prevent accidental overwrites or confusion caused by duplicate files.

Regine Garcia About 1 month ago

💡 Feature Request

Enable “Download All Files” for Client Request Folders

Right now, the “Download all files” option works for most folders, but not for the Request folder of a specific client. This makes it really time-consuming to download files when a client has multiple requests, since each request has to be downloaded one by one. It would be a big time saver if admins could bulk download all files inside a client’s Request folder in one go, just like other folders.

Regine Garcia About 2 months ago

💡 Feature Request