Use Cases
See how different teams can combine Giga's Chats, Tracks, Agents, Skills, Workflows, Pulses, and Connections around real work.
Giga’s building blocks can be combined around the way different teams actually work.
The examples in this section are patterns, not fixed templates. The exact systems, data, and actions available depend on the Connections, permissions, and live capabilities in your workspace.
Start with the work
A useful Giga setup usually begins with the job that needs to get done.
Then choose the primitives that fit it:
| Need | Giga primitive |
|---|---|
| Work through something directly | Chat |
| Keep an ongoing body of work together | Track |
| Give Giga durable standing background | Context Note |
| Reuse a named AI role | Agent |
| Reuse a task method | Skill |
| Reuse an ordered process | Workflow |
| Run recurring work on a schedule | Pulse |
| Work with live external systems | Connection |
Most useful setups combine several of these rather than relying on one feature alone.
Explore by team
Leadership
Pull together company context, recurring reviews, research, and decision support.
Operations
Coordinate recurring processes, cross-functional context, and connected operational systems.
Sales
Research accounts, work from CRM context, prepare briefs, and standardize recurring sales tasks.
Customer Support
Investigate issues, work from customer context, and reuse troubleshooting or response methods.
Marketing
Research, create and review content, coordinate campaigns, and keep ongoing work together.
Recruiting
Research candidates, standardize screening, prepare interview context, and track hiring work.
Finance
Work with approved financial data, recurring reporting, and structured review processes.
Product & Engineering
Keep technical context, research, implementation work, and reusable operating methods connected.
Example: one use case, several building blocks
Imagine a Sales team preparing for an account review.
Keep the account work in a Track
Store the ongoing account context, decisions, memory, and work product together.
Use live Connections
Pull current information from approved sales systems when the workspace makes those Connections available.
Apply a Skill
Reuse the team’s standard account-research or review method.
Run through an Agent
Use a named Sales Agent when a consistent role and operating context are helpful.
Schedule recurring work with a Pulse
Add recurring review only when the work genuinely needs to happen on a schedule.
Each primitive has a specific job. Together, they can form a reusable way of working.
Company Brain sits underneath the use case
Across these examples, Giga’s Company Brain remains permission-aware.
The context available to the work can include relevant:
- workspace and Group guidance
- Tracks, Context Notes, Observations, and Current Track State
- files
- Agents and Skills
- Workflows
- Connections and live external information
- user-level context
Giga retrieves what is relevant and permitted for the current task.
Use cases follow permissions
A use case does not bypass Giga’s access model.
For example:
- a Sales Agent cannot use a CRM Connection that is unavailable in its scope
- a teammate cannot access a Track simply because another teammate can
- a Workflow cannot invent access to a system
- a Pulse cannot create permissions by scheduling the work
- a Chat should not silently attach itself to a Track
The live workspace remains the source of truth.
Use cases are adaptable
These examples are meant to show how the primitives fit around real work.
They are not claims that every company uses the same process or that every named external system is automatically supported.
When a use case depends on an external tool, Giga should check the current integration and Connection surface before promising the exact action.
Image placeholder
Diagram showing a team use case in the center, surrounded by Chat, Track, Agent, Skill, Workflow, Pulse, and Connections, all sitting on top of Company Brain and permissions.