I was on a call with a CEO who told me he wanted to “plug an LLM into our database so it can answer any question about our business.” That sounds reasonable if you don’t know what an LLM actually is. Once you understand how they work, you realize that request is both simpler and more complicated than it sounds.
Let me explain what these systems actually do, without the hype or the jargon, so you can make informed decisions about where they fit in your business.
What an LLM Actually Is
A large language model is a system trained on enormous amounts of text — books, websites, code, conversations — that learned patterns in how language works. When you give it a prompt, it predicts what text should come next based on those patterns. It’s not searching a database. It’s not reasoning from first principles. It’s generating text that statistically fits the pattern of what a helpful, knowledgeable response would look like.
This is both incredibly powerful and fundamentally limited.
Powerful because the patterns it learned are rich enough that it can draft a marketing email, summarize a 50-page contract, write working code, translate a document into Spanish, and explain quantum physics to a five-year-old — all from the same model.
Limited because it’s generating plausible text, not verified truth. It doesn’t know what’s in your database. It doesn’t know today’s stock price. It doesn’t know whether the thing it just wrote is factually correct. It knows what a correct-sounding answer looks like.
What LLMs Are Good At in Business
Drafting and editing. LLMs are the best first-draft machines ever built. Marketing copy, email responses, proposals, documentation, reports — anything where you need a solid starting point that a human refines. I’ve seen content teams cut their first-draft time by 60-70% using LLMs, which means they spend more time on strategy and refinement and less time staring at blank pages.
Summarization. Feed an LLM a 40-page report and ask for a 5-paragraph summary. Feed it a week of customer support tickets and ask for the top themes. Feed it meeting transcripts and ask for action items. This is high-value, low-risk work that saves hours of human time.
Classification and routing. “Is this support ticket a billing issue, a technical issue, or a feature request?” LLMs are remarkably good at this kind of categorization. One client uses an LLM to classify incoming customer inquiries and route them to the right team — it’s accurate about 92% of the time, which is better than their previous keyword-based routing system.
Translation between formats. Convert a requirements document into user stories. Turn a database schema into API documentation. Transform a technical specification into a customer-facing FAQ. LLMs handle format translation well because it’s fundamentally a pattern-matching task.
Question answering with provided context. This is the “plug it into our database” use case, done correctly. You don’t give the LLM direct database access. You retrieve relevant documents or data, include them in the prompt as context, and let the LLM answer questions about that specific information. This is called retrieval-augmented generation (RAG), and it’s the most common pattern for business LLM applications.
What LLMs Are Bad At
Math and precise calculations. LLMs predict text patterns. “What’s 17.3% of $4,287,651?” is not a pattern-matching problem — it’s a calculation. Use a calculator. LLMs will give you an answer, and it will often be wrong.
Real-time information. LLMs are trained on data with a cutoff date. They don’t know what happened yesterday unless you tell them. Applications that need current information require connecting the LLM to live data sources — which is an engineering problem, not a model problem.
Guaranteed accuracy. LLMs generate plausible text, not verified facts. They will confidently state things that are wrong — this is called hallucination. For any application where accuracy is critical (medical, legal, financial, compliance), LLM outputs must be validated by a human or an automated fact-checking system.
Tasks requiring judgment about your specific business. “Should we enter the European market?” is not a question an LLM can answer meaningfully. It can help you structure the analysis, summarize market research, and draft a pros-and-cons document — but the judgment is yours.
The Practical Starting Point
Start with internal, low-risk applications: drafting internal communications, summarizing meeting notes, classifying support tickets, generating first-draft documentation. These use cases let your team learn how LLMs behave — where they’re reliable and where they need oversight — without risking customer-facing mistakes.
Once your team has intuition for what LLMs do well, expand to customer-facing applications with human review: AI-drafted support responses that agents edit before sending, AI-generated product descriptions that marketing reviews, AI-summarized account reports that account managers verify.
The companies that get value from LLMs are the ones that treat them as powerful tools with known limitations — not as magic boxes that replace human judgment.
Related: AI Strategy for Non-Technical CEOs | AI Hallucinations in Business Applications | AI vs. Automation
