# Who hands out the work? A reply to Markus Franz on Ippen's editorial team of agents, with our answer from six people and around 250 agents at Web Summit and from this newsroom, a person sets the work, one conductor agent hands it out, specialists and a reviewer do it, and a person decides what goes out, plus one thing we would add to one front door, a way to close it, sgit.ai

> Markus Franz, who leads the incubator lab at ippen.ai, described how Ippen Digital's editors now brief one Editorial Team in a chat, which works like a duty editor: it takes the request, decides which specialists are needed, hands out the work and brings back one answer, while a person still decides what goes out. Rules are easier to hold through one door, so they made the team the default way in, and the direct route to single specialists stayed, with the team's work coming on top. He ends with a question: if you run more than one agent, who hands out the work, a person or another agent? Our answer, from six of us running around 250 agents at Web Summit and from this newsroom, is both, at different moments. A person sets the work, in a voice note or a brief, and owns the outcome. One conductor agent hands it out: it is the one door, reads the board, briefs the specialists and collects their reports. Specialists do the work, each with a role and a behaviour policy, and a reviewer checks every claim. And a person decides what goes out; agents never send or post. We learned the same lesson Markus did, that one door is easier to govern, and the one who learned it fastest on our team had no technical background: start with one conductor and only talk to that one. And we would add one thing to a front door: a way to close it, a file every agent reads first.

*Source: <https://newsroom.sgit.ai/articles/who-hands-out-the-work.html> · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

[Home](../index.md) / [Articles](index.md) / Who hands out the work? A reply to Markus Franz on Ippen's editorial team of agents, with our answer from six people and around 250 agents at Web Summit and from this newsroom, a person sets the work, one conductor agent hands it out, specialists and a reviewer do it, and a person decides what goes out, plus one thing we would add to one front door, a way to close it

# Who hands out the work? A reply to Markus Franz on Ippen's editorial team of agents, with our answer from six people and around 250 agents at Web Summit and from this newsroom, a person sets the work, one conductor agent hands it out, specialists and a reviewer do it, and a person decides what goes out, plus one thing we would add to one front door, a way to close it

By [Dinis Cruz](https://sgit.ai/about/index.md) · 2026-11-17 · [article v1.0.0](versions/who-hands-out-the-work.md) · [newsroom v0.14.135](https://newsroom.sgit.ai/admin/versions.html) · agentsnewsroomsorchestrationconductorgovernanceweb-summitarticle

***Abstract:** Markus Franz, who leads the incubator lab at ippen.ai, described how Ippen Digital's editors now brief one Editorial Team in a chat, which works like a duty editor: it takes the request, decides which specialists are needed, hands out the work and brings back one answer, while a person still decides what goes out. Rules are easier to hold through one door, so they made the team the default way in, and the direct route to single specialists stayed, with the team's work coming on top. He ends with a question: if you run more than one agent, who hands out the work, a person or another agent? Our answer, from six of us running around 250 agents at Web Summit and from this newsroom, is both, at different moments. A person sets the work, in a voice note or a brief, and owns the outcome. One conductor agent hands it out: it is the one door, reads the board, briefs the specialists and collects their reports. Specialists do the work, each with a role and a behaviour policy, and a reviewer checks every claim. And a person decides what goes out; agents never send or post. We learned the same lesson Markus did, that one door is easier to govern, and the one who learned it fastest on our team had no technical background: start with one conductor and only talk to that one. And we would add one thing to a front door: a way to close it, a file every agent reads first.*

Who hands out the work: a person sets it, a conductor hands it out, specialists do it, a person signs off.

## In short

- **Markus Franz's point:** not an agent, a desk; one front door; a person signs off.
- **His question:** who hands out the work, a person or another agent?
- **Our answer: both,** at different moments.
- **A person sets the work and owns it;** one conductor agent hands it out.
- **Specialists and a reviewer do it;** a person decides what goes out.
- **One door is easier to govern,** and it should also be able to close.

## The post

Markus Franz of ippen.ai on Ippen Digital's editorial team of agents, LinkedIn, November 2026.

Markus Franz, who leads the incubator lab at ippen.ai, wrote: "We didn't build an agent. We built a desk." Editors at Ippen Digital brief one Editorial Team in a chat, which works like a duty editor: it takes the request, decides which specialists are needed, hands out the work and brings back one answer. Twelve specialists, eight of them in three small teams, for search, research, publishing, audience data and SEO. Before the team, every call to a specialist came from a person; from the week after launch, nine in ten came from the team. "An agent may draft, a person decides what goes out."

Two lessons in it I recognise exactly. Rules are easier to hold when most of the work comes in through one door, so they made the team the default way in. And they never closed the direct route: people still ask single specialists about as often as before, and the team's work came on top. He ends: "If you run more than one agent: who hands out the work, a person or another agent?"

## Our answer: both

For ten days around Web Summit, six of us (Dinis Cruz, Angelo Leggio, Vicky Wang, Silvio Switha, José Bota and Indi Gupte) ran around 250 named agents, more than 60 at once ([ten days at Web Summit](ten-days-at-web-summit.md)). PrompTugal.news, the newsroom we ran there, had desks of journalists, a reviewer and a curator ([PrompTugal.news, the newsroom we ran](promptugal-news-the-newsroom-we-ran.md)). This newsroom works the same way: my voice notes go to a desk of named agents, and every article passes gates before it is released.

The answer that emerged is that work is handed out twice:

1. **A person sets the work.** A voice note, a brief, a decision. The person owns the outcome and the direction.
2. **One conductor agent hands it out.** It is the one door: it reads the board, decides which specialists are needed, briefs them, and collects their reports ([how an agent team briefs its people](how-an-agent-team-briefs-its-people.md)).
3. **Specialists do the work,** each with a role, a brief and a behaviour policy that says what it may touch.
4. **A reviewer checks it,** a separate agent that checks every claim against its source.
5. **A person decides what goes out.** Agents draft; they never send or post.

## One door

We learned Markus's lesson too. The person on our team who ran one of the largest agent teams, with no technical background, put the rule in one line in her interview: start with one conductor and only talk to that one; let it hand out the work ([don't micromanage your agents](dont-micromanage-your-agents.md)). She stopped trying to read everything, and started to manage.

