Implementation Guide: Draft responses to irs notices and client tax planning memos

Hardware Procurement

Software Procurement

Prerequisites

• Microsoft 365 Business Premium (or E3/E5) deployed for all users with Entra ID and MFA enforced — this is a hard prerequisite for Copilot, DLP, and identity security
• Stable business-grade internet: minimum 50 Mbps symmetric, under 50ms latency to Azure/AWS US regions; 100 Mbps+ recommended for 10+ concurrent users
• Managed firewall with outbound HTTPS (port 443) allowed to AI platform endpoints (taxgpt.com, cpapilot.com, api.openai.com, copilot.microsoft.com) and DNS filtering to block consumer AI chatbots (chat.openai.com personal tier, gemini.google.com, claude.ai) to prevent inadvertent client data leakage
• Existing tax preparation software in use (Lacerte, UltraTax CS, Drake Tax, CCH Axcess, or equivalent) — the AI platform operates alongside, not inside, these systems
• Current Written Information Security Plan (WISP) on file — if none exists, WISP creation must be scoped as a separate pre-project engagement (8–16 additional hours)
• Firm has designated an internal AI Champion — a senior CPA or EA who will own prompt template development, quality review standards, and serve as the primary point of contact for AI-related workflow decisions
• IRC §7216 taxpayer consent forms updated to include disclosure to AI platform vendors as auxiliary service providers — must be reviewed and approved by the firm's legal counsel or tax compliance officer before any client data is uploaded to AI platforms
• Domain admin credentials or delegated admin access to the firm's Microsoft 365 tenant
• All workstations running Windows 11 Pro (22H2 or later) with latest cumulative updates applied
• Practice management platform (TaxDome, Karbon, Canopy, or equivalent) deployed and actively used — if not in place, TaxDome deployment should be scoped as a parallel workstream

Installation Steps

...

Step 1: Conduct WISP Audit and AI Vendor Risk Assessment

Before any technology deployment, update the firm's Written Information Security Plan (WISP) to address AI platform usage. This is required by the FTC Safeguards Rule and is the legal foundation for the entire project. Review the existing WISP, add a section on AI vendor usage, document the data flow from client documents through the AI platform and back, complete a vendor risk assessment for TaxGPT (or CPA Pilot), and verify SOC 2 Type II certification for all AI vendors that will process client data.

Step 2: Configure Network Security and DNS Filtering

Harden the network to ensure client tax data only flows to approved AI platforms. Configure the firewall to allow outbound HTTPS to approved AI service domains and implement DNS filtering to block consumer AI chatbot sites where staff might inadvertently paste client data.

# Firewall allow-list (add to outbound HTTPS rules):
# TaxGPT: *.taxgpt.com
# CPA Pilot: *.cpapilot.com
# Microsoft Copilot: *.copilot.microsoft.com, *.microsoft.com, *.office.com
# Zapier: *.zapier.com
# OpenAI API (if used via TaxGPT backend): *.openai.com

# DNS block-list (add to content filtering policy):
# Consumer ChatGPT: chat.openai.com (block personal tier, allow API)
# Google Gemini: gemini.google.com, bard.google.com
# Claude consumer: claude.ai
# Perplexity: perplexity.ai
# Other consumer AI: poe.com, you.com, character.ai

# taxgpt.com should resolve; chat.openai.com should be blocked or redirected

nslookup taxgpt.com
nslookup chat.openai.com

Step 3: Deploy and Configure Microsoft 365 Copilot

Enable Microsoft 365 Copilot for all licensed users. Before enabling, configure SharePoint sensitivity labels and DLP policies to prevent Copilot from surfacing or summarizing client tax data inappropriately. Copilot respects existing M365 permissions, so this step also includes a permissions audit to ensure oversharing is corrected.

Step 3a: Audit SharePoint/OneDrive Permissions

Step 3b: Create Sensitivity Labels in Microsoft Purview

Step 3c: Create DLP Policy

Step 3d: Enable Copilot Licenses

Connect-MgGraph -Scopes 'User.ReadWrite.All','Organization.Read.All'
$copilotSku = Get-MgSubscribedSku | Where-Object {$_.SkuPartNumber -eq 'Microsoft_365_Copilot'}
$users = Get-MgUser -Filter "department eq 'Tax'" -All
foreach ($user in $users) {
    Set-MgUserLicense -UserId $user.Id -AddLicenses @{SkuId = $copilotSku.SkuId} -RemoveLicenses @()
    Write-Host "Assigned Copilot to $($user.DisplayName)"
}

