Use a consistent record for each observation: ID, date, product, source, buying situation, exact words and outcome. Store your interpretation separately. A lost enquiry because a school offered a general course could indicate a mismatch with the buyer’s goal. The record should show the customer’s words and identify the inference.
CRM records and lost deals
Review the product, deal stage, payment, decision time and reason for loss. A salesperson’s note that something was “too expensive” could mean a budget shortfall, unclear scope or a comparison with a different service. Include purchases, lost deals, cancellations and repeat enquiries. Keep records from different products, periods and markets distinct when the conditions explain a difference.
Website analytics
Compare sources, devices, pages and configured events. A visit ending on the pricing page does not establish why someone left. In Russia, Yandex Metrica’s long-term interests report (Russian) estimates interests from online behaviour, and its coverage can differ from other reports. For UAE projects using GA4, begin with observed acquisition and site events and follow up on the reasons separately. Website visitors represent only the people you have already reached.
Search terms
Terms such as “English for a job interview”, “English for work” and “online conversation practice” can help frame research questions. For a Russian-market study, use Yandex Wordstat (Russian), recording region and device filters. For the UAE, use Google Keyword Planner with the relevant locations and languages. Search estimates measure activity on the selected platform. They do not give you the number of potential buyers.
Reviews and public discussion
Save the review and its URL. The same complaint about scheduling can mean different things for a shift worker and a parent. For Russian-market research, monitoring tools such as Brand Analytics can help locate public discussions. Reviewers may differ from other customers, and repeated posts may distort apparent frequency.