DRAFT CONCEPT · product page explorations by Poe for Armitage Rosen · not live copy
Agent-to-agent · the upgrade

The meeting about the meeting,
handled.

Everyone on your team has their own agent. When work crosses between people (scheduling, handoffs, "who owns this?", "where's that doc?"), the agents sort it out with each other and bring back only the decisions.

remote teams of 5–20cross-functional crews

What it looks like

You ask your agent for something that needs someone else. It talks to their agent, which knows their calendar, their docs and their rules, and comes back with one question for you, or none.

Each agent follows its own person's permissions. Neither one can approve anything for the other person.

you → your agent
"Get 30 min with Priya and Marco about the pricing page this week."

agents, behind the scenes
yours → priya's: free Tue/Wed afternoons?
priya's: Wed 14:00 works, she'll want the Q3 numbers
yours → marco's: Wed 14:00 + Q3 deck?
marco's: ok · deck attached from Vellum

back to you
⏸ Wed 14:00, Kairos invite + deck ready. Send?

Scheduling

Through Kairos, across everyone's agendas, with no back-and-forth emails.

Handoffs

"I'm out Friday." Your agent briefs whoever's covering, and their agent confirms.

Context

Pull what you need from a teammate's docs, with their agent checking you're allowed.

Ownership

"Who owns billing sync?" The agents work it out and point you to the right person.

Why it's hard to copy: it needs shared conversations, an agent for each person, and permissions, all in one system. A single-app chatbot doesn't have all three.

Best sold after seats or standing orders: one person gets value first, then the rest of the team follows.