Step 3e: Configure Copilot Settings

Step 4: Deploy TaxGPT (Primary Tax AI Platform)

Create the firm's TaxGPT organization account, configure user seats, set up client profiles, and establish the standard workflow for IRS notice response drafting and tax planning memo generation. If the firm chose CPA Pilot instead, follow the vendor's onboarding process (similar steps but different UI).

Client received CP2000 for TY2023 proposing $5,000 additional income from 1099-NEC not reported. Client did report this income on Schedule C line 1.

• Generate response and review for correct IRS notice type identification
• Verify proper citations (IRC sections, Treasury Regulations)
• Check for professional tone and formatting
• Validate accuracy of legal arguments

Step 5: Deploy and Configure Document Scanning Infrastructure

Install ScanSnap iX2500 scanners at each desk and the fi-8170 workgroup scanner at the central processing station. Configure scan profiles optimized for IRS notices and tax documents, and set up automatic routing to SharePoint or TaxDome. ``` # Step 5a: Install ScanSnap Home on each workstation # Download from: https://www.pfu-us.ricoh.com/scansnap/downloads/ # Run installer: ScanSnapHomeSetup.exe # Connect iX2500 via USB-C for initial setup, then configure Wi-Fi # Step 5b: Create scan profile...

Step 6: Build Zapier Automation Workflows

Create Zapier workflows (Zaps) that connect the document scanning pipeline, AI platform, practice management system, and email into an integrated IRS notice response workflow. These automations reduce manual handoffs and ensure every notice follows the firm's review process.

Zap 1: New IRS Notice → Create Task in TaxDome

• Trigger: New file in SharePoint folder 'IRS Notices/2025'
• Action 1: Create task in TaxDome — Task name: 'IRS Notice Response - [filename]', Assignee: [Firm's AI Champion or Senior CPA], Due date: +15 days from trigger (standard IRS response window is 30 days), Status: 'Awaiting AI Draft', Attach: Link to scanned document
• Action 2: Send Slack/Teams notification — Channel: #irs-notices, Message: 'New IRS notice received: [filename]. Task created for [assignee]. Due: [date]'

Zap 2: AI Draft Complete → Notify Reviewer

• Trigger: Tag applied in TaxDome: 'AI Draft Ready' (manually applied after generating draft)
• Action 1: Send email to assigned reviewer — Subject: 'AI Draft Ready for Review: [task name]', Body: 'An AI-generated draft response has been created for [client name]. Please review within 48 hours. Link: [TaxDome task URL]'
• Action 2: Update task status to 'Pending Review'

Zap 3: Approved Response → Client Portal Upload

• Trigger: Tag applied in TaxDome: 'Approved for Client'
• Action 1: Copy approved document to client's TaxDome portal folder
• Action 2: Send client notification via TaxDome
• Action 3: Update task status to 'Sent to Client'

• Configure at: https://zapier.com/app/editor
• Required connections: SharePoint (Microsoft), TaxDome, Slack/Teams, Gmail/Outlook

Step 7: Create Prompt Templates for IRS Notice Types

Build a library of optimized prompt templates for the most common IRS notice types. These templates ensure consistent, high-quality AI output and reduce the skill barrier for junior staff. Templates are stored in TaxGPT (if it supports custom templates) or in a shared SharePoint document library for copy-paste use.

• CP2000 (Proposed Changes / Underreporter) Response
• CP14 (Balance Due) Response
• CP503/CP504 (Collection Notice) Response
• Generic IRS Notice Response (catch-all)
• Tax Planning Memo - Annual Year-End
• Tax Planning Memo - Entity Selection Analysis
• Tax Planning Memo - Estimated Tax Payment Strategy

• System context (role, compliance guardrails)
• Input fields (client details, notice details, facts)
• Output format specification
• Citation requirements
• Disclaimer language

Step 8: Configure Security and Compliance Monitoring

Deploy endpoint protection, configure audit logging for AI platform usage, and set up compliance monitoring to ensure all AI-generated content follows the mandatory human review workflow. This step fulfills WISP requirements for monitoring and incident detection.

Step 8a: Deploy SentinelOne on all workstations

msiexec /i SentinelOneInstaller_x64.msi /qn SITE_TOKEN="[your-site-token]"

Step 8b: Enable M365 Unified Audit Log

Connect-ExchangeOnline -UserPrincipalName admin@firmname.com
Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true

Step 8c: Create Copilot Usage Alert in Microsoft Purview

Step 8d: Set Up AI Platform Access Logging

Step 8e: Create Conditional Access Policy for AI Platforms

Step 9: Pilot Deployment with Select Users

Roll out the complete solution to 2–3 senior tax professionals for a 2-week pilot period. During the pilot, these users process real IRS notices and create actual tax planning memos using the AI-assisted workflow. Collect detailed feedback on AI output quality, workflow efficiency, and any compliance concerns.

Pilot User Selection Criteria

• 1 senior CPA/EA (10+ years experience, can judge AI accuracy)
• 1 mid-level CPA (5-10 years, primary daily user profile)
• 1 junior staff (1-3 years, tests whether templates are usable without deep tax knowledge)

Pilot Metrics to Track

Create a shared Excel/Teams tracker to monitor the following metrics:

Pilot Process

• Day 1-3: Training session (2 hours) + supervised first use with MSP present
• Day 4-10: Independent use, daily check-in (15 min standup)
• Day 11-14: Collect metrics, conduct feedback interviews

Success Criteria

Step 10: Full Firm Rollout and Knowledge Transfer

Based on pilot results, refine prompt templates, update workflow documentation, and deploy the solution to all remaining firm users. Conduct a firm-wide training session and establish the ongoing support model.

Step 10a: Apply Pilot Learnings

Step 10b: Deploy to Remaining Users

Step 10c: Firm-Wide Training Session (2–3 Hours)

Step 10d: Distribute Documentation

Share via SharePoint and pin in Teams:

• AI Usage Policy (1-page summary of dos and don'ts)
• Prompt Template Library (SharePoint link)
• IRS Notice Response Workflow Diagram
• Quick Reference Card (laminated, desk-side)
• Escalation contacts (MSP helpdesk, AI Champion, vendor support)

Custom AI Components

CP2000 IRS Notice Response Prompt Template

Type: prompt A structured prompt template for generating professional responses to IRS CP2000 (Proposed Changes / Underreporter) notices. CP2000 is the most common notice type and proposes additional tax when reported income doesn't match IRS records from W-2s, 1099s, and other information returns. This template produces a complete response letter with proper formatting, legal citations, and supporting arguments. Implementation: ``` # CP2000 IRS Notice Response Prompt Template # Versi...

