The SaaS Demo Request That Starts in Hebrew and Finishes in English

A founder sees more mentions of the company in Hebrew AI answers. The sales dashboard shows new English-language opportunities. It is tempting to draw a line between the two. First ask whether the measurement system could even recognize a journey that switched languages.

Nir Levi’s interpretation of his Israeli GEO research puts qualified enquiries and revenue first. Mentions and citations help a team investigate visibility. The October prompt study measured answers and sources; it collected no customer journeys. To make the commercial question answerable, a SaaS company needs a small set of records it can connect without guessing.

Follow one enquiry through the handoff

Give the Hebrew and English demo forms separate page identifiers and the same definition of a completed submission. Store the language of the first form and the language requested for follow-up in different fields. Ask an optional, open discovery question, such as “Where did you first hear about us?” Keep what the buyer said separate from a referrer recorded by analytics. A direct visit with no referrer is simply unknown.

Trace a test submission from each form to the CRM before reporting on leads. Check that repeated submissions by one person do not become two opportunities. Have sales define qualification in advance: for example, the company fits the target segment and the person has a purchase problem the team can address. Track qualified opportunities, closed revenue and the time between them by cohort. A dashboard can then say “buyers reported AI discovery” when that is what was observed, while still showing cases whose discovery path is unknown.

Study and archived answers: https://nirlevi.com/en/research/israeli-geo-hebrew-english/