All services · AI for one work task

One workflow · verifiable output

AI assistant for sales representatives

For sales managers and representatives who need help preparing and progressing a sale. The assistant assembles client context, suggests a script, prepares a reply or quote, and drafts a summary. The salesperson is human: they verify information, communicate with the client, and approve commitments.

Denis Skripnik — a blind specialist in working with AI agents. I examine the task, configure the workflow, and work with you to verify the result against agreed rules.

AI agent setup is already selected in the brief. Name the scenario: “AI assistant for sales representatives”. Describe the files or systems you use, the result you need, and any exceptions. Start with a description of an anonymized sample.

Input: client context, company rules, and a current price list

• Selected client and deal information, authorized conversation history, and the client’s request from agreed sources or an export.
• Company rules: sales stages, permitted wording, restrictions, discount and commitment approval procedures, and approved templates.
• A verified, dated or versioned price list with product codes, currency, units, and price terms. Availability, lead times, and delivery are used only when supported by a confirmed source.

Output: materials for client conversations and quotes

• A source-linked client summary and a proposed conversation script following company rules: known facts and questions to clarify.
• A reply or quote draft using verified price-list items, with price references and unconfirmed terms flagged. Insufficient data produces questions for the representative, not a fabricated offer.
• A draft CRM summary: confirmed facts, open questions, and a proposed next action. The representative reviews and transfers it manually; no CRM records are created automatically.

Example: a discount request is not a promise

An illustration, not a client case study. A client requests 3 units of product A, a 10% discount, and delivery by Friday. Price list v3 lists A at RUB 10,000 per unit including VAT; company rules require separate discount approval, and no delivery date is confirmed.

The assistant assembles context and suggests a script to clarify timing. The quote draft shows 3 × 10,000 = RUB 30,000 including VAT before discount, with a reference to price list v3. The discount needs approval; delivery is unconfirmed. The representative agrees terms, edits the draft, and only then sends it to the client.

After the conversation, the representative supplies confirmed outcomes. The assistant drafts: “3 units of A requested; discount and timing not yet agreed,” and suggests checking delivery and requesting discount approval as the next action. The summary remains a draft until the representative reviews it.

What the implementation includes

• One agreed sales-team workflow: context sources, roles, company rules, a verifiable price list, and draft formats.
• Context → script → reply or quote → summary and next action. Calculations follow defined rules; generated wording does not replace price verification.
• Test examples covering an outdated price list, unknown product, unconfirmed delivery, an unapproved discount, and conflicting client history.

Minimum access and customer responsibilities

• Read-only access to selected deals, conversations, and rules within the permitted role; no whole-CRM access or message-sending permission is needed. Anonymized exports and files are sufficient to start.
• The customer supplies current rules and prices, assigns their owner and a reviewing representative, confirms permitted client-data processing, and agrees how sources will be updated.

Acceptance and assistant limits

In the customer’s environment, we test the complete workflow using agreed examples: context accuracy, script compliance, quote prices and arithmetic, visible unknown terms, and summary accuracy. Handover includes instructions and training for representatives to review and use drafts.

No autonomous outreach, prospecting, calling, negotiation, reply sending, or CRM changes. Only a human approves discounts, off-list prices, deadlines, and other commitments. Sales growth is not guaranteed; new channels, systems, roles, and volumes need separate agreement.

Sources, access, and your responsibilities

• An anonymized export is enough to start: remove information that could identify a person, business secrets, and unnecessary fields. Do not put passwords or keys in the brief.
• For implementation, we agree the minimum necessary permissions, preferably a dedicated account with read access only to selected sources. An export instead of production-system access is an acceptable alternative.
• You provide lawfully available samples, rules, an authorized environment, and a designated reviewer who resolves disputed data. We agree storage, deletion, and permitted model-provider data transfers in advance.

Acceptance, instructions, and training

At acceptance, we run the chosen workflow in the customer’s environment. We agree criteria, a test set with ordinary and disputed examples, output format, and error reporting before implementation. Handover provides operating and review instructions and training for the responsible employee; their format and scope are specified in the proposal.

Iteration count, correction of nonconforming results, requirement changes, and support after acceptance are agreed separately before starting. Unlimited revisions and ongoing support are not implied.

Timing, price, and external expenses

The price and exact duration are confirmed after reviewing a sample and before work starts. They depend on data quality, formats, volume, environment, and review requirements. Existing service price guidance is not a fixed quote for this scenario.

If a sample is insufficient to define the scope reliably, a paid discovery or bounded pilot can be agreed separately, with its own deliverable and criteria. It does not automatically commit either party to full implementation.

Server costs, paid services, and model usage are separate from implementation fees. Before starting, we agree what is necessary, who pays for accounts, and spending and processing limits. Payment for the work follows scope and quote confirmation only.