From a problem to a concept in minutes
Plain words in, a structured picture of the system out: what connects to what, and what it would change.
Tesryn Lab · Events & sales
Tesryn Signal
Scan a code, describe a problem, and watch the system that solves it take shape.
In use at events First built for Tesryn, at events and in meetings · 2026
01 — What it is
A stranger scans a code with their phone and describes a problem in their own words. Within moments they see it understood, field by field, and a system concept assembles in front of them, on their phone and on the big screen. They correct anything that's wrong, and leave with a private link to their concept. The person running the booth sees every conversation and follows up the same day.
The moment it earns its keepA stranger at a trade show stops for ninety seconds and leaves with a sketch of their own system, and Tesryn leaves with a conversation worth having.
What it proves we can do
02 — What it can do
Four things it does.
The understanding is correctable
What it heard is shown as named fields a person can fix, and the concept follows the correction.
Several screens, one room
Phones, a showcase screen and tablets people type into, with one view that shows who is where.
Follow-up drafted, sent by a person
Every visit leaves a follow-up ready to read, change and send from the operator's own email.
03 — How it connects
What it shares with the rest of the Lab.
The same things we know how to do keep coming back in different industries. This is where this one sits: what it proves, and what else proves the same thing.
A person approves before it's real Automation can prepare anything and finish nothing. The last step is always a person. Also proved by Podcast Maker, CAD Workbench, Reconstruction Research Studio, Application Engineering, Command Center, Tesryn Launch.
Plain language, no training day One action per screen, words the user already uses, and errors that say what to do next. Also proved by Reconstruction Research Studio, Part Finder, Referral Engine, Command Center, Tesryn Launch, Referral Platform, Insurance-aware Intake.
One conversation, many screens A phone, a big screen and a tablet showing the same moment, live, without anyone operating them. Also proved by nothing else, yet.
Only what's needed, deleted on request The least data that makes the thing work, with forgetting built in rather than promised. Also proved by Referral Engine, Referral Platform, Insurance-aware Intake.
Say it, see it, approve it, publish it Changes described in words become structured edits with an exact preview and an exact undo. Also proved by Referral Engine, Command Center.
The whole map — six sections, and everything that proves them.
04 — What it's held to
- No generated price, date or guarantee ever reaches a screen. Amounts are typed by a person.
- A visitor's words stay private to them and the operator, and they can ask for them to be forgotten.
What it isn't. Not a chatbot, and not a quote. It's the first conversation, made visible.
05 — The recipe stays in the lab
We'll tell you what it can do. Not how it's built.
Yours would be your own build, on your systems, and you'd own it outright: code, documentation, no lock-in. What we bring to it is the practice — we've solved this shape of problem before, so you're not paying for the first attempt. The method stays ours. And if what you need isn't here at all, that's the usual case — it's how every skill on this page started.