Web Case Study
Marketing Site for a Modern Remote Accounting Practice
Nuxt front end on a headless CMS
Scroll to move through the full page
Accountaire on desktop and mobile
Overview
A marketing site for a remote finance team serving ambitious businesses. It is built in Nuxt, with Strapi as the content layer, so the practice can publish without a developer.
Accountaire is a remote finance practice. It sells to businesses that compare firms carefully before calling one. The site has to carry that credibility, and it has to keep moving. A practice publishing services, guides and updates continuously cannot wait on a developer for every change.
The challenge
A professional services practice publishes services, guides and updates continuously. That stalls when every content change has to queue behind a developer.
Marketing sites for professional services fail slowly. The launch looks good, then the content freezes, because every edit is a ticket in somebody's queue. Six months later the site describes a practice that no longer exists. The team has quietly gone back to sending PDFs.
What we built
Built a Nuxt front end paired with Strapi as a headless content layer. The team edits and ships content directly, and the public site stays fast and server rendered.
We separated the content from its presentation. The front end renders on the server, so pages arrive fast and readable to crawlers. A headless content layer holds the material in a structured model the practice edits directly. Adding a service or publishing a guide became an editorial task rather than a deployment.
- Server rendered front end for speed and crawlability
- Structured content model covering services, guides and updates
- Editorial workflow that does not require a developer
- Service pages with clear routes into booking a call
- Responsive layouts checked at phone width first
Results
Accountaire does not carry a measured before-and-after metric. The outcome instead: Built a Nuxt front end paired with Strapi as a headless content layer. The team edits and ships content directly, and the public site stays fast and server rendered.
Technology used
We are technology agnostic by policy. This is a record of what Accountaire required, not a house standard.
Services behind this project
Accountaire drew on 3 services from our catalogue, matched to what a web project like this actually needed.
Web development
Browser based products and sites built as systems, not as decorated pages. The structure, speed and maintainability survive past launch.
Explore web development →Custom software development
Bespoke systems for teams with a very specific requirement. An off the shelf product would force them to change how they work.
Explore custom software →IT consulting
Independent advice on architecture, tooling, and sequencing. For organisations deciding what to build, what to buy, and what to leave alone.
Explore IT consulting →This work sits inside our Brand solution, for teams facing the same problem.
Related case studies
3 more case studies from work we have delivered, starting with other web projects.
The full portfolio holds every case study we publish, grouped by discipline.
Accountaire FAQs
Because the practice publishes continuously. Separating content from presentation means the team edits and ships without a developer in the loop. That is the difference between a site that stays current and one that ages.
It does. Pages arrive already rendered, so they load quickly for a prospect comparing firms. They are readable to crawlers without relying on the browser to assemble them first.
The practice does. The content model is structured, so editors work inside sensible boundaries. They add and update material without the ability to break the build.
Planning something like Accountaire?
Tell us what you are trying to build. We will tell you plainly what it would take, including the parts that would not be worth doing.
Last updated 3 September 2026
Contact Us
Lahore, Pakistan · London, U.K · Austin TX, U.S · Toronto, Canada