A candid, anonymized conversation with a top-ranked and fast-growing accounting firm
Last week, we announced Aiwyn Tax’s integration with Claude.
The response was immediate.
We heard from a number of forward-thinking firms — teams already deep in AI exploration, asking thoughtful, practical questions about what this actually means for their platforms, their professionals, and their clients.
One of those conversations stood out.
It was honest, nuanced, and exactly the kind of discussion we think more firms should be having right now.
We’re sharing it here (lightly edited and anonymized with that firm’s permission) in the spirit of building openly — and because we suspect these are the same questions many firms are working through.
What was your first reaction when you saw the Aiwyn + Claude announcement?
Firm:
“When I saw the product you released, it made me excited. There’s a lot of enthusiasm with Claude — I use it constantly. I have it connected to my Microsoft 365, HubSpot, whatever I can let it have its hands on.”
Aiwyn:
That’s the energy we’re seeing from forward-leaning firms. Not “should we pay attention to this?” — but “how fast can we move?”
What about your team?
Firm:
“Our team’s instinct is to put AI to work on real client data immediately. That tells us the tools are compelling, and it also tells us governance has to be in place first.”
Aiwyn:
That’s the real tension: the enthusiasm is genuine, and so is the governance gap.
The firms winning here aren’t ignoring one side of that equation — they’re taking both seriously at the same time.
How are you thinking about AI labs like Claude — the same way you’d evaluate Microsoft or Google as vendors?
Firm:
“We have the standard DPA that comes with our Teams agreement. But we haven’t crossed that bridge for our professionals yet. We’re stepping into it carefully.”
Aiwyn:
This came up a few times.
There’s 20 years of muscle memory around trusting platforms like Microsoft 365 or Google Workspace with firm data. AI tools are earning that trust from scratch.
The agreements feel less settled. The data flows feel less predictable.
That instinct isn’t wrong — it’s exactly right.
What’s the difference between going directly to Claude or ChatGPT versus using something like Aiwyn?
Firm:
“Someone would naively say: it’s just a wrapper on top of AI. What’s the point of paying these guys?”
Aiwyn:
Fair question. The right question, really.
First, data security and compliance — buttoned up up and down the stack. Table stakes.
Second, the math. Tax isn’t a domain where “mostly right” is acceptable. AI is probabilistic. Our calculation engine is not. Claude provides the intelligence. Aiwyn provides the deterministic calculations.
Third, the licenses. We have 50 state e-file licenses. If a return is ever going to get filed, you need a licensed e-file provider in the stack. That’s us.
Fourth, the end-to-end Aiwyn solution suite. Under our umbrella we have everything — native Aiwyn solutions and open integrations (to legacy systems and agentic newcomers) — that a modern firm needs to thrive amidst the shifting landscape in tax, and across the entirety of the accounting profession.
Firm:
“The way you framed it gives me a much better appreciation. People will often overlook that it’s not just going back and forth through Claude’s API — it’s going there, through you, through your calculations, and back. And I think that’s something people just miss.”
What concern, if any, do you have about AI tools?
Firm:
“Could a nefarious agent go out, pull in some code, start pinging your system and pulling massive amounts of data? I haven’t heard of examples of this actually happening — but that’s the what-if everyone’s talking about.”
Aiwyn:
AI tools doing web search, reading documents, executing actions — those are new surfaces.
But this is the new version of an old problem.
Just as engineers learned to code defensively against SQL injection and input attacks, building secure AI workflows requires the same discipline applied to new threat models.
It’s on software companies in this space — including us — to get that right.
Where does this land strategically for a firm like yours?
Firm:
“We’re building an AI adoption framework that scales across the platform. The firms that move deliberately, with the right agreements in place, will capture the most value.”
Aiwyn:
That’s exactly where we’re seeing things go.
Today’s Connector is intentionally an exploration layer — anonymized data, scenario testing, building intuition without operational risk.
What comes next is production: authenticated, governed, firm-controlled environments with real client data.
That’s where this gets really powerful — and we’re actively building toward it.
What’s your read on the broader moment in the profession?
Firm:
“The profession needed disruption. It’s been fascinating to watch. You’re innovators — and this is a week where it definitely feels that way.”
Aiwyn:
We’ll take it.
Six years in, building for six more — and then some.
The accounting profession is at an inflection point, and we intend to be part of what comes next.
What’s next
Aiwyn Tax is now available as an official Connector inside Claude.
Phase 1 is live today — built for exploration, scenario testing, and building internal intuition with anonymized data. Phase 2 is in development.
If you want to have a similar conversation — or get involved in shaping what comes next — we’d love to connect.
Join us to learn more
- Aiwyn Sessions (April 23) → Monthly co-founder Q&A focused on tax. Register here!
- Aiwyn Ahead (May 14) → Our annual roadmap and vision event. Register here!
- Office Hours → 1:1 time with our Tax team. Schedule here!
- Book a Demo → See how Aiwyn works for your firm. Schedule here!
