Experience

Describe the work. Queen Bee runs the team. You stay in the loop.

Busy Bee isn't a single tool you use; it's a small team you direct. Most of the surface area collapses to one loop: you describe what you want, Queen Bee scopes it and assigns the right agents, the team executes, and the deliverables come back to you for review. Once that clicks, the rest of the app is just the places where that loop plays out.

The loop

You start with a request, a sentence, a paragraph, a forwarded email. Queen Bee turns it into a plan: who does what, in what order, with what dependencies. The relevant agents pick up their tasks, working in parallel where they can and handing off where they need to. As each piece finishes, it surfaces back to you. You approve, push back, or redirect. Approvals move the project forward. Pushback queues another pass. Nothing irreversible happens without your sign-off.

That's the whole product, philosophically. Everything below is the surface area where that loop runs.

The four surfaces

The v3 app has four tabs, each focused on a different slice of the loop:

• Work - your home base. Drop new requests, see what's in flight, follow tasks in real time.
• Projects - long-running containers for related work. Group tasks, share context, track deliverables.
• Data - bring your own datasets, documents, and external connections so agents can work with your data, not just the open web.
• Analytics - see what your team got done, by agent, over time.

You don't need all four to get value. Most teams live in Work and Projects and only dip into Data when they have a dataset to attach.

A day in the life

Morning: you open Work and drop a request, "draft a weekly investor update from this Notion page." Queen Bee scopes it, spins up a Writer agent, drafts the update, and hands it back. You read, request a tighter intro, and approve.

Afternoon: you're on Projects: looking at the "Q3 Marketing Push" project. Three tasks are mid-flight. You skim the artifacts the team has shipped, leave a comment on the landing page mockup, and queue a follow-up task.

Evening: you check Analytics to see what the team got done this week, eleven tasks completed, mostly the marketing project, a couple of one-offs from Work. You head out.

That's the rhythm. Now dive into the surface you'll touch first: Work.