Skip to content

Runner, an independent concept forOlive Young

A new deal every morning. Ready the night before.

Runner drafts tomorrow’s deal every evening, the Olive Day picks and the reminder for members who asked. Merchandising approves every line.

One month. Every day’s deal ready the night before.

Give Olive Young’s merchandising team an AI drafting team for the month. Runner drafts tomorrow’s deal every evening, the Olive Day picks and one reminder for members who asked. Merchandising checks every price and approves every line.

The public context behind this proposal

Olive Young’s daily special changes every day: yesterday’s, today’s and tomorrow’s deals are all different. And from the 25th to the 27th of every month, Olive Day brings members coupons by tier, online and in store.

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 admin. More discovery.

Every day at Olive Young starts with a new deal, and every month ends with Olive Day for members. Each one needs its words, its prices checked and the right people told. Runner gives each team an AI team of its own. It drafts the night before. Your people approve. Start with one month, and put a price on those hours below.

“Discovery shopping became extremely popular, and our customers started calling Olive Young a 'beauty playground.'”

Lee Sun-jung, CEO of Olive YoungFrom Korea JoongAng Daily, December 9, 2025

Put in your deals, your pieces, your hours. Watch it add up.

Example numbers. Make them yours.

From Olive Young: a new daily special every day, so 365 a year.

Pieces a year
1,095
Hours of marketing work
1,095
What that time is worth
$82,125

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.

Merchandising, membership, stores, brand: each team at Olive Young 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 Olive Young.

  • 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 day and each channel. You know where you stand.

  • Checking

    Guardrails

    Checks consent, how often anyone hears from Olive Young and quiet hours, before anything goes out.

One month, day by day.

  1. Every evening

    Tomorrow's deal

    The next day's special, drafted the night before. Merchandising checks every price and approves every line.

  2. Before the 25th

    Olive Day's picks

    Posts for the month's Olive Day, from the picks your team chose.

  3. The 24th

    The reminder

    Only to members who asked to hear. Never in quiet hours. Nobody gets two.

  4. Every Monday

    The count

    What went out, what people opened, and spend against the cap.

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

Put tomorrow's deal in front of the right people.

Your runner drafts

Your runner drafts the deal's posts the night before, from the line-up your team set.

Your call

You decide the final line, the price and which brand runs which day.

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

    Tomorrow's deal, Olive Day's picks, the reminder: each one arrives written. Your team edits and approves instead of starting cold.

  • Monday's count, already counted

    What went out and what came back, for each day and each channel. Put together for you, every week.

  • Your limits work the night shift

    Quiet hours, how often anyone hears from Olive Young, 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.

    More
  • A record nothing can edit

    Every proposal, approval and send is kept on an append-only record. Nothing in it can be edited or deleted.

    More
  • Your model, your key

    Anthropic, OpenAI, Google, xAI or Ollama, on your own agreement and your own rate limits.

    More
  • Hard limits, one stop switch

    Caps on spend, sends and quiet hours that hold when nobody is watching. One switch stops all your @runners.

    More
  • Many teams, one organisation

    Each team gets its own crew, its own limits and its own numbers, under one account.

    More

Bring next month. We'll bring the drafts.

Bring next month’s line-up. 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 Olive Young. No Olive Young membership, online store, app, coupon system, in-store device 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.
See how it works

Built for Olive Young

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 page
How 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 boundaries
What 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.
Start with Runner’s security page