Skip to content
Runner
Sign in

Runner, an independent concept for

Every store’s week, ready to assemble.

Runner turns each store’s commercial calendar into its own posts, workshop invitations and one note for IKEA Family members who asked. Each store’s local marketing lead approves.

Walk me through it See the first project

One store. Every week. Its own calendar, told.

Give one IKEA store an AI drafting team for its week. Runner turns the store’s commercial calendar into its own posts and workshop invitations, and drafts one note for IKEA Family members who asked. Your local marketing lead approves every word.

The work to take on

Every store’s week needs its own posts. Your runner drafts them.

  • The store’s calendar, in the store’s own voice.
  • Your team edits instead of starting cold.

Who owns it

Your local marketing lead stays in charge.

  • Com & In checks every room set and range detail.
  • Every date and 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 calendar. That’s the brief.

  • The range in season, the room sets and the workshops.
  • This month’s IKEA Family offer or event.
  • The lines your team approved.

What comes back

Every message, written and waiting for your yes.

  • The week’s posts for the store’s own neighbourhood.
  • One note for IKEA Family members who asked to hear.
  • The weekend workshop 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 dates, prices and range details.
  • If it pays off, run it in every store.

What stays with you

Members, orders and customers stay with IKEA.

  • Runner uses only the calendar you supply.
  • No app, IKEA Family, loyalty or store-sales connection.
The public context behind this proposal

Ingka Group runs 411 IKEA stores and city stores in 32 countries. Every one keeps a commercial calendar of range, room sets, workshops and member offers, and every one tells its own neighbourhood, every week.

Sources reviewed November 10, 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 living room.

Every IKEA store runs on a commercial calendar: the range in season, the room sets, the workshops, the activities for kids, the offers for IKEA Family members. Each store has to tell all of it to its own neighbourhood, every week. Runner gives each store an AI team of its own. It drafts. Your local marketing lead approves. Start with one store's week, and put a price on those hours below.

“…customers truly appreciate having IKEA closer to them and in locations that naturally fit into their daily life.”

Juvencio Maeztu, CEO and President, Ingka GroupFrom Ingka Group's newsroom, March 11, 2026

Put in your stores, your weeks, your hours. Watch it add up.

Example numbers. Make them yours.

From Ingka Group, November 2026: 411 IKEA stores and city stores in 32 countries.

Store weeks a year
21,372
Hours of posts, events and member notes
85,488
What that time is worth
€5,129,280

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.

Local marketing, Com & In, IKEA Family, the country team: each team at IKEA 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 IKEA.

  • 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 IKEA and quiet hours, before anything goes out.

One store, one week.

  1. Monday

    This week's calendar

    From the store's commercial calendar, the week's posts for its own neighbourhood: the range in season, the room sets, what's on. Your local marketing lead approves.

  2. Midweek

    The IKEA Family note

    This month's member offer or event, written once, only for members who asked to hear. Never in quiet hours.

  3. Saturday

    The workshop post

    The weekend's workshop or kids' activity, ready before the doors open. The store checks every time and price, and a person signs off.

  4. 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

Turn this week's calendar into the store's own posts.

Your runner drafts

Your runner drafts the week's posts and event invitations from the calendar you approved.

Your call

Your local marketing lead approves each one, and checks every date and price.

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 posts, the IKEA Family note, the workshop 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 IKEA, 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 one store's week. We'll bring the drafts.

Bring next month’s calendar and one store. We’ll show the drafts and who checks each detail.

How Runner works

The small print.

An independent concept by Runner, built from public information. Not affiliated with or endorsed by IKEA. No IKEA app, IKEA Family membership, 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.
See how it works

Built for IKEA

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