Property
“2 rooms near the metro under 3k” → location, price, size → listings
zero-result rate · listing clicks · enquiries to sellers
Your customers search in sentences and your catalogue answers with filters. I build natural-language search and recommendations on your catalogue, tested on real queries. Recommendations can run on the TasteRay API, which I develop as CTO.
Who it’s for: For classifieds, marketplaces, shops and services with a large catalogue: property, products, content, events, jobs.
If customers search by product name and your current search handles that well, new search will change little. I check that in the test before anything is built.
A user types “two bedrooms near the metro under 3,000” or “a gift for my dad who loves cooking”, and the search engine looks for words. Some queries return nothing, others return a list that misses. In 2023 I shipped mieszkAI at Morizon and szukAI at Gratka: the first natural-language property search in Poland, over 220,000 listings. I can build something similar for you.
The implementation works if you have:
“2 rooms near the metro under 3k” → location, price, size → listings
zero-result rate · listing clicks · enquiries to sellers
“a gift for my dad who loves cooking” → intent and budget → products ranked with reasons
search clicks · add-to-cart · returns
“something light for tonight, no violence” → mood and preferences → recommendations from the TasteRay API
clicks · time to choose · return visits
from €3,500net · test
The starting price covers the five-day test on one catalogue in one language. Implementation on one search or recommendation surface is quoted after the test, as a fixed fee for a fixed scope.
Tell me which catalogue you want to search and how many items it has. Within 1–2 business days I’ll reply with a price, or with the questions I need answered to set one.
Or by email: michal@jaskol.ski
As of: November 2026
Because I know it from the inside: I develop this engine as TasteRay’s CTO. Every recommendation comes with an explanation of why it fits, and the user’s preferences are sent with the request, so you don’t need months of click history. I co-founded TasteRay, so I’ll say it plainly: if the test shows another engine or your own solution works better, that’s what I recommend.
Not to start. Natural-language search works on the descriptions in your catalogue, and TasteRay recommendations work on what the user says about their preferences. Click history helps later, when tuning the ranking.
First from the test: the same set of real queries, results judged blind by your expert. Then from an A/B test on part of the traffic. A better test score doesn’t guarantee higher conversion, so the decision to scale is made after the production test.
I calculate the cost per 1,000 queries before implementation and set a cap. Part of the traffic is served from cache and cheaper models; a more expensive model only goes where it improves the result.
Your team. The code lives in your repository, with documentation and the test set you can use to check every later change.
You keep working search, the test set and the A/B result. When new search exposes messy catalogue data, the next step is often an Agentic Workflow Sprint, for example attribute enrichment or listing moderation.