Blue Peak Healthcare
A revenue-cycle-management firm serving providers across the US, UK and Canada. The site had to read as credible to a compliance-minded buyer — and carry an AI assistant that can answer around the clock without ever going off-script.
- Next.js
- Turbopack
- Static output
- styled-jsx
- JSON-LD
- Closed-scope AI assistant
01 — The Problem
A site that has to survive a careful buyer, and an assistant that must not talk out of turn
Blue Peak handles revenue cycle management for healthcare providers — billing, coding, credentialing, A/R and denial management. The person evaluating them is a practice manager or a physician owner deciding whether to hand over the practice’s revenue to an outside firm.
That is not a casual buyer. The site is part of the diligence, so it has to be fast, structured and precise, and every page has to look like it was made by people who take compliance seriously.
Blue Peak wanted an AI assistant on the site. On a medical billing site, that is not a small feature request — it is the riskiest thing on the page.
A general-purpose chatbot here is a liability generator. A fluent, confident sentence about HIPAA, denial rates, or what Blue Peak guarantees becomes a claim the company has to stand behind, whether or not anyone at Blue Peak ever said it. The assistant had to be built to a different specification than “add a chatbot”.
02 — The Approach
Nothing on the page improvises
The site and the assistant were built on the same principle from opposite directions: neither should be capable of producing something Blue Peak did not intend.
Ship the whole site as pre-rendered output
The site is built with Next.js and Turbopack and served as pre-rendered HTML — the content is in the markup at first byte, with no application server behind it. All fourteen routes are static.
WhyA marketing site with no runtime has no runtime to compromise, nothing to patch on a schedule and nothing that can be slow under load. For a vendor asking a practice to trust it with revenue, a site that is never down and never slow is not a technical detail — it is part of the argument.
Give the assistant a closed answer space, not a personality
AIVA answers from Blue Peak’s own published content and declines what falls outside it. It is not a general assistant that happens to sit on a healthcare site; it is a way to navigate what Blue Peak has already said, in conversation rather than by menu.
WhyRefusing to answer is a correct answer here. Improvising is not. Bounding the answer space is the only version of this feature that a compliance-sensitive business can safely put on its own homepage — and it holds at 3am, when nobody is watching what the assistant says.
Structure the content the way the buyer arrives at it
Each of the four solution areas gets its own route — patient access, coding and documentation, billing and A/R, credentialing and enrolment — alongside Who We Serve, Technology, Insights and About, with Organization and ContactPoint structured data on top.
WhyNobody arrives wanting “our services”. They arrive with one problem — denials are climbing, credentialing is stalled — and a separate route per area lets them land on the exact thing they came for, and lets each area rank on its own terms.
03 — Key Technical Challenges
Two problems worth solving properly
An assistant on a healthcare site that must never improvise
The ordinary way to put AI on a website is to point a general model at it and let it talk. That is fine for a shoe shop. On a medical billing site it manufactures risk: the assistant is fluent, it is confident, it is on the company’s own domain wearing the company’s own branding, and anything it says reads as the company saying it.
There is a second problem underneath the first. A chat box on a healthcare site is exactly the sort of place a visitor might paste something about a real patient — which means the feature has to be designed knowing that, not discover it later.
AIVA is built as a closed ecosystem. Its answer space is bounded by Blue Peak’s own content, and a question that falls outside it is declined rather than guessed at. The assistant has no view on healthcare, no pricing authority and no opinions of its own to offer.
Framed that way, the feature stops being “a chatbot” and becomes something narrower and far more defensible: conversational access to material the company has already reviewed and published.
Blue Peak gets an assistant that answers visitors around the clock without ever committing the company to a position it did not take.
A booking form whose worst failure is two people missing each other
Blue Peak’s prospects are in the US, UK and Canada. The people fielding the demos are not. The conventional booking form asks for a date, a time and a time zone as three separate controls and quietly hands the conversion to the visitor — who is now doing arithmetic across zones at the precise moment you least want them distracted.
The failure is expensive and silent: both sides believe they have agreed a time, and one of them shows up to an empty call.
The slot list is pre-resolved. Rather than a time-zone dropdown sitting next to a clock, the form enumerates concrete labelled options — nine slots in IST and nine in EST — each one flagged and named with the region it belongs to.
Nobody converts anything. You pick a row that already says what it means, and the answer that reaches Blue Peak is unambiguous because it was never ambiguous.
The field most likely to waste a meeting becomes the one field where there is nothing to get wrong.
04 — What We Built
A credibility instrument with a safe assistant on it
The site
- Fourteen pre-rendered routes
- Four solution areas, each on its own page
- Who We Serve, Technology, Insights, About
OrganizationandContactPointstructured data
AIVA
- Closed-scope assistant on every page
- Answers only from Blue Peak’s own content
- Declines whatever falls outside that
- Built to be HIPAA-aware by design
Conversion path
- Demo booking across six service categories
- Eighteen labelled slots in two time zones
- Free revenue audit as the primary call to action
Platform
- Next.js, compiled with Turbopack
- Static output — no application server
- styled-jsx, scoped per component
05 — The Result
An always-on front desk that cannot say the wrong thing
Blue Peak has a site that loads as finished HTML, structured the way its buyers actually search, with an assistant on it that answers questions at any hour and stays inside what the company has already put its name to.
The restraint is the product. Anyone can attach a chatbot to a healthcare site in an afternoon; the work was in deciding what it must refuse to do, and then holding that line everywhere — including in the places where a more talkative assistant would have looked more impressive.
We have no traffic, enquiry or conversion figures to quote for this build. Everything described above is either visible on the live site or a decision we made while building it — there are no numbers here we are asking you to take on trust.
Want AI on your site that can’t embarrass you?
We build assistants with bounded answer spaces — useful at 3am, and incapable of inventing a position you never took.
Start a conversation