Runner, an independent concept for
New feature. Clear first step.
Runner turns an approved feature brief into social and email drafts. Your regional team checks eligibility, edits the copy and publishes through its existing tools.
A new feature needs a clear first explanation.
Give one regional consumer-marketing team AI help with the messages around a feature launch. Runner turns an approved product brief into social and email drafts. Your product and local marketing teams check the details and publish through the tools they already use.
The work to take on
Every feature launch needs explaining. Your runner drafts it.
- What changed, who gets it, how to try it, market by market.
- Your team edits instead of starting cold.
Who owns it
Your regional marketing lead stays in charge.
- A product marketer checks eligibility and steps.
- A local editor checks the tone.
- Nothing goes out without your say.
The first project
One feature, one market. A clear answer.
- Pick one with final instructions and a confirmed date.
What you provide
Hand over the facts you already have. That’s the brief.
- The approved description and who can use it.
- Devices, launch timing and the help link.
- Any claims to avoid.
What comes back
The whole launch, written and waiting for your yes.
- A launch post.
- A post showing one everyday use.
- An explainer email for your lifecycle team to send.
How it fits your tools
Say what to change. Get the next version.
- Your reply comes back as a revised version, your note beside it.
- Every version, note and approval is kept on a record nobody can edit.
- Nothing sends on its own; approved copy goes into your own tools.
How to judge it
Judge it in hours your team gets back.
- Time it against a similar feature launch.
- Count the corrections to eligibility and steps.
- If it pays off, run the next feature.
What stays with you
Listener data stays with Spotify.
- No listening histories, playlists or recommendations.
- No in-app messaging connection.
The public context behind this proposal
Spotify’s DJ expansion in May 2026 added languages and markets. Its Investor Day recap also describes local campaigns and partnerships as part of how it grows. Feature education is a concrete place to test campaign drafting alongside that work.
- Spotify: DJ expands with new languages and markets, May 7, 2026
- Spotify: Investor Day recap, May 21, 2026
Sources reviewed October 22, 2026. The first project above is Runner’s proposal.
The wider example below is scoped separately: live delivery needs connected channels, recorded permissions and a verified reporting source.
Less busywork. More culture.
From market teams to ad sales, every Spotify team has more to tell than hours to tell it. Runner gives each one an AI team of its own. It drafts. Your people approve. Start with one example, a new feature in every market, and put a price on those hours below.
“As Audiobooks in Premium rolled out across our first 22 markets, we saw listening grow significantly.”
Alex Norström, Co-CEO of SpotifyFrom Spotify's Investor Day, May 21, 2026: the co-CEOs' remarks
Put in your markets, your launches, your hours. Watch it add up.
- Market launches a month
- 184
- Hours of marketing work
- 1,104
- What that time is worth
- $82,800
These are your numbers, not a promise. Your @runners draft; your people still review and approve every piece. The figure is what the hours are worth, not a saving.
A team for every team.
Market marketing, global brand, ad sales, lifecycle: each team at Spotify gets this crew, inside its own limits. Each member has one job. Your people approve what goes out.
Drafting
Social lead
Drafts the posts for Instagram, Threads and LinkedIn. Your team approves each one, or lets a trusted channel run.
Writing
Email lead
Writes the emails, reminders and follow-ups. Sends only to people who asked to hear from Spotify.
Pacing
Budget keeper
Plans paid posts inside the budget you set, and asks before it goes up.
Counting
Growth lead
Puts every week's results against the target, market by market, channel by channel. You know where you stand.
Checking
Guardrails
Checks consent, how often anyone hears from Spotify and quiet hours, before anything goes out.
The build before the drop.
Two weeks out
The local version
Drafted by each market's runner from the launch brief. Edited and approved by the market team.
Launch day
The announcement
Posts go out market by market. Email only to people who asked to hear what's new, inside allowed hours. Nobody gets two.
Launch week
The paid push
Paid posts inside each market's budget. Anything more, and your runner asks first.
Every Monday
The count
Results against the target, market by market. You know where every market stands.
Your role. Your call. Your runner.
Choose your role. See what you'd hand one of your @runners, what comes back drafted, and the decision that stays with you.
Your brief
A new feature reaches your markets next month. Make it land in each one.
Your runner drafts
Your runner drafts each market's posts, the email for listeners who asked to hear what's new, and a paid plan inside the market's budget.
Your call
You choose the angle for each market and approve every word before it goes out.
Or let it run. When a channel’s drafts keep going out as written, your team can switch it to run on its own, inside the same limits. Any edit switches it back to asking.
Nobody hears the soundcheck. Everyone hears the show.
Someone checks every mic before the doors open. Your @runners lay out the drafts. Your team says go.
Your team starts at the edit.
Drafts arrive ready to edit
Posts, emails, the paid plan: each one arrives written, for every market. Your team edits and approves instead of starting cold.
Monday's count, already counted
Results against the target, market by market, channel by channel. Put together for you, every week.
Your limits work the night shift
Quiet hours, how often anyone hears from Spotify, the budget: held while nobody's watching. Pause it, and everything stops.
Built for how a big company works.
Visitor intelligence, in a waterfall
Company first. The person only where the law and their own consent allow, and never past a jurisdiction's limit.
MoreA record nothing can edit
Every proposal, approval and send is kept on an append-only record. Nothing in it can be edited or deleted.
MoreYour model, your key
Anthropic, OpenAI, Google, xAI or Ollama, on your own agreement and your own rate limits.
MoreHard limits, one stop switch
Caps on spend, sends and quiet hours that hold when nobody is watching. One switch stops all your @runners.
MoreMany teams, one organisation
Each team gets its own crew, its own limits and its own numbers, under one account.
More
Bring a market. We'll bring the drafts.
Bring one approved feature brief. We’ll show the regional team its first drafts.
The small print.
An independent concept by Runner, built from public information. Not affiliated with or endorsed by Spotify. No Spotify integration, listener data, playlist placement, music rights or advertising access is assumed. The characters are original fiction, not artists or Spotify staff.
Live in Runner today
- A team of AI marketers for every team, each member with one job.
- Posts, emails and ad plans drafted for your people to approve.
- Channels that run on their own once trusted, and stop at the first edit.
- Hard limits on spend, sends and quiet hours, and one switch to stop it all.
- The results, counted against your target, every week.
Built for Spotify
The team’s setup, the role views and the flow on this page. We build them with your team in a pilot, and no result is promised.
Runner’s security pageHow visitor context stays within permission
These are separate states, not an automatic ladder from anonymous visitor to named person.
- An arrival
- Collection follows the site’s consent policy. A visit is not a contact.
- A returning browser
- An anonymous identifier can relate allowed visits. It does not establish who the person is.
- Possible company context
- Jurisdiction and stricter operator limits govern identification. This is a provider claim with a source, not proof of employment.
- An explicit known relationship
- Linking anonymous history requires an explicit identify event. Identification itself grants no permission to send marketing.
In the US, person identification requires the customer’s own connected provider account and key. EU and UK identification stops at the organization. In South Korea, traffic-derived identification stops at the company, never the person. A visitor who identifies themselves or explicitly turns Recognition on is a separate, permission-based case. Accepting the general notice does not turn Recognition on. Global Privacy Control suppresses person identification everywhere. Nothing in the product can raise a jurisdiction limit.
Read the identification boundariesWhat a pilot covers with your security team
- Scope and access. Which teams and products, and who may approve. A senior job title grants nothing by itself.
- Data and permission. The data sources, processors, retention, jurisdiction and consent evidence for the work.
- Limits and stopping. The owner controls and approval steps. Approval never overrides eligibility or local law.
- Sign-in. Sign-in is an email link, a password or a passkey. If your security team needs single sign-on, it comes with an Enterprise plan: your people sign in through your own identity provider over SAML, and your admin connects it in Settings.
- Agreement. The use case and who reviews what, before any access. No SLA or certification is promised here.