Describe an automation.
Sell it monthly.
Write what the automation should do. Connect the tools it needs. Publish it. Subscribers pay you every month it runs for them.
Works with the tools your subscribers already use
From idea to subscription in an afternoon
Here's exactly what a creator built, how they described it, and what subscribers get.
UK plumber back-office on ServiceM8
The problem
A UK plumber using ServiceM8 finishes a job, closes it in the app, and then nothing happens. The QuickBooks invoice doesn't get raised. The customer doesn't get a receipt. The follow-up text asking for a review never goes out. The plumber does it manually, usually at 9pm.
What the creator described
The creator opened the builder and typed: "When a ServiceM8 job is marked complete, draft a QuickBooks invoice from the job's line items and labour time, wait for my approval, then send the customer a payment link by SMS and schedule a follow-up text in 3 days asking for a Google review."
What runs
ServiceM8 fires a webhook when a job closes. The automation pulls the job details, maps line items to QuickBooks products, creates a draft invoice, and sends the creator a Slack message with an approve/reject button. On approval, QuickBooks marks the invoice sent, Twilio fires the payment SMS, and a follow-up is scheduled. The whole sequence takes under 90 seconds.
What the subscriber sees
A Slack message with the invoice draft and two buttons. That's it. Everything else is invisible. They approve once and the rest happens without them.
Pricing rationale
The creator priced it at £39/month. A plumber doing 20 jobs a week saves roughly 40 minutes of admin daily. At any reasonable hourly rate, the automation pays for itself on the first job of the month.
Five types of automation
Each type maps to a different subscriber need. Most successful automations combine two or three.
Trigger & respond
Something happens in one tool and the automation reacts across others. Job completed → invoice drafted → SMS sent. The most common pattern.
Run on a schedule
Daily, weekly, or monthly. Pull a report, send a digest, check for anomalies, remind someone of something. Cron-style triggers with full tool access.
Human in the loop
The automation pauses and asks the subscriber to approve before continuing. Ideal for anything involving money, messages to customers, or irreversible actions.
Chain of actions
Long sequences with conditional branches. If the invoice is overdue, escalate. If the customer replies, update the CRM. Complex logic, described in plain language.
Keep tools in sync
Contacts updated in HubSpot appear in Mailchimp. Xero invoices reflected in a Google Sheet. Bidirectional or one-way, on a schedule or on change.
Smart alerts
Watch for conditions and notify the right person on the right channel. Slack, email, SMS, or a push notification — wherever the subscriber actually looks.
The tools your subscribers already use
Grouped by what they're for — not alphabetised. If something's missing, you can add it via the custom HTTP action.
Field service & job management
Accounting & invoicing
CRM & sales
Communication
Productivity & data
Six things most creators miss
The details that separate automations that subscribers keep from ones they cancel.
Credentials are per-subscriber
Each subscriber connects their own accounts. You never see their tokens. The automation runs with their credentials, not yours. This is what makes the marketplace model work — one automation, thousands of independent subscribers.
Approval steps pause the run
When you add a human-in-the-loop step, the automation pauses and waits — for up to 72 hours — for the subscriber to approve. If they don't, the run times out gracefully. No stuck state, no orphaned jobs.
Runs are logged and inspectable
Every run produces a log the subscriber can read. They can see what triggered it, what each step did, and what was sent or created. This is what builds trust. Subscribers who can see the log cancel less.
Pricing is yours to set
You choose the monthly price. You can offer a free trial period. You can update the price for new subscribers at any time. Existing subscribers stay on their original price until you explicitly migrate them.
The description is the spec
You describe the automation in plain language. The builder interprets it and shows you the steps it will take. You review, adjust, and publish. There is no visual flow builder — description is the interface.
Subscribers can pause, not just cancel
Subscribers can pause an automation — stopping runs and billing — without cancelling. When they unpause, billing resumes. This reduces churn from seasonal businesses or temporary situations.
What other creators have built
Month-end close assistant
On the last day of the month, pull all uncategorised Xero transactions, group them by merchant, and send the bookkeeper a Slack message with suggested categories and a one-click approve button.
Deal velocity alert
Every morning, check HubSpot for deals that haven't moved in 7 days. Send the owner a Slack digest with the deal name, last activity, and a link to the deal. No more forgotten pipeline.
Client onboarding sequence
When a new contact is added to HubSpot with status "new client", create a Notion workspace from a template, send a welcome email, and add a task to the account manager's Asana board.
Daily accountability check-in
Every morning at 8am, send a Slack message asking the subscriber to confirm their three priorities for the day. At 6pm, send a follow-up asking what they completed. Log responses to a Google Sheet.
What you keep
We take a small platform fee. You keep the rest.
Revenue share — you keep 90% of every subscription payment
Payouts processed on the 1st of each month
No limit on subscribers, no limit on automations, no limit on earnings
Coming soon
What's being built now.
Open the builder and describe your automation.
No code. No visual flow editor. Just describe what you want it to do.
Start building →Looking to subscribe to an automation? For subscribers →