Surveys your people answer by talking
Elenchus runs each survey as a short chat. The engine decides which question is current and when the survey is finished; the model helps ask and record, and nothing it says is kept until it has been checked.
From a question to an answer you can trust
Describe the survey
Say what you need to learn in plain words, and a draft comes back as questions you review and edit. Or write it by hand.
Publish it
Publishing freezes the questions, so nobody's answer is re-pointed at wording they never saw. A new question set is a new survey.
People answer by talking
Each person has a short conversation in their own language, on their phone, with follow-ups when an answer is thin.
Read what was said
Results come with the structured answers and the full transcript behind every one, so a finding traces back to a person's words.
The model is a collaborator, not the one in charge
A conversation is only useful if what gets recorded is what the person said.
The engine owns the survey
Which question is current, when the survey is finished and how many follow-ups are spent are decided by code, not by the model.
Answers are checked before they are kept
Everything the model records arrives through a schema-constrained tool call and is validated against what the person actually said.
Every turn is traced
Each model call is recorded with its tokens, cost and latency, and three hosted tiers fail over in order when one is down.
Free. Sign in and start
There is no plan to choose and nothing to pay. Signing in is the whole of signing up.
Free
For anyone with a Google or Microsoft account.
£0
No card, no trial that ends
- Sign in with Google or Microsoft, and your account is made on the spot
- Answer every survey that is open to anyone signed in
- Talk it through in any of 8 languages, on your phone
- Your answers are recorded as you said them, and checked before they are kept
Each company's answers stay in its own workspace
| Area | How it works |
|---|---|
| Company isolation | Every customer table carries its workspace, enforced by forced PostgreSQL row-level security. Production refuses to start on a database role that could bypass it. |
| Sign-in | Google with a verified address, or Microsoft. Your first sign-in creates a respondent account; an address that already has an account is never taken over by another sign-in. |
| What we store | Your email address, your name as the provider gives it, the time of each sign-in, and the answers and conversation of each survey you take. |
| Access | Five workspace roles. Only an owner or admin grants an analyst a survey, and every grant is recorded. |
| Retention | Responses are kept 90 days unless the owner sets otherwise. Expired answers and transcripts are purged, and each deletion is audited. |
| Audit | Account and access changes are written to append-only history in the same transaction as the change. |
Hear what your floor actually thinks
Start with one survey and one team. Answers are recorded as said, checked before they are kept, and traced back to the conversation they came from.