Skip to main content
The platform gives you two kinds of AI teammate, and knowing which to use when is the heart of building well:

T-W1N — your digital twin

Created automatically for every person. Private to you, invisible to colleagues, and acts as you — through your accounts, with your access. You don’t hire it; it’s simply yours.

Hired teammates

Colleagues you onboard deliberately. Each has its own identity — its own workspace account, contact details, app profiles, and access — visible to and usable by the whole organization.

The essential difference: whose identity?

T-W1N is a stand-in, not a separate person. In its own words:
I’m here for you, specifically. When you connect your workspace, I act through your accounts and show up as you, not as a separate identity on the side.
Emails it sends from your workspace come from you; files it touches are the ones you can reach; and it talks only to you — never to your colleagues or external contacts directly. Even its contact details are a platform-level routing layer rather than personal identity: shared numbers and addresses where incoming messages are matched to your verified identity and routed to your twin. A hired teammate is a genuine new colleague. It gets its own name, persona, and voice; its own dedicated Google or Microsoft account with its own gated access to files and apps; its own phone number, email, and WhatsApp; its own profile on Teams and Slack; and its own integration credentials. Everyone in the org can find it, message it, and work with it — and it can talk to anyone, human or virtual, under the response policies you control.

Start with twins, hire as you grow

For most organizations the right sequence is:
1

Everyone gets their T-W1N first

It’s automatic, it’s free of setup ceremony, and it piggybacks on each person’s existing account — one OAuth connect and it’s productive inside their inbox, calendar, and files. Individual productivity, solved.
2

Hire dedicated teammates when workflows outgrow one person

The signal is work that has a defined scope and a shared audience: multiple stakeholders need access, several people need to message the same assistant, or a process needs its own mailbox and file permissions rather than borrowing someone’s. That’s when a hired teammate with a dedicated account earns its keep.
Your T-W1N actively helps with this judgment — it’s briefed to spot the moment:
Sometimes a piece of work has outgrown a generalist and would be better owned by a dedicated colleague — one defined scope, its own identity, its own clock, a shared audience that isn’t just you. When I see that shape, I’ll name it plainly and propose what the colleague would be, what they’d own, and how we’d hand work to them. If you say yes, I set them up and pre-seed them with what we’ve already decided.

What’s in this section

T-W1N vs hired teammates

The identity model in depth — accounts, access, contact details, and integrations.

Onboarding a teammate

The hire flow: persona, voice, workspace account, computer — and life after hiring.

Liaising across the team

How hired teammates work with everyone — people and assistants alike.