Predictika · Trolling motor orders

An AI sales agent's trolling motor order, checked before it goes out

An AI sales agent prepares an order for Minn Kota trolling motors: the product line, the thrust, the shaft length, the mount, the control and sonar, the batteries, the boat weight and the total thrust it states. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the catalog and the fit rules and returns a verdict, every reason and the total thrust it computed.

Scope: Minn Kota trolling motors across twelve product lines (Endura, PowerDrive, Fortrex, Ultrex, Terrova, Ulterra, the QUEST models, Kayak Terrova and the Riptide saltwater models): thrust, shaft, mount, control, sonar, batteries, charger and boat weight. See everything this validator covers

This validator models orders of this kind, not just the scenarios shown below.

  • Lines and options — the thrust and shaft sizes each line is offered with, how each line mounts, and which controls and sonar options each line can have; saltwater use needs a Riptide model.
  • Power and fit — the voltage and the number of batteries that go with each thrust, a shaft long enough for the mounting height, and the stated total thrust against the computed total.
  • Approvals — total thrust below the guide for the boat weight, and an order without a battery charger, both for a person to confirm.

Any order that touches these rules is in scope — not only the scenarios pictured here. The product lines and the thrust and shaft sizes follow the public Minn Kota catalog; the voltage and battery rules, the shaft clearance, the boat weight guide, the charger referral and the sonar and control choices for each line are modeled from comparable products and marine practice and are not published by Minn Kota. No prices are modeled. Not covered: sonar units from other brands, downriggers, accessories and prices.

The AI sales agentBuilds the trolling motor order from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

6 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
Options that exist only on some product linesOnly with care
Each line has its own thrusts, shafts, controls and sonar choices, so every combination needs a rule that reads the line.		The line and every option are checked together on every call.
Power that follows the thrustOnly with care
The voltage and the batteries per motor depend on the thrust, so a battery rule has to compare the count with a threshold chosen by the thrust.		The thrust, the voltage and the batteries are checked together on every call.
A shaft that has to clear the mounting heightOnly with workarounds
The needed length is the mounting height plus a margin, so it must be computed before it is compared with the shaft.		The needed length is computed and compared with the shaft on every call.
A stated total that must match the computed totalOnly with workarounds
The total is the number of motors times the thrust, so a separate rule is needed to recompute it and compare it with the stated figure.		The stated total thrust is a field of the order and is compared with the computed total on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as a step is completed, so a rep often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the order; approval findings need a person to sign off; everything else is computed.

    
1112 lb thrust runs at 36 V and needs 3 battery(ies) per motor; the order has 2.
2This line is not offered with 70 lb of thrust.
3This line is not offered with a 87 in. shaft.
4A 48 in. shaft is shorter than the 50 in. needed (mounting height plus 20 in.).
5A 72 in. shaft is shorter than the 73 in. needed (mounting height plus 20 in.).
6Saltwater use needs a Riptide model; this line is not a Riptide.
7The requested sonar option is not offered on this line.
8The requested control is not offered on this line.
9The requested mount type does not match how this line mounts.
10The quote states 80 lb of total thrust; the motors give 160 lb.
1180 lb of total thrust is under the guide of 2 lb per 100 lb of loaded boat weight; a person should confirm the sizing.
12The order has no battery charger; a person should confirm the customer has a compatible one.
13This line is not offered with 112 lb of thrust.
14This line is not offered with a 60 in. shaft.
15112 lb thrust runs at 36 V and needs 3 battery(ies) per motor; the order has 1.
16The quote states 100 lb of total thrust; the motors give 112 lb.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Line, saltwater and power: An Ultrex order of 112 lb thrust for saltwater with a 60 in. shaft, a wireless remote, CHIRP sonar and one battery

    
The agent's request. Please order 1 Minn Kota Ultrex motor of 112 lb thrust with a 60 in. shaft on a bow mount at 30 in. mounting height, with a wireless remote control and CHIRP, for a 5,000 lb boat. The order has 1 battery, saltwater use and a charger. The order states 100 lb of total thrust. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Thrust not offered on this line. This line is not offered with 112 lb of thrust.
    • 
      
  • Shaft length not offered on this line. This line is not offered with a 60 in. shaft.
    • 
      
  • Freshwater motor in saltwater. Saltwater use needs a Riptide model; this line is not a Riptide.
    • 
      
  • Sonar option not offered on this line. The requested sonar option is not offered on this line.
    • 
      
  • Control not offered on this line. The requested control is not offered on this line.
    • 
      
  • Not enough batteries for the voltage. 112 lb thrust runs at 36 V and needs 3 battery(ies) per motor; the order has 1.
    • 
      
  • Stated total thrust does not match. The quote states 100 lb of total thrust; the motors give 112 lb.
    • 
    

    
