ANODA Discuss your product

Sales training platform, reworked for five roles

Combat Sales is where companies train their sales reps, from courses to recorded practice.We redesigned it for five roles and designed new features.

Combat Sales Superadmin home across all companies: saved time, students enrolled, current courses, trainers and reviewers, then the students’ daily status
80+
final desktop screens and interaction states
5
roles each with its own permissions and daily work
Redesign
of a live platform selected areas reworked, new features added

Combat Sales is a desktop platform for sales training: companies enrol their reps, trainers teach and review them, reviewers check recorded practice, and a Superadmin runs it across every client company. We did a targeted UI redesign of the existing product and designed new features into it, as multi-role SaaS product design with a baseline UI kit cleanup .

What runs through the platform

One chain, from a client company to a finished course:

  1. Companies

    • Switching
    • Statistics
    • Exports

  2. People

    • Trainers and reviewers
    • Students
    • Assignments

  3. Courses

    • Requests
    • Approval
    • Order

  4. Learning

    • Lessons
    • Discussions
    • Progress

  5. Practice

    • Recorded videos
    • Reviews
    • Evaluations

  6. Messages

    • Email rules
    • Schedules
    • Automated messages
Familiar Better
Selected flows reworked; the look and the places people knew kept.
Shared Separate
Five roles on one platform, each seeing its own work first.
Numbers Next task
Dashboards that point to what needs doing, not only report.

Every client company, read top to bottom

Found
The Superadmin looks after every client company, and a home where each figure weighs the same doesn’t say whose numbers these are or where to look first.
Decided
A home that reads in order: which company is in view, the year in five figures, where students stand today, the trends, then practice scores.
For the user
The Superadmin sees which company they’re in, and what needs attention, before opening a single table.
The earlier Combat Sales Superadmin home: four overview totals, a daily status ring of 41 students and four empty activity tiles
Before: the Superadmin home in the platform the client came with
In the way
Four totals of equal weight, a daily ring mostly at zero, and nothing that says which company the numbers belong to.
Combat Sales Superadmin home: the company switcher, saved time, 4,317 students enrolled, 43 courses, 27 trainers and 11 reviewers, the daily status of students, enrolment and bounce-rate charts and the randomizer score histogram
After: the Superadmin home across all companies; the figures are example data

  1. Whose numbers

    The company switcher, and the company’s name over the page.

  2. The year in figures

    Saved time, students, courses, trainers and reviewers.

  3. Where students are

    Learning, waiting for evaluation, finished or gone, today.

  4. The trend

    Enrolment and bounce rate by month.

  5. Practice scores

    How randomizer tests scored across the year.

How the work progressed

Roles and workflows first, then the screens in the platform’s own look, then change requests and walkthroughs from the client’s feedback.

  1. User Flow

    Who does what: five roles, their permissions and the workflows between them

    Artifact Role and workflow maps and a screen map

  2. UI & Design System

    Which areas to rework, which to extend, and how to keep the look people knew

    Artifact Final desktop screens and states, and a baseline UI kit cleanup

  3. Delivery

    What each change request needed, and what new users see first

    Artifact A clickable prototype, change requests, and Trainer and Student walkthroughs

One platform, a menu for each role

Found
Five roles share one platform, and a menu built for the Superadmin would bury a trainer’s four daily places under eleven.
Decided
Each role’s paths were mapped first; then each got its own menu: the full one for the Superadmin, a shorter one once a company is chosen, four items for a trainer, the course itself for a student.

  1. Superadmin: course approval

    Approve or reject a request; an approved row turns into Assign Trainer.

    Open the full map
    Superadmin map fragment: the Course Approval list, then the same list with approved rows turned into Assign Trainer buttons

  2. Trainer: time on reviews

    Asked once on the review screen, then answered or skipped.

    Open the full map
    Trainer map fragment: the one-time question on the video review screen, then its dropdown of session lengths

  3. Student: from the course to a self-test

    The course as weeks, a locked week that says why, then a test built from the weeks reached.

    Open the full map
    Student path: the Post Training course as week cards with a locked Week 2 and its tooltip, then Test Yourself with the reached weeks ticked and later weeks locked
Three Combat Sales menus: the Superadmin’s eleven items, the five left once a company is selected, and the trainer’s Home, Courses, Students and Notifications

The menu changes with the role

Left to right: the Superadmin across all companies, the same Superadmin inside one company, and a trainer.

  • Role and workflow maps
  • Screen map
  • Navigation states
  • Clickable prototype

Eight jobs, from the company to the student

The Superadmin’s work first, then the trainer’s, the reviewer’s and the student’s, then the rules around courses and messages. Every figure on these screens is example data.

Working inside one company

Found
The Superadmin sees every client company, and a figure read, or an action taken, in the wrong one misleads or reaches the wrong people.
Decided
A company switcher in the header; once a company is chosen, the menu, the dashboard and the figures narrow to it, and its statistics export as a file.
Dashboard with one company selected: the shorter menu, saved time, students, courses, trainers, a completed-trainings gauge and daily status
Companies page with company tabs, the company’s statistic, course cards with student counts and the trainers table with assigned courses and saved time
Export statistic panel over a preview of the company’s statistic sheet, with PNG, JPG and PDF formats and the document name

