Skip to main content

Spaces for teams and clients

One space per team, per client or per project keeps context clean — and someone who works across two simply belongs to both.

A
Written by Aaron Wittman

Shared spaces were built for households, and the same shape works for work:

  • A small team that keeps re-deciding things. Put decisions somewhere the whole team can read them — including why. Brand voice, pricing rationale, approaches tried and rejected.

  • Separate teams, one business. Engineering, GTM and support each get their own space with their own membership. Someone across two belongs to two.

  • One space per client. The agency problem — Client A's terminology bleeding into Client B's — goes away when each brand's context lives in its own space with only that account's people in it.

  • A contractor scoped to one project. Add them as an Editor to that one space; close it when the engagement ends.

  • Onboarding. The new person reads the space, and their own AI tool can answer from it, instead of asking around.

What's true today

Spaces, roles and AI-tool recall of shared memories all ship now. Team plans are US$19.99/user/month (founding pilots US$12.99/user, minimum 3 seats), with 150 memories and 300 document pages a month per seat and 10 shared spaces. There is no online Team checkout: talk to us via justonce.ai/contact about a pilot. Pooled allowances, an admin console and email-domain capture aren't built — we'd rather say so than promise a button that doesn't exist.

Did this answer your question?