2. Line, saltwater and power: The agent resubmits after fixing the errors

    
The agent's request. Please order 1 Minn Kota Riptide Terrova motor of 112 lb thrust with a 60 in. shaft on a bow mount at 30 in. mounting height, with a wireless remote control and no sonar, for a 5,000 lb boat. The order has 3 batteries, saltwater use and a charger. The order states 112 lb of total thrust. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Motor summary. 1 motor(s) at 112 lb thrust, 36 V, total thrust 112 lb, 60 in. shaft.
    • 
    

    
3. Mount, shaft and charger: An Endura order on a bow mount with a 42 in. shaft and no charger

    
The agent's request. Please order 1 Minn Kota Endura motor of 55 lb thrust with a 42 in. shaft on a bow mount at 30 in. mounting height, with a Tiller control and no sonar, for a 2,500 lb boat. The order has 1 battery, freshwater use and no charger. The order states 55 lb of total thrust. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Mount type does not fit this line. The requested mount type does not match how this line mounts.
    • 
      
  • Shaft too short for the mounting height. A 42 in. shaft is shorter than the 50 in. needed (mounting height plus 20 in.).
    • 
      
  • No charger on the order. The order has no battery charger; a person should confirm the customer has a compatible one.
    • 
    

    
4. Mount, shaft and charger: The agent resubmits after fixing the errors

    
The agent's request. Please order 1 Minn Kota Endura motor of 55 lb thrust with a 42 in. shaft on a transom mount at 20 in. mounting height, with a Tiller control and no sonar, for a 2,500 lb boat. The order has 1 battery, freshwater use and a charger. The order states 55 lb of total thrust. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Motor summary. 1 motor(s) at 55 lb thrust, 12 V, total thrust 55 lb, 42 in. shaft.
    • 
    

    
5. Shaft, batteries and total thrust: Two Terrova 80 lb motors with an 87 in. shaft, one battery and a stated total of 80 lb

    
The agent's request. Please order 2 Minn Kota Terrova motors of 80 lb thrust with a 87 in. shaft on a bow mount at 40 in. mounting height, with a wireless remote control and no sonar, for a 9,000 lb boat. The order has 1 battery, freshwater use and a charger. The order states 80 lb of total thrust. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Shaft length not offered on this line. This line is not offered with a 87 in. shaft.
    • 
      
  • Not enough batteries for the voltage. 80 lb thrust runs at 24 V and needs 2 battery(ies) per motor; the order has 1.
    • 
      
  • Stated total thrust does not match. The quote states 80 lb of total thrust; the motors give 160 lb.
    • 
      
  • Thrust below the boat-weight guide. 160 lb of total thrust is under the guide of 2 lb per 100 lb of loaded boat weight; a person should confirm the sizing.
    • 
    

    
6. Shaft, batteries and total thrust: The agent resubmits after fixing the errors

    
The agent's request. Please order 2 Minn Kota Terrova motors of 80 lb thrust with a 72 in. shaft on a bow mount at 40 in. mounting height, with a wireless remote control and no sonar, for a 7,000 lb boat. The order has 2 batteries, freshwater use and a charger. The order states 160 lb of total thrust. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Motor summary. 2 motor(s) at 80 lb thrust, 24 V, total thrust 160 lb, 72 in. shaft.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares an order for Minn Kota trolling motors: the product line, the thrust, the shaft length, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the catalog and the fit rules and returns a verdict, every reason and the total thrust it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please order 1 Minn Kota Ultrex motor of 112 lb thrust. The order has 1 battery, saltwater use and a charger. The rest of the request is on screen. The order states 100 lb of total thrust.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with seven findings, all in one answer. This line is not offered with 112 lb of thrust. This line is not offered with a 60 in. shaft. Saltwater use needs a Riptide model; this line is not a Riptide. The other four are on screen.
    6. 
      
  6. The validator returned seven blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the order are checked against each other and against the stated total.
    7. 
      
  7. What this shows: for a stated total that must match the computed total, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the product line to Riptide Terrova, the sonar to no sonar, the batteries to 3 and the stated total thrust to 112.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All seven earlier findings are cleared.
    13. 
      
  13. Seven problems caught in one call, fixed in one pass, and a clean order. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    14.