A launch where the mail mattered
more than the website.

Everglades Bookkeeping is a Florida bookkeeping practice run by Kristian Barnett, a certified QuickBooks ProAdvisor. It keeps books CPA-ready year round for marketing agency owners, freelancers and solo operators, and AI and automation studios.

Everglades Bookkeeping · Florida · service area

The offer is deliberately narrow: monthly bookkeeping, cleanup and catch-up work, and QuickBooks management, on flat monthly pricing rather than hourly billing.

Conversion Web Design

Visit evergladesbookkeeping.com

01 The brief

The domain was already doing a job

This was not an empty domain. It was running a GoDaddy Website Builder site, and the same domain carried live Microsoft 365 email, the practice’s actual inbox, and the address clients send financial documents to.

That inverts the risk of a normal launch. A website that goes down for an hour is an inconvenience. Mail that stops arriving at a bookkeeper mid-season is a business problem, and it is the kind of failure a rebuild causes quietly and discovers late.

02 What we built

Six decisions that shaped the build.

A static site with no build step

Twenty-eight flat files, no framework and no page builder. There is nothing in the stack that can expire, need patching, or stop rendering because a plugin updated.

Mail records moved before anything else

Every existing DNS record was recreated on the new nameservers and checked against the original zone first. The web records changed only after the mail records were verified in place, so the inbox never depended on the migration going right.

The mail CNAMEs left unproxied

An automated DNS import defaults every record to proxied, which breaks Outlook autodiscover and Teams lookups. Those records were set back to DNS-only by hand, a detail that only shows up as a client complaint days later.

A contact form that fails honestly

The form posts to a third-party endpoint and falls back to a plain mailto link if the request fails, rather than showing a success message for a message nobody got.

Crawler access checked at the edge, not just in robots.txt

The site allows answer-engine and AI crawlers explicitly. A hosting-level setting was overriding that and blocking them before robots.txt was ever read, so it was turned off and the block verified as lifted.

Nothing loaded from anyone else’s servers

Self-hosted fonts, no analytics, no tracking pixels, no external scripts. For a practice that handles client financial records, that is a claim worth being able to make and worth being able to prove.

03 Why we made those calls

Decisions worth explaining

Security posture was written down before it was published. The site describes specific controls, and each claim was put to the client to confirm rather than asserted on his behalf, describing a control that does not exist turns a gap into a misrepresentation.

Strict transport security was added only after HTTPS was confirmed working on both the apex and www. It is a one-way door: browsers that have seen it refuse plain HTTP for a year, so shipping it early would have been a trap rather than a hardening step.

On results. The site is live at evergladesbookkeeping.com and mail moved without an interruption. We are publishing no traffic, ranking or client-acquisition figures for this engagement, it was a build and a migration, and we do not publish numbers we have not independently measured.

We would rather publish a case study with no numbers than one with numbers we cannot stand behind. If you want figures from a prospective agency, ask how they were measured and over what window, the answer is usually more revealing than the figure.

04 More work