Tax Planning Memo Prompt Template

Type: prompt A structured prompt template for generating comprehensive client tax planning memoranda. Used for year-end tax planning, entity selection analysis, retirement contribution optimization, and other forward-looking advisory engagements. Produces a professional memo with analysis, recommendations, quantified tax savings estimates, and appropriate caveats.

Implementation:

# paste into TaxGPT, CPA Pilot, or M365 Copilot in Word

# Tax Planning Memo Prompt Template
# Version: 1.0
# Last Updated: 2025-07-15
# Usage: Copy into TaxGPT or CPA Pilot, or use with M365 Copilot in Word

---SYSTEM CONTEXT---
You are a senior tax advisor assistant helping a CPA draft a client tax planning memorandum. You must:
1. Provide specific, actionable recommendations tailored to the client's situation.
2. Cite relevant IRC sections, Treasury Regulations, and Revenue Rulings.
3. Quantify estimated tax savings where possible (use ranges if exact amounts are uncertain).
4. Present recommendations in order of impact (highest savings first).
5. Include implementation deadlines and action items.
6. Note any risks, limitations, or conditions that could affect the recommendations.
7. NEVER guarantee specific tax outcomes — use phrases like 'may reduce,' 'could result in,' 'estimated savings of approximately.'
8. Flag any areas requiring further analysis with [FURTHER ANALYSIS NEEDED: description].
9. Include standard disclaimer language.

---INPUT FIELDS---

Client Name: [NAME]
Entity Type: [Individual / S-Corp / C-Corp / Partnership / Trust / Multiple entities]
Filing Status (if individual): [Single / MFJ / MFS / HoH / QSS]
Estimated AGI/Taxable Income: $[AMOUNT] (current year projection)
Prior Year AGI/Taxable Income: $[AMOUNT]
State(s) of Residence/Operation: [STATE(S)]
Industry/Occupation: [DESCRIPTION]

Planning Scenario:
[Describe the planning context, e.g., 'Year-end tax planning for 2025. Client is a dentist operating as sole proprietor, considering S-Corp election. AGI projected at $450,000. Spouse W-2 income $85,000. Two children ages 8 and 11. Client maxing 401(k) through spouse employer. No current retirement plan for dental practice.']

