Runner, an independent concept for
One month’s plan, in every store’s own words.
Runner turns head office’s plan into each store’s own posts every week, and drafts one note for members who asked. Each store lead approves their own.
One store. Every week. Its own version of the plan.
Give one Musinsa Standard store an AI drafting team for its month. Runner turns head office’s plan into the store’s own posts every week, and drafts one note for members who asked. The store lead approves every word.
The work to take on
Every store’s week needs its own posts. Your runner drafts them.
- Head office’s plan, in the store’s own voice.
- Your team edits instead of starting cold.
Who owns it
Your store marketing lead stays in charge.
- Each store lead approves their own post.
- Every price is checked before anything goes.
- Nothing goes out without your say.
The first project
One store, one month. A clear answer.
- From the first Monday post to the fourth count.
What you provide
Hand over the month’s plan. That’s the brief.
- Head office’s story, looks and member coupons.
- Each store’s hours and its own news.
- The lines your team approved.
What comes back
Every message, written and waiting for your yes.
- A post for the store’s street, every Monday.
- One note for members who asked to hear.
- The weekend post, and Monday’s count.
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 last month.
- Count corrections to prices and store details.
- If it pays off, run it in every store.
What stays with you
Members, orders and customers stay with Musinsa.
- Runner uses only the plan you supply.
- No app, membership, coupon or store-sales connection.
The public context behind this proposal
Musinsa Standard runs 43 stores in Korea, nine of them in regional areas. Head office sets each month’s plan, and every store needs a version that fits its own street, every week.
- Musinsa: 43 Musinsa Standard stores in Korea, September 22, 2026
- Bloomberg’s interview with Musinsa, via The Star, July 2, 2026
Sources reviewed October 23, 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 street.
Every month, head office sets the plan: the season's story, the looks that lead, the member coupons. Then every Musinsa Standard store needs its own version, for its own street, every week. Runner gives each store an AI team of its own. It drafts. Each store lead approves. Start with one store's month, and put a price on those hours below.
“We have a strong ambition to become a true brand house that fosters a vast, multifaceted ecosystem of labels by incubating a diverse array of independent designers.”
Nam Cho, Co-Chief Executive Officer of MusinsaFrom Bloomberg's interview, via The Star, July 2, 2026
Put in your stores, your weeks, your hours. Watch it add up.
- Store weeks a year
- 2,236
- Hours of posts and member notes
- 6,708
- What that time is worth
- $503,100
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.
Musinsa Standard, store marketing, membership, brand: each team at Musinsa 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 Musinsa.
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, for each store and each channel. You know where you stand.
Checking
Guardrails
Checks consent, how often anyone hears from Musinsa and quiet hours, before anything goes out.
One store, one week.
Monday
This week's plan
From head office's plan, a post for the store's own street, in the voice its crowd answers to. The store lead approves.
Midweek
The member note
This month's coupons, explained once, only for members who asked to hear. Never in quiet hours.
Saturday
The weekend post
Ready before the doors open. The store checks every price, and a person signs off.
Every Monday
The count
What went out last week and what came back, for each store.
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
Make this month's plan fit every store.
Your runner drafts
Your runner drafts every store's version from head office's approved plan.
Your call
Each store lead approves their own, and checks every price before it posts.
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.
Your team starts at the edit.
Drafts arrive ready to edit
This week's post, the member note, the weekend post: each one arrives written for its store. Your team edits and approves instead of starting cold.
Monday's count, already counted
What went out and what came back, for each store and each channel. Put together for you, every week.
Your limits work the night shift
Quiet hours, how often anyone hears from Musinsa, 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 one store's month. We'll bring the drafts.
Bring next month’s plan and one store. We’ll show the drafts and who checks each detail.
The small print.
An independent concept by Runner, built from public information. Not affiliated with or endorsed by Musinsa. No Musinsa app, membership, coupons, store sales or customer data is connected. The people in the photography are fictional.
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 Musinsa
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.