diff --git a/README.md b/README.md
index 7ca9374..f063d81 100644
--- a/README.md
+++ b/README.md
@@ -8,16 +8,30 @@ If a bot can do your side of the conversation too, maybe the format was never do
 
 🤖↔️🤖
 
+## Demo / Video
+
+[![Screenshot](./screen.png)](https://workupload.com/file/hf7tT6qLjr6)
+
+(Klick for download.)
+
 ## The point
 
 Automated AI interviews are disrespectful to candidates. They waste your time, they reduce a conversation into a one-sided interrogation by a system that cannot actually listen, and they hide the fact that no one at the company cared enough to show up. Responder is a small demonstration that this format is hollow: if both sides can be automated, the "interview" is just two language models exchanging tokens.
 
 Use a real human. Or don't be surprised when candidates stop showing up as humans either.
 
+## The second point
+
+A job interview is not a one-way street — at least not one I want to drive down. I want to get to know the team too, hear what you're building, and figure out if we'd actually enjoy working together. If you ask me a technical question, you might get one back :-)
+
+As a freelancer I can afford to be picky about this. And honestly, so should you — the best hires come from conversations, not from interrogations conducted by a language model at 2 a.m. because it was cheaper than scheduling a call.
+
 ## How it works
 
 Responder captures the system audio of your call (what the bot says), transcribes it via Google Speech-to-Text, generates a response with Gemini based on your CV, and speaks the answer back through a virtual microphone that you select as the input device in your call app.
 
+It also has a memory, so the last 5? or so messages are taken into account.
+
 ## Requirements
 
 - Linux with PipeWire or PulseAudio (uses `parec` and a virtual sink/source)
diff --git a/screen.png b/screen.png
new file mode 100644
index 0000000..2e7c8a1
Binary files /dev/null and b/screen.png differ