For the last two years, the AI conversation has been dominated by one question: how big can we go? Trillion-parameter models, frontier benchmarks, $100B compute commitments. Bigger, smarter, more general.
But somewhere along the way, a quieter revolution started inside the enterprise. Companies stopped asking “what’s the most capable model?” and started asking “what’s the most useful one?”
Small Language Models — generally defined as models with fewer than 10 billion parameters — have emerged as the answer. They’re cheaper to run, fast enough for real-time workflows, and small enough to deploy on-prem or even on a laptop. That changes the economics and the privacy posture of AI in ways the headline-grabbing frontier models simply can’t match.
At Neurometric, we just crossed 3,000 active SLM users. You can download a fine tuned SLM from us without becoming a customer so, only a little over 2,200 of those users have applied for a key and are using Neurometric to host the SLM. But we’ve seen which pre-fine-tuned models are most popular from our SLM Marketplace, and we’ve talked to some enterprises directly who have asked for our help with larger scale SLM deployments.
If you’ve ever wondered what people use SLMs for in the real world - here are the top 5 things we’ve seen.
1. Summarization: Gist Generation at Scale
The single biggest workload across our user base is document summarization. Legal briefs, customer transcripts, research reports, internal wikis.
Why an SLM wins here: most summarization doesn’t need creative prose. It needs the gist — accurate, fast, and cheap enough to run across thousands of documents a day. Pushing a 50-page PDF through a frontier model with a giant context window costs real money. An SLM does the same job at a fraction of the latency and a tiny fraction of the cost. When you’re processing 10,000 documents a week, that math becomes existential.
2. Resume Screening: Extraction Without Hallucination
HR teams were one of the fastest verticals to adopt. The job isn’t to “write a beautiful candidate evaluation” — it’s to pull skills, years of experience, certifications, and seniority into a structured format.
That’s an extraction task, not a creativity task. And ironically, smaller, fine-tuned models are less prone to embellishment than their bigger cousins. Fewer parameters means fewer paths for the model to “fill in the blank” with something that wasn’t on the resume. For HR — where a hallucinated qualification is a compliance problem — the precision of an SLM is a feature, not a limitation.
3. Code Refactoring: Local, Low-Latency Suggestions
Developers using SLMs for code refactoring are the most popular group who download and use it themselves, rather than have us host it. The two reasons they seem to like the SLM approach:
Latency. An autocomplete suggestion that arrives 800ms after you stop typing is useless. Local SLMs respond in tens of milliseconds.
Security. Proprietary code never leaves the machine. For regulated industries and any company with a defensible codebase, that’s non-negotiable.
The frontier model can still review the architecture. The SLM handles the thousand small edits in between.
4. CRM Summary: Killing the Sales Busy Work
Sales reps don’t write call notes; they scribble them. The result is a CRM full of half-finished entries that nobody trusts.
Our users are using SLMs to convert messy voice memos and chat transcripts into structured CRM fields — next steps, objections, deal stage, sentiment. This is a textbook SLM workload: repetitive, schema-bound, and high-volume. A rep doing eight calls a day generates 40 summaries a week. Multiply by a 200-person sales org and you can see why running this on a frontier model is a non-starter.
5. Meeting Prep: Briefing Sheets Before the Call
The fifth pattern is what users are calling “pre-meeting intelligence.” Before a customer call, the SLM ingests prior emails, past call notes, account history, and recent product activity — then generates a one-page briefing sheet.
Speed is the metric here. The briefing needs to be ready in the 90 seconds between the previous meeting ending and the next one starting. Frontier models can’t hit that latency reliably. SLMs can.
So What Are People Actually Using SLMs For?
They’re not writing novels. They’re not passing the bar exam. They’re not solving open-ended research problems.
They’re doing the most common work tasks.
SLMs are workhorse models. Across our thousands of users, the pattern is consistent: repetitive, high-volume, structured tasks where you need roughly 90% accuracy at roughly 5% of the cost of a frontier LLM. That’s not a consolation prize — that’s the entire enterprise AI opportunity. Most business value isn’t locked behind PhD-level reasoning. It’s locked behind tasks too small and too numerous to justify a $0.10-per-call inference bill.
The Shift: From General Purpose to Specialized Agents
What our users are really previewing is the next phase of enterprise AI: a shift away from one giant general-purpose model handling everything, toward fleets of specialized agents each doing one thing exceptionally well.
The frontier model becomes the orchestrator. The SLMs do the work.
If you want to find where SLMs fit in your stack, don’t start with your hardest problems. Start with your most repetitive ones. Find the tasks your team does a thousand times a week that need to be correct, not clever. That’s the frontier now.
Bigger isn’t better. Specialized is.
The resume-screening point is the most counterintuitive data point here - smaller models being less prone to embellishment because there are fewer parameters to "fill in the blank" cuts directly against the usual assumption that small = lower quality. Across your 3,000 users, has SLM adoption plateaued at these five workload types, or is a next wave emerging? And if it's plateaued, is the constraint accuracy, lack of good fine-tuning data, or something else entirely? Happy to connect, let's talk more about it.