Specific Questions from Client:
[List any specific questions, e.g., '1. Should I convert to S-Corp? 2. What retirement plan should I set up? 3. Can I deduct the new dental equipment? 4. Any strategies to reduce self-employment tax?']

Key Financial Data:
- Gross Revenue: $[AMOUNT]
- Net Business Income: $[AMOUNT]
- W-2 Income (if any): $[AMOUNT]
- Investment Income: $[AMOUNT]
- Mortgage Interest: $[AMOUNT]
- State/Local Taxes Paid: $[AMOUNT]
- Charitable Contributions: $[AMOUNT]
- Retirement Contributions (YTD): $[AMOUNT]
- Estimated Tax Payments (YTD): $[AMOUNT]
- Other Relevant Items: [LIST]

---OUTPUT FORMAT---

Generate a professional tax planning memorandum with the following structure:

# MEMORANDUM

**TO:** [Client Name]
**FROM:** [Firm Name] (leave as placeholder)
**DATE:** [Current Date]
**RE:** [Tax Year] Tax Planning Analysis
**PRIVILEGED AND CONFIDENTIAL**

## Executive Summary
- 2-3 paragraph overview of key findings and total estimated tax savings
- Highlight the top 3 recommendations

## Current Tax Position
- Summary of projected current-year tax liability
- Comparison to prior year
- Identify key drivers of tax liability

## Recommendations

For each recommendation:
### Recommendation [#]: [Title]
- **Strategy:** Clear explanation of the strategy
- **Legal Authority:** IRC sections, regulations, and relevant guidance
- **Estimated Tax Savings:** $[range] (federal) + $[range] (state if applicable)
- **Implementation Steps:** Numbered action items
- **Deadline:** When action must be taken
- **Risks/Limitations:** Any caveats or conditions
- **Priority:** High / Medium / Low

## Summary of Estimated Savings
| Recommendation | Federal Savings | State Savings | Total |
|---|---|---|---|
| [Each recommendation] | $X | $X | $X |
| **TOTAL** | **$X** | **$X** | **$X** |

## Next Steps
- Numbered action items with deadlines and responsible parties

## Disclaimer
This memorandum is based on current tax law and the information provided as of [date]. Tax laws are subject to change, and individual results may vary. This analysis does not constitute legal advice. Please consult with our firm before implementing any of these recommendations. [Additional firm-standard disclaimer language.]

[DRAFT — REQUIRES REVIEW BY SIGNING PRACTITIONER BEFORE DELIVERY TO CLIENT]

---END TEMPLATE---

CP14 Balance Due Response Prompt Template

Type: prompt Prompt template for responding to IRS CP14 notices (Balance Due on Return). CP14 is the first notice a taxpayer receives when there is an unpaid balance. The response template handles scenarios including payment plan requests, penalty abatement arguments (first-time abatement or reasonable cause), and disputes of the assessed amount.

Implementation

# CP14 Balance Due Response Prompt Template
# Version: 1.0

---SYSTEM CONTEXT---
You are a senior tax professional assistant drafting a response to an IRS CP14 (Balance Due) notice. You must:
1. Identify whether the balance is correct, partially correct, or incorrect.
2. If the client disputes the amount, explain the specific discrepancy with supporting evidence.
3. If the client cannot pay in full, recommend and draft the appropriate resolution (payment plan via Form 9465, Currently Not Collectible status, or Offer in Compromise if applicable).
4. If penalties are assessed, evaluate eligibility for First Time Penalty Abatement (FTA) under IRM 20.1.1.3.6.1 or Reasonable Cause abatement under IRC §6651(a).
5. Cite IRC sections, IRM provisions, and Treasury Regulations accurately.
6. Maintain professional tone. NEVER fabricate citations.

---INPUT FIELDS---

Client Name: [FULL LEGAL NAME]
SSN (last 4): [XXXX]
Notice Date: [MM/DD/YYYY]
Tax Year: [YYYY]
Total Amount Due per Notice: $[AMOUNT]
  - Tax: $[AMOUNT]
  - Failure to Pay Penalty (§6651(a)(2)): $[AMOUNT]
  - Failure to File Penalty (§6651(a)(1)): $[AMOUNT]
  - Interest (§6601): $[AMOUNT]
Response Deadline: [MM/DD/YYYY]

