A client portal for accountants and a firm website that brings in the right clients
We build an accounting firm website that explains your services and fees clearly and loads fast on phones, and where your current portal falls short, a branded client portal or portal front end that connects to your document store, e-signature and practice system. Every form feeds the CRM and onboarding workflows. Projects typically cost $6,000 to $15,000 and take six to ten weeks.
The problem
Why accounting firm websites and portals lose clients
Prospective clients compare firms on their phones. A slow site with no clear services, no sense of fees and no simple way to book a call sends them to the next result. Many firm sites were built years ago and nobody is sure what they still say.
Existing clients, meanwhile, juggle a portal log-in, an e-signature email and a payment link from three different vendors. A portal that gathers those in one branded place, with strong log-in security, makes the firm easier to work with and keeps documents out of email.
What we build
What our client portal for accountants includes
Service and fee pages
Clear pages for each service line and client type, with fee guidance you choose to publish.
Booking and enquiry forms
Discovery-call booking and enquiry forms that feed the CRM pipeline.
Branded portal front end
One place for uploads, documents to sign, requests and invoices, connected to your existing tools.
Strong log-in security
Multi-factor authentication, encrypted transfer and storage, and role-based access.
Local and service SEO basics
AccountingService schema, location pages, fast pages and a technical audit before launch.
Hooks for the workflows
Portal uploads and forms feed onboarding, document collection and deadline tracking.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Client finds you
A prospect finds the firm through search or a referral.
-
02
Automated
Clear answers
Service and fee pages answer the common questions before they call.
-
03
Automated
Book or log in
Prospects book a call; clients log in to upload, sign or pay.
-
04
Staff review
Staff respond
Staff confirm bookings and keep pages and portal requests current.
-
05
Accountant or partner decides
Content sign-off
Technical content on the site is approved by a partner before publishing.
How it behaves
How the website and portal behave
What the client sees
- A fast site with clear services and a booking link
- One branded portal for uploads, signatures and invoices
- A secure log-in with a second factor
What staff see
- Bookings and uploads arriving in the right workflows
- Simple screens to update pages and requests
What the automation does
- Routes forms and uploads into workflows
- Keeps schema and sitemap current
Edge cases and fallbacks
- Client loses their second factor
- A staff-verified reset process, never by email alone.
- Document store unavailable
- The portal shows a status message and queues uploads safely.
- Old URLs from the previous site
- Redirected to matching pages so links and rankings carry over.
Architecture
An accounting firm website and client portal at a glance.
- Input
- Logic and services
- Output
- Data
- People
How it flows
- 1 Prospects arrive from search and referrals on a fast, clear firm website.
- 2 They book a discovery call; existing clients log in to the portal with multi-factor authentication.
- 3 Bookings, uploads and signatures feed the firm's workflows.
- 4 Documents land in the firm's document store and practice system, and staff keep requests current.
Project planner
How the project runs, phase by phase.
Client portal & accounting firm website project plan
Typical time to launch: about 8 weeks, then support
-
01
Discovery
About 1 week
Audit of the current site and portal, service lines, fee approach and security requirements.
-
02
Content and design
About 2 weeks
Page plan, wording with partners, portal screens and your brand.
-
03
Build
2 to 4 weeks
Site, forms, portal front end, MFA, integrations and schema.
-
04
Test
About 1 week
Security headers, MFA, uploads, speed, accessibility and redirects.
-
05
Launch
2 to 3 days
Go live, submit sitemap, migrate portal users in stages.
-
06
Support
Ongoing
Optional monthly care for updates, security patches and new pages.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and audit
Current site, portal, security needs and service lines.
$600 – $1,200
-
Content and design
Page plan, wording with partners and portal screens.
$1,500 – $3,500
-
Build
Site, forms, portal front end, MFA and schema.
$2,500 – $6,800
-
Integrations
Document store, e-signature, payments and workflows.
$800 – $2,000
-
Testing and launch
Security, speed, accessibility, redirects and launch.
$600 – $1,500
-
Total project estimate
$6,000 – $15,000
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. A website alone sits at the lower end; a portal front end connected to several systems sits higher. Hosting and vendor plans are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Hosting and domain: Billed by your hosting provider and registrar.
- Portal and document vendors: Each vendor's own plan.
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
Privacy and consent
Rules we design for, with the sources.
US: encryption and MFA
The Safeguards Rule requires encrypting customer information in transit and at rest and multi-factor authentication for anyone accessing information systems, so the portal is built to it.
Source: www.law.cornell.eduUS: written security plan
The portal and its vendors go into the firm's written information security plan, which the IRS reminds return preparers is required.
Source: www.irs.govEU: AI disclosure if you add a chat
If the site adds an AI assistant, Article 50 of the EU AI Act requires telling people they are interacting with AI from 2 August 2026.
Source: artificialintelligenceact.euFree tools
Try these first, free.
Guides to read first
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.
FAQ
Client portal & accounting firm website questions, answered.
Often a better website plus the portal built into your practice software is enough. We build a custom portal front end only when clients are juggling several tools or your current portal cannot do what you need.
Multi-factor authentication, encryption in transit and at rest, role-based access, activity logs and vendors your security plan covers. We test all of it before launch.
SmartVault has a documented REST API, Canopy has a newer API, and TaxDome's supported route is Zapier. The exact depth is confirmed per project.
Many prospects look for them, and fee guidance with clear notes on what affects price can help them call. What you publish is your decision.
Yes. Services, fees, team and office details are editable without a developer.
Discovery calls booked from the site, portal adoption, documents received by portal rather than email, and Search Console impressions for service pages.
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.
More for accountants
All servicesCRM 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