Route Easy Requests to a Smaller Model: A Cost-Aware Classifier Step for Small-Business Workflows (Python) A developer outlined a lightweight Python routing layer that sends simple customer messages, such as hours or address questions, to a smaller, cheaper model while reserving the large model for complex requests like contract review. The approach combines keyword and attachment-based rules with a small classifier fallback, logs each routing decision, and recommends comparing a week before and after to track route volumes and how many easy answers needed human edits. Not every incoming message needs your most capable model. "What time do you open?" and "Please read this contract and flag the risky clauses" should not be priced the same way. A small routing step keeps AI automation costs down for a small business https://www.nxflowai.com/blog/how-to-audit-business-workflow-before-ai without hurting answers that matter. EASY HINTS = "opening hours", "address", "price list", "where are you" def rule route msg : text = msg "text" .lower if msg.get "attachments" : return "hard" if len text < 120 and any h in text for h in EASY HINTS : return "easy" return None def route msg, small classify, log : r = rule route msg if r is None: r = small classify msg "text" returns "easy" or "hard" log {"id": msg "id" , "route": r} return r def handle msg, small model, large model, small classify, log : if route msg, small classify, log == "easy": return small model msg "text" return large model msg "text" Compare a week before and after: how many items each route handled, and how many easy answers needed a human edit. We use variations of this in workflow builds for small teams.