Product
Envisioning holds its client and partner calls on Starlings. The room runs from our own Mac or iPhone, nothing is recorded, and guests need no account. What was said is written down on the host's device and filed on the project it belongs to.
The meeting
Send a link. Guests need no account, and nothing is recorded. The host's device writes the transcript, and Starlings files it on the project.
Starlings never records audio or video.
Guests enter a name and an email. No account.
The host admits each guest. No audio or video flows before that.
The host's Mac or iPhone transcribes the meeting and shows captions to everyone.
When the meeting ends, Starlings files the transcript and a summary to the project or contact.
All of these work in the browser. Nothing to install.
Share one link. People pick a time when you are free.
Your Mac or iPhone runs the meeting. It decides who gets in, not a server.
Everything Starlings keeps lives in Envisioning's own Cloudflare account.
How it fits together
The diagram shows every service Starlings runs on and what travels between them. Video goes directly between participants. The transcript goes to a Worker that never sees video. The full diagram, down to the bucket and the queue, is on feature status.
The devices a person is looking at.
/room/<slug> with no account; a signed-in member gets the five surfaces too. It never hosts.Audio and video, end to end, never recorded.
One Cloudflare Worker. Text only — it never sees a stream.
Room state, the words, the ledger, the files.
Services Meet reads and writes on a member's behalf.
/admin/connectors; the next one is a card, not a page.contact@envisioning.com.After the meeting
A project keeps its chat, tasks, issues, documents and past meetings together.
Open a project, a lead, or a partner and everything about it is there: the conversation, the tasks, the issues, the history, the documents.
Everything you owe, on the project it belongs to.
GitHub issues, read and answered inside the project.
Starlings finds a commitment in the transcript and proposes it as a task.
One conversation per person, group, or project. The same thread on every device.
Write a private note now. File it into shared work later.
Zoom, Teams, Webex, or Google Meet: your Mac records the call, writes the transcript, and files it with your Starlings meetings.
Everything Envisioning has written, next to the project it is about: proposals, briefs, contracts, published work.
One room for Envisioning. Members join directly. No waiting room.
Forward an email to a channel's address. Starlings posts it as your message.
Anything in the company, from any screen.
Team lists agents next to people. Message one, answer a question with choices, or hand it a task.
Four ways to reach a person. Each name says what it asks.
Tasks and issues share one set of stages. Agents hold cards the way people do. Starlings writes every move into the project.
The workspace
Home for today, Calendar for the week, Work for what needs you, Team for who is around.
Static simulated views of Meet using representative data.
Modules in your order, on every device.
See who is free before you reach them.
Company meetings, your tasks, and your personal calendars in one place. Personal calendars stay private.
What needs you and what you owe, on the project it belongs to.
Private and shared
Quick Notes and personal calendars stay private. Anything you file into a project, conversation, document or the company calendar takes that place's access rules.
Your quick notes and personal calendar sources are yours alone.
When you put something in a shared place, it becomes company data.
The platform
The native apps and the web app share the same building blocks.
Built for each platform, at parity. The same rooms, the same workspace, the same Home.
Client credentials, sealed on your device. The server cannot read them.
Starlings is the app. The CRM, the CMS, and the vault are each a service of their own, with its own store and its own key.
One record per project, lead, partner, and person. Every app reads and writes the same one.
Your Claude reads and writes company data through Starlings, as you. Starlings logs every call.
Trust and privacy
The product controls who can join, what leaves your device, and where shared work is stored.
Every entry point checks who you are. Starlings trusts no request because of where it came from.
Starlings keeps the text of a meeting and the minimum about each person.
Every control says what it does. The room announces who joins, who leaves, and who raises a hand.
Starlings is in English and Portuguese. Pick once and every device follows.
Media on LiveKit, transcription on the host's device, everything else on one Cloudflare Worker.
Connectors
Map each source to a project once. Starlings files nothing on its own.
One connector per tool. Map a channel, a repository, or a folder to a project. Starlings files its past and new items on that project.
The state of each feature on every platform.
Tell us how your people and agents work today.