Skip to main content

Your human-facing work, structured for AI.

PokaMind is a human-facing AI platform that structures an organization's own playbooks, policies and practice conversations into interaction-ready data, then builds what its people need on top, starting with AI roleplay practice, on a screen or on a robot.

Every engagement starts with a scoped build on your own material. First, we show you the platform on one of your situations.

What you already have

  • Playbooks and call scripts

    How you want it done

  • Policies and handbooks

    What people are allowed to say

  • Training programs and case files

    What you already teach

  • The situations your team reports

    Where it goes wrong today

PDF, DOCX, PPTX, TXT or MD, or a workshop with the people who own the situation.

What we structure

Your interaction model

People
Who is on each side, what they want, how hard they push
Knowledge
What your documents say, with the source kept
Moments
The situations, how they open, how they turn
Signals
What can be observed in practice: words, voice, face, body

Checked by code; authored layers approved by a person

Where it runs

  • Roleplay practice

    Flagship
    ScreenLive
  • Team view

    ScreenLive
  • Briefings

    ScreenIn development
  • EMORI

    RobotIn pilot
Diagram. How a PokaMind build moves from your material to the people who use it.

Customers, pilot partner, backers and press

Teams at ABB, BioInvent and Career 180 have used PokaMind. EMORI is in pilot at Badalona Serveis Assistencials. Backed by Vinnova and Almi. Featured in Dagens Nyheter. A KTH Royal Institute of Technology spin-out.

  • ABB logo
  • BioInvent logo
  • Career 180 logo
  • Evren logo
  • KTH Royal Institute of Technology logo
  • Vinnova logo
  • Almi logo
  • Dagens Nyheter logo

Start with the conversation that costs you most

Pick who is on the other side. Each situation is a starting shape. Yours is written from your own material.

Who is on the other side of the conversation

See all seven solutions

For sales enablement, customer success and service leaders.

The renewal that went quiet

Sales and negotiation

You

You are the account lead on a renewal that has gone quiet. The contract expires in three weeks and procurement has stopped replying.

The AI plays

Alex Renner

Procurement lead

Has been told to cut supplier spend this quarter, and has a cheaper quote already on the desk.

“I have a cheaper quote on my desk and a target to cut supplier spend this quarter. Tell me why we should renew.”

Alex Renner opens.

Example scenario. Yours is written from your own material.
  • The renewal that went quiet

    Reps run discovery, objections and renewals against a buyer who has a budget, a boss and an incumbent, then see where they held the line and where they gave it away.

    For: Account executives, Sales enablement, Customer success, Procurement teams

  • The call that is already angry

    Support and service teams practice de-escalation against someone who starts upset, then see how steady their pace and voice stayed while it happened.

    For: Service desks, Customer success, Retail and branch teams, Contact centers

  • The first real call

    New hires rehearse the conversations of week one before week one, so their first difficult call is not their first attempt at it.

    For: Enablement leads, Onboarding managers, Support and service teams, Graduate programs

See all seven solutions

Every engagement starts with a scoped build

The platform is the product. The scoped build is where our team works with yours to shape it around your organization: we structure your material, build what you need on it, and test every scenario before anyone on your team sees it.

Step

What happens

You bring

You get

Scope

What happens

We choose, with you, the one or two situations that cost you most, who is in them, and what good sounds like in your organization.

You bring

The situations, and the people who own them.

You get

A written scope you sign off.

Structure

What happens

We turn your material into interaction-ready data: the people, the knowledge, the moments and the signals that matter.

You bring

Playbooks, policies, training material, and the cases your team reports.

You get

Scenario briefs you can read and correct before anything is built.

Build and test

What happens

We build it on the PokaMind platform, in the languages your people use, and run every scenario ourselves before launch.

You bring

A reviewer on your side.

You get

Practice your team can open on the first day.

Run and review

What happens

Your people practice. You see where the team needs more of it. We review it against the scope with you and agree what to build next.

You bring

Your view of what changed on the floor.

You get

A review, and a plan to extend or hand over.

