Strategy · · 6 min

When not to build with AI

A practical test for when rules, search or ordinary software beat machine learning on cost, latency, auditability and trust.

Abstract illustration of connected computing and data systems
Conceptual illustration; not a client system or measured result.

Start with the decision, not the technology

The useful question is not 'where can we use AI?' but 'which decision or task is slow, costly or inconsistent today, and why?'. Once the cause is clear, the right tool usually becomes obvious — and it is often not a model.

Machine learning earns its place when the pattern is too complex or changeable to write by hand and enough representative examples exist to learn it. Outside that zone it adds cost and uncertainty without adding value.

Compare the options honestly

Each approach has a natural fit. The table below is a starting point for a feasibility conversation, not a rule book.

Compare the options honestly: decision checks
SituationUsually better choiceWhy
Logic fits in a policy documentRules or workflow softwarePredictable, cheap to run and easy to audit.
Users need to find known documentsSearch with good metadataSimpler to evaluate; add generation only if summaries are genuinely needed.
Few or unrepresentative examplesCollect data firstA model cannot learn a pattern it has not seen.
Complex, variable patterns with labelled historyMachine learningThis is where models outperform hand-written logic.

Warning signs a project should pause

None of these mean AI is impossible — they mean the groundwork is missing.

  • Nobody can describe what a correct output looks like.
  • Every error would need a full, case-by-case explanation.
  • No owner is available to monitor quality after launch.
  • The expected saving is smaller than the cost of evaluation and maintenance.

The hybrid path

Many reliable systems combine both: rules handle the clear cases and hard constraints, and a model handles the ambiguous remainder with a human review step. This keeps the auditable parts auditable while still capturing value where patterns are fuzzy.

Working on something similar?

Discuss your workflow, available data and operating constraints with Talee’s engineers to assess a suitable next step.

Talk to an engineer
FAQ

Questions about this topic

03 · Questions

01

How do I know if my problem needs AI?

+

If the logic can be written as clear rules and the data is structured, ordinary software is usually better. AI fits when patterns are complex or variable and representative examples exist.

02

Is a feasibility review worth it before building?

+

Yes. A short review of the decision, the data and the cost of errors often prevents months of work on a model that a simpler approach would beat.

03

Can rules and machine learning work together?

+

Yes. A common design uses rules for clear cases and constraints, and a model for ambiguous cases with human review.

Related reading