And, as at Ippen, the direct route stayed open. I still work directly with a specialist when the job is mine to steer, and the conductor's work comes on top.

## A door that can close

One thing we would add to a front door: a way to close it. When I needed to stop every agent across six people's accounts, the pausing took seconds, but each conductor only heard the order at its next wake, and some agents never read it at all. The fix was a file every agent reads first, before any work: a HOLD ([stopping a hundred agents](stopping-a-hundred-agents.md)). One door makes the rules easier to hold; a file at the door makes the stop easier to hold too.

## What this does not claim

- **Ippen's figures and design are Markus's;** I quote only his post.
- **Our numbers are from our own records** of the ten days, published in the series.
- **Our conductors are agents with policies,** not a product; each person ran their own.

## Where this comes from

Markus Franz's LinkedIn post, read on 17 November 2026. Earlier on this site: [ten days at Web Summit](ten-days-at-web-summit.md), [PrompTugal.news, the newsroom we ran](promptugal-news-the-newsroom-we-ran.md), [how an agent team briefs its people](how-an-agent-team-briefs-its-people.md), [don't micromanage your agents](dont-micromanage-your-agents.md), [stopping a hundred agents](stopping-a-hundred-agents.md).

## Threads

Agents & policyStartups & strategy[This article as a graph →](graphs.md#who-hands-out-the-work)

### Builds on

- [Ten days at Web Summit: what six people and around 250 agents built between 3 and 13 November, in order, and the series of articles that will tell each part](ten-days-at-web-summit.md) Six people and around 250 agents, ten days at Web Summit: what we built, in order, and the series that will tell it.
- [PrompTugal.news, the newsroom we ran at Web Summit: desks of agents that captured, mapped, wrote and reviewed 73 signed articles in ten days, an accountant that counted every run, and fifty outreach drafts that no agent was allowed to send](promptugal-news-the-newsroom-we-ran.md) PrompTugal.news: 73 signed articles in ten days from desks of agents, a reviewer for every draft, and fifty outreach drafts no agent could send.
- [How an agent team briefs its people: one JSON file, one PDF, four questions in a fixed order, copied from the book team to the Web Summit team in one night, the mistakes the method caught, and why this newsroom still briefs me in a chat](how-an-agent-team-briefs-its-people.md) How an agent team briefs its people: four questions in order, one JSON file and a PDF, copied from the book team to the Web Summit team in one night.
- [Don't micromanage your agents: what changed for Vicky Wang when she stopped reading everything her agents did and started managing them, how her team was backed by agents from another team, and why every company will want specialist agents that support all its teams](dont-micromanage-your-agents.md) Vicky Wang stopped reading everything her agents did and started managing them, backed by specialist agents from another team: a model for companies.
- [Stopping a hundred agents: the Big Stop, the hand brake and the final hold at Web Summit, why pausing took seconds but hearing the order took up to an hour, what kept running anyway, and why a stop has to be a file every agent reads first](stopping-a-hundred-agents.md) Stopping a hundred agents at Web Summit: pausing took seconds, hearing the order took up to an hour, and a stop has to be a file every agent reads first.

### Continued by

- [Partners sell, we build: the AgentiCCells partner programme in full, three kinds of partner, a freelancer, a small consultancy and a larger firm, what each one sells, the agent team behind even the smallest website cell, the rules of engagement, who owns what, who invoices, who gets paid and when, what stays with the partner, and why a partner who takes the open code and does it alone is still a win](partners-sell-we-build.md) The AgentiCCells partner programme: three kinds of partner, the agent team they resell, and the rules of engagement, 50/50.

[All articles](index.md) · [All graphs](graphs.md)

Article No. 448 · [start a reading list with it](https://newsroom.sgit.ai/for/make.html#r=448)

**Posting this article on LinkedIn?** The cover is [who-hands-out-the-work.jpg](banners/who-hands-out-the-work.jpg) (1920×1080, title and key ideas on it). Upload it as the article cover, paste the title, then select and copy the body from this page.

**Want the next issue by email.** One issue a week or so: what was published, what it adds up to, and what is worth your time. [Subscribe to the SGit Newsroom →](../subscribe/index.md)

[← All articles](index.md)


---

*[Site index for agents](../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/who-hands-out-the-work.html)*
