~/proof · demo evidence

Eight systems. Open any of them.

Not a slide deck and not a list of logos. Every card below is a URL that answered on 2026-07-25 and a thing you can click through yourself in about a minute — the menu loads, the form accepts, the dashboard renders. If it isn't clickable, it isn't on this page.

Book 20 minutes — I'll walk any of these live or start clicking ↓

Read this before you read the rest

There are two kinds of proof. This page only carries one of them.

Tier DDemo proof

“I can show you this working, on screen, right now.” A live URL, a stack, a flow you can walk end to end. Everything below is this, and I'll screen-share any of it on a call without preparing anything first.

Tier OOutcome proof

“this produced $X for client Y.” I have almost none of it saved in a form I'm allowed to publish, so you will not find a single growth percentage or revenue figure here. When a client result is measured and I have written permission, it gets added — with the denominator.

Most portfolios blur the two, because Tier O sells harder. The blur is the reason you can't trust most portfolios. You can check every claim on this page in the next sixty seconds, which is the whole point of writing it this way.

The systems

Everything here is running in production

One card each: what it does, what it's built on, and a link that opens the real thing. The screenshots are captures of the live sites, taken the same day the URLs were rechecked.

glacierfortcollins.com200

Local business site · owner console

Glacier Ice Cream

A full production site for a Fort Collins ice cream parlor. Customers browse the menu, order online and pay by card. The owner signs into a console and edits hours, prices and content themselves — no redeploy, no ticket to me. Every form on the site captures a lead into a CRM rather than an inbox. Built on Next.js and TypeScript with Supabase for data, Stripe for payments and Vercel for delivery. Live at glacierfortcollins.com. Click through it — the menu, the cart and the checkout are all real, none of it is a mockup.

Browse the menu and add an item to the cart
Reach a real Stripe checkout
Submit the contact form and watch it accept a lead

Next.jsTypeScriptSupabaseStripeVercel

Open glacierfortcollins.com

icecreamfortcollins.com200

Publishing platform · content pipeline

Ice Cream Fort Collins

A city magazine that keeps moving between issues. A scheduled pipeline drafts and files local content, a directory keeps venue records current, and a weekly edition assembles from both. It also consumes a public events feed from a separate platform I built, so two independent systems stay in sync without anyone copying data between them by hand — the part most content sites never get to. Next.js and TypeScript on Supabase, deployed on Vercel. Live at icecreamfortcollins.com.

Open the current issue and the 2026 rankings
Browse the directory the pipeline maintains
Follow a listing sourced from the events feed

Next.jsTypeScriptSupabaseScheduled jobsVercel

Open icecreamfortcollins.com

cnefit.app200

Consumer member app · booking

CNE Fit Tracker

A member app for a Boulder personal-training gym. A prospect requests a free trial, the request writes a lead record, and the booking step pulls real appointment slots from a scheduling service and writes the confirmed booking back to it. No third-party booking widget — the whole rail is ours, so the gym owns its calendar and its customer data. Members log workouts, nutrition and progress; the owner sees it from an admin console. Next.js PWA in TypeScript on Supabase, deployed on Vercel. Live at cnefit.app.

Start the free-trial request flow
See real appointment slots returned, not a static list
Reach the member signup

Next.jsPWATypeScriptSupabaseVercel

Open cnefit.app

thefortlist.com200

Events platform · public API

The Fort List

A nomination-gated events platform for Fort Collins. Visitors browse what is on and subscribe to a newsletter that enrolls them in a real sequence; members sign in for the private list. It publishes a documented public JSON feed that a separate magazine site consumes — a working integration between two systems, which is harder and more useful than either site alone. Next.js and React on Supabase, with AWS SES for mail and signed JWT sessions. Live at thefortlist.com.

Browse live music and venues
Subscribe and get enrolled in a real sequence
Hit the public events endpoint and read the JSON

Next.jsReactSupabaseAWS SESJWTVercel

Open thefortlist.com

trend-os.io200

Market intelligence · dashboards

TrendOS

A market-intelligence platform that runs scheduled collectors against dozens of public sources, deduplicates what comes back, and surfaces ranked signals in an authenticated dashboard. It also ships a status surface that reports its own pipeline health, so a collector that silently stops returning data shows up as broken instead of quietly reporting zero — the failure mode that makes most scraping projects untrustworthy after month two. Python and FastAPI for collection, Next.js for the dashboards, Postgres for storage. Live at trend-os.io.

