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.
New
02-
New Improvement Notifications
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 Notifications
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.
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.