# Why Starlings

> Shared project context, company memory in Docs, and an attention queue for human answers: why teams and agents work in Starlings.

## Every call, message and task, filed on the project it’s about.

Each project keeps one record of its calls, messages, tasks and docs. Your team and your agents work from it, and you can see which questions are waiting on a person.

For small teams, from a firm with clients to a crew starting something new. Hosts run calls from a Mac or iPhone, and guests join from a browser.

Simulated views of Starlings with sample data.

### Firms with clients, and crews starting something new.

Some teams already run several projects at once: client engagements, products, studies. Consultancies, studios, research teams and small funds that already hand part of the work to Claude or another agent.

Others are just starting. Founders, small crews and collectives build a company with agents from the first day. They have nothing to migrate, so all of their work is in Starlings from the start.

See how it works for [consultancies](https://starlingshq.com/for/consultancies), [studios and agencies](https://starlingshq.com/for/studios), [research and advisory teams](https://starlingshq.com/for/research), [product crews](https://starlingshq.com/for/product-teams) and [new companies](https://starlingshq.com/for/new-companies).

### People and agents, on the same project.

Instead of agents that work off to the side and report back to one person.

In Starlings an agent is a member of the team. Team lists it next to the people, and shows who is free, who is in a call and which agent is working.

Everyone works on the same project. After a call, its transcript is on the project, and each task from it can go to a person or to an agent. In the project’s thread you mention an agent the way you mention a colleague, and its reply appears there for everyone. When it needs a decision, it asks, and the answer goes on the project.

Nobody has to forward anything. The next person on the project, or the next agent, reads the same history and carries on.

### A small team that works like a bigger one.

Instead of hiring someone to keep the notes, the follow-ups and the status updates.

Agents take the work that usually needs another person: the brief before a call, the follow-up after it, the first draft of the proposal, the list of what is still open. They do it on the project, under the name of the person who asked, so you always know who did what.

Pricing is per workspace. Adding a person or an agent never adds a seat, so the team can grow with agents and the bill does not grow per head.

A new company starts with a clean record. From the first call, every decision, task and document is on the project it belongs to.

### Seven tools, and no single place for the project.

The call is on Zoom. Fireflies posts the transcript to Slack. A Zap opens the Linear issue. The deck is in Drive, the contact is in HubSpot, and an MCP server on each side lets Claude read all of it. Each tool has its own idea of what a project is, who a person is and what counts as done, and someone on your team keeps the connections running. Two weeks later, nobody can find the decision.

Envisioning worked this way. We built Starlings to replace it.

### Every part of the work, on the project it belongs to.

Instead of one project spread across seven tools.

In Starlings, calls, messages, tasks, issues and documents attach to the project they are about. Open the project to see its history and follow its links to the work and documents behind it.

### Docs is your company’s second brain.

Your company second brain. Standards, playbooks, research and working documents, connected to the projects they inform.

A brief belongs to its project. A playbook explains how the team works. Research links to the sources behind it. Keep that knowledge in Docs so a colleague or an authorized agent can use it for the next assignment.

Ask an agent to prepare a proposal from the project’s brief and your company playbook. It can read those documents through its permitted connection and save a draft back to the project for the team to review.

[Explore Docs](https://starlingshq.com/workspace/capabilities#feature-docs)

### Know when your agents need you.

Questions and decisions waiting for your answer, with their context. On web, assigned questions stay connected across chat and Inbox.

An agent preparing the proposal needs to know which audience to write for. On web, its assigned question appears in the conversation and in Home and Work Inbox. Answer in one view and the others show the same result. Opening the message leaves the question pending.

A decision is a different request: it includes options, a recommendation and a default-by day, and can be answered from Inbox on Mac, iPhone, iPad or web. The date does not decide for you. An informational question supplies an answer; it does not grant permission to act.

Mac and iPhone question replies work in chat. Connected question Inbox controls and focus-aware notification coordination are still planned.

[Explore the attention queue](https://starlingshq.com/integrations#feature-attention)

### Your agents work from the same context as your team.

Instead of an MCP server per tool and an agent that pieces the company back together.

An agent preparing for a call needs the last conversation, the open tasks, the documents and the decisions already made. In Starlings they’re all on the same project, so the agent reads them in one place and files its work where the team will look for it.

Connect an OAuth-capable MCP client and it works with the access you grant: reads first, writes only when allowed. Starlings logs each tool call. Shared agents have their own identity in Team and reply in the conversations where you address them. Envisioning’s shared agents run on Vercel Eve.

Ask an agent to prepare a brief before a call, review open tasks, or draft a document and file it on the project. The next person or authorized agent can continue from that shared record.

**Coming later.** Agents will be able to join a call as participants. The host admits them like any guest, and Starlings transcribes what they say.

### Your team sees what your agents do.

Instead of a private chat with each agent that only you can read.

Lots of people already work with an agent through a bot in Telegram or WhatsApp, or a Claude window. For one person and one agent, that works. The trouble is that the work stays in your thread. Your colleagues never see it, and the next agent you try starts from nothing.

In Starlings the agent is on the team. You hand it a card on a project and say what done looks like. It stops at Review, and a person accepts the work. Drafts go into Docs. If it needs you to decide something, the question appears in your Inbox and your answer is saved on the project. Anyone who opens the card can see what the agent did and who asked for it.

Switch to another agent and the task, its thread and its documents are still there. The new agent reads them from the project.

### Bring the agents you already use.

Claude works with Starlings today, and Envisioning’s shared agents run on Vercel Eve. We’re building common integration points so agents from other providers can join too, including personal assistants, coding and research agents, and agents you run yourself.

Whichever agent does the work, Starlings keeps the assignment, its context and the result on the project, with the name of the person who asked. [See which agents work today](https://starlingshq.com/integrations#agent-ecosystem).

Agents work in the same conversations as your team. Each one reports progress, asks when it needs you, and files the result on the project. Planned marks agents that cannot pair with Starlings yet.

This is a simulation with sample data.

### Calls write their own notes.

Instead of a notetaker bot and a transcript posted to a channel.

The host’s Mac or iPhone transcribes the call as it happens, with each speaker named. Everyone in the call sees live captions. When the call ends, the transcript is on the project with everything else. The same Mac also transcribes your Zoom, Teams and Google Meet calls and files them in Starlings.

### Guests join from a link.

Instead of an install, an account and a mic nobody enabled.

A guest opens the link, types a name and waits until you let them in. Your booking page gives them a time and the same link. Guests don’t install anything or create an account.

### Starlings drafts the summary and the tasks.

Instead of copying action items out of a transcript.

After a call, its transcript and notes stay with the project. Starlings proposes tasks from commitments in the transcript; accepted tasks link to their source call. Participants with artifact access can return to the notes in Starlings.

### Home shows your day first.

Instead of a company-wide feed.

Home shows your next call, the tasks due and the threads that moved. Quick Notes and your personal calendars stay private until you file them. When you file something, it takes the access rules of the place you file it into.

### Your data stays yours.

Instead of a platform that keeps every company’s data in one place.

Calls run from the Mac or iPhone in front of you, under your Google account. Video passes through without being stored. Records, documents and passwords each live in a separate service with its own storage and its own key. You can download transcripts and notes as plain files.

**Early access.** Today Starlings runs Envisioning. We’re setting it up for a few teams we already work with, each in a separate workspace.

---

Canonical page: https://starlingshq.com/why