Client's Situation:
[Choose one or describe:]
- [ ] Balance is CORRECT and client will pay in full
- [ ] Balance is CORRECT but client needs a payment plan
- [ ] Balance is INCORRECT — describe discrepancy
- [ ] Client requests penalty abatement

Penalty Abatement Basis (if applicable):
[Choose one:]
- [ ] First Time Abatement (FTA): Client has clean compliance history (filed timely and paid timely) for the 3 tax years preceding the penalty year
- [ ] Reasonable Cause: Describe circumstances (serious illness, natural disaster, death of family member, reliance on tax professional, fire/casualty destroying records, etc.)

Payment Plan Details (if applicable):
- Amount client can pay monthly: $[AMOUNT]
- Requested plan duration: [MONTHS] months
- Client's current financial situation summary: [BRIEF DESCRIPTION]

---OUTPUT FORMAT---

Generate a formal letter to the IRS with:
1. Standard header block (client info, notice info, tax year)
2. Clear statement of the response type (payment, dispute, abatement request, or combination)
3. If disputing: detailed explanation with document references
4. If requesting FTA: explicit reference to IRM 20.1.1.3.6.1 criteria and statement of compliance history
5. If requesting reasonable cause: narrative matching the factors in Treas. Reg. §301.6651-1(c) and IRM 20.1.1.3.2
6. If requesting payment plan: reference to IRC §6159 and include Form 9465 preparation notes
7. Enclosure list
8. Professional closing

[DRAFT — REQUIRES REVIEW BY SIGNING PRACTITIONER]

---END TEMPLATE---

IRS Notice Intake and AI Drafting Workflow

