Interactive scenarios for behavioural research
Turn your vignette into a situation participants experience.
Build it visually. Run it inside your survey.
From vignette to experience
The same research question. A different way to ask it.
The figures don't match the ones you sent me.
What do you say?
Flag the discrepancy now Wait until the reviewThen I'll put it in the record before we meet.
An illustrative playback. The timeline holds at the choice, then follows the selected branch.
A room. A colleague. A conversation that asks something of you. Your participant enters the situation you designed.
You choose the setting, the cast, the dialogue, and when each moment happens.
The scene pauses at a choice. What happens next can depend on their answer, their condition, or an earlier event.
Watch the playhead hold at the interaction, then continue into the selected branch.
Choices, timings, and signals become a dataset, joined to the identifiers your survey already uses.
One row per run, with a timestamped event log when you need the detail.
Arrange the setting, cast, dialogue, and decisions on a visual timeline. See the whole path before a participant does.
Pick a setting, put characters in it, write what they say and what you want to ask, then lay it all out on the timeline. What you arrange is what your participants get.
Hand your script and our preparation guide to whichever AI you use. Drop the study file it returns into Workframe, read it over, and carry on editing by hand.
Build visually. Place clips on five tracks. Preview the scenario as you work.
Already have a script? Use your AI with our preparation guide, import the study file, then review and refine.
Read the authoring guideStart with the included library, or bring your own photographs and characters. The stimulus stays in your hands.
PNG, JPG, or WebP. Upload once, reuse across studies.
Sources up to 40 MB. Your account library holds 500 MB and up to 1,000 files. Workframe can resize and convert on upload, or keep your original pixels. Replace a source and clips using it follow.
Inside your existing workflow
Keep consent, randomisation, and survey items where they are. Embed the scenario as one step in your questionnaire.
Q7. Take part in the situation below, then continue.
Dr. ChenThe figures don’t match the ones you sent me.
Flag the discrepancy now
Wait until the review
Copy the setup Workframe generates. Answers save as embedded data, and Next waits until the scenario finishes.
Participant and session IDs travel into your export, ready to match with the submissions you already have.
The scenario can run anywhere a page can be embedded. Automatic answer-saving depends on the host. Other platforms are not yet tested by us; pilot the complete flow before collecting data.
Download your complete dataset as CSV or JSON. Keep the choices, conditions, timings, and IDs together.
Download an example CSVPublishing freezes the study. Every run records its version, so you can cite what participants actually saw.
Participant summaries and detailed event timelines. Integrity checks flag missing fields.
Test runs stay out by default. Survey identifiers pass through as given; missing IDs stay empty.
Draft for free. Publishing is free throughout the pilot. After that, pay once per published study, with revisions included.
Billing is not switched on during the pilot, and we will tell you before that changes.
Both are on the list. We are not putting dates on them, because a date we miss is worse than no date at all. If either one would settle it for your group, say so in your access request; what we hear shapes the order we build in.
Data handling, access, retention, and deletion, documented so your team can make an informed decision.
They open the study, complete the scenario, and leave. Any session token is stored scrambled and expires.
The complete list of third parties that process your data on our behalf:
There are no others. No analytics, email, advertising or tracking vendor touches participant data. We will notify pilot accounts before this list ever changes.
Responses, event sequences, timing, and the identifiers your survey or recruitment tool passes in. Those identifiers (a Qualtrics response ID, a Prolific PID) are stored as given and appear in your export, because joining a run to your survey data and approving payment is what they are for. Separately we derive a one-way participant key from them, which is what detects repeat attempts. Workframe never asks a participant for a name, an email address or an account, and never receives one unless your own survey passes it into one of those identifier fields, so pass in a study-scoped ID, not a direct identifier.
Access to a project and its results is limited to the account that owns it. Researcher sign-in is handled by Clerk; every authoring request is independently verified server-side before it reaches project data. Everything runs on Cloudflare's infrastructure, so your study data and uploaded media sit with a single provider; we will supply the signed hosting and durability details on request.
Your dataset is downloadable as CSV or JSON at any time, in full, with no row cap and no request needed.
From your account you can delete a single study and its collected data, or delete your entire account and everything in it.
No advertising or marketing use of participant data. No selling or sharing with third parties. No tracking pixels or third-party analytics on the participant surface: an iframe inside your survey should not carry anyone else's beacons.
Workframe is a data processor for the participant data you collect. You remain the controller and the person your IRB approved. The full documents: Privacy Notice, Data Processing Agreement, Subprocessors and Cookies and storage.
A few labs at a time
Tell us what you want to run. We’re opening pilot access by invitation, with direct help from the people building Workframe.
No self-serve signup yet. We reply personally, usually within two working days.
hello@workframeapp.comNo, but it is the path we support best. Workframe gives you the setup pieces to paste into Qualtrics, stores the recorded answers there, and keeps the survey from moving on before the scenario finishes. Other survey tools can show the scenario too, but automatic answer-saving depends on what that platform supports.
No. Building, publishing and reading results all happen in the browser. Survey setup is copy and paste: Workframe prepares what Qualtrics needs, and you do not edit it.
No. Your platform keeps consent, the survey items, randomisation and payment. Workframe is one step inside that survey, the step where the scenario plays. We haven't built survey items, panels or analysis, and we don't plan to.
Yes, and it means you can cite the stimulus itself instead of describing it. Every published version keeps a stable identifier, and that identifier is what your placement URL points at, so a replicator runs exactly what your participants ran. Quote it in your methods section.
Nothing, for participants already running: they are on a frozen published version. Your edits sit in the draft until you publish again, which creates a new numbered version. Each run records the version it was on.
Upstream, in your survey, by whatever mechanism you already trust. Workframe reads the condition and assignment values your survey passes in and shows the content whose rules match. Your randomisation stays exactly where it is.
Per study, once. Whether it collects 40 responses or 4,000, the fee is the same, and republishing a revision never costs again. A new study means a new project, with its own participants, dataset and results page. Drafts are free; you only pay at the moment you publish, and published data stays exportable.
The scenario renders on a fixed 1920 × 1080 stage that scales to fit, so it displays and it works. It hasn't been optimised for small screens, and dense dialogue is harder to read there. If a chunk of your sample will complete on a phone, pilot it on one first. The authoring tool is desktop-only.
Collected data is retained for as long as your study exists, on managed Cloudflare infrastructure with their durability guarantees. It is not a substitute for your own archive: export a copy at the end of collection.
Email us. During the pilot you are writing to the people who built it, and a study that is live with real participants goes to the front of the queue.