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
01-
New New feature Whitelabel
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.