Development Agency
Contact Sign in Get a project quote

Service

Accountant website development

For sole practitioners, bookkeepers and small firms who want a website that takes enquiries by business type, collects documents from prospects securely, books discovery calls into the right diary and keeps a deadline calendar the firm maintains itself, designed around how the practice actually signs up a client.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A sole-practitioner accountant with around ninety clients has a five-page brochure site built years ago.

  • The contact form sends an email with a name and a message, so every enquiry starts with the same three questions by reply: what kind of business are you, roughly what turnover, and what do you need done.
  • Prospects who want to send last year’s accounts attach them to that email, which is the one place the practitioner would rather they did not.
  • Discovery calls are arranged by a chain of messages, then forgotten when the prospect does not confirm.

Where it gets harder

The service pages say “accounts, tax and bookkeeping” without stating what an engagement includes, so fee conversations begin from different assumptions on each side.

  • A deadline list the practitioner wrote for clients two years ago is still live and nobody is sure which dates on it are current.
  • Guides sit as PDF attachments on a page that was never organised, and the practitioner’s professional body membership is mentioned in a footer nobody reads.
  • The site brings in work, but every enquiry costs an hour of administration before anyone knows whether it is a fit.

Scope of the service

What the build covers

A custom accountant website build normally covers the front door of the practice and the first steps of onboarding. Service pages carry a structured engagement scope: what is included, what is not and what the client is expected to provide, written by the firm and shown consistently on every service. A fee enquiry form asks the questions the practitioner would otherwise ask by email, including business type, turnover band, number of employees and the services wanted, and routes the result to the right person with the answers already attached. Secure document upload lets a prospect send accounts, bank statements or a previous adviser’s letter into a private area rather than an inbox, with the firm notified and the files held with access logging. A discovery call booking step offers slots from the practitioner’s diary and confirms by email. A deadline calendar is content the firm maintains: dated entries with a description and a reminder opt-in for clients, shown as a list and feed. A resources library holds guides, checklists and templates organised by topic. Qualifications and body memberships are displayed from a maintained record, not hard-coded text.

We work through the practice with you first: which services are offered and what each engagement includes, how enquiries are qualified today, whether prospects send documents before the first call, who takes discovery calls and from which diary, which deadlines the firm wants to publish and how guides are currently kept. Each becomes a named workflow stage in the scope document.

Deliberately out of scope

  • The practice management system itself, which the accounting practice service covers
  • Tax filing and submissions to any authority, which remain with the firm and its filing software
  • Any form of financial or tax advice, which the site never gives. Deadline entries are the firm’s own content and the firm is responsible for keeping them current

When the scope grows

Scoping scenario

A two-partner firm with a separate bookkeeping brand wants one site with two service lines, an enquiry form whose questions change by line, document upload that lands in a different folder per partner, and discovery calls booked into whichever partner handles that business type. The routing rules by business type make this a custom build, and the scope document says so plainly.

Deliverables

What you receive

  • Discovery notes from mapping how an enquiry becomes a client in your practice
  • A written scope document naming each stage from enquiry to onboarding, the form questions, the routing rules and what is left out
  • Designs of the service page, the fee enquiry form, the upload area and the booking step on phone and desktop
  • The build, deployed to your hosting or ours, with content entered for every service and guide you supply
  • Migration of existing guides, deadline entries and any enquiry history worth keeping
  • Training for the practitioner and administrator on editing services, deadlines and guides
  • Handover material and full ownership of the source code and your content

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to your current site, your service list, your diary tool and the guides and deadline list you already publish.

    Project stage: Onboarding

  2. Planning

    Discovery with the practitioner and whoever handles enquiries; the enquiry questions, routing rules, upload handling and deadline content are written into the scope document.

    Project stage: Planning

  3. Design

    Service pages, the enquiry form and the upload step designed for a prospect on a phone; the editing screens designed for the administrator at a desk.

    Project stage: Design

  4. Development

    Built in layers: services and content first, then the enquiry form and routing, then secure upload, then booking, deadlines and the library.

    Project stage: Development

  5. Client review

    The practice runs test enquiries, uploads and bookings from the devices prospects use and tells us where the questions or routing do not match how it qualifies work.

    Project stage: Client review

  6. Revisions

    Changes from the review are made and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    Content entered and proofread by the firm, redirects from the old site mapped, upload storage and notifications tested, launch checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The practice takes enquiries, documents and discovery calls through the new site; hosting and maintenance continue under their own agreement if taken.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Diary and calendar platforms for discovery call slots and confirmations
  • Practice management and CRM systems that receive qualified enquiries
  • Secure document storage the firm already uses, so uploads land where client files live
  • Email providers for enquiry notifications, confirmations and deadline reminders
  • E-signature providers for engagement letters once a proposal is accepted offline
  • Identity verification providers, as a record of the result and date, where onboarding starts on the site
  • Analytics and consent tooling configured to UK data protection practice

How we would approach it

Worked example

Concept demo

A two-partner firm with a separate bookkeeping brand

The situation

A firm with two partners and a bookkeeping brand run under a different name wants a single site that presents both lines, an enquiry form whose questions change depending on whether the prospect wants year-end work or monthly bookkeeping, uploads that land in a different secure folder for each partner, and discovery calls offered from whichever partner’s diary handles that business type.

Why it is a custom build

The custom route is needed because routing by business type across two diaries and two storage destinations goes beyond the single practitioner and single diary the package assumes.

The scope we would propose

  • A service-line attribute on every page and form, conditional question groups on the enquiry form, per-line upload destinations with separate notifications
  • A booking step that reads availability from two diaries and chooses by the business type answered
  • One deadline calendar shared by both brands with entries tagged by audience

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of service lines, brands or partners presented on one site
  • Depth of the enquiry form and whether questions and routing change by business type
  • Secure upload requirements, including storage destination, retention and access logging
  • Diary platforms to connect for discovery call booking and whether more than one diary is involved
  • Volume of guides, templates and deadline entries to migrate and organise
  • Practice management or CRM systems that should receive enquiries
  • Hosting choice: your own hosting or ours

Start from a package

Accountant website package

A practice website with engagement-scope service pages, a fee enquiry form by business type, secure prospect upload, discovery call booking, a firm-maintained deadline calendar and a guides library for sole practitioners and bookkeepers.

Custom build
View the package

FAQ

Frequently asked questions

How do you decide whether we need a custom build or the package?

During discovery we compare how your practice takes on clients against the accountant website package. If one service line, one enquiry form, one diary and one upload destination cover your practice, we quote for the package. Routing by business type, several partners or brands, or enquiries that must land in a specific practice system point to the custom route.

Does the site give tax or financial advice to visitors?

No. Service pages describe what your engagements include, guides are content you write and own, and the deadline calendar lists dates you maintain. Nothing on the site calculates, files or advises; those remain the responsibility of the practice and its clients.

Can prospects send us documents safely before we have signed them up?

Yes. The upload area stores files in a private location with access logging, notifies the practice and never sends the files by email. Retention rules for prospects who do not become clients are set by you and applied by the system.

Will the deadline calendar keep itself up to date?

No. Entries are content the firm enters and maintains, and the site shows what you have entered with the date you last reviewed it. We build the editing screens and reminder opt-in; the firm is responsible for what the dates say.

Who owns the site afterwards?

You do. The source code, the content and the enquiry records are handed over at delivery. Hosting and maintenance are optional and separately agreed, and you can move the site to another provider.

Get a project quote for accountant website software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences