Overview
Notermed is an AI-powered medical transcription product — "notes that write themselves" — that generates clinical notes from patient conversations. CS2 built the public marketing surface and the authenticated application shell on a single Next.js codebase, with a dynamic AuthProvider that routes visitors into either the product app or the marketing pages depending on session state.
The challenge
What the business needed
Notermed is a SaaS product, not a brochure site. The same domain has to serve two jobs: convince a doctor or clinic administrator that the product is worth a trial (marketing layer), and be the app itself once that user signs in (product layer). Most SMB site builders can't do either side of that well, and stitching a WordPress marketing site to a separate SPA usually means double-domains, double-branding, and double-SEO pain. Notermed needed one codebase that handled both.
The build
What CS2 shipped
CS2 built Notermed on Next.js with an AuthProvider that wraps the entire app, so the same URL can render the public marketing hero for anonymous visitors and the authenticated product UI for signed-in users. Assets are hosted on AWS S3 with CloudFront in front, giving the app fast cold-start loads globally. Page-level SEO metadata is set per route ("AI-powered medical transcription that automatically generates clinical notes from your patient conversations."), so Google indexes the marketing surface without exposing the gated product.
Highlights
What's on the site today
- Single codebase for marketing site + authenticated product app
- AuthProvider-wrapped routing, so the same URL behaves differently per session
- SEO metadata set per route for indexable marketing pages
- AWS S3 + CloudFront delivery for global low-latency loads
- HIPAA-appropriate architecture posture (no third-party site builders touching PHI)
Tech stack
What it's built on
- Next.js (App Router)
- React
- Client-side AuthProvider
- AWS S3 + CloudFront hosting
- Server-rendered SEO metadata
Outcome
How it operates today
Notermed has a single Next.js codebase that serves marketing traffic, handles auth, and renders the product — no Webflow-plus-SPA duct tape, no SEO split across subdomains. The product itself listens to a clinician's conversation with a patient and generates a structured clinical note automatically, removing the after-hours charting tax that drives physician burnout. A doctor lands on the marketing site, signs up, and is generating notes inside the same domain — no jarring handoff to a separate app shell.
What this proves
How CS2 ships a real SaaS product — marketing, auth, and app on one Next.js codebase — instead of duct-taping a template site to a separate web app.