AI for Accountants Vol. 4 - Claude
Welcome to issue #009 of New Age Accounting — Vol. #4 of AI for Accountants. Claude: Chat vs. Cowork vs. Code — and when to use each.
Most accountants who’ve tried AI have only ever used one mode — the chat box. Type a question, get an answer. That’s it. And honestly, that’s where most people stop.
But that’s like buying a Swiss Army knife and only ever using the bottle opener.
The same AI you’ve been using for chat can write and run code, build tools, and execute multi-step workflows — all without a computer science degree, a developer on staff, or an enterprise budget.
This is where the Accounting Engineer starts to take shape. Not just someone who uses AI — someone who knows which tool to use and when.
Today we’re covering three modes: Chat, Cowork, and Code. Same AI. Completely different capabilities. By the end of this issue you’ll know what each one is, when to use it, and what it looks like in an accounting workflow.
Let’s go.
Chat
Chat is where everyone starts — and for good reason. You type, it responds. Back and forth, in real time, like a conversation with someone who has read everything.
What it is: the conversational interface. You bring the question, the task, or the problem. Claude brings the knowledge, the drafting ability, and the patience to work through it with you.
When to use it: anything that benefits from a back-and-forth exchange. Drafting variance commentary. Summarizing a contract. Explaining a complex accounting standard in plain language. Preparing talking points for a board meeting. Writing the close narrative your CFO actually wants to read.
Here’s what a Chat prompt looks like in practice:
“You are a controller preparing the October board commentary. Marketing came in $47K over budget due to a unplanned conference sponsorship. Revenue beat by $120K because two enterprise deals closed in the final week. Write a two-paragraph variance explanation in plain language for a CFO audience.”
That’s Chat at its best. Specific context, clear task, defined audience. The output comes back ready to use or one refinement away from being sent.
The thing most accountants don’t realize: Chat isn’t just for one-off tasks. The conversation is the tool. The longer and more specific the thread, the better the output gets. Vol. 3’s framing techniques — establishing a role, providing an example, asking to be asked — all live here. If you’re not using those yet, go back and give it a read.
Chat is the foundation. But it’s not the ceiling.
Cowork
Chat is a conversation. Cowork is something else entirely.
Cowork is Claude working alongside you on a multi-step task — not just responding to one prompt but executing a workflow. You hand it a complex job. It breaks it down, works through the steps, and comes back with something you couldn’t have produced as fast on your own.
This is where AI stops feeling like a tool and starts feeling like a team member.
What it is: Claude operating autonomously across multiple steps within a single task. Think of it like handing a project to a highly capable colleague and saying "here's what I need" — and coming back to a finished product instead of a blank page.
When to use it: complex tasks that would normally require moving between multiple tools and sources. Anything where the output has multiple parts. Anything where you’d normally spend an hour pulling pieces together before you could even start the real work.
Here’s what a Cowork task looks like in practice:
You’re about to renew a vendor contract. Instead of spending two hours reading through the agreement, cross-referencing terms, and drafting a memo from scratch, you hand it to Claude:
“Here is our vendor contract with [vendor name]. I need you to: 1/ Summarize the key terms — payment schedule, renewal clauses, termination rights. 2/ Flag anything that should concern us before renewal. 3/ Draft a one-page memo for our CFO summarizing your findings and recommending whether we proceed.”
One prompt. Three deliverables. What used to take a morning now takes minutes.
The thing most accountants don’t realize: most people never get here because they stop at Chat. Cowork requires you to think differently about how you assign work — not “what do I need to ask” but “what outcome do I need and what would it take to get there.”
Code
This is where most accountants stop reading. Don’t.
You don’t need to know how to code to use Claude’s code capabilities. You need to know the problem well enough to describe it. That’s the accountant’s advantage — you understand the close, the reconciliation, the report better than any developer ever will. Claude handles the syntax. You handle the problem definition.
What it is: Claude writing, running, and debugging code on your behalf. You describe what you need in plain language. Claude builds it.
When to use it: building things that don’t exist yet. A close checklist that lives in a system instead of someone’s head. A dashboard that pulls your key metrics together in one place. An automation that flags reconciling items over a set threshold and surfaces them without you having to hunt for them. A tool that reformats a messy data export into a clean, board-ready table in seconds instead of an hour.
Here’s what a Code prompt looks like in practice:
“I want to build a financial reporting dashboard for our monthly close. It should include revenue, gross margin, operating expenses, and net income — with actuals vs. budget for each. Make it clean, visual, and something I can open in a browser and share directly with my CFO and leadership team."
You didn’t write a single line of code. You described the problem. Claude built the solution.
The thing most accountants don’t realize: the first build doesn’t have to be perfect. It doesn’t have to be scalable on day one. It just has to work better than what you had before. Start with one process that frustrates you every month. Describe it to Claude. See what it builds. Refine from there.
Bringing it all together
Three modes. One decision framework.
Ask yourself: what am I actually trying to do?
If you need to draft, summarize, explain, or refine something — Chat.
If you need to hand off a complex multi-step task and get a complete output back — Cowork.
If you need to build something that doesn’t exist yet — a tool, an automation, a dashboard — Code.
They’re not mutually exclusive either. The best workflows use all three. You might Chat to define the problem, use Code to build the automation, and then hand the output to Cowork to summarize and package for the CFO.
That’s the full toolkit. That’s what it looks like when an accountant stops using 10% of what’s available to them.
Pick one task from your current workflow and deliberately use a mode you haven’t tried before. If you’ve only ever used Chat — describe a process to Claude and ask it to build you something. If you’ve never tried Cowork — hand it a multi-step task and see what comes back.
The gap between where most accountants are and where they could be isn’t talent. It isn’t access. It’s awareness.
Keep building.
Here’s my question to you:
Which of the three modes are you most excited to try — and what’s the first task you’re going to use it on? Drop it in the comments — I read every one.
The purpose of New Age Accounting is simple: to empower accountants — at every level — to become builders, not bookkeepers. Whether you’re a staff accountant, a controller, or a CFO, there’s something here for you. Some topics will be high level, others will come with step-by-step guides, and some will include the exact prompts and tools you need to start building today.
If you’ve made it this far, you’re already thinking differently about this profession. Subscribe and come build with us.