Georgia AI: Building On-Demand Sales Coaching That Actually Works
How we built Georgia, an AI role-play engine for sales coaching, what broke early, and what first users reported after real calls.

The Problem Nobody Talks About in Sales Enablement
Sales coaching is expensive. A good coach charges $300 to $500 an hour. Enterprise training programs run $2,000 to $5,000 per rep per year. Most salespeople get formal coaching twice, maybe three times annually. A quarterly review and a ride-along if they are lucky.
Then a rep gets a meeting with a CFO at a 200-person company and has 18 hours to prepare. There is no coach available. The manager is in a different time zone. The rep watches a YouTube video and hopes for the best.
That is the gap Georgia was built to close.
Georgia is an AI role-play SaaS that gives sales reps on-demand practice with realistic simulated prospects. You tell it who you are meeting, what they care about, and what objections you are expecting. Georgia plays the prospect. You run the call. You get feedback.
This is the full build story.
What "Realistic" Actually Requires
The first version of Georgia was a chatbot with a persona. It had a name, a job title, and a short description. Reps could type responses and get replies.
It was not useful.
The problem was that the simulation had no memory and no pressure curve. A real CFO does not ask a single objection and accept your answer. They circle back. They get colder when you dodge. They interrupt. They test you on pricing when you least expect it.
Our early testing showed that reps finished sessions feeling confident, then struggled on live calls. The simulation had not prepared them for escalation.
We rebuilt the engine around three principles.
First, persona depth. Each simulated prospect has a full context profile: company size, recent business events, stated priorities, known objections, and a skepticism level. The model uses this to stay in character across the full conversation, not just for the first two exchanges.
Second, pressure escalation. Georgia tracks how well the rep is answering. Weak answers trigger harder follow-up questions. Strong answers earn brief engagement before the prospect pushes on the next concern. The conversation difficulty adjusts in real time.
Third, session memory. If a rep claims their product reduces churn by 30% at the top of the call, Georgia will hold them to that number 15 minutes later. Inconsistency gets flagged. Real buyers catch that. The simulation needed to catch it too.
Building the Feedback Layer
Role-play without feedback is just practice. Feedback without specificity is just noise.
This was the hardest part of the build. Giving a rep a score out of ten does nothing. Telling them "you talked too much about features" is slightly better but still vague. What they need is: "You described the product for 90 seconds after the prospect asked about price. That signals you are avoiding the question. Here is how to acknowledge price directly and pivot."
We structured the feedback output around four categories: clarity, objection handling, pacing, and discovery quality. Each category gets a short paragraph with a specific timestamp or exchange referenced. No scores. No stars. Just plain language tied to something that actually happened in the session.
One early user described it this way: "It was like getting notes from someone who had been on 500 calls and had no reason to be polite."
That was exactly what we were going for.
What Broke in Early Versions
Honesty about the build: several things failed before we got to a product worth shipping.
The first persona system was too rigid. Reps figured out the script within three sessions. The prospect would behave the same way in the same situations, so reps memorized responses instead of developing instinct. We moved to a more generative approach where the persona behavior has structured variability. Same core character, different conversational paths.
The feedback model hallucinated early on. It would cite exchanges that did not happen or misattribute statements. That is a credibility-killing bug in a coaching product. We added a grounding step that ties all feedback to logged transcript segments before output. Slower, but accurate.
Session length was also a problem. Reps would quit after five minutes. We found that sessions under 12 minutes produced almost no behavioral change based on follow-up surveys. We added a light commitment mechanic: Georgia will not generate a full feedback report until the session hits a minimum threshold. Simple, slightly annoying, necessary.
First User Feedback
The first cohort was 14 sales reps across three companies. Mixed experience levels. B2B SaaS, professional services, and one manufacturing company moving into direct sales.
Average sessions per user in the first 30 days: 22. Several ran more than 40.
Three reps specifically mentioned using Georgia the night before a major call. One closed a deal he described as one he had lost twice in previous roles at other companies with similar prospects. He attributed it to knowing exactly where his pitch was falling apart beforehand.
The most common piece of feedback from users: "It is harder than I expected." That is the right answer.
The Practical Takeaway
If you are building a coaching or training product on top of AI, the simulation quality is the product. A persona that breaks under pressure teaches nothing. Feedback that is vague teaches nothing.
Start with what a real expert would say in the debrief, then build backward to the simulation that would make that feedback accurate. Do not start with the chatbot and hope the insight follows.
Georgia is live. If you are a sales leader looking at a tool like this for your team, or a founder building in the AI coaching space and want to compare notes on the architecture, reach out.
