> ## Documentation Index
> Fetch the complete documentation index at: https://docs.forge.shieldtp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account strategy overview

> Bring account context, opportunities, activities, proposals, and recurring insights into one workflow.

Account Strategy helps service and growth teams work from the same customer context. Depending on your rollout and connected provider, Forge can surface accounts, opportunities, sales activities, AI BDR proposals, touchpoints, and Custom Agent insights.

## Main surfaces

<CardGroup cols={2}>
  <Card title="Opportunities" icon="bullseye-arrow" href="/account-strategy/opportunities-and-activities">
    Review open opportunities, stage, close timing, context, summary, files, and related work.
  </Card>

  <Card title="Activities" icon="calendar-check" href="/account-strategy/opportunities-and-activities">
    Work through calls, meetings, tasks, and other provider-backed activities.
  </Card>

  <Card title="AI BDR" icon="sparkles" href="/account-strategy/ai-bdr">
    Review evidence-backed proposals in a human-operated queue.
  </Card>

  <Card title="Accounts" icon="building" href="/account-strategy/accounts-and-insights">
    Combine helpdesk, project, sales, touchpoint, and custom insight context.
  </Card>
</CardGroup>

## Source-of-truth boundary

The connected CRM or PSA remains authoritative for provider-backed opportunities and activities. Forge maintains a synchronized view and supports selected interactive updates where the provider and organization configuration allow them.

Availability differs by provider. For example, a provider may support synced opportunity records but not every interactive editor or activity detail view.

<Warning>
  Treat summaries and Custom Agent insight cards as decision support. Confirm material commitments, amounts, dates, contacts, and stages in the source provider.
</Warning>

## A useful operating rhythm

1. Review accounts or opportunities that need attention.
2. Read recent activities and supporting evidence.
3. Use scoped Chat to identify gaps or prepare the next conversation.
4. Review AI BDR proposals as proposals—not completed actions.
5. Make the external change in a supported Forge workflow or the source provider.
6. Keep the provider record current so the next analysis begins from the right state.