AI just came for your firm dashboard, not just your files
It's 4:30 on a Thursday. A partner stops at your desk and asks how much unbilled WIP is sitting on the Henderson group. You know a number exists. It lives in a dashboard, behind three filters, in a report somebody maybe refreshes monthly. So, you say the honest thing. "I'll get back to you."
Two product launches in early June went straight at that moment. Firm360 and Abacor each shipped Claude connectors that answer plain-language questions about firm data. Not client files. Firm data. WIP, realization, overdue invoices, meeting commitments, open action items.
Most AI coverage in this profession is about doing the work. This is about running the firm. And here's the thing. The line between those two ideas blurred within a single news week.
In this post, you'll learn what launched, why the read-only detail matters more than the demo, and what Canadian firms should ask before anyone connects an AI to practice data.
What actually launched in early June
Two connectors, two days apart. Same idea, different data.
Firm360 turned firm health into a conversation
On June 2, Firm360 launched its Claude Connector. Firm360 is a US practice management platform built by accountants. The connector lets partners and practice leads ask questions in plain English and get answers pulled from live Firm360 data.
It handles the numbers partners actually run the firm on:
- Work-in-progress. A partner can ask "What's our current WIP across open engagements?" and get the figure in seconds.
- Realization, write-ups, and write-downs. How billed amounts compare against time on the clock.
- Overdue invoices and AR. Which clients are sitting past 60 days.
- Client-level profitability. Which relationships quietly lose the firm money.
Four details matter more than the demo:
- It's read-only. Firm360's own announcement is blunt about it. Claude can answer questions about the firm. It can't change anything in the platform.
- It's a limited beta. You need an active Firm360 subscription plus a Claude Pro or Team plan.
- The data stays put. Firm360 states firm data stays inside its platform and isn't used to train the underlying model.
- Setup takes minutes. Nothing to migrate and nothing for IT to build. Remember that last one. It cuts both ways.
Firm360 also frames this as a starting point, not a finished product. Its launch post describes a deliberately narrow scope, a beta cohort shaping the roadmap, and a public date for general availability still to come. Read that as honest. Then read it as a reminder that early numbers deserve early skepticism.
Abacor made meeting history conversational
Abacor is a New York-based AI assistant for accounting firms that records and structures client meetings. It announced its own Claude connector in a June 1 blog post, and the trade press picked it up on June 4.
Once connected, Claude can pull from everything Abacor has captured:
- Past meetings. Summaries, action items, transcripts, decisions made, and risks raised.
- Commitments. Search an entire meeting history for the promise you half remember making.
- Meeting prep. Which upcoming meetings have briefs ready and which don't.
- Open items. What's due this week across every engagement, and who owns it.
Unlike Firm360's beta, Abacor's connector is available now to its existing customers worldwide. Permissions follow your role in Abacor, so Claude only sees what you're already allowed to see. It also works alongside other connectors like Gmail, QuickBooks, Xero, and Microsoft 365 in the same conversation.
These aren't the same product. One is the firm's financial vitals. The other is its working memory. Put them side by side and a pattern shows up.
The quiet shift: AI that answers about the work
For the last couple of years, accounting AI news has been about production. Drafting memos. Tying out statements. Agentic tools that prepare sections of an audit file, like the CaseWare and MNP partnership we've covered here before.
These connectors do something different. They don't prepare anything. They answer questions about capacity, billing health, and open commitments. The work about the work.
Both run on the same plumbing. The Model Context Protocol, or MCP, is an open standard Anthropic released in late 2024 and has since donated to the Linux Foundation. Think of it as a standard plug between a chat window and a software database. Once a vendor builds a connector, the AI can query live data. No exports, and no pasting from a stale PDF report. Accounting tools have been adopting it all year, with QuickBooks, Xero, and Microsoft 365 connectors already in use.
For a senior or a manager, the appeal is obvious. The questions that interrupt review time are rarely deep ones. Where does the file stand. What did we promise this client in March. Who hasn't been billed. Today each of those costs a dashboard safari or an email to whoever owns the report.
Picture a Monday in busy season. Before your first file, you ask which engagements moved over the weekend, which clients still owe documents, and where your team's hours went last week. Three answers, one chat window, no tabs. That's the pitch. And for once, the pitch describes something a working senior would actually use.
But be honest about the limits:
- The answer is only as good as the data. If time entries post late, the WIP figure is wrong. Now it's wrong faster and with more confidence.
- AI can misread clean data too. A fluent answer isn't a verified one. Anything you'll repeat to a partner or a client needs a second look at the source.
- Beta means beta. Firm360 itself describes the launch scope as deliberately narrow, with general availability still ahead.
Treat these tools like a keen junior. Fast and genuinely useful, and nothing goes out under your name without review.
Where insight ends and action begins
Here's the part that should get your attention as a practitioner.
Firm360 drew a hard line. Read-only. Claude can tell you the number, and it cannot touch the number.
Abacor's launch materials step past that line. Among its suggested prompts is one that asks Claude to update journal entries directly in the general ledger based on changes discussed in a client meeting, then produce refreshed financial statements.
That isn't insight. That's action. And it showed up in the same news week as a vendor selling restraint.
CPA Ontario has described this divide in its writing on agentic AI. A generative tool lists your flight options. An agentic tool books the flight. When AI moves from reporting a number to changing a record, the questions change completely:
- Who approved the entry?
- Where does the change sit in the audit trail?
- Would the file survive a practice inspection if a chat prompt posted the adjustment?
So here's a practical stance. Insight tools are a reporting question. Action tools are a controls question. They deserve different checklists, even when they arrive in the same product.
There's an assurance angle too. If your firm performs audits or reviews, CSQM 1 already expects you to manage technological resources as part of your system of quality management. A connector that touches client information, or one that can write to a ledger, belongs in that conversation. Not in a partner's personal experiments.
What this means for Canadian firms
Neither tool may be yours. Firm360 describes itself as serving firms across the United States. Abacor is available worldwide, but it's a meeting tool, not your practice management system.
The pattern still matters here, for two reasons.
First, your stack is next. If your firm runs on CaseWare Cloud, iFirm, or a similar Canadian setup, the question isn't whether this kind of connector reaches your tools. It's when, and whether your firm settles its policy before or after someone plugs one in. Worth raising at your next vendor renewal call.
Second, confidentiality doesn't wait for the tools to mature. Practice management data is soaked in client information. Names, fee arrangements, billing disputes, engagement status. Under the CPA codes of professional conduct, you're required to protect confidential information obtained through professional relationships, and passing it to a third party carries responsibilities. PIPEDA sits behind that for personal information. CPA Ontario has also published pointed questions for members on AI, including how firms ensure third-party generative AI products meet legal, regulatory, and governance requirements.
Now remember the setup detail from earlier. Configuration takes minutes and needs nothing from IT. That's the sales pitch, and it's also the exposure. A partner with a personal Claude login could wire firm data into a chat on a Tuesday afternoon with nobody else in the loop. Write the policy before that Tuesday.
The policy doesn't need to be long. One page covering who may connect AI tools to firm or client data, which tools are approved, what data is off limits, and where questions go. That single page turns a Tuesday afternoon surprise into a request someone can actually evaluate.
Six questions to ask before you connect anything
Bring this list to the next vendor demo, or to the enthusiastic partner who found the setup page:
- Is it read-only? If write access exists, can you disable it at the permission level? Is every write logged?
- Whose account and whose plan? A firm-managed Team plan with admin visibility is a different risk than a partner's personal subscription.
- What does the AI provider do with the data? Get training and retention commitments in writing, not from a sales call.
- Do permissions mirror the source system? Abacor's role-following approach is the right pattern to demand. The AI should never see more than the user can.
- What client information ends up in chat history? Names, fees, and disputes appearing in AI conversations are disclosures. Treat them that way.
- Who verifies before it gets repeated? A number quoted to a client or a bank is your number. Not the AI's.
None of this says don't connect. It says connect the way you'd let a new hire near client data. Scoped, supervised, and documented.
The bottom line
- Firm360 launched a Claude connector on June 2 covering WIP, realization, write-downs, overdue invoices, and client profitability. Limited beta, read-only by design, on a US-focused platform.
- Abacor announced its connector June 1, with coverage on June 4. It makes meeting history, commitments, and action items conversational, and it's live for existing customers now.
- The shift is real. After years of AI that does the work, these tools answer questions about the work.
- Watch the line between insight and action. Read-only access is a reporting question. Write access is a controls question. One vendor drew the line and the other's marketing crossed it in the same week.
- Canadian firms should move first on policy, not tools. Confidentiality obligations apply the moment practice data flows through an AI. Decide who may connect what before a setup wizard decides for you.
Your practice management vendor will pitch you something like this within the year. Now you know what to ask when they do.
New posts land every week at The Adjusting Entries. If this one gave you better questions for the next technology conversation at your firm, come back next week. There's always another entry to adjust.