Type: workflow End-to-end workflow definition for processing an IRS notice from receipt through AI-assisted draft generation, human review, client approval, and final submission to the IRS. This workflow enforces the mandatory human review required by Circular 230 and ensures §7216 compliance at each data handling step. Designed for implementation in TaxDome or Karbon practice management platforms. Implementation: ``` # IRS Notice Response Workflow # Platform: TaxDome (or Karbon — ada...

Section 7216 Consent Verification Check

Type: integration A pre-flight compliance check that runs before any client data is submitted to an AI platform. Verifies that a valid IRC §7216 consent form is on file for the specific client, preventing unauthorized disclosure of taxpayer information. Implemented as a Zapier workflow or manual checklist integrated into the TaxDome task template.

TaxDome Configuration

Custom Fields (add to Client profile)

Task Template Checklist (add to 'IRS Notice Response' template — Stage 2)

Zapier Validation Zap

• Zap Name: '7216 Consent Gate'
• Trigger: TaxDome task moves to Stage 3 ('AI Draft Generation')
• Filter: Check if TaxDome client custom field '7216_AI_Consent_Status' equals 'Not Obtained' OR 'Declined' OR 'Expired'

Action if filter matches (consent not valid)

Subject: 'COMPLIANCE BLOCK: §7216 Consent Required for [Client Name]'
Body: 'The IRS Notice Response task for [Client Name] cannot proceed to AI drafting because a valid IRC §7216 consent form is not on file. Current status: [consent_status]. Please obtain signed consent before using any AI platform to process this client\'s tax data. This is a legal requirement — violations carry criminal penalties of up to $1,000 and 1 year imprisonment per offense.'

Action if filter does NOT match (consent is valid)

Sample §7216 Consent Form Language

# must be reviewed by firm's tax attorney before use

CONSENT FOR DISCLOSURE OF TAX RETURN INFORMATION
Pursuant to Internal Revenue Code Section 7216

I, [Taxpayer Name], SSN: XXX-XX-[Last 4], hereby authorize [Firm Name] to disclose my tax return information to the following third-party service provider(s) for the purpose of providing tax preparation and advisory services:

Service Provider: [AI Platform Name, e.g., TaxGPT Inc.]
Purpose: AI-assisted drafting of IRS correspondence, tax research, and tax planning analysis
Data Disclosed: Tax return data, IRS notice information, financial information as needed for the specific service requested
Data Handling: [AI Platform] processes data in encrypted cloud environment, SOC 2 Type II certified, data is not used for model training, data is deleted after [retention period per vendor DPA]

This consent is valid for tax years: [20XX] through [20XX]
This consent expires on: [DATE — typically 1 year from signing]

I understand that I am not required to sign this consent, and that my tax preparation services will not be affected if I decline. If I decline, [Firm Name] will prepare my documents using traditional (non-AI-assisted) methods.

I may revoke this consent at any time by providing written notice to [Firm Name].

Taxpayer Signature: _____________________ Date: __________
Spouse Signature (if MFJ): _____________________ Date: __________

AI Output Quality Scoring Agent

Type: agent A structured quality scoring system that reviewers use to rate every AI-generated document. Scores are tracked over time to identify prompt templates that need refinement, measure ROI, and demonstrate due diligence compliance. Implemented as a Microsoft Forms survey linked to a Power BI dashboard or simple Excel tracker.

Implementation

Microsoft Forms Survey Configuration

Form Name: 'AI Draft Quality Review' — Create at https://forms.office.com

SharePoint List Configuration

Form responses automatically flow to a SharePoint list. Create the following calculated columns:

'Overall Quality Score'     = Average of questions 6–9
'Time Savings (minutes)'    = Q11 - Q10
'Time Savings (%)'          = (Q11 - Q10) / Q11 * 100
'Hallucination Flag'        = IF(Q13='Yes', TRUE, FALSE)

Monthly Dashboard Metrics (Excel or Power BI)

Review Cadence

• Weekly: AI Champion reviews scores, flags any documents rated ≤ 2
• Monthly: MSP and firm management review dashboard
• Quarterly: Refine prompt templates based on lowest-scoring categories

Testing & Validation

Client Handoff

The client handoff should be conducted as a 3-hour in-person or virtual session with the firm's managing partner, AI Champion, and all staff who will use the system. Cover the following topics in order: 1. System Overview (30 min): Walk through the complete architecture — scanners, TaxGPT/CPA Pilot, M365 Copilot, Zapier automations, and TaxDome workflow. Show the data flow diagram from the WISP update. Explain what happens to client data at each step and where it is stored. **2. Compliance...

Maintenance

Monthly Maintenance Tasks (2-4 MSP hours/month): - Review AI platform usage metrics (login frequency, documents generated per user, credit consumption for CPA Pilot) - Review quality scoring dashboard — flag any templates with average scores below 3.5/5.0 for prompt refinement - Check TaxGPT/CPA Pilot for platform updates, new features, or changed terms of service - Review M365 Copilot usage reports in the admin center — identify underutilized licenses for reallocation or additional training...

Alternatives

CPA Pilot as Primary Platform (Budget Option)

Replace TaxGPT ($1,200–$1,600/user/year) with CPA Pilot ($19–$49/user/month, credit-based) as the primary AI drafting platform. CPA Pilot covers IRS notice responses, tax research, memo drafting, and client communications at a fraction of the cost. The credit-based model means the firm only pays for what it uses. Tradeoffs: Cost savings of 50–75% on AI platform licensing, making this ideal for firms with fewer than 10 professionals or those with lower notice volume. Tradeoff: CPA Pilot may ...

Blue J for Complex Tax Research (Enterprise Option)

Add or replace TaxGPT with Blue J (~$1,500/seat/year) for firms that need advanced tax outcome prediction and deep research capabilities beyond standard IRS notice response drafting. Blue J excels at analyzing ambiguous tax positions and predicting likely IRS or court outcomes based on case law analysis. Tradeoffs: Higher cost ($1,500/seat/year with custom enterprise pricing) and more complex onboarding, but significantly stronger for firms handling tax controversy, complex entity structuri...

On-Premise LLM Deployment (Maximum Privacy Option)

Instead of cloud-based AI platforms, deploy a local LLM server running open-source models (e.g., Llama 3.1 70B or Mistral Large) via Ollama on a dedicated workstation with an NVIDIA RTX 4090 GPU. All client data stays on-premises — no §7216 consent needed for AI platform disclosure because no third-party receives the data.

Microsoft 365 Copilot Only (Minimal Change Option)

Skip the tax-specific AI platform entirely and rely solely on Microsoft 365 Copilot ($21–$30/user/month) embedded in Word, Outlook, and Excel. Use Copilot to draft IRS notice responses and tax planning memos from detailed prompts, leveraging the firm's existing document templates and prior work stored in SharePoint as context.

Canopy Tax Resolution Module (Workflow-Focused Option)

Instead of a general AI drafting platform, deploy Canopy's Tax Resolution module ($50/user/month on top of $45/user/month base) which provides structured IRS notice management, automatic IRS transcript pulling, built-in letter templates for common notice types, and workflow tracking. Less AI-powered but more structured and compliance-focused.