Why does the platform matter for a professional-services site?

Because speed and reliability are trust signals in a category where trust is the product. A slow, awkward site undermines a claim of competence before anyone reads a word, and the platform decides how much effort speed costs.

What does the framework actually do for us?

It renders pages ahead of time so they arrive as fast files, handles images and code splitting sensibly by default, and keeps the site's structure legible to search engines. The point is that the fast option is the default rather than a project.

What does the CDN layer add?

It serves the site from near the visitor, handles encryption and redirects, and gives you a place to block abuse. For a firm, the practical effect is consistent speed regardless of where the visitor is and one place to control the site's edge behaviour.

Do we need a content management system?

Only if several non-technical people need to publish independently. For most firms, where one or two people edit occasionally, a system adds a service to maintain and a failure mode without solving a problem you have.

Less than firms expect: the framework and platform update on a cadence, and a static marketing site has little moving underneath it. What does need an owner is the content, which is where firms actually go stale.

Is this over-engineered for a small firm?

It is the same amount of work as a page-builder site and a faster result, which makes the comparison one of familiarity rather than complexity. The over-engineering risk is real for applications and mostly absent for a marketing site built this way.

What does it cost to run?

Very little at the traffic a professional-services site sees: hosting is inexpensive and the edge layer has a usable free tier. The cost is in building it well once, and the ongoing bill is usually smaller than a subscription page-builder plan.

How does this affect search visibility?

Speed and clean structure both help, and the largest effect is that pages exist as real server-rendered documents rather than something assembled in the browser. That is what search engines and answer engines can read reliably.

What happens if we want to change agencies?

You own the repository, the domain, and the content, so the site moves with you. That is worth checking explicitly, because platform lock-in is the quiet cost of the proprietary builders and it surfaces only when a firm tries to leave.

Can we edit content ourselves?

For text and images, yes, through whatever editing seam is set up. The honest answer is that some changes need a developer, and the question worth asking before the build is which changes you expect to make and whether those are covered.

Is this different for a larger firm?

Larger firms need more editorial workflow and often a real management system, plus governance across regions or practice areas. The platform underneath stays the same; what changes is who can publish and what review they pass through.

What should a firm actually ask a developer?

How fast will pages load on a phone, what can we edit ourselves, who owns the accounts, and what happens if we leave. Four questions, all answerable plainly, and the answers separate a durable build from one you will regret in two years.

Professional Services Next.js Cloudflare

The Platform Under a Fast Professional Services Site: Next.js and Cloudflare in Plain English

Most firm sites are built on plumbing that makes them slow to load and painful to change. The platform choice is why, and it is fixable.

John Cravey with AIFounderJun 17, 20262 min readUpdated Jul 6, 2026

A website is software, and the software it is built on decides how fast it loads, how well it ranks, how safe it is, and how cheaply you can change it. Most professional services firms inherit a platform chosen for the builder's convenience, then live with slow pages and a site nobody wants to touch. You do not need to be technical to make a better choice. You need to know what the choice affects.

Free estimate · 2 minutes

One retained client usually pays for a year of this.

The estimate sketches the version we would build for your practice, at your caseload. Sixty seconds, no opt-in.

#The plain-English version

Two things sit under a modern site. A framework, which is how the pages are built and delivered, and an edge network, which is how those pages reach a visitor anywhere. Get both right and your site loads in well under a second, holds up under traffic, and costs little to update. Get them wrong and every page is a small tax on every visitor, and every change is a quote from a developer.

#The technical version

#Next.js: the framework

Next.js renders pages on the server and ships mostly static, pre-built HTML to the browser, so the visitor sees content immediately instead of waiting for a heavy app to boot. For a content-and-conversion site, which is what a firm site is, that is the right default: fast first paint, clean URLs, schema rendered server-side where AI engines and Google can read it reliably. It is the same framework we build every Frontend Horizon site on.

#Cloudflare: the edge

Cloudflare puts copies of your site in data centers around the world and serves each visitor from the nearest one, so a page does not travel across the country before it loads. It also absorbs attacks and bad traffic before they reach your site. For a firm whose reputation is the product, the security and uptime alone justify it; the speed is a bonus that also helps you rank.

#By firm size

Solo and micro: you benefit most and pay least. A modern static-first site on this stack is fast and nearly free to host, and it ages far better than a page-builder template.
Small and medium: the win is changeability. A well-built platform means a new practice page or a hundred location variants is a small task, not a redesign.
Large and enterprise: this is about performance at scale, security posture, and a content model your team can publish into without a developer for every edit.

A good platform makes the site fast in principle. Actually keeping it fast is the next layer, measured in Core Web Vitals, and the point of all of it is the AI and search visibility we cover in the AEO piece. The framework and edge tradeoffs are documented well at the Next.js docs.

Curious what your current site is costing you in speed and fragility? Run the estimator and we will tell you, plainly.

Answers

Frequently asked questions

Why does the platform matter for a professional-services site?: Because speed and reliability are trust signals in a category where trust is the product. A slow, awkward site undermines a claim of competence before anyone reads a word, and the platform decides how much effort speed costs.
What does the framework actually do for us?: It renders pages ahead of time so they arrive as fast files, handles images and code splitting sensibly by default, and keeps the site's structure legible to search engines. The point is that the fast option is the default rather than a project.
What does the CDN layer add?: It serves the site from near the visitor, handles encryption and redirects, and gives you a place to block abuse. For a firm, the practical effect is consistent speed regardless of where the visitor is and one place to control the site's edge behaviour.
Do we need a content management system?: Only if several non-technical people need to publish independently. For most firms, where one or two people edit occasionally, a system adds a service to maintain and a failure mode without solving a problem you have.
Who maintains this?: Less than firms expect: the framework and platform update on a cadence, and a static marketing site has little moving underneath it. What does need an owner is the content, which is where firms actually go stale.
Is this over-engineered for a small firm?: It is the same amount of work as a page-builder site and a faster result, which makes the comparison one of familiarity rather than complexity. The over-engineering risk is real for applications and mostly absent for a marketing site built this way.
What does it cost to run?: Very little at the traffic a professional-services site sees: hosting is inexpensive and the edge layer has a usable free tier. The cost is in building it well once, and the ongoing bill is usually smaller than a subscription page-builder plan.
How does this affect search visibility?: Speed and clean structure both help, and the largest effect is that pages exist as real server-rendered documents rather than something assembled in the browser. That is what search engines and answer engines can read reliably.
What happens if we want to change agencies?: You own the repository, the domain, and the content, so the site moves with you. That is worth checking explicitly, because platform lock-in is the quiet cost of the proprietary builders and it surfaces only when a firm tries to leave.
Can we edit content ourselves?: For text and images, yes, through whatever editing seam is set up. The honest answer is that some changes need a developer, and the question worth asking before the build is which changes you expect to make and whether those are covered.
Is this different for a larger firm?: Larger firms need more editorial workflow and often a real management system, plus governance across regions or practice areas. The platform underneath stays the same; what changes is who can publish and what review they pass through.
What should a firm actually ask a developer?: How fast will pages load on a phone, what can we edit ourselves, who owns the accounts, and what happens if we leave. Four questions, all answerable plainly, and the answers separate a durable build from one you will regret in two years.

Question we did not answer? Ask us directly and we will answer it here.

Tagged#Professional Services #Next.js #Cloudflare

Written by

John Cravey

Founder

Founder of Frontend Horizon. Writes most of the long-form work on the FH blog.