Skip to main content
Graphic illustrating AI model challenges in multi-step reasoning, handling extensive context over 128K tokens, and large-scal

Editorial illustration for Small models lag in multi‑step reasoning, >128K context, and large‑scale coding

Small models lag in multi‑step reasoning, >128K context,...

Updated: 4 min read

Small models are cheap, fast, and private. They are also, in several very specific ways, dumb as rocks.

There's a hard ceiling. It's not about speed or cost, it's about raw capability. You can quantize and fine-tune a small model until the end of time, but it will never, ever do five things well: follow a complex, abstract chain of thought; keep a coherent thread through more than 128,000 tokens of context; write production-grade code across a sprawling codebase; or demonstrate anything resembling depth in languages outside English and Chinese.

If your task touches any of these, prepare for quiet, consistent failure. The old benchmarks won't help you spot it. MMLU, HumanEval, GSM8K are effectively useless now, saturated above 85% and muddied by training data leakage.

The new ones that actually show a difference are GPQA Diamond, SWE-bench Verified, ARC-AGI-2, HLE, and LiveCodeBench. That's where the gap screams.

Their June 2025 paper, Small Language Models are the Future of Agentic AI (Belcak et al.), argued that the narrow, repetitive sub-tasks inside most agent pipelines don’t need a frontier model, and estimated that 40 to 70% of enterprise AI tasks can run on sub-10B models.

The decision isn't big versus small. It's about the nature of your problem. Choose the small model for predictability.

When you need an answer in under a second, every time. When the data cannot, under any circumstance, leave your control. When you must get the exact same output tomorrow that you got today.

That's the real trade: you're swapping raw intellectual horsepower for operational certainty.

Do not mistake local execution for safety, though. The model's flaws travel with its weights. The biases, the blind spots, the brittle reasoning, they're all still there, just running on your hardware now.

Pick the tool that actually works for the job, not the one that looks good on a chart. Know your territory. Then own it.

Common Questions Answered

What are the five key limitations of small language models according to this article?

Small models struggle with five specific capabilities: following complex, abstract chains of thought; maintaining coherence through more than 128,000 tokens of context; writing production-grade code across sprawling codebases; and demonstrating advanced reasoning tasks. While small models are cheap, fast, and private, these limitations represent a hard ceiling that cannot be overcome through quantization or fine-tuning alone.

Why should I choose a small model over a large model for my use case?

Small models should be chosen when you prioritize predictability and operational certainty over raw intellectual horsepower. They are ideal when you need answers in under a second consistently, when data cannot leave your control for privacy reasons, or when you require the exact same output repeatedly across different days.

Can quantization and fine-tuning improve a small model's multi-step reasoning abilities?

No, according to the article, quantization and fine-tuning cannot overcome the fundamental limitations of small models in multi-step reasoning. There is a hard ceiling on small model capabilities that cannot be surpassed through these optimization techniques, regardless of how extensively they are applied.

What is the real trade-off between small and large language models?

The real trade-off is not about speed or cost, but about swapping raw intellectual horsepower for operational certainty. Small models provide predictability and control, while large models offer superior reasoning capabilities but with less certainty in execution and greater resource requirements.

Does local execution of a small model guarantee safety?

No, the article cautions against mistaking local execution for safety. While running a small model locally may provide privacy benefits, the model's inherent flaws and limitations travel with it regardless of where it is executed, so local deployment does not automatically ensure safety or reliability.

LIVE19:49Microsoft Merges Copilot Apps, Cuts Features in Strategy Shift