We build AI systems for accounting and CPA firms.
Busy season is a pile of documents, reminders and the same questions from clients. We build AI systems that handle the collecting, chasing and first drafts, and leave the review and the sign-off to your CPAs.
At a glance
- What it is
- AI systems designed, built and installed in the tools your firm already uses, with a reviewer approving anything a client sees.
- What it costs
- $10,000 to $20,000 for the AI readiness assessment, credited in full if you go on. $25,000 to $75,000 to build. Or start with one workflow, $7,500 fixed. Support after launch is optional, $3,000 to $10,000 a month.
- How long
- Two to three weeks for the assessment. Six to twelve weeks to build. About three weeks for one workflow.
- What you keep
- The workflows, prompts, configuration and documentation, in your own accounts.
- Who leads it
- Anthony Clemenza leads every engagement.
- The legal side
- We build systems. The firm decides what client tax information a tool may see, and we build so the system can follow the firm's consent process. What any rule requires of you is for your own counsel.
What we build for an accounting firm.
- 01
Client document collection
Clients upload documents through a portal, each one labeled, and clients who have not sent what you need get a reminder. The documents flow into the software you already prepare returns in.
- 02
Drafts of client messages and memos
First drafts of client emails, research memos and review notes, with the sources shown so a reviewer can check them.
- 03
First-pass bookkeeping
Transactions sorted into categories, with a queue of exceptions that a person clears.
- 04
Answers about status
Clients ask where things stand, after hours or in busy season, and get an answer drawn from your own system. Anything that needs advice goes to a person.
- 05
Proposals and engagement letters
Assembled from your own templates for the advisory work you offer, for a partner to approve.
- 06
Operating controls
Who may use which tool, what client information each can see, a log of what happened, and access that ends when someone leaves.
How the system treats client information.
The firm decides what a tool may see
You choose what client tax information a tool may see, and we build so each tool sees only that. The system is built so it can follow the firm's consent process, and every use is logged.
A reviewer in the loop
Our systems keep a reviewer in the loop and keep source references for every draft.
Made-up data while we test
We test with made-up data, not your clients' returns, until you decide a system is ready for the real thing.
Your CPAs decide every position, sign every return and advise every client. The systems collect, sort and draft. We do not give tax or accounting advice, and we do not tell you what any law or professional rule requires of you. That is for your own counsel.
What we have already built.
These run in companies our principal owns or leads. They show what we can build, not results for anyone else.
A private client portal
Documents, messages, invoices and signing in one place, with each client's records kept apart.
A single ledger traced to the transaction
Bank feeds, invoicing and nightly reconciliation, so a total can be followed back to the entry behind it.
Tamper-evident signing
A document is fingerprinted when it is issued, and a signature is refused if a word has changed.
Questions people ask before they begin.
How much does AI implementation cost for an accounting firm?
$10,000 to $20,000 for the readiness assessment, then $25,000 to $75,000 to build, fixed in writing once the scope is agreed. The assessment is credited in full against the build. If you would rather start with one job, the First Workflow is $7,500 fixed, and that fee is credited against Implementation if you continue within six months.
How can an accounting firm use AI without putting client tax data at risk?
By deciding first what each tool may see, and building so it sees only that. We set up business-account access, keep a log of every use, test with made-up data, and write down where client information goes. No system is risk-free, so we tell you plainly what each tool can reach before you approve it.
Do we need client consent before putting tax return information into an AI tool?
That is a legal question for your own counsel, and we do not answer it. What we build around is your answer: the firm decides what client tax information a tool may see, and the system is built so it can follow your consent process, for example by seeing only the clients who have said yes.
Is it a problem if our AI vendor is outside the United States?
We list, for every tool, where it processes your data, so you know before you choose it. Whether that location matters for your firm is a question for your own counsel. We can build around the answer, for example by choosing tools that fit it or by keeping certain information out of a tool altogether.
What should be in our written information security plan once we use AI?
We do not write the plan. We give you a plain-English description of each system: what it can see, where data goes, who approves what, and how to turn it off. Whoever writes your plan can use that description, and your own counsel can tell you what the plan must contain.
What is an AI readiness assessment for an accounting firm, and what do I get?
It is two to three weeks of study and a written report. We interview you, walk through how your firm really runs day to day, and write down where AI could take work off your people and where it should stay out. You also get a ninety-minute review with Anthony Clemenza. The report is yours to use with us or without us.
What do you build for an accounting firm?
Working systems inside the tools you already use: client document collection and reminders, drafts of client messages and memos with sources, first-pass bookkeeping with an exceptions queue, and answers to client status questions. Each one has a person approving what leaves. You get the systems, the guide and the access, not a subscription.
Which tasks should a CPA firm automate first, and which never?
Start with collecting and chasing documents, drafting client messages, and sorting transactions into a queue a person clears. Never automate signing a return, taking a position for a client, advising on a tax question, or filing anything. Those stay with your CPAs. We build the preparation only.
How do we keep a reviewer accountable for AI-drafted work?
Every draft carries its sources and waits in a review queue. A named reviewer approves, edits or rejects it, and the system records who and when. Nothing is sent or filed by the system itself. The reviewer's name stays on the work, which is where it belongs.
How long does it take to get AI working in your firm?
About three weeks for one workflow, and six to twelve weeks for a full implementation. For a full build, the two-to-three-week assessment comes first. Your part is a few conversations, access to the people and records we need to see, and your approval at each step. We confirm the dates in writing before work starts.
Can we get a system running before busy season?
Tell us your calendar when you apply. One workflow takes about three weeks, so we can build before your busy season starts, or wait until it ends and build without interrupting your people. We would rather start on a quiet week than a deadline week, and we say so up front.
Who owns what you build?
You do. The workflows, prompts, configuration and documentation are yours at handover, in your own accounts, and you can run them without us. Operate, our monthly support, is optional and ends on notice, so leaving us never means losing what we built. Your data stays in your own accounts too.
What happens when the AI is wrong, and who catches it?
A person catches it, at the approval step, before anything reaches a client. We also write down what the system gets wrong in the first weeks and tune it. We cannot promise it never errs, which is exactly why a person approves every output and why the sources are shown with each draft.
What happens after launch, and do we need a monthly plan?
No plan is required. Everything we build is documented and yours to run. If you want someone watching it as your tools and staff change, Operate is $3,000 to $10,000 a month, covers monthly tuning and a quarterly review with Anthony Clemenza, and ends on notice.
Start with an assessment, or with one workflow.
Based in New York and South Florida. We take engagements anywhere; travel outside those areas is billed at cost.
- The Diagnostic
$10,000 to $20,000, two to three weeks
- Implementation
$25,000 to $75,000, six to twelve weeks
- Operate
$3,000 to $10,000 a month, ongoing
- The First Workflow
$7,500 fixed, about three weeks