For engineers
You built the product. Runner runs the marketing team.
Connect your code. Runner builds a growth team around what the product is and how it sells, drafts the work, and brings consequential decisions back to you.
How it works
- An owner or admin asks from Settings → Team within 14 days of your first plan payment.
- You get back what you paid, less the plan credits you used and any AI or media Runner paid for.
- Your plan ends that day. Later plan payments and bought credits aren't covered.
Solo is $79 a month, AI included. See plans

northstar/relay
main8f4c2a1Repository snapshot
Example- Product
- Developer platform
- Business model
- Usage-based subscription
- Stack
- Next.js · TypeScript
Team built around it
Head of Growth
Copy lead
Social lead
You shipped it. Your growth team says it.
Connect Runner to Claude Code or another MCP client, say what went out today, and each channel's lead writes its own post. Nothing goes out until you approve it.
Connect once, from Claude Code
claude mcp add --transport http runner https://app.runtheworld.ai/api/mcpclaude mcp login runnerOr connect Claude or ChatGPT~/relay
Examplegit log --oneline -2
a41c9e2 Dark mode on every screen (#482)
7d03b5f Export any report to CSV (#486)
Have the growth team build some channel posts around the features we shipped today and talk about them this week.
runnergrowth.brief_posts
- channels
- linkedin, x, instagram, bluesky, reddit
- idea
- Today's two features, talked about all week
- material
- #482 Dark mode on every screen. #486 Export any report to CSV.
5 posts drafting, each waiting in Approvals
Approvals 5 waiting
ExampleLinkedIn lead
Waiting for your approval
Two things shipped in Relay today: dark mode on every screen, and any report out to CSV in one click.
X lead
Waiting for your approval
dark mode is live in relay. every screen, including the ones you open at 2am.
Instagram lead
Waiting for your approval
Lights down. Relay has dark mode now.
Bluesky lead
Waiting for your approval
New in Relay: export any report to CSV, with the columns you already see.
Reddit lead
Waiting for your approval
We added dark mode and CSV export to Relay this week. Here's how we built both.
Nothing goes out until you approve it.
More things to say
The day you ship
Turn today's changelog into a LinkedIn article and a short post for X.
growth.brief_article+growth.brief_postsThe LinkedIn lead writes the article, the X lead the post.
Use the screenshots from the PR as the pictures.
growth.brief_postsThe team writes around your own pictures, up to four.
Write it the way I'd post it from my phone, not like a press release.
growth.brief_postsWritten the way someone on your team posts from a phone.
That week
What's waiting for my approval?
content.list_draftsEvery draft with its status, and a link to open it.
The deploy slipped. Pull Thursday's post.
content.cancel_postIt comes off the calendar before it goes out.
This Reddit thread is asking for what we built. Draft a reply.
community.draft_commentA reply waits in Approvals, and you post it.
The week after
Did the launch posts bring anyone in?
growth.scoreboardWhat each channel brought in, week by week.
When people ask ChatGPT, does it name us?
visibility.ai_mentionsWhich assistants name you, and who they name instead.
Draft this month's newsletter around the release.
newsletters.save_draftA draft issue that reaches nobody until you send it.
Your code becomes the brief.
Connect GitHub and Runner reads your default branch to learn what the product is, how it sells and the kind of business it is. It builds the team in the background and shows the latest commit alongside what it learned.
What the repository read gives you
- A proposed team for this product, with one job per member.
- A product and business summary you can correct before the team uses it.
- The sources behind each proposal, with the latest commit visible for provenance.
fernhollow/orchard-billing
PublicmainSignals Runner found
- instruction files
- dependency names
- configuration keys
- an accent colour
Runner reads your default branch: its file paths and latest commit, dependency names without their versions, configuration keys without their values, your Markdown and text files, and your stylesheet's accent colour. A committed .env is never fetched, and the planning steps send a model names and paths plus short excerpts of your README and other Markdown at the root or in docs/, never commit messages.
Your project
Suggestions ready to review
- Product typeStrong match
- Direct commerceFrom a dependency name
- Instructions in effect1 open conflict
- One file governs the root, another its own directoryFrom your instruction files
- Brand colourApplied, and yours to change
- Taken from your own stylesFrom a stylesheet
- How this product winsReady for your review
- Three phases, every step linked to its pageFrom the model you connected, at this commit
Each selected channel gets someone who knows its job.
Choose the channels in this example and each gets its own AI lead. The leads draft while you keep the product decisions and approve from one list.
Where the work goes
- LinkedIn Pages, Instagram, Facebook Pages, Bluesky and Mastodon publish what you approve at the time you set.
- On X and Reddit, one press opens the post already written, and you press send.
- Newsletters and LinkedIn articles are drafted too, and an article always waits for a person.
People doing the marketing
Before Runner
4channels each to write


Founder / engineer
With Runner
4channel leads drafting
LinkedIn leadDrafting
X leadDrafting
Reddit leadDrafting- Email leadDrafting
LinkedIn, Instagram, Facebook, X, Bluesky and Reddit are trademarks of their owners. Runner is not affiliated with any of them.
Growth plays become an engineering queue.
Runner picks the repeatable growth plays that fit your stage and identifies every requirement. When the product needs a change, it can draft a pull request for you to review, merge and deploy.
The handoff stays precise
- Ready means every requirement for that motion is already in place.
- A missing code step names the change and, with a repository connected, where it belongs in your stack.
- Runner drafts the change on a branch and opens a pull request only after a person approves it. Your team keeps the merge and deploy.
Which growth plays fit?
Example- Capture: turn visitors into contactsReady
- Onboarding and activation1 need
- Customer referrals1 need
Engineering step
A referral link per customer
Review the consequential parts. Set limits for the rest.
Every draft comes with the brief it was given. Approve it from one list, or set limits for work that can go out without waiting. Anything that fails a check comes back with the reason.
The controls that stay yours
- Daily limits start at zero, so nothing goes out on its own until you raise them or save a rule.
- One switch stops every member of the team at once.
- Approved marketing email goes only to people who agreed to receive it.
Approvals
Example- Drafted
- Approved
- Scheduled
LinkedIn lead
Your company's LinkedIn Page
We moved onboarding to one short call and one checklist. Here are the three steps we cut, and why the call stayed.
3 waiting
Keep the stack you already trust.
Search Console and Google Analytics sync in. HubSpot or Salesforce can start the next follow-up draft when a deal moves, and Runner checks whether ChatGPT, Claude and Gemini name your product.
One loop, without another spreadsheet
- The sent follow-up leaves a note on the deal in HubSpot or Salesforce.
- AI visibility shows which assistants named you and gives you three fixes.
- Your team plans from your own Search Console and Google Analytics numbers.
HubSpotDeal stages start follow-ups
SalesforceA note on the deal
ChatGPTAsked what buyers ask
ClaudeAsked what buyers ask
Search ConsoleYour searches, synced
Google AnalyticsYour traffic, synced
Start with one product and one team.
Solo covers one product and one person. Team adds more channel leads and another person to approve beside you.
Another person is $19 a month, on any plan.
How it works
- An owner or admin asks from Settings → Team within 14 days of your first plan payment.
- You get back what you paid, less the plan credits you used and any AI or media Runner paid for.
- Your plan ends that day. Later plan payments and bought credits aren't covered.
Solo
You run the business, and you're the whole company.
$79a month, AI included
- Products, a team each
- 1
- Channel leads per team
- Up to 3
- People who can sign in
- 1
- AI credits a month
- 3,000
Team
One business, and the full team working it.
$179a month, AI included
- Products, a team each
- 1
- Channel leads per team
- Up to 6
- People who can sign in
- 2
- AI credits a month
- 8,000
- Managed ad budget
- Included
Questions about Runner for engineers
Does Runner change my code?
A repository read changes nothing. When a growth motion needs code, Runner can draft the change as a pull request after a person approves it. You review, merge and deploy it yourself.
Can my coding agent tell the growth team what we shipped?
Yes. Connect Runner to Claude Code or another MCP client, then say what went out and which channels should hear about it. Each channel's lead writes its own post from your notes, and every post waits in Approvals until you approve it. A product's owners and admins can brief the team this way.
What else can I ask Runner from Claude Code?
Ask what's waiting for your approval, pull a scheduled post, turn a changelog into a LinkedIn article, see what each channel brought in, or check whether ChatGPT names your product. Drafts wait for you, and answers come from your own Runner numbers.
Do I have to write a marketing strategy first?
Start with your code and a target. Runner proposes the team, picks the growth plays that fit the business's stage and says what each one needs. You correct the context and approve the plan.
Will it post without me?
Daily limits start at zero. Work waits for approval until you raise a limit or save a rule for that kind of work, and anything that fails a check comes back to Approvals with the reason.
Can I use my own model?
Yes. Choose from the model connections Runner supports and set the model and thinking level for the team members that use one.
Keep building the product.
Runner gives the marketing work a team, a queue and a set of limits you control.
How it works
- An owner or admin asks from Settings → Team within 14 days of your first plan payment.
- You get back what you paid, less the plan credits you used and any AI or media Runner paid for.
- Your plan ends that day. Later plan payments and bought credits aren't covered.










