EMPVResearch NotesIT
EMPV / RESEARCH NOTESNOTE / 004

FIELD NOTE / COMMERCIAL OPS

Automating a quote request without automating the decision

The bottleneck is not always calculating a price. Often it is collecting the information a person needs to make a fast and well-informed decision.

Published2026-09-29 ยท 5 min
QuotingLead qualificationHuman reviewWorkflow
01 / The false objective

An automatic quote is not always the right outcome.

In project-based work, technical services or highly variable jobs, price depends on information that emerges during the conversation. Fully automating the quotation can therefore move the problem rather than solve it.

The first objective can be simpler: make sure the team receives a request that is already understandable.

02 / Collection

Ask only for information that changes the evaluation.

A good flow is not an endless form. It starts from the few variables that determine the next path and adapts questions to the type of request.

The output is consistent context, not an automatic decision.

  • separate required and optional information
  • adapt questions to the request type
  • make missing data visible
  • keep room for free-form context
03 / Qualification

Structuring is not the same as judging.

The system can check completeness, classify the request and prepare a summary. But if margin, risk or feasibility require experience, the decision can remain human.

That boundary is useful: automation removes mechanical work without hiding a commercial choice inside an opaque score.

04 / The outcome

The team starts from context, not reconstruction.

The commercial or technical team should be able to open a request and already have the elements needed for an initial evaluation. That means fewer clarification messages, less re-entry and fewer forgotten details.

Automation prepares the decision. It does not necessarily need to make it.

EMPV / TAKEAWAY

The best automation point may be before the quote, not inside the price.

Research Notes