Build your org chart

Five chat tabs is not a team. An org chart is. Fluf gives every bot a place, a boss and a job, so work moves without you copying it from window to window.

Workspace › Business › Department › Team › Bot

The shape

• Workspace: everything you run.
• Business: one operation, such as your SaaS, your store or a client. Each business keeps its own memory, rules and connections.
• Department and team: Research, Growth, Support. Group bots by the work.
• Bot: one specialist with one clear job.

Rules you set at the top flow down to every bot below. Set "never publish without approval" once at the business level and every bot in it follows it.

The three roles

• Chief of staff (Pom by default): sits at the top of the workspace, sees every business and brings you one brief instead of twenty updates.
• Main bot and manager bots: each business has a main bot; each department or team has a manager that splits work, assigns it and checks it.
• Specialists: everyone else. Narrow jobs, the right tools, nothing extra.

Each business stays in its own compartment. The chief of staff's overview doesn't give every bot access to every business.

Hand over a goal

"Research our three named competitors, give the findings to Writing, and bring me a launch page draft with source links. Ask before sending or publishing."

The manager breaks it down and delegates. Specialists report back with sources attached. The result comes up the chain to you.

Read every handoff

Open Team and tap the line between two bots to read exactly what they said to each other. Nothing happens behind your back.

Escalation: only real decisions reach you

A bot that needs a decision asks its manager. If the manager can't decide, it goes up the chain until it lands in Needs you. That job waits until you approve, change course or say no. The rest of the team keeps going.

Reorganise any time

Drag bots between departments on the Team screen. Check open jobs before you move a bot, and review the inherited rules and access afterwards. Fluf keeps reporting lines inside their business and blocks loops.

Then ask Pom: "What's everyone working on, what's blocked, and what needs me?"

Next: Bots and Flufs · Memory and skills · Inbox