A note on why we built Cruma

Teams, workspaces, and orgs

Rooms for departments, boundaries for businesses, handoffs for everything between.

One rule sorts almost everything: an org contains related businesses; a workspace runs one private business. Departments are rooms inside a workspace, not separate silos.

People and roles

Bring people in by invite. Members see what their role allows, and nothing more: the crew literally cannot retrieve beyond a member’s visibility. Handoffs between people and crew are explicit, so “who has this now” always has an answer.

When to split into workspaces

A second workspace makes sense when the boundary is real: different staff, different customers, different systems, private economics, or a separate legal entity. Sales, Marketing, and Finance in one company are rooms. A restaurant group’s catering arm with its own team and books is a workspace.

A multi-business group

Cascadia Hospitality Group runs Event Works, Catering, Evergreen Venues, and Rentals as separate workspaces. Each has its own members, tools, memory, and Playbook. The group coordinates them; it does not merge them.

Handoffs, not shared drawers

Work crosses businesses through governed handoffs. A handoff names what is being asked, exactly what is shared, and what is withheld; the answer comes back as an artifact, and the record shows the crossing.

Handoff anatomy

Event Works asks Catering: create an allergen-safe menu for 310 guests.
Shared: guest count, dietary restrictions, event date, venue kitchen summary.
Not shared: client margin, private client notes, internal staffing.
Returned: menu summary, capacity confirmation, risk note.

Event Works never browses Catering’s raw files, and vice versa. Each business stays private; the work still flows.

What the group sees

Three directions, nothing ambient:

  • Across: handoffs between workspaces, as above.
  • Up: published rollups: each business reports its summary to the top, on purpose, not by exposure.
  • Down: shared assets and policies copied from the group into each business.

The org handles billing, admin, the user directory, and governance. It is not a master key.

Next: Billing, plans, credits, and what never gets touched.

The work moves
while you sleep.

Point Cruma at the business. It works across the tools you already use and speaks up before you ask. Your mornings can start somewhere else.

  • Works across the tools you already use
  • Advises, unasked, with its sources
  • Nothing consequential without you
Request your invite

Two fields. You'll hear from a real person within two days.

We onboard in small waves, with real help getting set up. Read why we built this.

Already have an invite? Open Cruma