Sales Dojo

• 

## Sales Dojo

Sales Dojo turns a company’s sales playbook into a live training gym.

Most sales teams already have scripts, call notes, onboarding docs, and advice from the top rep. What they usually do not have is a real place to practice before live calls.

That gap is expensive.

It slows down new reps, makes coaching inconsistent, and leaves managers guessing whether their team is actually improving.

Sales Dojo fixes that.

A team can paste its methodology, objections, banned claims, and approved next steps, and Sales Dojo turns that into:

• live practice scenarios
• AI roleplays
• instant coaching
• scorecards
• rep improvement tracking

The result is simple: instead of hoping reps absorb the playbook, teams can actually train it.

## Why we built it

This project came from a real problem we had already felt ourselves.

We had built a sales training game around our own internal sales playbook. Once we used it, the bigger insight became obvious: the valuable part was not the company- specific version. The valuable part was the system behind it.

Every serious sales team runs into the same friction:

• the best reps hold too much of the real sales judgment
• playbooks exist, but practice does not
• new reps do not get enough safe repetition
• coaching is inconsistent
• managers cannot easily tell who is improving and who is not

That is what pushed us to pull the concept out of one internal use case and rebuild it as a standalone product.

The core belief behind Sales Dojo is this:

A sales playbook should not stay a document. It should become a practice environment.

## What Sales Dojo does

Sales Dojo helps teams go from static documentation to live training.

A team can:

1. create a workspace
2. paste its sales playbook
3. define banned claims and approved next steps
4. generate a scenario library from that playbook
5. practice against AI prospects
6. get scored on each round
7. review what worked, what missed, and what to say instead
8. track rep improvement over time

This makes the product useful in two ways at once:

• it helps reps practice before real conversations
• it helps managers see whether training is actually working

## The product decision that mattered most

We made one decision early that shaped the whole experience:

the live roleplay stays on one screen.

We did not want the core training loop to feel like a form, a quiz, or a wizard.

We wanted it to feel like a game arena:

• scenario context
• prospect opener
• turn-by-turn conversation
• reply box
• coaching and score feedback

That made the product faster to understand, stronger to demo, and much more usable.

## How we built it with MeDo

We built Sales Dojo with MeDo as the core development environment, but we did not treat it like a one-shot code generator.

We treated the build like a structured product conversation.

Instead of asking for “an app,” we broke the product into stages:

• scaffold the product
• shape the landing page
• build workspace and playbook onboarding
• build scenario generation
• build the one-screen roleplay experience
• build scorecards and results
• build leaderboard and progress views
• polish the demo flow

That mattered because Sales Dojo is not one feature. It is a connected system. The quality came from giving MeDo a clear product frame, then tightening each layer until the app felt coherent.

The most impressive part of the build was not just that MeDo generated code. It was that it helped turn a strong product insight into a usable full-stack application, including:

• workspace flow
• playbook ingestion
• scenario generation
• live roleplay UX
• coaching and scoring
• leaderboard framing

We pushed hard on product language, interaction quality, and clarity so the result felt intentional instead of generic.

## What we learned

### 1. Sales training is a real product category At first this looked like an internal tool. Very quickly, it became clear that the underlying need is much broader.

Many teams do not need more sales documents. They need a better way to turn those documents into practice.

### 2. AI alone is not the product The AI matters, but the real value comes from the interaction model around it.

The roleplay experience had to feel:

• immediate
• focused
• game-like
• easy to scan
• easy to repeat

Without that, it would have felt like just another chatbot.

### 3. Multi-turn building with MeDo is far stronger than vague one-shot prompting The best output came from:

• defining the product clearly
• tightening scope
• iterating screen by screen
• improving flow, not just code
• using conversation to sharpen both logic and UX

That made the app stronger as a product, not just as a prototype.

## The hardest parts

### Turning a company-specific tool into a general product The first version carried assumptions from one company’s workflow. We had to strip those away and keep only the universal pattern:

playbook in -> training system out

### Avoiding generic AI product feel A lot of AI products become vague and forgettable. We had to keep tightening:

• the homepage message
• the one-screen gameplay loop
• the coaching structure
• the score/review flow
• the overall feel of the app

### Choosing the right scope A full product version would go much further:

• account auth
• saved workspaces
• stored playbooks
• persistent sessions
• team management

For the hackathon, we focused on the highest-leverage version: a working, polished product that makes the value obvious quickly.

## Why this matters

Sales Dojo solves a real problem.

Sales teams know they should train. Most of them just do not have a system that makes training:

• usable
• repeatable
• measurable
• tied to their own way of selling

We believe the future of sales enablement is not static documentation.

It is interactive practice built directly from the team’s own sales logic.

That is what Sales Dojo is built to do.

## Built with MeDo

We used MeDo as the core tool for:

• product scaffolding
• full-stack generation
• multi-turn UI refinement
• flow design
• feature expansion
• hackathon-ready polish

Sales Dojo is a strong fit for MeDo because the product itself is built around structured interaction. We were not just generating screens. We were shaping a system.

That made MeDo valuable not only for writing code, but for helping us turn a clear product idea into a working, demo-ready application.

Built With

• medo