Automations
Rules that do the chasing, so nobody has to.
Write a rule in plain sentences: when something happens, and only if the conditions you set are met, Launchglass asks the right person for what’s needed, with a due date — and keeps after it until it’s done.
The problem
Most “automation” stops at a notification.
A notification isn’t work.
An email saying something changed doesn’t mean anybody acted on it, or even read it.
The useful automations cost extra.
General-purpose tools ration automation by plan and by monthly run count, so the process ends up running by hand anyway.
Timing depends on somebody’s memory.
Gate prep starts when somebody remembers the review is next week. Usually the day before.
The solution
When this happens, and these conditions are met, do this.
Triggers on what happens
A card is created, a field or a whole section changes, somebody votes, or somebody comments.
Triggers on dates & schedules
Daily, weekly or monthly — or relative to any date on the card: “30 days before Target Launch”, in your workspace’s timezone.
Conditions that read the card
Match on its values, with AND/OR groups and transitions like “becomes” or “was empty, now set”. The builder shows how many cards match right now.
Actions that create work
Request fields from a person, a group, or whoever’s named on the card, with a due date. It lands in their My Work and closes itself once they’ve answered.
And the rest of the busywork
Set fields, send a notification in your own words, or copy the card to another board with its fields mapped and a link back.
Safe to switch on
New rules start switched off, and each is titled with the sentence it describes, so anybody can read what it does.
Questions
Common questions.
What can trigger a rule?
A card being created, a field or section changing, a vote, a comment, a schedule (daily, weekly or monthly), or a date on the card coming up — with several offsets allowed, like 30 days and 7 days before launch.
Can one rule assign work to a different person on every product?
Yes. A request can go to a named person, a group, or whoever is in a person field on the card — the program manager, say — so a single rule works across every product.
What happens if somebody doesn’t respond?
The request sits in their My Work with its due date, a reminder goes out automatically, and it shows as overdue to anyone checking what a launch is waiting on. An admin can chase it, reassign it or move the due date.
Do we need IT to set up automations?
No. Rules are written in the browser as plain sentences. Whoever runs the process can write them and change them.
Get started
Get started free, or let us show you.
Start on the Free plan, no credit card required, and run your first process on it. Rather see it first? Book a 15-minute demo on a process like yours.