Open the public trends and topics surfaces
Read the status page reporting its own pipeline health
See source counts and freshness stated with the data

PythonFastAPIPostgresNext.jsScheduled collectors

Open trend-os.io

localbusinessfactory.com200

The factory the rest come out of

Local Business Factory

The system the other client sites on this page came out of. One brand config drives scaffolding, wiring and deployment, so a new business site arrives with its rails already connected instead of being reassembled by hand every time. A shared component package means a fix made once reaches every site built on it. That is the difference between an agency that rebuilds and a system that compounds. TypeScript and Next.js in an npm workspace, deployed on Vercel. Live at localbusinessfactory.com.

Scroll to the running client tiles — each links to a real build
Open any tile and land on the live site
Read the per-tile launch state and capture date

TypeScriptNext.jsnpm workspacesSupabaseVercel

Open localbusinessfactory.com

teneo.io200

Long-form content generation

Teneo

A platform that turns one idea into a finished long-form manuscript, a cover and publish-ready files, then puts them behind a storefront a reader can inspect. Multi-stage generation with structure planned before drafting, not one long prompt — which is why the output holds together across tens of thousands of words. This is the system behind the book work I delivered before moving into automation, and it still runs today. Next.js front end on AWS with Stripe checkout. Live at teneo.io.

Start the free preview flow from one idea
Read a finished title in the public library
Inspect a generated storefront

Next.jsAWSDynamoDBStripeLLM pipelines

Open teneo.io

traviseric.com200

This site · build record

traviseric.com

The site you are reading. It pulls my GitHub activity through its own API routes and renders build pace and focus over real time windows, with the limitations printed next to every number rather than buried. It also runs a consulting enquiry path that was tested end to end in production — flagged test submissions written, asserted in the database, then deleted. Next.js 15 and TypeScript on Supabase, with NextAuth and Stripe, deployed on Vercel. Live at traviseric.com.

Open /now for build pace over real windows
Open /projects for the tracked build registry
Use the enquiry path at the bottom of this page

Next.js 15TypeScriptSupabaseNextAuthVercel

Open traviseric.com

Built, receipted, not filmed

Three things I can't show you here — so I won't pretend to

These are real and internally certified, but no recording exists yet. A staged demo of a system I haven't captured would be the exact thing this page is built to avoid, so they get described instead and walked live on a call.

AI phone ordering

receipt on file · no capture

A voice agent answers the restaurant phone, takes the order, prices it against the live menu, and texts the caller a payment link. The site re-prices the cart and mints the charge in the restaurant’s own account — the voice agent is never a payment authority and never takes a card by voice.

Certified internally on 2026-07-15 and locked to three venues. No call recording exists yet, so there is nothing to show you here. I will walk it live on a call instead.

Booking and reminder rail

receipt on file · no capture

Scheduling, CRM and SMS/email wired as one rail: a booking writes the contact record, confirmations and reminders anchor to the appointment, and cancellations or reschedules re-anchor them. Quiet hours and messaging compliance are enforced in one place instead of per-integration.

Live-verified across the services on 2026-07-07. The proof is a message arriving on a phone over a period of days, which is not a screenshot.

Compliance-gated outreach composer

receipt on file · no capture

A cold-outreach composer that refuses to emit a draft that breaks its own rules — suppression, consent and honesty gates run before anything is rendered, and a blocked draft fails closed rather than going out unflagged.

It is source I can read to you and run in front of you; there is no user-facing screen to screenshot.

Next step

Pick something above and make me walk it

The fastest way to find out whether I can build your thing is to watch me open one of these and go wherever you point. Twenty minutes, no deck.

Book a 20-minute call

How this form is wired

It writes to a database, forwards to the CRM, and emails me directly — three independent channels, and it only reports success if at least one accepted the message. The booking link above runs on scheduling software I built rather than a rented calendar widget, which is itself part of the demo.

How this page is kept honest

Every URL was requested and returned HTTP 200 on 2026-07-25. The screenshots were captured from those same live pages on the same day, not from a design file.

Each entry maps to a row in a committed claim allowlist. A build check fails if this page asserts anything that file doesn't carry, or if any copy matches an outcome-claim pattern.

Stated capability is deliberately narrower than what these systems do. Where something is built but unproven in production, it is named in the section above rather than quietly upgraded.

The longer version of this record — claim maturity states, limitations and what would move each one up a level — lives on /projects and /now.

There are two kinds of proof. This page only carries one of them.

Tier DDemo proof

Tier OOutcome proof