Fixed quote after a free call

CRM automation for accounting firms, from first enquiry to signed engagement

Most accounting firms track prospects in an inbox, a spreadsheet and the partner's memory. We connect your website forms, referral emails, calls and booking links to one CRM pipeline, either HubSpot or the CRM features inside Karbon, TaxDome or Canopy, follow up on unsigned proposals automatically and push every newly signed client straight into your practice system with the right services and jobs. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why accounting firms lose prospects between enquiry and engagement

Prospective clients reach an accounting firm in bursts: a run of new sole proprietors in January, landlords before a filing date, companies after a bad year with their last accountant. Each enquiry lands wherever the sender chose, and the partner who took the call is often the only person who knows it exists.

Proposals then go out from a separate tool, and nobody is responsible for chasing the unsigned ones. When a client finally signs, someone re-types their details into the practice system, the ledger and the portal, and the services they bought are set up by hand. It is slow at the top of the funnel and error-prone at the bottom.

What we build

What our CRM for accounting firms includes

One pipeline for every source

Website forms, referral emails, booking-link appointments and calls flow into one pipeline with the service the prospect asked about.

Stages that match how firms sell

Enquiry, discovery call, proposal sent, proposal signed, onboarding, active client, with an owner on every record.

Proposal chasing

Polite reminders on unsigned proposals from Ignition or your proposal tool, and a task for the partner when one goes quiet.

Signed means set up

An accepted proposal creates or updates the client in Karbon, TaxDome or Canopy, with work items for the services agreed.

Referral tracking

Which referrers, partners and campaigns bring clients who sign, recorded on every deal.

Pipeline reporting

A weekly email with new enquiries, proposals out, value signed and stalled deals by service line.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Enquiry captured

    A form, email, booking or call creates or updates a contact and deal in the CRM.

  2. 02 Automated

    Discovery booked

    The prospect gets an acknowledgement and a link to book a discovery call.

  3. 03 Automated

    Proposal chased

    Unsigned proposals trigger reminders and a partner task after a set number of days.

  4. 04 Staff review

    Partner follows up

    The partner or manager calls, adjusts scope and records the outcome.

  5. 05 Accountant or partner decides

    Engagement accepted

    Whether to take the client on, and on what terms, is decided by the partner.

How it behaves

How the accounting firm CRM behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the prospect sees

  • A prompt acknowledgement and a discovery-call link
  • A proposal from the partner and one or two polite reminders
  • A welcome and onboarding request once they sign

What staff see

  • One pipeline board with an owner on every deal
  • Tasks when a proposal stalls
  • New clients already set up in the practice system

What the automation does

  • Captures and de-duplicates enquiries
  • Watches proposals and chases with stop rules
  • Creates clients and jobs when an engagement is accepted

Edge cases and fallbacks

Existing client asks about a new service
Matched to their record and added as a new deal, not a duplicate client.
Proposal accepted with changed scope
The partner confirms the services before jobs are created.
Prospect asks for a tax opinion by email
Routed to the partner; no automated reply touches the question.
CRM or practice system API outage
Events are queued and retried, and the admin team gets an alert.

Architecture

A CRM pipeline for an accounting firm at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Website forms Service enquiries Referrals Email and partners Booking link Discovery calls n8n Capture and match CRM pipeline HubSpot or PM tool Proposal tool Ignition or similar Partner Calls and scope Practice system Client and jobs
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Enquiries arrive from website forms, referral emails and discovery-call bookings.
  2. 2 n8n matches each one to an existing contact or creates a new deal with the service requested.
  3. 3 Proposals go out from your proposal tool and are chased; the partner handles scope and pricing conversations.
  4. 4 When a proposal is accepted, the client and their jobs are created in the practice management system.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

CRM for accounting firms: pipeline to signed engagement project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Enquiry sources, proposal tool, practice system, service lines and how deals are tracked now.

  2. 02

    Design

    2 to 3 days

    Pipeline stages, field mapping, chase timing, duplicate rules and the hand-off into the practice system.

  3. 03

    Build

    1 to 2 weeks

    Source capture, CRM pipeline, proposal triggers, client creation and the weekly report.

  4. 04

    Shadow run

    About 1 week

    New enquiries flow into the pipeline while the team keeps its current list, and we compare both.

  5. 05

    Launch

    1 to 2 days

    Switch over and walk partners and admin staff through the board.

  6. 06

    Support

    Ongoing

    New service lines, stage changes and report tweaks.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n HubSpot CRM API or the CRM inside Karbon, TaxDome or Canopy Ignition (Zapier triggers on accepted proposals) Karbon API and webhooks Calendly API v2 Gmail or Microsoft 365

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Sources, stages, proposal triggers and field mapping.

    $200 – $400

  • Build

    Capture, matching, chase rules and client creation.

    $500 – $1,300

  • Integrations

    CRM, proposal tool, practice system and calendar.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with your current list.

    $100 – $250

  • Launch and training

    Switch-over and partner walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM, proposal tool and n8n subscriptions are billed to you directly. A two-way link with the practice system can add a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM and proposal tool: Each vendor's own plan (HubSpot, Karbon, TaxDome, Canopy, Ignition or what you use).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

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
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: tax return information has its own rules

Section 7216 rules limit how tax preparers use and disclose tax return information; consents must be signed, dated and name the purpose and recipients. We keep return data out of marketing workflows unless the firm has that consent.

Source: www.law.cornell.edu

UK: marketing emails and texts

PECR requires consent, or the soft opt-in conditions, for marketing by electronic mail, with a simple way to refuse in every message.

Source: www.legislation.gov.uk

EU and UK: CRM vendors are processors

Article 28 GDPR requires a binding contract with any processor, covering its instructions, confidentiality and security. We check the CRM's data processing terms before go-live.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 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. 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. 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. 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

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

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

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

CRM for accounting firms: pipeline to signed engagement questions, answered.

It depends on what you already run. Karbon, TaxDome and Canopy include client and pipeline features that suit firms living in those tools; HubSpot is flexible with a documented API if you want marketing and sales in one place. We help you choose, and we can work with a CRM you already pay for.

If enquiries come from more than one place, or proposals go unsigned without anyone noticing, yes. A small firm usually needs one pipeline, a chase rule and a clean hand-off into the practice system, which fits a single workflow.

Karbon has an API for contacts and work items, with webhooks. TaxDome's supported route today is its Zapier integration, which can create, update or find contacts. We confirm which fields and job templates your account allows before quoting.

Yes. Ignition publishes Zapier triggers for accepted proposals, which we use to start the client set-up. Where your proposal tool has a different route, we confirm it per project.

No. A proposal chase is two or three messages at most, stops as soon as the proposal is signed or declined, and respects opt-outs.

Enquiries by source and service line, time to first reply, proposals sent and signed, value signed and how long deals sit in each stage.

Free 20-minute call

Want this 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.

Book a free 20-minute call