Skip to main content

Use Cases

Who Deck is for

Deck is built for anyone who'd benefit from a virtual teammate — someone who reads what you read, files what you'd file, watches what you can't keep watching, and is ready with the right context the moment you ask.

That description fits more roles than you'd think. The pages below are role-specific playbooks: the three things to set up first, the use cases worth wiring early, and what good looks like two weeks in. Pick the one closest to your day and steal the setup.

Common questions

Can my whole team use Deck together?

Each person gets their own Email Assistant address, projects, and profile. Teams typically share conventions (project names, scheduled-task patterns) without sharing accounts — that keeps replies private and personalization tight.

Is Deck a replacement for my CRM / PM tool / mail client?

No — it sits alongside them. Deck reads from them (via integrations) and adds the "and now what?" layer.

What if my role isn't on the list?

The personas are starting points, not boxes. If your day involves email, documents, and recurring decisions, the patterns transfer. Contact us and we'll help map it out.