# Route Easy Requests to a Smaller Model: A Cost-Aware Classifier Step for Small-Business Workflows (Python)

> Source: <https://dev.to/ujjwal_dubey_9/route-easy-requests-to-a-smaller-model-a-cost-aware-classifier-step-for-small-business-workflows-52d9>
> Published: 2026-11-18 15:05:35+00:00

**Recommendation:** Route short, hint-matching messages to a small model and attachment-bearing ones to the large model, then compare route volumes and human-edit rates before and after.
More in the playbook "Controlling LLM cost": <https://wpnews.pro/playbooks/llm-cost>

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.
