AI TEAM · SALES

Reference team model

From a commercial signal to a prepared opportunity without losing context between tools.

The Sales AI Team shows how specialized roles can collaborate around acquisition, research, follow-up and CRM without turning the commercial relationship into an uncontrolled automated sequence.

WHY A TEAM

The problem: sales often breaks at the handoffs

An opportunity may start in marketing and move through research, email, CRM, calendar and reporting. When each step lives in a different tool or owner, leads go untouched, data becomes incomplete, messages are duplicated and meetings lose context. The team coordinates those handoffs; it does not replace commercial judgment or grant contractual authority to AI.

SPECIALIZED ROLES

Who participates

The composition is adapted per company. This reference model combines four common functions.

01Signals and context

Marketing Operations

Classifies sources, campaigns and intent signals and prepares useful context for the next role.

02Research and follow-up

Sales SDR AI

Researches accounts, prepares contacts, maintains CRM activity and organizes follow-up within approved rules.

View deep profile
03Inbox and replies

Email Manager AI

Organizes responses, identifies intent, proposes next steps and keeps each thread associated with the correct opportunity.

04Process visibility

Reporting AI

Consolidates activity, pipeline state and operating metrics without inventing attribution or unconfirmed revenue.

Profiles without a deep page are shown as catalog opportunities. Their presence in this composition does not imply an out-of-the-box deployment without adaptation.

EXPLICIT HANDOFFS

How the team works

Educational example of a B2B prospecting flow. Real actions depend on consent, data, tools and commercial policy.

  1. 01

    1. Detect a signal

    An approved source generates a lead or account to review while preserving its origin.

  2. 02

    2. Enrich context

    Only permitted information is gathered and structured so the SDR does not start from zero.

  3. 03

    3. Prepare follow-up

    The Sales SDR proposes or performs permitted actions, records activity and keeps CRM as the operating source.

  4. 04

    4. Interpret the reply

    The email role connects the conversation to the opportunity and routes a meeting, objection, disqualification or human review.

  5. 05

    5. Measure and escalate

    Reporting updates the state and a person intervenes before discounts, commitments, negotiation or relevant exceptions.

SYSTEMS AND CONTEXT

Typical systems

Not all are required. Only the sources needed for the approved process are connected.

CRMEmailCalendarMarketing automationFormsResearch sourcesSales documentsReporting / BIInternal APIs

GOVERNANCE

Human control points

Automating follow-up does not mean delegating commercial authority.

  • Approval of pricing, discounts, terms or contractual commitments.
  • Review of sensitive messages, unvalidated claims or brand exceptions.
  • Compliance with consent, contact preferences and prospecting policies.
  • Decisions where identity, intent or data quality is not reliable.

MEASURABLE OUTCOMES

What to measure

These are possible indicators, not improvement promises. They should be compared with a real baseline.

01

Time to first follow-up

02

Leads with a next action

03

CRM completeness

04

Human time per opportunity

05

Qualified meetings

06

Handoffs requiring correction

CONCRETE SITUATIONS

Use cases

Inbound lead

Classifies the source, retrieves context, creates or updates the record and prepares the next SDR action.

Campaign reply

Connects the email to the correct account, identifies intent and proposes a meeting, follow-up or disqualification.

Stale pipeline

Detects opportunities with no activity or missing fields and prepares correction tasks before reporting.

Meeting preparation

Summarizes interactions and authorized context so the person enters the conversation with consistent information.

LIMITS

Realistic limits

  • It does not guarantee sales, meetings or conversion.
  • It should not send indiscriminate or non-consensual outreach by default.
  • It does not negotiate or commit commercial terms outside explicit permissions.
  • Pipeline quality depends on CRM, source and integration quality.
  • Marketing Operations, Email Manager and Reporting are catalog compositions that require adaptation to the real environment.

FAQ

Frequently asked questions

Is it an autonomous CRM?

No. The team can work on an authorized CRM, but the CRM remains a separate business system and policy defines which fields and actions each role may change.

Can it contact leads automatically?

Follow-up can be prepared or enabled within approved channels, consent, rules and limits. Unrestricted autonomous outreach is not assumed.

Who approves discounts or proposals?

The company defines the thresholds. Consequential commercial commitments can remain human even when the team prepares context and drafts.

Does every employee see all information?

No. Handoffs should carry only authorized context and each role keeps separate permissions.

DESIGN YOUR SALES FLOW

Start where opportunities or human time are currently being lost.

We can map acquisition, CRM, email, calendar and reporting and decide which part should be coordinated first.