How we work, in full

Why we structure your material before we build anything

Generic AI does not know your customers, your policies or what good sounds like in your organization. Data is only ready for AI when it is ready for a specific use, so every build starts by structuring yours into one interaction model. We call the result interaction-ready data.

  1. People

    What it holds

    What it holds:

    Who is on each side of the conversation, what they want, and five dials for how hard they push.

    Built from

    Built from:

    Your roles, personas and customer types.

  2. Knowledge

    What it holds

    What it holds:

    What your documents say, split into passages that keep their source.

    Built from

    Built from:

    Playbooks, policies, handbooks, product documents.

  3. Moments

    What it holds

    What it holds:

    The situations, how they open, how they turn, and the techniques that work.

    Built from

    Built from:

    Your training material and the cases your team reports.

  4. Signals

    What it holds

    What it holds:

    What can be observed in practice: words, voice, face and body, described with 31 named communication styles.

    Built from

    Built from:

    The practice sessions your people take part in.

Checked by code. Authored layers approved by a person.

Diagram. The four layers of a PokaMind interaction model.

What a session records

  • What was said
  • Tone of voice and pace
  • Pauses
  • Expression
  • Eye contact
  • Posture and gesture

What it is designed not to infer

  • Emotions or mood
  • Inner states or personality
  • Honesty, intent or attitude
  • Who someone is, from their face or voice

When a signal was not captured, the record says so. It is never filled in with a guess.

See the platform

On a screen: our flagship solution

AI roleplay practice, built from your own material

An AI plays the other person, in character, from your playbooks and policies. Your people say it out loud. The analysis runs while they speak, and the written breakdown arrives when they finish, pointing to specific moments: what they said and how they said it.

Example session: a renewal that went quiet

Written for this page.

  1. 00:08AI, as Alex Renner
    I have a cheaper quote on my desk and a target to cut supplier spend this quarter. Tell me why we should renew.
  2. 01:52You
    Before we talk price, can I ask what changed on your side since the last renewal?
    • Words: a question, asked early
  3. 03:30You
    I just sort of wondered if maybe we could look at the timeline again.
    • Words: three qualifiers before the ask
    • Voice: pace picked up
  4. 04:41You
    If we hold the price, what would need to be true for you to sign this month?
    • Words: one direct ask
    • Voice: a pause held after it

When the session ends

Strengths

  • You asked before you priced.
  • You let the pause after the ask do the work.

Development opportunities

  • State the ask once, without qualifiers.

Questions to carry forward

  • What would you say if they asked for the discount again?

Then run it again.

Illustration. The kinds of moments a written breakdown covers, in an example session written for this page. Not a customer session and not a product screen. Timestamps are added for this illustration; the written breakdown has none.

The person who practiced gets

A written breakdown when the session ends: strengths, what to change, and questions to carry into the next run. The chance to run it again straight away.

Their manager sees

In PokaMind, each person's practice activity and session scores over time, never the conversation, the transcript or the written breakdown. PokaMind is built for development, not to rate, rank or screen people.

  • 9 languages, with Arabic in Egyptian or Saudi dialect
  • 31 named communication styles
  • 20 drill formats built from the same material
What a session records
On a robotIn pilot

The same practice, on a robot in the break room

Hospital reception staff rarely get time away from the desk to train. EMORI is a small robot that runs PokaMind practice by voice, in Catalan and English, where they already take their breaks.

In pilot at Badalona Serveis Assistencials, a public healthcare provider in Catalonia, funded by the EU ARISE program.

  1. 01

    Staff member speaks

  2. 02

    Session analyzed: observable signals only

  3. 03

    Published as ROS4HRI person topics

  4. 04

    Robot is built to turn, nod or settle

Diagram. Design of the robot's data path. In pilot: parts of this path are still being rolled out on the pilot robot.
See how EMORI works

Loading EMORI

It follows your cursor. Try a move below.

Interactive 3D model of the Reachy Mini robot EMORI runs on. Not footage from the pilot.

