How it works

An interview with no AI in it, and one AI call that earns its place.

The site interviews you through a chat rail. Every answer is checked by deterministic rules — code you could read, not a model — and filed while you watch. Only after everything validates, and only after you choose to leave contact details, does one AI call write your answers into a brief. That is the entire system: five steps, in this order.

1. 01ArrivalBuiltThe edge reads the arrival — country, city, language — before any HTML is made, and the greeting comes back in your language.Nothing about you is written down. What was read is at /api/visitor, and it is the same profile the page itself gets.
2. 02InterviewBuiltFive questions in a chat rail, each answer filed visibly into its own document while you watch.There is no AI in this step. Every check is a rule written in code — a length, a shape, a threshold — and you can open devtools and confirm it.
3. 03ValidationBuiltEach answer passes deterministic gates before it is filed, and the set of answers passes a structural threshold before anything else may happen.Junk stops here. The model never sees an answer that has not already passed.
4. 04BriefBuiltAfter you choose to leave a name and email, one AI call — the only one in the system — writes your answers into a short brief, shown on screen.If the call fails or its output fails validation, you get a quote-based brief assembled from your own words instead. You always receive a brief.
5. 05Email and bookingPart-builtThe brief is emailed to you and becomes the description on the call you book.The email half is written: your brief is kept 30 days so a booking can carry it, and the email carries the link that deletes it sooner. Booking itself is not built yet.

Nothing you type leaves the browser until you submit, and nothing before that point is stored anywhere. The last step is only part-built — the booking half is not written yet, and this page will say so until it is. Try the interview