Runner, an independent concept for
Every boutique’s week, cut to measure.
Runner turns the season’s story into each boutique’s own posts, and drafts its invitations and client notes for clients who asked to hear. Each store manager approves.
One boutique. Every week. Brioni’s story, told to its clients.
Give one Brioni boutique an AI drafting team for its month. Runner turns the season’s story into the boutique’s own posts, and drafts its invitations and client notes for clients who asked to hear. Your store manager approves every word.
The work to take on
Every boutique needs its own posts. Your runner drafts them.
- The season’s story, in the boutique’s own voice.
- Your team edits instead of starting cold.
Who owns it
Your store manager stays in charge.
- Bespoke checks every date, cloth and detail.
- Every price is checked before anything goes.
- Nothing goes out without your say.
The first project
One boutique, one month. A clear answer.
- From the first Monday post to the fourth count.
What you provide
Hand over the season’s story. That’s the brief.
- The collection, the cloths and the pieces that lead.
- The month’s trunk show or Maestria evening.
- The lines your team approved.
What comes back
Every message, written and waiting for your yes.
- A post for the boutique’s clients, every Monday.
- The invitation, for clients who asked to hear.
- The thank-you after, 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, cloths and details.
- If it pays off, run it in every boutique.
What stays with you
Clients and their wardrobes stay with Brioni.
- Runner uses only the story you supply.
- No client book, CRM or store-sales connection.
The public context behind this proposal
Brioni runs around 40 stores worldwide, and every one keeps its own clients. Each season’s story, each trunk show and each Maestria evening needs a version for those clients, in Brioni’s voice, every week.
- Kering: Brioni’s bespoke craft, May 2026
- WWD’s interview with Brioni’s CEO, June 19, 2026
- Brioni’s posting: Bespoke Ambassador, Bruton Street, London, September 17, 2026
- Brioni’s posting: Store Manager, Dallas, June 8, 2026
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 fitting room.
Every season, Rome sets the story: the collection, the cloths, the trunk shows when the tailors come to town, the Maestria evenings in store. Then every Brioni boutique needs its own version, for its own clients, every week, in a voice that sounds like Brioni. Runner gives each boutique an AI team of its own. It drafts. Your client team approves. Start with one boutique's month, and put a price on those hours below.
“Customers appreciate us for our authenticity.”
Federico Arrigoni, Chief Executive Officer of BrioniFrom WWD's interview, June 19, 2026
Put in your boutiques, your weeks, your hours. Watch it add up.
- Boutique weeks a year
- 2,080
- Hours of posts, invitations and client notes
- 10,400
- What that time is worth
- €936,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.
Retail, client relations, Bespoke and Maestria, marketing: each team at Brioni 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, invitations and follow-ups. Sends only to clients who asked to hear from Brioni.
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 boutique and each channel. You know where you stand.
Checking
Guardrails
Checks consent, how often any client hears from Brioni and quiet hours, before anything goes out.
One boutique, one week.
Monday
This week's story
From the season's story, the boutique's post for its own clients: the cloth, the cut, the piece that leads. Your store manager approves.
Midweek
The invitation
A trunk show with the tailors, or a Maestria evening: one invitation, written once, only for clients who asked to hear. Never in quiet hours.
After the evening
The thank-you
One note for the clients who came and asked to hear more. Every date and detail is checked, and a person signs off.
Every Monday
The count
What went out last week and what came back, for each boutique.
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 season's story fit the boutique's clients.
Your runner drafts
Your runner drafts the boutique's posts and client notes from the story Rome approved.
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 invitation, the thank-you: each one arrives written for its boutique, in Brioni'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 boutique and each channel. Put together for you, every week.
Your limits work the night shift
Quiet hours, how often any client hears from Brioni, 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 boutique's month. We'll bring the drafts.
Bring next month’s story and one boutique. 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 Brioni. No Brioni client book, CRM, store sales or client 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 Brioni
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.