Image
AI Employee
Sales

The sales ops coordinator as an AI Employee

Records, reports and proposals share one dependency, the record. This is how an agent holds the coordinator’s seat between them while the revenue owner keeps every decision that reaches a customer.

Records, reports and proposals share one dependency, and nobody owns it

Today

Clean in bursts, dirty by the next meeting

  • The CRM gets cleaned in bursts, usually the week before a forecast meeting, and is dirty again by the next one.
  • The pipeline report is assembled by hand by the one person who knows which fields to trust.
  • Proposals start from the last proposal rather than from a template, so the pricing in them is whatever was true for the previous customer.
  • On the org chart that is one coordinator's job; in practice it is three people's overtime.
With agents

One role keeps the record, the report and the proposal in agreement

  • The report and the record stop disagreeing.
  • A proposal starts from the template and the record.
  • You review what leaves the business, and little else waits on you.

How an agent runs it

Records, reports and proposals are three jobs that share one dependency, the record. This role holds the seam between them, with one gate on anything that reaches a customer.

01

Maintains

Keeps each record in the state your rules describe, so the report and the proposal both start from a record that agrees with the work. Hygiene as a workflow has its own page; here it is one duty of the role.
02

Reconciles

Compares stage, next step and activity across the record and lists where they disagree.
03

Assembles

Builds the pipeline view in your existing format on the cadence you set. The report as a workflow is its own entry; the role owns keeping it current.
04

Drafts

Prepares proposals and quotes from your templates with the record's data filled in and the source of each value shown.
05

Human gate

Routes every proposal before it is sent, every price or term that differs from the template, and every merge, deletion or owner change to the revenue owner, because those actions reach the customer or change what the business has offered.
06

Tracks

Records which proposals are open, what stage they cite, and which have gone quiet, so the report and the proposal log agree.
07

Flags

Names the deals whose record and activity moved apart since the last cycle, with both shown.

Results

What changes when the number in the meeting is the number in the system

Report and record agree

One role maintains both from the same activity, so the number in the meeting is the number in the system.

Last customer's terms stay put

Assembly pulls from fields the role already keeps current, so the last customer's terms never travel to the next one.

You review what leaves the business

The gate sits on send, price and ownership, and the work inside those lines keeps moving.

Where this fits

AI Employee

Tier 2 through the AI Employee door: a full role of known-process work handed to one governed agent. The proof step is a single workflow, and CRM hygiene is already written; this role is the scale step that page points toward. Its boundary is records, reports and proposals under one gate. It does not hold pricing authority, forecasting judgement, or the customer conversation, and it does not qualify or route inbound leads. From here the pattern can extend toward an agent-run revenue operation, as a direction rather than a promise. How It Works describes how the gates are built.

Tier 2 / Scale
How It Works

Questions, answered

It drafts. A person sends, and any price or term outside the template is gated by default and opens only on your decision. The templates and the records stay in your systems, so the work can be run by hand at any point without the agent.

AI Opportunity Audit

Find the fields your report and your proposal disagree on

Bring last week's pipeline report and the most recent proposal, and find the fields they disagree on.