From the source
Amazon's guide tells teams to decide whether each workflow step needs a model at all, since routing every task through an LLM makes small calls a large production line item.
- The post says unneeded calls cost in three ways: spend grows with request count, latency stacks as each call adds hundreds of milliseconds, and output varies for the same input.
- It walks through three ordered questions, stopping at the first that meets the step's requirements: can a rule check success, can a model write the rule once, and does the step pick one answer from a fixed list.
- Steps that fail all three are open-ended and run on a right-sized model on Amazon Bedrock, while rule-shaped tasks should stay in deterministic code.
- For routing and classification, the post lists four options: a small Bedrock model with structured outputs, embedding similarity, a trained classifier on Amazon SageMaker AI, or Strands Decider.
- Strands Decider is an experimental open source decision model under the Apache License 2.0 that returns a calibrated confidence with each answer, and its README reports answers at a confidence of 0.9 or more are right about 95 percent of the time on short classification tasks.
- Because it is experimental, the post says to validate that result on your own data before production use, and to check any escalation signal against labeled data.






