Roadmap
What you can use today, and what comes next.
Forms, workflows, the CRM, the client portal, health checks and proposals are built and ready. Booking, the inbox, email, payments and more are in beta. What comes after is planned below, in order.
Thrum opens soon. Sign up now and you’ll be among the first in.
Built
22 · In the product today, with the date it shipped.
An ownership check on every request
20 OctEvery request that opens a client by its id checks that the client is yours.
Notifications
20 OctA bell and alert emails for your team, with repeats grouped and each person choosing what they hear about.
The Make importer
19 OctBring a Make scenario across as steps, switched off, with a report of what came over.
Where leads came from
18 OctSee which channel brought in every lead, booking and record.
Pricing per seat
17 OctSolo, Agency and Scale, per seat, with a 14-day trial.
The Overview
13 OctEvery client’s numbers on one page, and what needs you first.
Multi-page forms and results
12 OctOne question or one page at a time, with logic, design, and performance by page and field.
Onboarding
10 OctSign up, add a first client with their brand and form, and watch a test lead arrive in their real portal.
Spam protection
7 OctTrap fields, timing checks and rate limits on every form, with suspicious submissions held for your review.
The CRM
5 OctPeople, companies and deals, filled in by forms and workflows, with custom objects, merging and any record as it was on a past date.
The form library
1 OctForm templates written for many trades, in six layouts.
Step numbers
1 OctSee what every step did, over the last week or the last year.
Proposals that set the client up
1 OctYour client accepts with a code, and their workspace, pack and portal set themselves up.
Packs and the library
1 OctStart from a starter, a playbook or a whole pack. Each installs switched off, with its checklist.
Loops, paths at once, schedules, files
30 SepLoop over a list, run several paths at once, schedule in the client’s time zone, and carry files through a run.
The n8n importer
30 SepBring an n8n workflow across as steps, switched off, with a list of what it still needs.
Templates and rollout
29 SepBuild a workflow once, fill in each client’s details, and roll out new versions without losing their edits.
The monthly report
29 SepOn the 1st, every client gets their month in one sentence and a few numbers.
Health
29 SepLearns each workflow’s rhythm and tells you when one goes quiet, fails or slows down.
White-label
28 SepBrand the portal with a live preview, put it on the client’s domain, and send its email from their address.
The client portal
28 SepYour client sees their leads and their month on their phone, in their own colours. No password to remember.
A workspace for every client
28 SepEach client kept apart with their own encrypted keys, on an engine that retries and reports every step.
Beta
13 · Beta means the module is built and tested, and hasn’t yet run against the live service it depends on, such as Stripe or Twilio. The tag comes off once it has.
Newsletters
23 OctIssues, referrals, sponsors, imports and subscriber sign-in.
Payments
23 OctProducts, pay pages and subscriptions on the client’s own Stripe.
Social posts and outside blogs
22 OctA calendar, a composer, Bluesky, and publishing to WordPress, Ghost, Webflow, Joomla and Shopify.
The blog
21 OctA blog for each client, on their portal or their own subdomain.
Email campaigns and sequences
21 OctCampaigns and sequences from the client’s own domain, to their own list.
The portal on the home screen
19 OctInstall to the phone’s home screen, with push for new leads.
Website chat
19 OctA chat button on the client’s site, answered from the inbox.
Booking
18 OctA booking page in the client’s brand, reminders, and a booking question in forms.
Approvals
6 OctA workflow waits for a yes from your team or the client.
The inbox
6 OctTexts and email with leads, one thread per person, with workflow messages in the thread.
Client invoices
1 OctBill each client monthly for their texts and emails, from your own Stripe.
The agent step
30 SepA model given a task and a few app actions as tools.
App steps and triggers
1 OctSteps for other apps on the client’s own key, and workflows that start when something happens in an app.
Next
11 · Planned next, in this order. Each gets a date when it ships.
Posting to more networks
Automatic posting to the networks that get a reminder today.
Google Calendar sync
Two-way, for booking.
Deposits and checkout in forms
Booking deposits, invoice links and a checkout block in forms, on the client’s own Stripe.
Sending without your own email account
Campaigns sent through Thrum’s own email service.
More connectors
More apps, and the Beta tag off the ones already built.
AI workflow generation
Describe a workflow and get a draft to edit.
Advice from your runs
Suggestions for your workflows, worked out from how they run for real clients.
Public API
Read and change clients, workflows and runs from your own code.
Embed SDK
Put the client portal inside your own product.
Regions and self-hosting
Choose where your data lives, or run it on your own servers.
SOC 2
An audit, when a customer with a procurement process asks for one.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.