Prompts our own bookkeepers send Claude every day.
On a call, we show you this live. This page is for the part after the call, when you’re back at your desk wondering what to actually type. These are real requests from our team, lightly reworded to remove client detail, organized by the work they cover.
You don’t learn a tool from a feature list. You learn it from the asks.
Numbers Game runs on our own book of clients before it ever ships to a firm. The examples below are drawn from that work, the close, the reconciliation, the journal entries nobody wants to build by hand, the emails, the tax notices. Copy one, adapt it to a real client, and see what comes back.
Two names come up below. NG MCP is the connector itself, what gives Claude secure, scoped access to a client’s QuickBooks file, and what ships publicly as the Numbers Game skill. NG Wizard is the automated close-and-audit skill we layered on top of it, built for the way our own team actually runs a close. Both started as shorthand inside our own firm before either was a product.
Month-end close & book audits.
The single most common ask on our team, every month, for every client.
“Run the March close for Lattimer & Co., GL only, we don’t have a bank statement yet.”
Claude works the close checklist end to end: posts the missing accruals, flags unclassified transactions, and produces a Close Report with the P&L and Balance Sheet attached, ready to send.
“Audit 2025 and 2026 year-to-date for Halcyon Robotics and tell me if the books are actually closed. Don’t post anything.”
Three flagged items, a missed depreciation entry, a duplicate reversal from March, and one vendor miscoded to the wrong P&L line, each with its dollar impact, before a single write touches QuickBooks.
New client onboarding & handover.
Getting oriented on a client before you touch anything, or handing one off cleanly when you leave.
“I’m taking over Halcyon Robotics from another accountant on our team. Give me an overview before I touch anything, customers, recurring expenses, main vendors.”
A one-page briefing pulled straight from the books, no changes made, so the new accountant walks into their first close already oriented instead of guessing.
“New QuickBooks connection for Boreal Software, the account’s empty except for bank statements. What can you do before we get the chart of accounts?”
A clear split of what could start immediately, like categorizing bank transactions from vendor names, versus what needed to wait, so onboarding didn’t stall on one missing document.
Bank & credit card reconciliation.
The dollar-by-dollar hunt that used to eat an afternoon.
“Reconcile the Chase card through June 30. It tied out clean as of May 31, find the gap starting there.”
The difference isolated to four transactions the bank feed had skipped, matched against the statement, reconciled to the cent.
“Compare this month’s statement to what’s in QuickBooks for Northwind Freight and tell me what’s missing or duplicated.”
A line-by-line match, two missing deposits and one duplicate expense flagged for review, nothing changed yet.
The entries that aren’t routine.
Deferred revenue, amortization, depreciation, the JEs that take judgment, not just data entry.
“Create the monthly deferred revenue journal entry, one line per customer, based on this export from QuickBooks.”
The JE built with a separate line for each customer, held for review instead of posted, with a flag on the accounts where the schedule didn’t tie to the prior month.
“This subscription renewed for $3,600 in April, expense it evenly over the next 12 months and show me the entries before you post anything.”
All 12 monthly entries laid out with the vendor name on every line, ready to approve in one pass.
Vendor & expense analysis.
Ad hoc spreadsheet work that used to mean an afternoon in a pivot table.
“Run a vendor scan for Northwind Freight, check where each vendor is categorized against our chart of accounts and flag anything that looks wrong.”
Six vendors flagged as booked to the wrong account, mostly software subscriptions sitting in Office Supplies, with a one-line fix recommended for each and nothing changed yet.
“Split this $4,200 conference bill between two employees’ cards and summarize what each owes.”
A clean two-column breakdown by cardholder, reconciled to the receipt, ready to attach to the expense report.
Payroll reconciliation & classification.
Matching a payroll run to the GL, and catching the miscodes before the client does.
“Reconcile the whole year against this payroll journal, including the loan forgiveness that ran through one pay period.”
A pay-period-by-pay-period walk-through, matched to the GL, with a call-out on the one period where the forgiveness amount needed its own line.
“An employee was miscoded to the CEO’s compensation line last month, find the mapping and fix it going forward.”
The mapping error traced back to a payroll memo, corrected for the current period, with confirmation that no other employees were affected.
Most of what we asked Claude to do wasn’t polished. It was terse, typo’d, and written mid-close, and it worked anyway.
Build the shortcut once, reuse it on every client.
This is where NG Wizard came from, not a shipped feature, a conversation that turned into one.
“I want to run this exact reconciliation every month for every client, turn this conversation into a reusable skill.”
A skill built from the actual back-and-forth, saved once, and used unprompted on every connected client from then on. This is close to how NG Wizard itself started.
“Some clients’ payroll comes from a different platform and the GL accounts differ by client, update the skill to ask clarifying questions instead of guessing.”
The skill adjusted to branch by platform and account structure, so one skill covers every client instead of one per platform.
Emails, memos, and the conversations that follow the numbers.
The close isn’t done until someone can explain it to a client or a partner.
“Draft a reply to this client, the reconciliation ran long and we had to file an extension. Keep it warm but direct.”
A draft that owns the delay, gives a real date, and doesn’t over-apologize, ready to send as written, or edit first.
“Write a short memo to the partner explaining why gross margin moved 8 points this quarter.”
Two paragraphs, plain language, tied straight back to the two accounts driving the swing.
Board decks, investor updates, and buyer diligence.
Grounded in QuickBooks, not reconstructed from memory the night before.
“Pull the P&L and Balance Sheet for the last 3 years into one Excel file for the board deck. No invented numbers, everything should tie back to QuickBooks.”
One workbook, three years side by side, with a note flagging the one account that needed a manual tie-out.
“We need a letter on our letterhead explaining our accounting methods for a buyer’s due diligence request.”
The letter drafted in the firm’s own voice, citing the client’s actual policies, ready for partner sign-off.
Notices, filings, and the research nobody has time for.
Not tax prep, the compliance questions that come up while keeping the books.
“We got a state franchise tax notice. Check it against last year’s filing and tell me if we should have filed.”
The notice compared to the prior return, confirmation that a filing was missed, and the fastest path to resolve it.
“What’s the deadline and filing method for the California ES–100?”
Answered in two sentences, with a link to file directly, no research detour needed.
Beyond the books.
Not every use case is a journal entry. A few of ours aren’t.
“Check my Asana and my inbox and build one printable list for today, grouped by client, with anything I’ve already handled taken off.”
One list instead of two dashboards and an inbox to check separately.
“Write a case study about how our accounting support helped a client, audience is founders and CFOs evaluating outsourced accounting.”
A first draft grounded in what actually happened with that client, ready for us to fact-check and publish.
“We’re adding a controller to this client’s account before they’re hired, prepare a file review and summary I can share, without real dollar figures yet.”
A branded overview built from the actual books, with figures deliberately left out until the hire is confirmed.
“Was March payroll posted yet for Lattimer & Co.?”
A one-line yes or no, checked against QuickBooks in real time, no ticket, no waiting on someone else to look.
None of this posted itself.
Every example above stops at a proposal. Claude drafts the entry, the email, the reconciliation, a person on our team reviews it and decides what actually reaches QuickBooks or a client’s inbox. That’s not a limitation we’re working around. It’s how we’d want it run on our own books.
Bring a real QuickBooks file. See what it asks back.
Book a 30-minute walkthrough with a partner on the call, or start self-serve and try one of these prompts on your own book.