Runner, an independent concept for
A collection. A local invitation.
Runner drafts the copy around one collection event. Your brand team checks the story; your store team checks the details. Publish through your existing tools.
One collection. A clear invitation to discover it.
Give a local retail-marketing lead AI help with the copy around one collection event. Runner drafts the social announcement and customer email from the product story you approve. Your brand team keeps the look, the voice and the decision to publish.
The work to take on
Every collection needs telling in-store. Your runner drafts it.
- The story, plus the store, the date and the product facts.
- Your team edits instead of starting cold.
Who owns it
Your retail-marketing lead stays in charge.
- A merchandiser checks product facts.
- The store manager confirms the event.
- Nothing goes out without your say.
The first project
One collection, one store. A clear answer.
- One language, with a local reviewer and final material.
What you provide
Hand over what you’ve already approved. That’s the brief.
- The collection story and product descriptions.
- Cleared images, the store and the event details.
- Price and availability, confirmed separately.
What comes back
Every message, written and waiting for your yes.
- A post inviting people to the store.
- A caption on one verified product detail.
- An event email for people who asked for local news.
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 collection event.
- Count the corrections to product and event details.
- If it pays off, run it again at the same store.
What stays with you
Stock, prices and customers stay with Autry.
- Runner uses only the facts you supply.
- You supply cleared photography; no likeness generation.
The public context behind this proposal
Autry’s September 2026 announcement describes a focus on direct retail, selective distribution and international expansion. Its collection collaborations and ambassador programme give each local campaign a specific story to tell.
- Autry: CEO appointment and direct-retail strategy, September 2026
- Autry: global ambassador announcement
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 desk. More shop floor.
From the next capsule to the next city, every Autry team has more to say than hours to say it. Runner gives each team an AI team of its own. It drafts. Your people approve. Start with one example, the events in your stores, and put a price on those hours below.
“The opportunity now is to translate those strengths into an increasingly powerful brand universe and narrative, one that speaks directly and empathetically to consumers…”
Danilo Piarulli, Chief Executive Officer of AutryFrom Autry's announcement of its new CEO, September 15, 2026
Put in your stores, your events, your hours. Watch it add up.
- Store events a month
- 24
- Hours of marketing work
- 144
- What that time is worth
- €10,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.
Retail, brand, wholesale, digital: each team at Autry 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: a capsule, an opening, a night in store. 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 Autry.
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, channel by channel. You know where you stand.
Checking
Guardrails
Checks consent, how often anyone hears from Autry and quiet hours, before anything goes out.
Before the doors open.
Two weeks out
The invitation
Posts and an invitation, drafted by your @runners. Edited and approved by the store team. Then the city hears about it.
Event week
The reminders
Only to people who signed up. Only inside allowed hours. Nobody gets two.
The morning after
The thank-you
A thank-you, and what's next in store. For everyone who asked to hear more.
Every Monday
The count
Sign-ups against the target, store by store. You know where every store 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
Fill a store for its next event, in its own city.
Your runner drafts
Your runner sets the store, the date and the invitation, then drafts the posts and reminders around it.
Your call
You choose the event, the audience and what a good night looks like.
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 sees the prep. Everyone feels the opening.
Someone sets out the pairs before the doors open. Your @runners set out the drafts. Your team says go.
Your team starts at the edit.
Drafts arrive ready to edit
Invitation, reminders, posts: each one arrives written. Your team edits and approves instead of starting cold.
Monday's count, already counted
Sign-ups against the target, store by store, channel by channel. Put together for you, every week.
Your limits work the night shift
Quiet hours, how often anyone hears from Autry, 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 store. We'll bring the drafts.
Bring one collection and one store event. We’ll prepare the copy for your team to review.
The small print.
An independent concept by Runner, built from public information. Not affiliated with or endorsed by Autry. No Autry catalog, inventory, orders or customer data is connected. Artwork depicts an original court-shoe prop and makes no claim about an Autry product.
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 Autry
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.