What should we build next?
Every idea agencies have sent us, grouped by status. The ones we commit to end up on the roadmap; the ones we ship link back to the changelog.
Every idea, out in the open.
Highest-voted first within each status. If an idea here matters to you, email us and we will bump it.
Automations
02-
New New feature
Preconfigured automations library
Ship with a library of ready-made automations — unsigned-proposal follow-up, invoice payment reminders, lead follow-up sequences, review-request drips, client onboarding workflows, no-show rebooking, stale-lead re-engage…Ship with a library of ready-made automations — unsigned-proposal follow-up, invoice payment reminders, lead follow-up sequences, review-request drips, client onboarding workflows, no-show rebooking, stale-lead re-engagement — that users can clone in one click and adapt, instead of building every flow from scratch.
-
New Improvement
More automation triggers and actions
Expand the automation library with new triggers (form submitted with a specific value, tag added, document signed, payment received) and new actions (send SMS, update custom field, post to webhook with HMAC, assign owner…Expand the automation library with new triggers (form submitted with a specific value, tag added, document signed, payment received) and new actions (send SMS, update custom field, post to webhook with HMAC, assign owner).
Billing
01-
New Improvement
One-time and recurring line items on a single invoice
Add both one-time charges and recurring line items to the same invoice. Useful for setup fees alongside monthly retainers without creating two separate invoices or juggling subscriptions for mixed engagements.
Documents
04-
New Improvement
Document builder with shapes, design blocks, and layouts
Move the document builder beyond plain text and line items. Add shapes, dividers, icons, image blocks, background colours, columns, and design templates so proposals and contracts can actually look designed — closer to a…Move the document builder beyond plain text and line items. Add shapes, dividers, icons, image blocks, background colours, columns, and design templates so proposals and contracts can actually look designed — closer to a Canva doc than to a Word doc.
-
New New feature
Document analytics — section-level engagement tracking
Track how recipients engage with a sent document — which sections they lingered on, which they skipped, how long they spent overall, how many times they re-opened it, and whether they shared the link. Turn proposals from…Track how recipients engage with a sent document — which sections they lingered on, which they skipped, how long they spent overall, how many times they re-opened it, and whether they shared the link. Turn proposals from a black box into a data trail that tells you what resonated and where you lost them.
-
New New feature
Document folders and categories
Right now all documents — proposals, contracts, invoices — live in one flat list. As the volume grows, the only way to find things is to search or filter. Folders give you a permanent organisational layer on top of that.…Right now all documents — proposals, contracts, invoices — live in one flat list. As the volume grows, the only way to find things is to search or filter. Folders give you a permanent organisational layer on top of that.
What you’d be able to do:
You create named folders — “Contracts 2025”, “Active Proposals”, “Archived Clients” — and assign documents to them. The documents page gets a folder sidebar on the left. Click a folder and the list instantly narrows to its contents. All the existing filters (type, status, search, tags) still work, now inside the selected folder.
Moving documents is frictionless:
- Drag a document row onto a folder in the sidebar
- Select multiple documents and use “Move to Folder” from the bulk action bar
- Use the ⋯ menu on any single document
Folders are customisable — each one gets a colour and an icon (briefcase, star, archive, etc.) so you can tell them apart at a glance.
It’s non-destructive by design. Deleting a folder never deletes the documents inside — they just return to “Unfiled.” Every document is always reachable through “All Documents” regardless of whether it’s been organised or not.
Workflow documents (proposal → contract → invoice chains) move as a unit — assigning one document in a workflow to a folder moves the whole chain together, keeping the workflow intact.
What it doesn’t do (keeping scope tight):
- No nested sub-folders (flat list only, can be added later)
- Folders are for documents, not templates
- No folder-level access control — all team members see all folders
-
New New feature
Agency-level shared templates
Right now every subaccount maintains its own separate set of document templates. If an agency runs 20 subaccounts, keeping proposal and contract templates consistent across all of them means manually duplicating and upda…Right now every subaccount maintains its own separate set of document templates. If an agency runs 20 subaccounts, keeping proposal and contract templates consistent across all of them means manually duplicating and updating each one whenever something changes — a pricing structure, a legal clause, a brand update. There’s no single source of truth.
What this adds:
The agency gets a shared template library — a dedicated set of templates that live at the agency level, above individual subaccounts. Agency admins build and maintain these templates once, and they become available to every subaccount under that agency instantly.
From the agency admin’s perspective:
Any existing template can be “published to the agency library” with a single toggle. New templates can be created directly in the library. Published templates show a “Shared” badge in the template list. The agency admin is the only one who can edit or unpublish them — subaccounts can use them but can’t modify the originals.
From the subaccount’s perspective:
When creating a new document, subaccount users see a new “Agency Library” tab alongside their own templates. Clicking any library template creates an independent copy for their subaccount — pre-loaded with all the content, line items, variables, and settings from the original. They customise their copy freely without affecting the master template or any other subaccount’s copy.
The optional “restrict” mode:
Each subaccount can optionally be set to agency templates only. When enabled, the subaccount cannot create their own custom templates at all — they can only use what the agency has approved. This is useful when an agency needs brand or legal consistency enforced across all their clients, not just recommended.
Concrete examples of how agencies would use this:
- A legal firm agency publishes standard contract and NDA templates — all client subaccounts get the correct, up-to-date versions immediately
- A marketing agency builds a polished proposal template with their brand — every subaccount sends proposals that look identical and on-brand
- A franchise operation enables “restrict” mode — franchisees can only use the franchisor-approved pricing and service templates
What it doesn’t do (keeping scope tight):
- Subaccounts cannot push their templates up to the agency library — only agency admins can publish
- Editing a shared template does not retroactively update copies already cloned by subaccounts — it only affects new clones going forward
- Templates stay as document templates only — not forms, not automations
Forms
01-
New New feature
Form templates library
Right now, creating a new form starts with a completely blank canvas. For teams who just need a standard contact form or a client intake questionnaire, that means building the same common field patterns from scratch ever…Right now, creating a new form starts with a completely blank canvas. For teams who just need a standard contact form or a client intake questionnaire, that means building the same common field patterns from scratch every time — and usually getting it slightly wrong or inconsistent compared to similar forms they’ve built before.
What this adds:
When a user clicks “Create Form,” instead of landing directly in an empty builder, they first see a template gallery — a grid of pre-built forms they can use as a starting point. Each template shows its name, a short description of what it’s for, and a preview of the fields it includes. One click clones it into their account as a regular editable form.
The starting library would include:
- Contact Form — Name, email, phone, message. The baseline. Auto-creates a contact on submission.
- Discovery Call Request — Name, email, company, what they’re looking for, timeline, approximate budget. Designed to qualify leads before a first call.
- Client Intake — Longer questionnaire for onboarding a new client: business info, goals, current tools, how they heard about you.
- Event RSVP — Name, email, attendance confirmation, dietary requirements, plus-one toggle.
- NPS Survey — 0–10 rating scale with a conditional follow-up: promoters get an ask to leave a review, detractors get an open text box to explain why.
- Customer Feedback — Star rating, what went well, what could improve, overall experience.
- Lead Generation — Streamlined: name, email, company size, area of interest. Short enough that people actually complete it.
- Job Application — Position applying for, availability, key experience summary, how they found the role.
The form that gets cloned is fully independent from the template — editing it doesn’t change the template, and other users cloning the same template get their own separate copy. All settings, field types, conditional logic, and submit behaviour come with it and can be freely changed.
The user experience:
The “New Form” flow gets a two-step feel: pick a starting point (template or blank), then land in the builder with everything already populated. Users who prefer starting blank still can — “Start from scratch” is always visible alongside the templates.
Why it matters beyond convenience:
Templates also serve as in-app examples that show users what the form builder is capable of. A new user who opens the NPS Survey template immediately understands conditional logic, rating scales, and multi-section layout — without having to read any documentation.
What it doesn’t do:
- Templates are platform-provided — users can’t submit their own forms to the shared library (that’s a separate, more complex feature)
- Cloning a template is a one-time copy — there’s no “sync updates from template” once it’s been cloned
Integrations
02-
New New feature
Two-way SMS inbox
Send and receive SMS messages inside the app — a unified inbox that ties into CRM records so conversations stay linked to the contact. Reply from the same view where you see their documents, bookings, and notes.
-
New New feature
MCP server integration for AI clients
Connect and control Manage It from an LLM client (Claude, ChatGPT, etc.) via a Model Context Protocol server. Query records, trigger automations, draft documents, and move data — all from the AI assistant of your choice.
Notifications
02-
New Improvement
Notification grouping
When a popular form gets 15 submissions in an hour, the notification bell fills up with 15 identical entries: “New Form Submission — Discovery Call Request”, over and over. Clicking any one of them goes to th…When a popular form gets 15 submissions in an hour, the notification bell fills up with 15 identical entries: “New Form Submission — Discovery Call Request”, over and over. Clicking any one of them goes to the same place. The other 14 are just noise that buries the notifications that actually need individual attention — like a payment received or a contract that was declined.
What this adds:
The notification bell collapses repeated events of the same type into a single grouped entry with a count, shown over a rolling time window (roughly since the last time you cleared your notifications).
Before:
🗂 New Form Submission — Discovery Call Request 2 min ago 🗂 New Form Submission — Discovery Call Request 4 min ago 🗂 New Form Submission — Discovery Call Request 7 min ago 🗂 New Form Submission — Discovery Call Request 14 min ago 🗂 New Form Submission — Discovery Call Request 22 min ago ✍ Contract Signed — Acme Corp 35 min ago 💳 Payment Received — $3,200 from TechStart Ltd 1 hr agoAfter:
🗂 5 new submissions for Discovery Call Request 2 min ago [5] ✍ Contract Signed — Acme Corp 35 min ago 💳 Payment Received — $3,200 from TechStart Ltd 1 hr agoThe [5] badge on the grouped entry shows the unread count within that group. Clicking it goes directly to the submissions list filtered to that form — one click to see all five, rather than clicking through each notification individually.
What gets grouped and what stays individual:
Not every notification type benefits from grouping — some events are important enough that each one deserves its own line. The logic is intentional:
- Form submissions (same form) — grouped: “8 new submissions for [Form Name]”
- Bookings created (same scheduler) — grouped: “4 new bookings for [Scheduler Name]”
- Contacts created — grouped: “12 new contacts added”
- Signature completed — individual: each signed contract matters
- Payment received — individual: each payment deserves attention
- Document declined — individual: requires immediate action
- Team member joined — individual: infrequent, always relevant
The unread count badge on the bell icon:
The total badge count on the bell doesn’t change in meaning — it still represents total unread events, not visible rows. So if 15 form submissions arrive, the bell still shows 15 (not 1), accurately reflecting how much new activity there is. The grouping only affects how those notifications are displayed inside the dropdown, not how they’re counted.
Marking as read:
Clicking a grouped notification marks the entire group as read in one action — the same as today’s “mark all as read” but scoped to just that group. The individual “mark all as read” button at the top of the dropdown still clears everything at once.
What it doesn’t do:
- Groups don’t persist across days — if you clear your notifications and more form submissions arrive the next morning, a fresh group starts. Grouping is a display behaviour, not a data restructuring.
- It doesn’t merge notifications from different forms into one entry — “5 submissions for Discovery Call Request” and “3 submissions for Client Intake Form” remain separate groups.
-
New New feature
Notification digest mode
Every event in the system generates its own notification — a signature, a payment, a form submission. On a busy day that means a stream of individual emails landing one by one. For an active agency handling dozens of doc…Every event in the system generates its own notification — a signature, a payment, a form submission. On a busy day that means a stream of individual emails landing one by one. For an active agency handling dozens of documents and forms, the volume gets noisy fast. People start ignoring notifications entirely, or turn them off — and then they miss the ones that actually matter.
What it adds:
Each user gets a choice: keep notifications immediate as today, or batch everything into a single summary email delivered once a day or once a week. You pick the rhythm that fits how you work.
How it works:
When digest is on, every notification that would have triggered an email gets quietly held. At your chosen interval, the system sends one clean email grouped by type: “3 signatures completed, 2 payments received, 5 form submissions today.” You see the full picture at a glance — what happened, how many, and a direct link to jump in.
Works alongside your existing controls. The per-type toggles you already have still apply. You can keep payment notifications immediate (because you want to know the moment money arrives) while setting form submissions and booking confirmations to daily digest. The two systems layer on top of each other.
Per-user, not per-account. Each team member sets their own preference independently. An owner who wants a morning summary gets it; a team member who prefers real-time stays on real-time. Nothing changes unless someone opts in.
What it doesn’t touch:
In-app notifications — the bell icon — still update in real time regardless of email preference. Digest Mode is purely an email setting. If you want certain types always immediate, the existing per-type toggle handles that without turning digest off entirely.
Reporting
03-
New New feature
Team performance dashboard
Managing a team inside the platform today means clicking into individual lists and mentally filtering by person. Want to know how many proposals Sarah sent this month versus last month? You’d scan the documents lis…Managing a team inside the platform today means clicking into individual lists and mentally filtering by person. Want to know how many proposals Sarah sent this month versus last month? You’d scan the documents list and count. Want to see who’s completing the most bookings? You’d check the bookings view and piece it together. There’s no single place where you can look across your whole team and immediately understand who’s busy, who’s falling behind, and what the activity trend looks like over time.
What this adds:
A dedicated Team page under the reporting section — visible to account owners and managers — that shows every active team member as a row, with their key activity metrics side by side. One view, the whole picture, for any time period you choose.
What you see for each team member:
- Documents sent — proposals, contracts, invoices sent in the period
- Documents signed — documents that reached a completed/signed status
- Sign rate — signed ÷ sent, shows how effective their outreach is
- Revenue collected — total amount paid on documents they own
- Contacts added — new contacts created by this person
- Bookings completed — appointments they ran that were marked complete
- No-show rate — no-shows as a percentage of their total bookings
- Last active — when they last logged in and took an action
Next to each member’s name, a small sparkline chart shows their documents-sent trend across the weeks in the selected period — so you can see at a glance whether someone’s output is growing, steady, or declining, without needing to read the numbers carefully.
Date range control:
The dashboard defaults to the current calendar month. A date picker at the top lets you switch to any custom range — last 7 days, last quarter, a specific month, year to date. Every metric on the page recalculates instantly for the selected window. A “vs. previous period” comparison toggle shows each number with a small up/down indicator against the equivalent prior period.
Sorting:
Click any column header to sort the team by that metric — see who sent the most documents, who collected the most revenue, or who has the highest sign rate. Immediately useful for a weekly team review.
Drilling in:
Clicking a team member’s row opens a side panel with their individual breakdown — a list of their documents, bookings, and contacts created in the period, each linking directly to the relevant record. No separate navigation required.
Export:
The full table exports to CSV with one click — the same streamed export pattern used on the contacts and documents pages. Useful for dropping into a team review spreadsheet or sharing with someone who doesn’t have platform access.
Who can see it:
The dashboard is visible to users with the appropriate management permission. Regular team members can see their own row only. Owners and managers see the full team. This uses the existing RBAC permission system — no new permission concepts needed, just a check of the existing team.view permission level.
What it doesn’t do:
- It doesn’t show commission calculations or financial targets — it’s an activity dashboard, not a compensation tool
- It doesn’t cover automations run (those are system-level, not meaningfully attributed to a person)
- Subaccounts with only one team member will see a single-row table — the feature is most useful with three or more active staff
-
New New feature
Feature usage dashboard
Plan limits exist on every subaccount — a cap on how many contacts, documents, forms, and automations you can have under your current subscription. Right now the only place you’d notice you’re approaching a l…Plan limits exist on every subaccount — a cap on how many contacts, documents, forms, and automations you can have under your current subscription. Right now the only place you’d notice you’re approaching a limit is if the platform blocks an action when you hit it, or if you happen to notice a small usage indicator somewhere in the interface.
There’s no place to go and proactively check: where do I stand across everything, with how many days left in my billing period?
What this adds:
A single page at Settings → Usage that lays out every plan limit in one clean view, showing exactly where you are right now and how much headroom you have left before the period resets.
What the page looks like:
Each feature gets its own card with a labelled progress bar:
Contacts ████████████░░░░░░░░ 847 of 1,000 used (153 remaining) Documents sent this month ██████░░░░░░░░░░░░░░ 23 of 100 used (77 remaining — resets in 12 days) Forms ████████████████░░░░ 8 of 10 used (2 remaining) Automations ████░░░░░░░░░░░░░░░░ 3 of 25 used Team Members ██████████░░░░░░░░░░ 5 of 10 usedThe bar colour shifts from green to amber at 70% usage and to red at 90% — a visual warning before the limit becomes a problem. If a feature has no cap on your plan (unlimited), the card shows “Unlimited” with a full green bar instead of a number.
The trend line:
For monthly-resetting limits (documents sent), the card shows a simple sentence beneath the bar: “At your current pace, you’ll send approximately 58 documents this month — 42 under your limit.” Or, if trending toward the ceiling: “At this pace you may hit your document limit before the month ends. Your limit resets in 12 days.”
This is calculated from the current count divided by days elapsed in the billing period, projected to the end of the period — straightforward arithmetic, no machine learning needed.
The upgrade prompt:
When any metric is above 80%, a contextual note appears: “You’re approaching your contacts limit. Upgrade your plan to remove this cap.” This links to the billing page with the current plan highlighted. For agency-managed subaccounts, it notes that the agency admin controls the plan.
Why it matters:
Teams who are close to a limit and don’t know it get surprised mid-month when something stops working. This page turns that surprise into a proactive decision. It also gives subaccount owners a simple, honest answer to “what are we paying for and are we using it?”
What it doesn’t do:
- It doesn’t show historical usage month-over-month (that’s a reporting feature, not a limits dashboard)
- It doesn’t let you adjust limits from this page — that stays in the billing section
-
New New feature
Custom report builder
Every feature in the platform has its own data view — the contacts list, the documents index, the bookings calendar, the form submissions table. Each one has filters and basic exports. But none of them talk to each other…Every feature in the platform has its own data view — the contacts list, the documents index, the bookings calendar, the form submissions table. Each one has filters and basic exports. But none of them talk to each other, and none of them let you ask a question that crosses those boundaries, aggregates data your way, or saves a view you want to come back to every week.
The Custom Report Builder is a dedicated space for answering business questions with data already in the system — without needing to export CSVs into a spreadsheet and piece things together manually.
How it works:
Building a report is a four-step flow:
- Choose your data source. Pick what you want to report on: Contacts, Documents, Form Submissions, or Bookings. Each source exposes the fields that make sense for it.
- Select your columns. Drag the fields you want to see into the report. For contacts: name, email, tags, date created, lifetime value. For documents: type, status, contact name, total amount, date sent, days to sign. For bookings: scheduler name, guest name, date, duration, status, assigned team member. You build exactly the table you want — no fixed columns, no hidden fields.
- Add filters. Narrow the data down. Same filter operators already used throughout the platform (equals, contains, greater than, before date, etc.) — applied here to whichever columns you’ve chosen. Examples: documents where status is “sent” and total is over $5,000; contacts created in the last 30 days with no documents; bookings in Q1 that were cancelled.
- Choose a visualisation. View the data as a table, or switch to a chart — bar, line, or pie. Charts aggregate automatically: a bar chart on document data would group by status and show counts; a line chart on contacts would show new contacts per week over 90 days. The table is always available alongside the chart.
Saved reports:
Any configured report can be saved under a name — “Monthly Revenue Pipeline”, “Lead Source Breakdown”, “Unsigned Proposals > $10k”. Saved reports appear in a reports index, reload instantly, and always reflect live data. Editing a saved report opens the same builder with the existing configuration restored.
Export:
Every report can be exported as a CSV (downloads immediately, same data as the table view) or as a formatted PDF (branded, with the chart rendered at the top, table below — generated via the same PDF engine used for documents).
Shareable links:
A report can be shared via a signed link that gives read-only access to the current results — no login required. The link expires after 7 days by default (configurable). Useful for sending a client a snapshot or sharing a weekly metric with a stakeholder who doesn’t have a platform login.
Examples of reports teams would build immediately:
- Unsigned proposals over 14 days old — documents, filtered by type=proposal, status=sent, sent date > 14 days ago. Instant follow-up list.
- Revenue by month — documents, filtered by status=paid, grouped by paid_at month, bar chart. One view replacing a spreadsheet that used to take 20 minutes.
- Lead source breakdown — contacts, grouped by tag (UTM source tag), pie chart. Shows where new clients are actually coming from.
- Booking no-show rate by team member — bookings, grouped by assigned user, filtered by status=no_show vs completed. Identifies patterns without manual counting.
- Form conversion by source — form submissions, grouped by referring form, showing submission count vs view count. Spots which lead forms are underperforming.
Whitelabel
01-
New New feature
Subaccount snapshots attached to plans
Standing up a new subaccount today means starting from a blank slate. Every subaccount you provision needs its pipelines configured, CRM fields created, tags set up, document templates loaded, forms rebuilt, automations…Standing up a new subaccount today means starting from a blank slate. Every subaccount you provision needs its pipelines configured, CRM fields created, tags set up, document templates loaded, forms rebuilt, automations wired, schedulers defined — the same manual work, over and over. For an agency onboarding clients weekly, that’s hours of repetitive setup before the account is actually usable, and it’s easy to forget something or drift between clients.
What this adds:
You build one subaccount exactly the way you want every client account to look — templates, forms, automations, pipelines, custom fields, tags, schedulers, integrations, branding — and take a snapshot of its configuration. That snapshot becomes a reusable blueprint. Attach it to a plan tier, and every new subaccount provisioned on that plan bootstraps itself from the snapshot automatically. The client lands in a fully configured environment on day one instead of an empty shell.
How it works:
- Build a reference subaccount. Pick any existing subaccount (or spin one up fresh) and configure it the way a perfect starting environment should look. Name it something obvious — “Real Estate Starter”, “SaaS Agency Baseline” — so you remember what it’s for.
- Take a snapshot. From the agency admin, click Create Snapshot on that subaccount. You get a checklist of what to include: pipelines, custom fields, tags, document templates, form templates, automations, schedulers, saved filters, email/SMS templates, branding (logo, colours, portal copy). Tick what’s in, leave what’s out. Customer data (contacts, sent documents, real bookings) is never captured — only configuration.
- Attach it to a plan. In the plan editor, pick one or more snapshots to associate with the plan. A plan can have a default snapshot or a menu the client picks from at provisioning time.
- Provision lights it up. Any new subaccount created under that plan runs the snapshot on first boot — creates all the pipelines, fields, tags, templates, and automations listed in the snapshot. The account is usable the moment the client logs in.
Applying a snapshot to an existing subaccount:
Snapshots aren’t only for new accounts. From any subaccount’s settings, agency admins can Apply Snapshot to layer it on top of the current state. The default is non-destructive: anything that already exists stays untouched; anything missing from the current subaccount gets added. An optional “overwrite matching items” toggle lets you force the snapshot’s version to win on conflicts, useful when you’ve updated a master template and want existing clients to get the new one.
Updating a snapshot:
Snapshots are versioned. Rebuilding a snapshot from an updated reference subaccount creates a new version without touching the old one. Existing subaccounts aren’t retroactively updated — the snapshot only runs at provisioning (or when an admin explicitly re-applies it). This keeps client accounts stable and predictable.
Examples of how agencies would use this:
- A real-estate-focused agency builds a Realtor Starter snapshot — lead pipelines, listing CRM fields, a buyer-intake form, a showing-request scheduler, a follow-up automation sequence — and attaches it to their Starter plan. Every realtor they onboard gets it instantly.
- A multi-vertical agency maintains three snapshots — Restaurants, Law Firms, SaaS — and lets the sales rep pick the right one when provisioning a new client based on what the client does.
- A franchise operator attaches a single locked snapshot to their franchise plan. Every franchisee gets the exact same setup — same fields, same forms, same automations — with no room for drift.
What it doesn’t do:
- Snapshots never move customer data (contacts, documents, submissions, bookings, messages). They capture configuration only.
- Existing subaccounts are not automatically updated when a snapshot is re-versioned — you apply explicitly, on demand.
- There is no public marketplace for sharing snapshots between different agencies in v1 — snapshots live inside your agency only. A shared marketplace would be a separate, later feature.
Your agency's own software product.
Start your agency account, connect your domain, upload your logo, and ship your first branded client sub-account in under an hour. No credit card required.