Runner builds a growth team for your product, on the model you connect.
One click proposes the whole team: an orchestrator that owns your number, up to six channel agents that each own one channel, and two advisors who disagree on purpose. You set the target. Once an admin approves the launch and you finish it, the agents start drafting into your approvals, and with a mandate switched on, the email agent runs on its own inside the limits you set.
Nothing goes out until someone approves it, or until you switch on limits it works within.
Runner gives every agent a share of one number.
Runner builds the team from what it already knows about your product: what you sell, who it's for, how it sells and the channels you've connected. You set the target and the date. Runner never forecasts it.
An orchestrator
Owns the sum and no channel. It holds the plan together and runs the weekly review.
Up to six channel agents
One for each channel: email, LinkedIn, Instagram, Threads, WhatsApp, Discord, Kakao or web chat. Each knows the unit it works toward, what it drafts, and the consent and platform rules it works under.
Two advisors
One pushes for volume, the other protects your audience. Runner says which should lead for your product and why. They disagree on purpose, and you decide.
Runner gives each agent an account of its own when the team goes live.
Set the number and the date, then send the launch for approval. An admin confirms it's them and approves it, and nothing exists before they do.
Then you finish the launch, and each agent is created with its own account and a single permission: drafting for its channel. Pause any one of them from the team's roster in one press, with no approval to wait for.
Your number, by your date
How the target splits
Each segment is one agent's share. Together, they make up the whole target.
Orchestrator
Owns the sum and no channel
Own account · Draft email
Brief: Follow up with new trial sign-ups in their first week.
Sends to New trial sign-ups
Only people with recorded marketing consent receive anything.
- Paused
Advisors
- Intensity Leads here
Pushes for volume
- Relationship
Protects your audience
Before you see the team, Runner checks it.
- The shares add up to the whole
- One agent owns each channel
- No forecast language
- No email address, phone number or secret in a brief
A team that breaks a rule is never offered for launch.
Runner's agents draft around the clock, straight into your approvals.
Every fifteen minutes, each agent can file one draft for its channel, written on your model under its AI budget and set beside the brief it came from.
Three at a time
An agent stops at three undecided drafts. A draft nobody decides expires after a day, so the queue stays current, never a backlog.
Filed as what it is
A message to a person is filed as outreach and a public post as content, each with its own checks. A product owner or admin approves either.
Every draft names its model
A draft records the model that wrote it, and one with no recorded model is refused rather than filed.
Approve an email, and it goes out
Approve an email draft and Runner sends it to the people in its audience who opted in to marketing email, checks their consent again as it sends, and stops at 250 people per approval.
Drafted by Email agent for email
Holding at three
Where it goes
Emails the audience New trial sign-ups
Only people in this audience who have opted in to marketing email receive it. Consent is checked again when it sends. At most 250 people per approval.
The brief it was given
Follow up with new trial sign-ups in their first week.
The draft
Welcome follow-up for this week's trials
Written by your model.
Your decision
Requires owner or adminRunner's email agent runs on its own inside the limits you set.
Switch on a mandate, and the email line's scheduled drafts stop waiting for you. Each one that passes every check goes out on its own, and anything that fails one comes to Approvals with the reason.
It starts at zero
A new mandate allows no emails and no posts a day, so nothing runs on its own until you set the limits.
A second factor to switch it on
An owner or admin switches a mandate on with a second factor, and raising a limit takes another. Lowering one, or stopping everything, takes none.
Consent, then every limit
An email goes only to contacts with recorded marketing consent, checked again as it sends, inside your daily cap, your spacing for each contact and your quiet hours.
Email first
Email is the one channel that runs on its own today. Every other channel's drafts wait for a person.
Mandate
An example mandate, read back
Switching on asks you to confirm it's you. Pausing or stopping never does.
On its own, inside these limits
Send up to 40 marketing emails a day in all, only to contacts with recorded marketing consent.
Email any one contact at most once every 7 days.
Send no email between 21:00 and 08:00, in the contact's time zone, or UTC when it isn't known.
Send the email line's scheduled drafts to New trial sign-ups.
Check every piece of copy against 1 claim set and 1 brand rule set before it goes out.
It asks a person first
Anything that fails a check, such as over today's limit, too soon for a contact, in quiet hours, or outside your claims or brand rules, goes to Approvals with the reason.
Moving share between lines after the weekly review.
Raising any limit or extending the end date. The team may offer; only you can accept, with a second factor.
It never
Email anyone without recorded marketing consent. A visit, an identified company or an enquiry is never consent.
Turn a company it identified into a person to email.
Act after the kill switch, or resume anything a person paused.
Delete or rewrite anyone's work.
One kill switch stops every line and every limit at once, with no second factor.
Runner proposes moving share toward the work you approve, once a week.
The orchestrator counts how many of each agent's drafts you approved last week and weighs that against the agent's share. Then it proposes moving up to five points from the agent with the fewest approvals per share point to the one with the most. An admin approves the move.
Nothing moves on its own
Every move waits for an admin. If Runner couldn't read an agent's count, that agent sits the week out rather than being read as zero.
A share is a job, not a promise
A share is what a line is asked to carry, never what it will deliver.
Weekly review
Waiting for an admin- Threads Gives five points
- Email Takes five points
Current split · Dashed outline: current split.
Proposed. Waiting for an admin.
Give your product a growth team.
Connect your product, connect a model, and the first team is one click away. Access is by application while the product is young.
Apply for access