Trainers and reviewers, each in their role

Found
Trainers and reviewers work side by side but do different jobs, and a reviewer lost among trainers is a quality check nobody runs.
Decided
One team table with the role on every row and a filter for it, each person’s courses and students, and a student assigned right from the row.
User management table of trainers and reviewers with email, phone, role, assigned course chips, number of students and an Assign Student button
User management table with the role filter open: all, trainers or reviewers

Every student, and what to do with them

Found
A student can be on several courses with different trainers, and a list of names says nothing about who is stuck or waiting.
Decided
A students table with status, dates, scores before and after, the final exam and the team on each course row, with editing, logging in as the student and reassigning a trainer in the row’s menu.
Students table with counts in progress, pending evaluation, finished and left, course rows with status, dates, scores, final exam, position, team and points, and a row menu with edit, log in as user, reassign trainer and restore password

A trainer’s day, in order

Found
A trainer has students on several courses, questions waiting and videos to review, and metrics of equal weight don’t say what comes next.
Decided
A home that leads with students and open questions, then today’s reviews with the videos inline and the coming final evaluations; and a students tab split by course, with each student’s progress.
Trainer home greeting the trainer by name: saved time, current students on three courses, the weekly students chart, student questions with Open discussion, and today’s activity ring
Trainer’s students tab for post-training students, split by course, with status, completed modules, a progress ring, activity and start and completion dates

Recorded practice, reviewed in the course

Found
Students record practice pitches, and a video with no clear review step is a file in a queue; the time a trainer spends on it is invisible.
Decided
Review sits inside the course, next to its materials and final evaluation: the video, a comment and Complete feedback, then the next one. The first time, the platform asks how long a session usually takes; after each review it sets the time spent against that.
Pop-up after a video review comparing the minutes spent this time with the usual time and the total time saved

Materials a student can find again

Found
Scripts, role-play videos, worksheets and links pile up across two courses, and a student hunting for last week’s video gives up before the next door.
Decided
One resources page grouped by kind: collections, text, video, files to download and useful links, each link tagged by source, with search and a filter, and the course progress kept in the header.
Student resources page: collections, text and video resources with their round cover thumbnails, files to download and useful links tagged YouTube, Article or Blog post, with search and an All resources filter

Courses requested, approved and ordered

Found
Students ask for courses, and an approval queue without a clear next step becomes the bottleneck of the whole platform.
Decided
A Course Approval list with each request’s course and date, approved or rejected on the row, and an approved student then given a trainer; courses in Published and Draft, reordered by dragging.
Courses page with Published and Draft columns and a course card being dragged to a new position

Messages that go out on their own

Found
Welcome letters, deadlines, reviewed videos and evaluations each need a message, and nobody can send them all by hand.
Decided
Notification settings for students, trainers and reviewers: when to notify, a sending schedule by weekday, and for every event a switch, the channel, the timing and an editable template.
Notification settings with a custom schedule: sending hours for each weekday and the main and additional notification groups
Trainer notification settings: deadline approaching, video reviewed and other events, each with a switch, channel, timing and email template

A UI kit tidied, not rebuilt

Found
New features had to look like the platform people knew, and the kit behind it needed tidying before it could carry them.
Decided
A baseline cleanup of the existing kit: components aligned and extended within the platform’s own colours, then reused across roles instead of drawn again.

One trainer picker, two jobs

The same picker moves a student to another trainer and gives an approved student their first one.

  • Trainer picker for reassigning: the student, the current trainer and the list of trainers with their number of students
    Students: Reassigning a trainer.
  • The same trainer picker after a course approval: the student and the list of trainers with one selected
    Course Approval: Assigning after approval.

A notification rule, on and off

Switched on, its channel, timing and template are live; switched off, the whole rule dims but keeps its text.

  • Two notification rules: Deadline approaching switched on with its email channel, 10 minutes and template; Video was reviewed switched off, its channel and template dimmed
    On, then off

Where the product ended up

The parts of Combat Sales that got in the way reworked, and new features designed into it, in the look its users already knew: company context and dashboards for the Superadmin, the team and students to manage, a trainer’s day in order, recorded practice reviewed inside the course, lessons, course approval and automated messages, with Trainer and Student walkthroughs and a tidied UI kit.

Delivered with a screen map and a clickable prototype, then through change requests. The redesign went live; we didn’t write its code or deploy it, and these screens are our design files, not a record of every state that shipped.

final desktop screens and interaction states
80+
roles in one platform
5

In the client's words

ANODA understood how different users rely on our dashboard to follow training progress and decide what to focus on next. They helped us organise that information around each role’s priorities, making the dashboard easier to navigate and the next steps clearer. We also appreciated how carefully they worked within our existing brand guidelines, making small refinements to typography, spacing and visual hierarchy that gave the platform a more polished feel while keeping it recognisably ours.

Davis Carbo Combat Sales

5.0

Afraid every role will get the same dashboard with a new label?

In Combat Sales, the Superadmin starts from every client company, a trainer from today’s students and questions, a student from the course, all in the platform they already knew. Bring us your roles, and we’ll show where each one’s work should start.

Discuss your product Explore more case studies

What we brought to Combat Sales

The product

The interface and the work