What teams at ABB, BioInvent and Career 180 say

Product, HR and L&D leaders at organizations that have used PokaMind practice.

While it felt a bit unusual talking to a screen during the training, the results and feedback have been excellent. It's definitely worth it. It has created a safe learning environment for our teams.

Emma Meurling

VP Human Resources, BioInvent International AB

Read the BioInvent story
Their analysis is deep and informative, drawing on learner responses, tone of voice, facial expressions, and more...

Ali Saleh

Head of Product, Career 180

PokaMind was a valuable and engaging learning experience that delivered clear insights for our team. The platform proved intuitive and full of potential in supporting modern learning needs.

Maria Iuliana Maxim

Operations Academy & Development, ABB

Questions buyers ask before they start

Straight answers on what we build, what it observes, and who sees the results.

See all questions

PokaMind is a human-facing AI platform that structures an organization's own playbooks, policies and practice conversations into interaction-ready data, then builds what its people need on top, starting with AI roleplay practice, on a screen or on a robot. In practice, an AI plays the other person in a conversation your team finds hard, such as a stalled renewal, an upset customer or a patient who has waited too long, and each person gets a written breakdown of what they said and how they said it when the session ends. Teams at ABB, BioInvent and Career 180 have used PokaMind. It is built by PokaMind AB in Sweden and was co-founded by Dr. Youssef Mohamed, who holds a PhD from KTH Royal Institute of Technology.

Every PokaMind engagement starts with a scoped build. You share the material behind the conversation: playbooks, call scripts, policies, training programs and the situations your team reports most. PokaMind structures it into an interaction model: who is on each side and what they want, what your documents say, how the situation opens and turns, and which signals are worth observing. One document of up to 100,000 characters can become a planned course of 1 to 10 modules, and code checks that every idea is covered exactly once before a person approves the plan. Every scenario is tested before your team sees it.

AI roleplay practice is a spoken conversation with an AI that plays the other person, in character, built from your material. While the person speaks, PokaMind analyzes observable communication across four channels: words, voice, face and body. When the session ends, they get a written breakdown that points to specific moments, what they said and how they said it, with strengths, what to change and questions to carry into the next run. They can run it again straight away. Practice runs in nine languages, and each session is described with 31 named communication styles, calibrated against the person's own baseline in that session.

A software product, with our team doing the first build. PokaMind is a software platform, and every engagement starts with a scoped build in which our team works with yours to structure your material and design the solution your people need. We build and test it on the platform, and your own owners can then edit and add scenarios themselves. Because the custom work is always delivered through the platform, what we build for you keeps running after the engagement ends, and a second situation builds on the material you have already structured.

No. PokaMind's practice analysis is built around observable communication: what was said, tone of voice, pace, pauses, expression, eye contact, posture and gesture. It is designed not to infer emotions, inner states or personality, and it does not identify anyone from their face or voice. A few older labels in the app are still being renamed to match. Under the EU AI Act, detecting a readily apparent expression such as a smile is not emotion recognition, while concluding how someone feels is. PokaMind is built for practice and development, not for rating or screening people.

PokaMind treats conversation data as sensitive. The platform is hosted in the EU on Google Cloud, encrypted at rest and in transit, and handled in line with GDPR. Camera frames are analyzed on PokaMind's servers, not on the learner's device. Speech transcription and language analysis run through AI sub-processors that may process data outside the EU; they and the transfer safeguards are listed in the data processing terms we provide during evaluation. The products described on this site are B2B only, for working adults 18 and over. PokaMind's information security program is aligned with ISO/IEC 27001 and maintained internally; it is not a third-party certification. Security documentation is provided during evaluation.

Start with one situation

Tell us who your people talk to

And what you already have. One situation is enough to start. We read what you send, then show you the platform running on it.

  • We look at your material before we talk
  • You see the platform on your situation, not a slide deck
  • A person reads every brief and replies by email

Send us your brief

Four fields are required. The rest help us prepare.

What do you already have? (optional)

We use these details only to reply to you. Privacy Policy