A Generic AI Gives Generic Answers. Here’s How to Change That.
Most finance teams use AI the same way they use a search engine: ask a question, get an answer, move on. The teams getting the most out of it have done something different. They've made the AI their own.
Key takeaways
- A basic AI gives basic answers. Out-of-the-box AI doesn't know your chart of accounts, your reporting definitions, or how your team classifies spend, and re-explaining it every session means leaving most of the value on the table.
- Power you don't need is money you're wasting. The skill isn't just knowing how to prompt. It's knowing which model tier to reach for and how much context to give it.
- Teach it once, use it forever. Custom skills encode your team's processes, formats, and terminology so the AI follows your way of working every time, without being reminded.
- Automating finance processes can free up 30% to 40% of a finance team's capacity, time that shifts from manual execution toward the analysis and strategic work that actually moves the business forward.
- Connectivity is the difference between AI that assists and AI that works. When the AI can read directly from your CRM, HRIS, and FPu0026amp;A platform, the export-clean-upload cycle disappears, and so does the lag between the question and the answer.
The problem with general-purpose AI
There’s a version of AI that most finance professionals encounter first: a capable, general assistant that answers well when you ask it something general. Ask it to summarize a document, draft an email, or explain a concept, and it delivers. But ask it to produce variance commentary in the format your CFO expects, using your company’s definition of gross margin, with a tone calibrated for your board, and it starts guessing.
That’s not a flaw in the technology. It’s a configuration problem. AI doesn’t know your business by default. It knows what you tell it, in each conversation, every time. If you’re re-explaining your reporting structure, your terminology, and your preferred output format every time you open a new chat, you’re leaving most of the value on the table.
The teams getting disproportionate returns from AI have solved this. They’ve stopped using AI as a search engine and started using it as a configured tool, one that understands how their organization works before they ask the first question.
Choosing the right model for the right task
The first layer of LLM customization is one most finance professionals overlook: model selection. Not every task requires the most powerful model, and using the wrong tier is either wasteful or slow.
The FinanceOS Academy frames this as a three-tier decision. The fast, lightweight model, Haiku, GPT-4o Mini, or Gemini Flash, is the right choice for routine work: formatting a table, extracting specific numbers from a report, translating a document, writing a simple email. These tasks don’t need heavy reasoning. They need speed at a fraction of the cost. The mid-tier model, Sonnet, GPT-4o, or Gemini Pro, handles the majority of finance work: writing variance commentary, analyzing a P&L, building Excel formulas, and summarizing board materials. This is the daily workhorse. The top-tier model, Opus or OpenAI’s o1, is reserved for tasks that genuinely require it: deep multi-step reasoning, cross-referencing several documents for subtle inconsistencies, catching something that requires real judgment rather than pattern recognition.
The mistake most teams make is defaulting to the most powerful model for everything, or pasting an entire annual model to ask one question about a single quarter. A Harvard Business School and Boston Consulting Group field study found that knowledge workers using AI correctly completed tasks 25% faster and produced output rated over 40% higher quality, but those gains depended entirely on matching AI to tasks within its capability range. The skill isn’t just knowing how to prompt. It’s knowing how much context to give and which model to give it to.
Skills: encoding your team’s expertise once
The most powerful form of LLM customization available to finance teams right now isn’t fine-tuning a model or building a custom integration. It’s creating skills, a capability of an AI assistant like Claude.
Skills are specialized instruction sets that tell the AI how to perform a specific task at a professional level. Think of them as expertise modules. When the AI uses a skill, it follows your team’s best practices, just like a trained colleague who knows the right way to format a variance report or structure a budget model. The difference is you only have to teach it once.
A custom skill can encode anything your team does repeatedly: the specific format your monthly board report takes, the exact layout of your revenue recognition memos, the way your organization defines and categorizes certain cost lines, the tone and structure your CFO expects in a liquidity narrative. You describe the task, the format, the rules, and any examples. From that point on, the AI follows your process every time, without being reminded. It’s the difference between having a capable assistant and having one that already knows how your team works.
Automating finance processes through properly configured AI can free up 30% to 40% of a finance team’s capacity, according to McKinsey, time that shifts from manual execution toward the analysis and strategic work that actually moves the business forward. Custom skills are how you close that gap systematically, rather than solving the same formatting problem in every new chat session.
Connectors: pulling live data from the tools you already use
The second layer of customization is connectivity. A general-purpose AI works on the data you paste into it. A configured AI works on the data that already exists in your systems.
Connectors link an AI assistant like Claude to the external tools and platforms your finance team already relies on: your FP&A platform, your CRM, your HRIS, your file storage, your contract management system. Once connected, the AI can read from these tools directly, and in many cases write back to them, without copying and pasting data between systems or switching between browser tabs.
The practical difference is significant. Instead of exporting pipeline data from Salesforce, cleaning it, and uploading it to ask a question, you connect Salesforce once and ask: “What’s our pipeline volume for Q2 by deal stage?” The AI pulls the data directly, runs the breakdown, and gives you an answer. No export, no pivot table, no waiting for the sales ops team to send a report. 59% of finance leaders report using AI in their finance function in 2025, according to Gartner’s 2025 AI in Finance Survey, and connectivity to live systems is what separates the teams seeing real returns from those still copying and pasting.
This is where FinanceOS and an AI assistant’s customization capabilities converge. FinanceOS acts as the single integration point, connecting to 600+ ERP, accounting, and HRIS platforms and maintaining a governed, continuously refreshed data layer that Claude can query directly through the FinanceOS plugin. When your team has set up connectors, installed the finance and data plugins, and encoded your reporting processes as custom skills, the configuration layer is complete. The AI doesn’t need to be given a file. It doesn’t need to be reminded what gross margin means at your company or how your chart of accounts is structured. It reads that from FinanceOS. The export-clean-upload cycle disappears. The re-explanation at the start of every chat disappears. What’s left is a finance workstation that knows your business, works from current data, and produces outputs that follow your team’s format and your organization’s definitions, every time, without starting from scratch.
The bottom line
Most finance teams are using AI at a fraction of its potential, not because the models aren’t capable, but because the models don’t know the organization. Choosing the right model tier, encoding your team’s processes as custom skills, connecting the AI to the systems where your data actually lives, and installing the right plugins, these aren’t advanced steps for technical teams. They’re the configuration layer that turns a general assistant into a tool your entire finance function can rely on. The gap between teams who’ve done this and those still re-explaining their chart of accounts in every new chat will only widen from here.