Runner, an independent concept for
Every question answered, even mid-rush.
Runner answers one café’s common questions, replies to every catering and cake request, and drafts the member offer. The owner approves every word.
One café. Every week. Every question answered.
Give one Paris Baguette café an AI team for its week. Runner answers the common questions from the café’s own details, replies at once to every catering or cake request, and drafts the member offer. The owner confirms every order and approves every word.
The work to take on
Every café’s week is full of questions. Your runner answers.
- The common questions, from the café’s own details.
- A reply to every catering and cake request, at once.
Who owns it
The café owner stays in charge.
- The owner confirms every order, price and date.
- Brand approves every menu name and line.
- Nothing goes out without your say.
The first project
One café, four weeks. A clear answer.
- From the first question to the fourth Monday count.
What you provide
Hand over the café’s details. That’s the brief.
- Hours, holiday hours and the cake menu.
- What the café caters, and how to order.
- The member offer, as the brand wrote it.
What comes back
Every answer and message, ready for your yes.
- Answers to the common questions, any time of day.
- A reply to each catering or cake request.
- The member offer, 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 the owner gets back.
- Time it against a week the owner handled by hand.
- Count corrections to hours, prices and items.
- If it pays off, run it at the next café.
What stays with you
Sales, members and orders stay with Paris Baguette.
- Runner uses only the details you supply.
- No point-of-sale, ordering, catering or PB Rewards connection.
The public context behind this proposal
Paris Baguette has more than 300 bakery cafés across North America. In each one, the counter, the ovens and the phone share the same hands, and the questions keep coming: holiday hours, custom cakes, a tray for a 9 a.m. meeting.
- Paris Baguette: 300+ bakery cafés in North America, October 21, 2026
- 1851 Franchise: a Paris Baguette franchisee in Vinings, Georgia, February 11, 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 phone tag. More warm bread.
A café owner runs the counter, the ovens and the phone. Mid-rush, someone asks whether the café makes custom cakes, someone wants a tray for a 9 a.m. meeting, and this week's member offer still needs telling. Runner gives each café an AI team of its own. It answers, drafts and follows up. Your people approve. Start with one café's week, and put a price on those hours below.
“I’m the sole owner, so I’m handling everything from staffing to business management.”
Kimberly O'Dell, Paris Baguette franchisee, Vinings, GeorgiaFrom 1851 Franchise, February 11, 2026
Put in your cafés, your weeks, your hours. Watch it add up.
- Café weeks a year
- 15,600
- Hours of questions, replies and posts
- 46,800
- What that time is worth
- $3,510,000
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.
Café owners, catering, brand marketing, member offers: each team at Paris Baguette 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 Paris Baguette.
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 café and each channel. You know where you stand.
Checking
Guardrails
Checks consent, how often anyone hears from Paris Baguette and quiet hours, before anything goes out.
One café, one week.
Every day
The questions
Open on Thanksgiving? Custom cakes? The café's chat answers from its own hours and menu, and hands anything else to the team.
Any time
Catering and cakes
A request on the café's form gets a reply at once, and lands with the owner to confirm.
Midweek
The member offer
This week's offer, emailed only to members who asked to hear. Never in quiet hours.
Every Monday
The count
What went out last week and what came back, for each café.
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
Keep up with this week's questions and requests.
Your runner drafts
Your runner answers the common questions from your café's own details, and drafts a reply to every catering or cake request.
Your call
You confirm every order yourself, and approve every post and email.
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
The catering reply, the member offer, the week's post: each one arrives written for its café. The owner edits and approves instead of starting cold.
Monday's count, already counted
What went out and what came back, for each café and each channel. Put together for you, every week.
Your limits work the night shift
Quiet hours, how often anyone hears from Paris Baguette, each café'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 café's week. We'll bring the drafts.
Bring one café and its next week. We’ll show the answers, 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 Paris Baguette. No Paris Baguette point-of-sale, online ordering, catering platform, PB Rewards 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 Paris Baguette
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.