Deal Milestone Detection

Challenges Deal Milestone Detection addresses

Done by hand, sales execution means gathering customer message and deal state, working through 2 separate passes over the same material, then producing does this move the deal?, what the message contains and proposed crm update. None of it is difficult and all of it is exacting, which is the combination people are worst at holding. The errors that matter are the ones a tired reader does not notice, and they surface later — in a reconciliation, or in somebody’s reply. It starts whenever something arrives, which means someone has to be watching for it to start at all. As volume grows the work does not get harder, only longer, and the first thing to go is the checking.

Deal Milestone Detection runs that same sequence end to end and returns the result as structured artefacts. What it cannot settle it hands over rather than guesses at, and your correction is kept: it asks “Was this the right read?” after every run, and those answers become the set it is measured against. Nothing that moves money, alters a contract or reaches a customer executes without human approval, and every action is written to an audit log. The gain is in the volume that no longer has to be read, not in removing the judgement.

How it works

Step 1: Detecting milestones

First of 2. It works from customer message and deal state and feeds the step after it.

Key Tasks:

• Working from the run so far: This step takes customer message and deal state and carries it toward step 2.
• Following the same rules each time: The behaviour is configuration rather than judgement made fresh per run, so sales execution is handled the same way every time.
• Surfacing what it cannot settle: Anything ambiguous is passed on as ambiguous rather than resolved silently.

Outcome:

• Passed on: The result passes to the next step, with anything unresolved carried forward as an open item rather than dropped.

Step 2: Writing the CRM note

Last of 2. It takes what step 1 produced and produces does this move the deal? and what the message contains.

Key Tasks:

• Writing from the run, not from a template: The text is built from what this run actually found, so two sales execution outputs differ where the underlying records differ.
• Leading with what needs a decision: The exceptions come first and the routine detail follows, because the reader is deciding rather than reading.
• Staying inside the evidence: Nothing appears in the text that is not supported by a record the run examined. Gaps are stated as gaps.

Outcome:

• Artefact ready: A finished artefact, traceable line by line to the records behind it, ready for a person to accept or correct.

Step 3: Your review, and what it changes

The run ends with a person, not with a result being filed.

Key Tasks:

• Asking a specific question: It asks “Was this the right read?” rather than for a rating. A question about this run is answerable; a score out of five is not.
• Keeping the correction: What you change is recorded against the case that produced it, so the disagreement is retrievable rather than absorbed.
• Building the evaluation set: Those cases become what the agent is measured on. It is scored against your judgement rather than against a general benchmark.

Outcome:

• A measured agent, not an assumed one: The cases Deal Milestone Detection handles well and the cases it does not are both visible, and the second list is the one that decides what changes. Nothing is retrained silently on the back of a single correction.

Why use Deal Milestone Detection?

• A batch is one run, not a hundred: It works the whole set in a single pass and returns a row per item with its verdict, so the volume that needs no attention never has to be opened.
• Machine-readable for whatever comes next: One of the artefacts is a structured payload, so this agent can sit in the middle of a pipeline rather than only at the end of one.
• Works from the message itself: The body and its attachments are the input, so a request does not have to be transcribed into a form before anything can happen to it.
• Starts from the message itself: A matching message in the connected inbox is the trigger, so nothing sits in a queue waiting to be noticed. Messages that do not match are left alone rather than processed and discarded.
• Corrected by the people using it: After each run it asks “Was this the right read?”. Those answers become the evaluation set, which means it is measured against your judgement rather than ours.