How to Build an Accountant Website Without Writing Code

Describe the practice in plain language, let an AI builder generate the site, then edit the draft until the wording is yours. On Zugo a single-page accountant site is a quick build of about a minute and a multi-page version with separate service pages takes a few minutes. Trust, not design, is what converts here.

That last point shapes everything below. Nobody chooses an accountant because the hero section is beautiful. They choose because the site answered three questions before they had to ask: are you qualified, do you handle situations like mine, and what happens when I get in touch.

What does an accountant's website actually need to do?

It has one job: turn a stranger's cautious curiosity into a first conversation. Everything on the page either advances that or delays it.

• Credentials, stated plainly. Your qualification, your registration, the years you have practised. This is the single most-read line on an accounting site and it belongs above the fold, not in a footer.
• Who you serve. Sole traders, small limited companies, landlords, contractors, restaurants. Naming your niche loses you the wrong enquiries, which is the point.
• Services with scope. Not "bookkeeping" but "monthly bookkeeping including bank reconciliation and quarterly VAT returns". Vagueness reads as evasion in this profession.
• Pricing posture. Fixed fees, a starting-from number, or an honest "we quote after a call". Any of the three beats silence, which visitors read as expensive.
• One clear next step. A booking link or a short intake form. Not both, and not a phone number alone.

Testimonials help more here than in most sectors, because the service is invisible and the risk feels personal. Two named client quotes with the type of business attached outperform a page of stock badges.

What should go into the prompt?

Name the practice, the client type, the pages, and the tone. The builder fills every gap you leave with a guess, and the guesses are generic by default.

Build a website for a chartered accountant practice serving sole traders
and small limited companies in Manchester.
Pages:
1. Home: qualification and years in practice above the fold, three
   service cards, two client quotes, one call to action.
2. Services: four services, each with what is included and what is not.
3. Pricing: three fixed-fee packages with a from-price, plus a line
   saying complex cases are quoted after a call.
4. About: photo, qualification, registration number, short history.
5. Contact: intake form with name, email, business type, turnover band,
   and what they need help with.
Tone: calm, precise, no jargon, no stock-photo optimism.

The final line does real work. Left to itself, a generator reaches for handshake imagery and phrases like "your trusted partner in financial success". Explicitly refusing that in the prompt saves several rounds of editing.

If starting from a blank field feels wrong, Zugo ships 25 templates and forking the nearest professional-services layout means your first move is replacing content rather than describing structure.

Which pages does a practice actually need?

Fewer than most accountancy sites have. Here is what each page earns its place by doing, and what you can safely postpone.

A five-page build is a multi-page platform: 12 credits for the first three pages plus 3 for each one after, so this list lands at 18 credits before edits. That arithmetic is worth doing before you decide the blog is essential in week one.

How should the intake form work?

An accountant's enquiry form is not a contact form. It is the first minute of a qualifying call, and the fields you choose decide how much of that call you skip.

Ask for business type, approximate turnover band, current bookkeeping setup, and the deadline they are worried about. Four extra fields cost the visitor twenty seconds and save you a discovery email thread. Do not ask for anything you would not read.

The form needs to reach you, which is a connector rather than a design decision. Resend handles the email delivery, so submissions arrive in your inbox instead of disappearing into a rendered page that submits into nothing. That failure is silent and common, and it is the reason to test your own form before publishing. Our contact form guide covers the setup end to end.

If you want enquiries stored rather than just emailed, Supabase gives you a table behind the form, which turns your website into the front end of a simple pipeline. From there, a lightweight CRM is a natural second project.

What does it cost and how long does it take?

Pricing is per action. A single-page site is 6 credits, a multi-page platform is 12 credits for the first three pages plus 3 per page after that, and any edit is 3. Free comes with 5 credits, Pro is $25 a month for 200 credits, and Business is $99 a month.

Time follows the same shape. Generation is about a minute for one page and a few minutes for a platform. The evening goes on edits: rewriting the service descriptions in your own voice, fixing the tone of the pricing page, and getting the intake fields right.

Every build is booted in a sandbox before it reaches you, so a build that failed to open is reported as a failure rather than handed over as a blank page. That lowers the risk of publishing something dead. It does not check that your registration number is correct, and you should.

What should you check before it goes live?

Do this on a phone, because a client checking accountants on a lunch break is not at a desk.

Submit your own intake form and confirm the email arrives. Read the services page out loud and cut any sentence that could describe any accountant anywhere. Verify every regulatory detail: qualification, registration, company number, and the wording of any professional body reference. Check that your pricing page says what happens when a case is complex.

Then do the boring one: search your own name and firm name, and make sure the site's title and description read like a human wrote them. These are cheap to request in the first prompt and irritating to retrofit later.

Finally, check the site against the calendar. An accountancy site is seasonal, and a homepage still promoting last year's filing deadline in the middle of a new season undermines the one quality you are selling. Put the deadline text somewhere you can edit in a single pass.

Where does an AI builder stop for an accounting practice?

Four honest limits, and the first one is the one that matters.

Do not treat a generated form as a secure document portal. Tax documents, identity papers, and bank statements need a system built for handling them, with the compliance posture your professional body expects. A website form is for enquiries, not for a client's P60.

It is a website, not practice management. Deadlines, ledgers, filings, and workflow live in accounting software. A site can link to your portal; it should not try to be one.

Specific business logic takes iteration. A fee calculator with real rules, or an onboarding flow with conditional steps, gets built through several edits rather than one prompt. That works, and it costs edits.

Complex products need a team. Zugo does not replace a development team once the project becomes a real application. When it does, GitHub export hands you an ordinary repository and the project is yours.

For a practice that needs a credible, specific, quickly published site, none of that blocks you. If your work is closer to consulting than compliance, the same method applies with different pages: see how to build an agency website. Otherwise, write the paragraph describing your practice and look at the draft it produces at zugo.dev.