Case Study
Case Study: Accounting Firm Onboarding & Tax Season
We built a connected set of automations for a multi-partner accounting firm serving individuals, landlords and small companies: a CRM pipeline that hands signed clients into the practice system, onboarding with engagement letters and due diligence evidence, tax document collection that chases itself, bank feed triage for the bookkeeping team and a weekly deadline view that shows what is blocked and why. Partners now see problems weeks earlier, and preparers spend tax season preparing.
- Firm type
- Multi-partner accounting firm: tax, bookkeeping and payroll
- Team involved
- Partners, client managers, bookkeepers, firm administrator
- Systems connected
- Practice management system, QuickBooks Online and Xero, client portal, e-signature, CRM, n8n
- Delivery
- Scrum, 1-week sprints, about 8 weeks to full launch
The challenge
Where the practice started
Prospects reached the firm by web form, referral email and phone, and proposals went out from a separate tool. Nobody owned the unsigned ones, and new clients were re-typed into three systems.
Onboarding evidence arrived in email threads. Engagement letters, identity documents and prior-accountant details were rarely in one place when work began.
Every filing season began with the same document requests sent by hand, and prepared returns waited on single missing items that nobody had chased.
Bookkeepers looked up past coding line by line, and managers found blocked jobs only when they opened them in the final weeks.
Goals
What the project had to change
- Every enquiry sits in one pipeline, and a signed proposal sets up the client automatically.
- Every new client has a complete onboarding file before work starts.
- Document requests and reminders run on schedule for every job.
- Bookkeepers start from suggested coding with reasons, and clients get one query list.
- Managers see each week which deadlines are blocked and why.
What we built
What we built, as one connected system.
CRM pipeline
We connected web forms, referral emails and booking links to one pipeline, chased unsigned proposals, and turned accepted proposals into clients and jobs in the practice system.
Service detailsClient onboarding
Each accepted proposal now sends the right engagement letter for e-signature, requests identity and ownership details through the portal and assembles one file with gaps listed for the partner.
Service detailsDocument collection
Request lists are built from last year's file, uploads are matched to items and reminders escalate toward each internal deadline until the job is ready.
Service detailsBookkeeping triage
Uncategorised lines get a suggested category with a reason, unknowns become one client query, and month-end exceptions are summarised for review.
Service detailsDeadline tracking
Every deadline is linked to the information it depends on, and managers get a weekly due, ready and blocked view with escalations.
Service detailsArchitecture
How the firm's workflows connect
- Input
- Logic and services
- AI step
- Data
- Output
- People
How it flows
- 1 Enquiries, jobs from the practice system and ledger data feed one n8n instance.
- 2 Five workflows update the CRM, send portal requests and e-signature envelopes, and use AI steps for upload matching and coding suggestions.
- 3 Staff work the files, queries and suggestions; partners accept clients and approve anything that leaves the firm.
- 4 Every step is logged, and managers get a weekly status view.
How it behaves
How the system behaves day to day
What clients see
- A quick reply and a call booking link when they enquire
- An engagement letter to sign and one clear onboarding list
- A personalised document list with a secure upload link
- One tidy query list instead of scattered emails
What staff see
- One pipeline board and one onboarding file per client
- Jobs moving to ready as documents arrive
- Suggested coding to accept or change
- A weekly blocked-jobs view
What the automation does
- Captures, requests, matches and chases on schedule
- Applies opt-outs and the firm's data rules everywhere
- Logs every step and alerts the administrator on failure
Edge cases and fallbacks
- A prospect asks a tax question by email
- Routed to a partner; no automated reply discusses it.
- Ownership details differ from the public register
- Flagged in the onboarding file for the partner.
- A ledger connection expires
- That client is skipped and the bookkeeper is asked to reconnect.
- The practice system is unreachable overnight
- The weekly view is marked stale rather than shown as current.
- n8n or the portal has an outage
- Reminders pause and resume, staff work as before, and the administrator gets an alert.
Integrations
What we connected
QuickBooks Online
Accounting ledgerUncategorised transactions, customers, invoices and balances for triage and reporting.
Intuit's QuickBooks Online Accounting API with OAuth 2.0 and webhooks.
Xero
Accounting ledgerContacts, invoices, bank transactions and reports for triage and exception summaries.
Xero Accounting API; Xero does not offer reconciling bank statement lines through its public API, so reconciliation stays in Xero.
Karbon
Practice managementContacts, work items, client requests and status for onboarding, chasing and deadlines.
Karbon API and webhooks; API access depends on your Karbon plan, confirmed per project.
Ignition
Proposals and engagementAccepted proposals start client set-up and onboarding.
Ignition's Zapier triggers; API access depends on Ignition plan, confirmed per project.
SmartVault
Document storage and portalUploads, folders and document requests for collection and portals.
SmartVault REST API with OAuth 2.0.
DocuSign
E-signatureEngagement letters and approvals sent and filed on completion.
DocuSign eSignature REST API and Connect webhooks.
Companies House
UK public company registerCompany details for onboarding comparisons.
Companies House public data API.
HubSpot
CRMContacts, deals, pipeline stages and tasks.
HubSpot's CRM REST API.
Slack and Microsoft Teams
Staff alertsEscalations, blocked jobs and failure alerts.
Incoming webhooks and APIs.
n8n
Automation platformRuns the workflows, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 8 weeks, then support
-
01
Discovery
Week 1
We sat with the administrator, bookkeepers and a client manager, mapped enquiry-to-filing steps, agreed data rules and confirmed vendor agreements against the firm's security plan.
-
02
Design and access
Week 2
Pipeline stages, onboarding checklists per client type, document lists per job type, API access to the practice system and ledgers.
-
03
Sprint 1: CRM pipeline
Week 3
Built and shadow-ran the pipeline and proposal hand-off; demo and sign-off.
-
04
Sprint 2: onboarding
Week 4
The pipeline went live. Built engagement letters, evidence requests and the onboarding file.
-
05
Sprint 3: documents
Week 5
Onboarding went live for new clients. Built request lists, upload matching and reminders on a pilot group.
-
06
Sprint 4: bookkeeping
Week 6
Document collection went live for one job type. Built coding suggestions and exception summaries; bookkeepers compared both ways.
-
07
Sprint 5: deadlines
Week 7
Bookkeeping triage went live for agreed clients. Built dependency rules and the weekly view.
-
08
UAT and handover
Week 8
The team ran user acceptance testing on every workflow, then we switched everything on and handed over the run book.
-
09
Support
Ongoing
Weekly check-ins through the first filing peak, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Captures enquiries and chases unsigned proposals
- Creates clients and jobs from accepted proposals
- Sends engagement letters and onboarding requests
- Builds document lists, matches uploads and sends reminders
- Suggests coding with reasons and groups client queries
- Shows blocked deadlines with reasons each week
The team does
- Chase incomplete onboarding files personally when needed
- Check flagged uploads and call stuck clients
- Confirm or change every coding suggestion
- Prioritise blocked jobs and reassign work
Accountant or partner decides
- Accept or decline every new client and set the risk rating
- Make every tax and accounting judgement
- Approve returns and accounts before filing
- Decide extensions and approve every submission
Compliance handled
Privacy, consent and safety, built in.
No tax advice from automation
Nothing technical is answered automatically; tax questions route to a partner.
Written information security plan
Every vendor in the build was added to the firm's security plan, as the IRS reminds preparers the FTC requires.
Source: www.irs.govSafeguards Rule controls
Encryption in transit and at rest, multi-factor authentication and service provider oversight were built in from the start.
Source: www.law.cornell.eduTax return information
Return data stays out of marketing workflows; Section 7216 consent rules were reviewed with the firm.
Source: www.law.cornell.eduUK clients: due diligence evidence
For UK engagements, onboarding gathers the evidence regulation 28 describes; the partner makes the risk decision.
Source: www.legislation.gov.ukProcessor contracts
AI and automation vendors are covered by processor terms for any EU or UK personal data.
Source: gdpr-info.euOutcomes
What changed for the practice
- Every enquiry now sits in one pipeline with an owner, and signed clients appear in the practice system without re-typing.
- New clients arrive with one onboarding file instead of an email thread.
- Document requests and reminders go out on schedule for every job, without staff remembering to send them.
- Bookkeepers start from suggested coding with reasons, and clients receive one query list.
- Managers see blocked deadlines weeks earlier, with the reason attached.
What we track
The measures the practice watches.
Proposal conversion
Proposals sent, signed and days to signature by service line.
Onboarding completeness
Share of new clients with a complete file before work starts.
Jobs waiting on clients
Average days a job is blocked by missing documents.
Bookkeeping time
Time per client to clear the bank feed and share of suggestions accepted unchanged.
On-time preparation
Jobs ready before the internal date, by month.
Cost estimate
What a project like this costs
-
Discovery and design
Process mapping, data rules, checklists and the backlog for all five workflows.
$900 – $1,900
-
Onboarding module
Engagement letters, evidence requests and the onboarding file.
$800 – $2,000
-
Document collection module
Request lists, upload matching and reminders.
$800 – $2,000
-
Bookkeeping triage module
Coding suggestions, client queries and exception summaries.
$700 – $1,900
-
Deadline tracking module
Dependency rules, weekly view and escalations.
$600 – $1,600
-
CRM pipeline module
Source capture, proposal chasing and client set-up.
$700 – $1,600
-
Integrations
Practice system, ledgers, portal, e-signature and CRM.
$200 – $500
-
Testing, UAT and launch
QA, user acceptance testing, launch and training.
$300 – $1,000
-
Total project estimate
$5,000 – $12,500
Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every firm gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Free self-hosted Community edition on the firm's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- Vendor plans: Practice system, CRM, portal, e-signature and ledger subscriptions at each vendor's own pricing.
- AI usage: Pay-per-use model fees, usually small at firm volumes.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, if text reminders are used (Twilio's published US pricing).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Email Deliverability Check FreeMX, SPF, DKIM, DMARC, MTA-STS and BIMI with ready DNS fixes
- Website Security Scan FreeSSL, security headers, cookies and exposed file checks
- Website Monitoring Scheduled re-scans, score emails and 5-minute uptime alerts
- White-Label Reports PDF reports with your logo, name and color, and shareable links
Free website tools for practices
Services in this case study
CRM for accounting firms: pipeline to signed engagement
Every enquiry from your website, referrals, calls and partners in one CRM pipeline, with proposals, follow-ups and a hand-off into your practice system the moment an engagement is signed.
From $1,000 · About 4 weeks Details
Client onboarding, engagement letters & due diligence
Turn a signed proposal into a complete client file: engagement letter for e-signature, identity and ownership evidence, prior-accountant details and a risk summary ready for the partner.
From $1,000 · About 4 to 5 weeks Details
Tax document collection & automated chasing
Personalised request lists built from last year's file, a secure upload link, uploads matched to each item and reminders that chase on schedule until the job is ready to prepare.
From $1,000 · About 3 to 4 weeks Details
Bookkeeping automation & bank reconciliation triage
Unreconciled bank lines grouped and given a suggested category with a reason, missing receipts turned into one client query, and month-end exceptions summarised for review.
From $1,000 · About 4 to 5 weeks Details
Accounting workflow automation & deadline tracking
Every client obligation by jurisdiction linked to the information it depends on, a weekly view of what is due, ready and blocked, and escalations before a date is at risk.
From $1,000 · About 4 weeks Details
Accountant or partner decides
-
AI for Accountants: Automating the Admin Around MTD, Bookkeeping and AMLAutomation · 8 min read
-
Tax Season 2027: How Accountants Can Automate Document ChasingAutomation · 11 min read
-
Client Document Collection Automation for Accounting FirmsAutomation · 8 min read
-
Email Fraud Protection for Accountants: Invoice Fraud, HMRC Phishing and DMARCEmail Deliverability · 10 min read
-
AI Receptionist for Small Business: Costs, Uses and Safe SetupAutomation · 10 min read
Free 20-minute call
Want this built for your accountant?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- IRS: What tax preparers need to know about a data security plan
- 16 CFR 314.4 (FTC Safeguards Rule elements)
- 26 CFR 301.7216-3 (consent to use or disclose tax return information)
- 15 USC 7001 (E-SIGN Act)
- UK Money Laundering Regulations 2017, regulation 28
- GOV.UK: Making Tax Digital for Income Tax eligibility
- 47 CFR 64.1200 (TCPA rules)
- UK PECR regulation 22
- GDPR Article 28
- EU AI Act, Article 50
- Karbon Developer Center
- TaxDome: Integration with Zapier
- TaxDome integrations overview
- Canopy API
- CPA Practice Advisor: Canopy unveils external API platform
- Zapier: Ignition integrations
- SmartVault developer portal
- Intuit: QuickBooks Online webhooks
- Xero feedback: Reconcile via the API (Xero response)
- Dext help: Data health API
- DocuSign developers: adding a Connect webhook to envelopes
- Companies House developer hub
- Calendly developer: getting started
- HubSpot API overview
- Twilio US SMS pricing
- n8n pricing
- Google autocomplete phrasing checked for keywords (crm for accounting firms, accounting client onboarding, tax document collection, bookkeeping automation, ai receptionist for accountants, client portal for accountants)