Use CasesSales

Sales

Practical ways sales teams can use Giga for account research, pipeline context, preparation, and recurring sales work.

Sales work often depends on information spread across CRM records, research, notes, previous decisions, and team context.

Giga can bring those pieces together around the account or opportunity while keeping access tied to the current workspace and connected systems.

Research accounts

A Skill can capture the team’s repeatable account-research method.

For example, it might define:

  • which company facts to collect
  • what buying or business signals matter
  • which evidence to prioritize
  • how to separate confirmed facts from inference
  • the format of the final account brief

That same method can then be reused across different accounts.

Keep important accounts in Tracks

Use a Track when the work around an account or opportunity will continue over time.

A Track can keep:

  • durable account background in Context Notes
  • meaningful developments in Memory
  • Current Track State and decision history
  • files and authored work product
  • linked Chats around the account

This helps the team pick up the work without rebuilding the account context every time.

Work with live CRM context

A Connection can give Giga access to a CRM or another approved sales system when the current workspace supports it.

That can let Giga work with current information such as:

  • account data
  • opportunity context
  • recent activity
  • other provider data exposed by the Connection

The exact records and actions available depend on the connected provider, the account permissions, and the live tool surface.

CRM access stays permission-aware

A connected CRM does not give every user or Agent access to every record or action. Giga follows both its own workspace permissions and the provider’s access rules.

Prepare for a customer conversation

A sales rep can use a Chat to prepare for a call or meeting.

A useful pattern might be:

Gather current context

Pull together relevant account information from the Track, available files, and approved Connections.

Identify useful signals

Surface meaningful changes, risks, opportunities, and open questions.

Prepare the brief

Return the context in a concise structure the rep can use before the meeting.

For repeated preparation, save the method as a Skill or the full process as a Workflow.

Standardize sales processes with Workflows

A Workflow can capture sales processes that have several meaningful stages.

Examples include:

  • account research → qualification → brief
  • opportunity review → risk assessment → next-step summary
  • call preparation → evidence review → meeting brief
  • account handoff → context review → internal summary

The Workflow stores the process order while Skills can carry reusable task methods inside individual steps.

Use a Sales Agent for a stable role

A Sales Agent can be useful when the team wants a consistent AI role across repeated sales work.

The Agent can carry:

  • durable instructions
  • sales-specific context
  • approved Skills
  • permitted Connections
  • a consistent way of presenting results

Its actual access still depends on the Group, user, Connections, and live permissions.

Run recurring pipeline work with Pulses

A Pulse can schedule sales work that should happen repeatedly.

Examples include:

  • weekly pipeline review
  • recurring account-health review
  • periodic opportunity-risk check
  • scheduled review of meaningful changes around a Sales Track

An Agent or Track can provide the target when the recurring work needs that context.

Draft follow-up with the right safeguards

Giga can help prepare follow-up messaging from the current context.

If the live Connection supports sending messages, outward-facing actions should still follow the applicable confirmation rules.

A useful pattern is:

  1. gather the relevant account and meeting context
  2. draft the message
  3. review it
  4. confirm before sending when the action requires confirmation

This keeps research and drafting fast without silently taking an external action.

Example: strategic account review

Imagine your team has a Track for a strategic account.

A weekly Pulse could then review meaningful changes around the account or pipeline when recurring monitoring is useful.

Image placeholder

Sales account diagram showing Account Track + CRM Connection + Account Research Skill + Sales Agent, with an optional recurring Pulse.