Illustration: a laptop with an abstract account overview, printed charts and a notebook on an office desk.
An illustration of the setting, not a photograph.

Account preparation in hours.
Current context on demand.

Account intelligence workflow. A shared AI workspace that helped technical account teams investigate customer accounts and act across existing systems, with human review and established access permissions.

Context
Company and project details remain confidential.
Service
Account intelligence, system integrations, action workflows and team onboarding.
Industry
Enterprise software
Specialty
Build and integrate AI
Status
Used internally by technical account teams.

Overview

Technical account managers needed current context across customer relationships, support cases and engineering work. The internal AI workspace connected those sources and gave teams one place to investigate an account, generate a report and prepare actions.

The workspace supported account preparation within a customer success organization of roughly 200+ technical account managers serving 1,000+ customers.

Challenge

Account preparation meant finding the right people and gathering information from meetings, support cases, product work and account records. Parallel conversations could lead to repeated work, and the picture could change while someone was still preparing.

Before the workspace, gathering and coordination could take 2–3 days, with information already becoming outdated by the time the preparation was complete.

Solution

The workspace connected Gainsight, Salesforce account records and cases, Jira, Slack, Google Workspace including Gmail and Drive, and internal knowledge sources. Teams could query across those systems and generate an account report on demand.

It also supported actions in connected tools. Users could create, read, update and delete information where their existing permissions allowed it, with broader access in Gainsight and more limited access in Jira and Salesforce. Human review stayed in the loop before actions were executed.

An onboarding plan introduced Claude Code, MCP setup, the marketplace and plugins. Team members could then extend the workspace with their own context and workflows.

Results

Hours to prepare.
Minutes to generate.

Preparation before
Typically 2–3 days of gathering and coordination
Preparation afterward
Under two hours, including reading and understanding
Account report generation
Under ten minutes on demand
Organizational context
Approximately 200+ TAMs and 1,000+ customers; active adoption was not measured
Action controls
Human review and the user’s existing permissions across connected systems

Timings are based on Francois’s experience using the workspace rather than a formal time study. Preparation includes reading and understanding the generated report. Organization size is approximate; active usage, account coverage, cost savings and retention impact were not measured.

  • Account information could be queried across connected tools through one shared workspace.
  • On-demand reports reduced repeated manual gathering before customer conversations.
  • Teams could prepare and execute permitted actions with human review.

Relevant experience for system integration, account intelligence and human-reviewed actions.