Runner, an independent concept for
Every store one of a kind. Every post too.
% Arabica designs every store for its own place. Runner gives each one an AI team that drafts its week of posts, and a reply to every review in the reviewer’s own language, all in one % Arabica voice. Each store manager approves.
One country. Every store. Its own week, in one voice.
Give each of one country’s % Arabica stores an AI team for a month. Runner drafts every store’s posts from its own photographs, writes its Naver Blog and KakaoTalk Channel posts in Korean, and has a reply ready for every review in the reviewer’s own language. Each store manager approves every word.
The work to take on
Every store needs its own week. Your runner drafts it.
- The store’s posts, from its own photographs.
- Naver Blog and KakaoTalk Channel posts, written in Korean.
- A reply ready for every review, in its own language.
Who owns it
Each store manager stays in charge.
- Your country team sees every store in one list.
- Brand checks the voice, and every detail before it goes.
- Nothing goes out without your say.
The first project
Korea’s five stores, one month. A clear answer.
- From the first Monday post to the fourth count.
What you provide
Hand over the month and the photos. That’s the brief.
- What’s in the cup this month, and what’s on in store.
- Each store’s own photographs, in a shared folder.
- The lines your team approved.
What comes back
Every post and reply, written and waiting for your yes.
- Each store’s posts for the week, every Monday.
- Naver Blog and KakaoTalk Channel posts, ready to paste.
- A reply for each review, 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 the edits each draft needed.
- If it pays off, run it in every country.
What stays with you
Your stores, guests and sales stay with % Arabica.
- Runner uses only the month and the photos you supply.
- No ordering, store-sales or partner-system connection.
The public context behind this proposal
% Arabica lists 251 stores in 30 countries and regions, five of them in Korea: four in Seoul and one at Incheon Airport. Each is designed for its own place, from a library to an airport gate, and over the door at Shinsegae Gangnam the logo glows in Hangul. Its partners build the brand a whole country at a time.
- Locations, from % Arabica, November 2026
- Its stores in South Korea, from % Arabica
- The designer’s note for its Seoul Shinsegae Gangnam store
- The designer’s note for its Incheon Airport T2 store, January 2026
- Franchise inquiries, from % Arabica, March 2025
Sources reviewed November 15, 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 counter.
% Arabica designs every store for its place: a library, an art centre, an airport gate. Then each one needs its own week: what's in the cup, told to its own crowd, Korea's channels in Korean, and a reply to every review in the language it was written in. Runner gives each store an AI team of its own, writing in one % Arabica voice. It drafts. Your store manager approves. Start with one country's stores, and put a price on those hours below.
“Each store is uniquely designed in collaboration with world-class designers…”
% Arabica, to the partners who build it country by countryFrom % Arabica's franchise page, March 2025
Put in your stores, your weeks, your hours. Watch it add up.
- Store weeks a year
- 13,052
- Hours of posts and review replies
- 39,156
- What that time is worth
- $1,957,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 store.
Each store gets this crew, inside the limits its country team sets. Each member has one job, and every draft reads like % Arabica. Your people approve what goes out.
Drafting
Social lead
Drafts each store's week from its own photographs. In Korea, the Naver Blog and KakaoTalk Channel posts come written in Korean.
Editing
Copy lead
Edits every draft into one % Arabica voice before the checks, and adds no fact of its own.
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 % Arabica and quiet hours, before anything goes out.
One store, one week.
Monday
This week's post
What's in the cup this week, from the store's own photographs, written for its own crowd and edited into % Arabica's voice. The store manager approves, and it goes out at its slot.
Midweek
Korea, in Korean
The same week for the Naver Blog and the KakaoTalk Channel, written in Korean and ready to paste.
Every day
Every review, answered
Google's reviews found by the store's name, any other site's from a screenshot. Each gets a reply in its own language. The store posts it.
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 week's posts fit the store's own crowd.
Your runner drafts
Your runner drafts the week's posts from the store's own photographs, in % Arabica's voice.
Your call
You approve each one, and check every detail before it goes.
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 Korean channels, the reply to last night's review: each one arrives written for its store, in % Arabica's voice. 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 % Arabica, each store's 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 country's stores. We'll bring the drafts.
Bring next month’s plan and Korea’s five stores. We’ll show the drafts and who approves each one.
The small print.
An independent concept by Runner, built from public information. Not affiliated with or endorsed by % Arabica. No % Arabica app, ordering, store sales, partner system or guest 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 % Arabica
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 a Bespoke 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.







