Skip to content
Mark Warren
Menu

All work

Prospect demos

Prospect demo apps on the shared platform

A working, private demo for each prospect, built from one codebase on the shared chat agent, with the first one built and deployed in a day.

How it fits together

  1. Inputs

    • Prospect content

      A knowledge base and a persona written for the prospect's business, checked with a dry run before anything is provisioned.

    • Page config

      One small file sets the prospect's colors, products, and copy.

  2. Engine

    Showcase app

    One Next.js codebase, deployed once per prospect and selected by an environment variable.

    • Next.js
    1. Product-scoped chats

      Each product card opens a chat scoped to that product, answered by the shared chat agent in the prospect's persona.

      • Claude
    2. Answer variants

      The same question answered side by side for different tones, lengths, and audiences.

    3. Local mock agent

      The page is built and tested against a mock agent before any real tenant exists.

  3. Outputs

    • Private demo site

      A sample home page in the prospect's own colors, a quote form, and a section on how the agent is guarded.

    • Review before showing

      A smoke test and a partner review come before the prospect sees it.

Guardrails

  • Password gate and no search indexing
  • Demo leads go only to FirstCoast, never to the prospect
  • Every provisioning step waits for approval

The problem

A prospect understands an AI agent best when it is answering questions about their own business. Slides cannot do that, and a custom build for every prospect costs too much before anyone has agreed to anything.

What I built

  • A showcase app that becomes a different prospect's demo by configuration, not by forking the code.
  • Chats that run on the same production chat agent service the platform's sites use, with the prospect's persona and knowledge base.
  • A written runbook that takes a demo from knowledge base to deployed site in a fixed sequence of approval-gated steps.
  • A password gate, no search indexing, and lead routing that keeps demo traffic away from the prospect's inbox.

How I built it

Next.js on the multi-tenant platform, with each demo provisioned as a tenant so its content and persona live in the same systems as a real client's. The first demo went from persona to deployed site in one day.

What it shows

I build rapid prototypes on real infrastructure, so a demo that lands can become the product instead of being thrown away.