Branching scenarios your learners actually finish.
Build role-plays, case studies and interactive stories on a visual canvas, no code. Share a link, send it to your LMS or play it with a class, and see exactly where people go wrong.
No learner accounts · Any browser · SCORM & xAPI · Free in beta
Try it — a two-minute sim
Step 1
“The order arrived broken. That’s the third time this year.” The customer is typing again. What do you do first?
01 — The problem
Slides and quizzes don't teach decisions.
People can pass a multiple-choice test on the escalation policy and still lose the customer on Monday, because the test never made them choose under pressure and live with it. A branching scenario does: one wrong reply and the conversation is somewhere else, and they feel it.
Most teams don't build them because the tools are either a developer project or a licence and a week of training. That is the part Skaz fixes.
Who builds with it
02 — Who it is for
Training & L&D
Practice the conversation, not the slide
Customer calls, feedback talks, safety drills. Build the branching version in an afternoon, ship it to your LMS and see every decision your team makes.
Teachers & tutors
Homework they’ll actually play
Language practice, case problems, diagnostics. Opened from a link with no accounts, or played by the whole class at once as a Jam.
Interactive fiction
Stories with teeth
Branch often, write loud. A cast with faces, sound, a wheel of fate and endings worth collecting, on your own domain.
Marketing
A demo people finish
Product tours and quizzes that branch on what the visitor says. Embed one in a landing page and read the drop-off.
How it works
03 — Three moves
Start a story
From a blank canvas or one of nine finished templates. Type the situation, add a character, an image or a question.
Draw the choices
A line from any choice to what happens next. Loops, dead ends, second chances, timers: all fair game.
Publish & share
Hit publish and grab a link, an embed or an LMS package. Nothing for players to sign up for.
Everything it does, on one page
04 — The toolbox
Write the story, give the player something worth playing, get it to people, and find out what happened. Every feature fits one of those four jobs.
01
Write
Build the story on a visual canvas.
- Visual branchingScenes and the choices between them on one canvas. Move whole branches, drop a scene into any line.
- Characters & dialogueA cast with a portrait for every mood, talking line by line like a visual novel.
- Variables & conditionsKeep score, remember choices, and route on what someone did twenty scenes ago.
- Questions mid-sceneAsk anything; the answer lands in a variable and in your exports.
- SoundAudio scenes, plus music and effects that carry across scenes.
- Templates & AI co-writerStart from nine finished scenarios, or describe one and read the draft.
02
Play
What the player gets on the other side.
- Choices against the clockGive a decision a timer; hesitate and the story picks for you.
- Wheel of fortuneThe player spins, the story follows. Weighted slices, no rerolls.
- Endings worth collectingNamed endings, and a mandala that fills in petal by petal.
- How others choseAfter each fork, the share of players who made the same call.
- Scenes that play themselvesA line can land and move on by itself, no button.
- Pick up where you left offClose the tab mid-story and come back to the same scene.
03
Share
Get it in front of people, wherever they are.
- A link, an embed, your domainPlays in any browser. Put it on your site, or on story.yoursite.com.
- SCORM & xAPIDownload a package and upload it to your LMS like any course.
- Jam: play as a classThe story on the big screen, the class voting from their phones.
- Your brand, not oursA player with no trace of Skaz, on Studio and Team.
- Sign-in & 18+ gatesAsk players to sign in, or check their age before the first scene.
04
Measure
Find out what actually happened.
- Statistics & drop-offCompletions, endings reached, and the block where people stop.
- Live sessionsWho is playing right now and what they have collected so far.
- Learner reportsOne row per person: attempts, finishes, endings, last answers.
- Exports & webhooksAnswers as a spreadsheet, the story as open JSON, each finished run posted to you.
- Teams & client spacesEditors and viewers on your stories, filed by the client they are for.
05 — Jam
The whole class plays one story
Put the story on the big screen. Students join from their phones and vote at every decision; the majority decides where it goes next. Like a quiz game, except the answers change the plot.
- Join with a six-digit code or a QR. No accounts, no apps.
- You run the room: open the vote, lock the door, remove a name. You can only break a tie, never overrule the class.
- While a vote is open, everyone sees how many voted, not for what.
- Up to 300 players in a room, and it counts as a single play.
482 913
The guard is asleep. The keys hang right above him.
06 — Characters & dialogue
Give your story a cast
Define a character once, with a name, a colour and a portrait for every mood, and bring them into any scene. The Dialogue block plays like a visual novel: one line at a time, faces changing with what they say.
- Mark one character as the player, and their choices read as replies.
- An angry customer looks angry; the portrait switches with the line.
- Change a character once and every scene they appear in follows.
Does anyone here know how to land a plane?
07 — Analytics
See where they fail
A scenario is a guess until someone plays it. Every story keeps a live list of sessions and counts what matters. No analytics setup: it is just there.
- Who started, who finished, and which ending they reached.
- The exact block where everyone else stopped.
- One row per learner for stories that ask players to sign in.
- Answers as a spreadsheet, or posted to your webhook the moment a run ends.
Sessions
68%
Reached an ending
4
Endings found
The refund call
Where they stop
A co-writer who never takes the pen
08 — AI co-writer
Staring at an empty canvas with a policy document open in the other tab? Describe the scenario you need and the co-writer drafts it, scenes, choices and the lines between them, right inside Studio. You read the draft before it lands, and every block stays yours to rewrite.
Ask in plain words
"A refund call that goes wrong three different ways, one of them the rep’s fault." That is the whole prompt.
Read the draft first
The co-writer streams back scenes, choices and transitions as a draft card. Nothing touches your canvas until you say so.
Apply and keep editing
Accept it and the blocks appear on the canvas, wired up and ready to rewrite. A first draft, not a black box.
Don't watch a demo. Play one.
09 — Examples
How it compares
10 — Comparison
These are all good tools, and each of them can build a branching scenario. They differ in what it costs you to get one in front of people: syntax to learn, files to host, and whether anything tells you what happened afterwards.
Other tools change; check their sites before you decide. Pricing is left out here on purpose — ours is just below, and quoting someone else's price is a good way to quote it wrong.
11 — For schools
Nothing to review, because nothing is collected
Students open a link, or join a Jam with a code, and play. No account, no email, no real name: nothing personal about them reaches us unless you deliberately ask for it inside the scenario. That is what makes this GDPR-friendly by default, and it is why no education records are disclosed under FERPA: none are provided.
Good questions
13 — FAQ
No. Skaz is a fully visual editor: you place scenes and draw the choices between them. If you can write the conversation, you can build it here.
Yes, that is what a Jam is for. Put the story on the big screen and students join from their phones with a code or a QR, no accounts. At every decision they vote and the majority decides; you only break ties. Up to 300 players in a room.
Yes, and it is built to keep you out of a privacy review. Students play from a link with no account, no email and no name, so nothing personal about them reaches us: GDPR-friendly by default, and no education records are disclosed under FERPA because none are provided. A scenario only ever collects what you deliberately put in it. Details are in the privacy policy at skaz.io/privacy, and privacy@skaz.io answers school vendor reviews.
Yes. On Studio and Team, download any story as a SCORM 2004 or xAPI package and upload it like any other course. Detailed results (endings, answers, drop-off) stay in Skaz, in the statistics and learner reports. If your LMS takes HTML, a one-line embed works too.
Yes. Answers export as a spreadsheet, a webhook can post each finished run to your own service, and the story itself (every block, link and variable) downloads as open, documented JSON. Importing a story back from JSON is not there yet.
Yes. Build for your clients, charge for it, and keep what you make: we claim no ownership of your scenarios. File each story under its client, invite colleagues as editors or viewers, and on Studio and Team the player shows no trace of Skaz.
Yes. Each story has a live list of sessions and statistics: completion rate, which endings were reached and the block that loses the most people. For stories that ask players to sign in, learner reports give you one row per person, with their consent. Everything exports as a spreadsheet or posts to your webhook.
The whole toolbox is live: branching, characters and dialogue, variables, timers, the wheel, sound, the AI co-writer, Jam, publishing, custom domains, embeds, SCORM, statistics and reports. Beta means we are still polishing and shipping fast, and everyone who joins now keeps a free Creator plan forever as a thank-you for testing early.
No. It drafts a branch when you ask for one and shows it to you before anything lands on the canvas. Ignore it and Skaz is a plain visual editor.
Yes. Mark the story adult and Skaz checks the reader’s age before the first scene. You can also pick categories and require sign-in for any story. What may go behind that check is set by the content rules at skaz.io/rules: adult themes yes, pornography no.
No card. No catch. Beta access.
It's totally free(for now)
Join the beta and keep the Creator plan forever.