← The Bench
Methodology

Most AI starts with capability.
We start with voice.

The Bench Method is the 5-step process for designing AI coworkers — Benches — that speak in your voice, run on infrastructure you own, and sharpen through deliberate iteration. It is the methodology behind every product in The Bench.

How we build a Bench

01

Voice Extraction

Before any code, we capture voice. Through structured working sessions, we extract the specific vocabulary, cadence, refusal patterns, and signature phrases that make you sound like you — the things you say that others don't, and the things you would never say. Most AI work skips this entirely or reduces voice to a "professional/friendly" dial. The Bench Method treats voice as the primary design constraint.

Input
1–2 working sessions with the operator. Recorded client interactions when available.
Process
The Voice Rubric — a proprietary set of tonal probes designed to surface what is distinct, not just what is preferred.
Output
A Voice Profile: a structured, reviewable, editable document of vocabulary, cadence, and behavioral rules.
02

Soul File Design

The Voice Profile becomes a Soul File: a versioned document that drives the Bench's behavior. Not a system prompt. A character bible with operational rules — identity, beliefs, vocabulary library, escalation triggers, refusal patterns, signature phrases. The Soul File is the artifact that makes a Bench a Bench. It is the IP that survives every model upgrade.

Input
Voice Profile + a clearly defined scope of work for the Bench.
Process
Structured authoring against the Soul File schema. Reviewed and approved by the operator before deploy.
Output
A versioned Soul File in plain text — editable forever, portable across models.

A Bench is not a chatbot. It is a coworker with a soul file — and the file belongs to the operator.

03

Infrastructure Deploy

The Bench runs on infrastructure the operator owns. API keys in their name. Hosting on their accounts. Logging on their stack. We set it up; they hold the keys. No vendor lock-in. No black box. If they ever want to fire us, the Bench keeps working — that is the design.

Input
Soul File + access to the operator's accounts and chosen runtime.
Process
Setup against the Infrastructure Checklist — runtime, persistence, logging, kill switches, cost guardrails.
Output
A live Bench running in the operator's name. Documented and handed over.
04

Channel Integration

A Bench shows up where clients already are — Discord, SMS, email, web, custom apps. The same Bench speaks slightly differently across channels: short and fast on SMS, structured on email, casual on Discord. Channel-aware persona is part of the design, not a feature added later.

Input
A running Bench + the operator's channel list and audience map.
Process
Wire-up against the Channel Playbook. Per-channel tone tuning written into the Soul File.
Output
A Bench accessible from every channel that matters, sounding right in each one.
05

Iteration Loop

A Bench is never finished. Every week, real conversations surface edge cases, missed tones, and refinements worth keeping. The Soul File is edited — not retrained. That is the design discipline: persona refinement as a continuous, deliberate loop, owned by the operator. Most AI improves by being replaced. A Bench improves by being maintained.

Input
Real conversations from the past week + operator feedback and flagged moments.
Process
Weekly review against the Iteration Checklist. Soul File edited, versioned, redeployed.
Output
A Bench that gets sharper over time. The operator's voice, captured more accurately each week.

What makes this different

Persona over prompts

The character is the product. The model is replaceable; the Soul File is not.

Operators own everything

Keys, infrastructure, Soul File — all live with the buyer. If they ever leave us, the Bench keeps working.

Voice first, always

Voice is the design constraint, not a setting. We extract it before we build anything.

Soul files, not system prompts

Versioned, editable, persistent. A document that anyone on the team can read, edit, and own.

Iteration as discipline

A Bench sharpens through structured weekly review — not by being rebuilt every six months.

Productized methodology

Every Bench is bespoke. The Method is the same. That is what makes it teachable, sellable, and repeatable.

The Method, productized.

The Real Estate Bench is The Bench Method built for independent agents and brokers. 4 founding spots are open now.

View the Real Estate Bench Email Christy