Chapter 6 of 11 · ~1 min
Price it, draft it
Pricing is a rule. It was always a rule; it lived in a spreadsheet and a rep's sense of what would close. A model must never price anything, because a model is never precise and a price has to be. So the price is a Code step: unit price by range, a volume tier at fifty, two hundred and five hundred units, two points more for an existing customer, and a policy cap of fifteen percent that no step below a person may exceed.
The model writes the note. Once the numbers exist, an Agent writes three sentences to the contact. It is given the numbers and told never to change them, and it has no tools. This is the pattern from the business course, the rule decides and the model explains, at the point where it earns its keep: nobody wants a rep writing forty cover notes a week, and nobody wants a model deciding discounts.
The document. A Code step assembles the quote as HTML from the price and the note. A CreateDocument node turns it into a PDF descriptor, and a ShowDocument node shows it to the prospect with download buttons. The document is built from state, so it is always consistent with the numbers the rule produced.
The line a rule cannot cross. If the prospect asked for more than fifteen percent, the price step says so in a field called needs approval. Nothing here acts on it. The next chapter does.
Experiment
Live workflowPricing and the document, live. Pick a range, a quantity and the discount you would like. Try asking for more than fifteen percent and see what the workflow does and does not do.
Price it, draft it. A rule prices, a model writes the note, a document appears.
Not deployed yet
This workflow is written and checked, and will be switched on shortly. The steps shown below are the real ones.
Big question
In your process, which number is being decided by feel that should be decided by a table?
