The TechRegent Platform
The consultancy's own operating spine — the site you are reading, and everything standing behind it.
A boutique practice run by one operator needs the infrastructure it sells: a way to be found, understood, booked, and tracked, with no manual step between a visitor's intent and a record in the pipeline. It has to be fast, inexpensive to run, and difficult to break by accident — because there is no team on call to repair it.
- 01
Static by default
Every page is rendered at build time and served as a file. Exactly one route runs on demand: the lead endpoint. There is no database, no session layer, and nothing at runtime that can fail while a prospect is reading.
- 02
Fail soft on the revenue path
The contact form posts to an internal route that writes to a durable form service first, then attempts a CRM sync. If the CRM is unreachable, the lead is still captured and the visitor still sees a success state. The integration is an enhancement, never a dependency.
- 03
One file governs every endpoint
Contact addresses, booking slugs, form identifiers and published pricing live in a single configuration module. Changing a provider — or an entire brand — is an edit in one place rather than a search across a codebase. The rebrand behind this site is what proved the decision.
- 04
Own what you depend on
Typefaces are self-hosted and served from the site's own origin, so rendering never waits on a third-party network and no visitor request leaves for one. The booking embed renders a plain direct link beneath it, so the path to a booked call survives the embed failing to load.
- 05
Machine-readable by construction
Structured data describes the practice, its founder, and its credentials. The sitemap and robots policy are generated from the same route table that builds the pages, so they cannot drift out of sync with the site itself.
- Framework
- Next.js App Router, TypeScript — statically generated, one dynamic route
- Booking
- Cal.com embed across five event types, with a direct-link fallback rendered beneath it
- Lead capture
- Internal API route → durable form service → best-effort CRM sync behind an environment-gated token
- Delivery
- Vercel, apex and www with permanent redirect, TLS, full DNS cutover
- Identity
- JSON-LD professional-service schema including founder credentials; generated sitemap and robots
- Typography
- Three self-hosted variable families, subset and served from origin