Guided entry points
Topic shortcuts give users a starting point, while the message field supports questions in their own words.
Spinio AI Recommendation Platform
We built the web and mobile experience, recommendation logic, knowledge layer, and structured query engine needed to move from a user's intent to relevant catalog options.
AI recommendationsWeb & mobile
20,000
items in the recommendation catalog
1,000
providers represented
1
custom text-to-SQL recommendation engine
The Starting Point
The client saw an opportunity to help consumers navigate a catalog of around 20,000 items from 1,000 providers. The experience needed to understand what a user wanted, apply preference and catalog data, and make the result easier to explore than a conventional filter interface.
Personalization Needed Real Product Logic
A generic model could produce plausible suggestions, but useful recommendations had to be tied to the available catalog and the signals the product knew about each user.
Large catalog structure
The system had to search and compare thousands of available items and providers rather than rely on model memory.
Preference-based ranking
User preferences and entity tags needed to influence which results appeared and why they were relevant.
Controlled product knowledge
Knowledge-base answers and live-service information had to remain connected to the product's actual sources.
Our Role
We designed the recommendation approach, trained the text-to-SQL engine, built the web and mobile products, connected the knowledge and live-service layers, and shaped the experience around personalized discovery.
Define the recommendation logic
We connected natural-language intent to structured catalog data, preference signals, and entity tags.
Build the complete product
We delivered the recommendation experience across web and mobile rather than stopping at an isolated AI service.
Connect the product layers
We brought catalog retrieval, knowledge-base answers, and the user interface together in one recommendation experience.
From User Intent to Catalog Recommendation
The workflow uses the conversational request to create a structured path through the catalog.
1. Understand the request
The product identifies what the user is looking for and the context that should shape the result.
2. Translate intent into a query
The text-to-SQL engine converts the request into structured retrieval against the available data.
3. Apply preferences and tags
User signals and entity attributes help rank the catalog options for relevance.
4. Return an explorable result
The recommendation is presented inside the product with the information needed to continue discovery.
A conversation built around the catalog
The interface brings guided discovery and open-ended questions into one chat experience. Actual screenshots from the public product are shown below.
A responsive chat interface
The public web experience adapts the same conversation model to a smaller screen, with a compact header and horizontally arranged topic shortcuts.
The Product Beyond the Recommendation
The recommendation engine works as part of a larger consumer product with the data, knowledge, and interfaces required to support discovery.
Web and mobile experiences
Users can access the discovery flow through products designed for both platforms.
Structured recommendation engine
Text-to-SQL keeps recommendations connected to the catalog rather than generic model knowledge.
Knowledge base
Controlled content supports questions that need more than a ranked list of items.
Live-service connectors
External service information can enter the experience where the recommendation requires it.
The Outcome
We delivered the recommendation platform across web and mobile, with a catalog of roughly 20,000 items and 1,000 providers. The build combined preference logic, structured retrieval, and product knowledge in one experience. These figures describe the catalog covered by the build.
What This Proves
Recommendation products become credible when AI is grounded in real catalog structure, preference data, and product logic. A plausible suggestion is not enough if the system cannot explain where the available options came from.
Planning a recommendation product?
We can help connect conversational intent to real catalog data, preference logic, and a complete discovery experience.
Product walkthrough
Inside the product
1 / 2
Actual product
Actual product
01
The public desktop chat offers topic shortcuts and a free-text question field. Actual screenshot captured September 7, 2026.
What the client says
On working with Adamant Code to build the product.
“It felt like working with a true partner and not just a development agency.”
Talia Tsadick
Executive
Have an AI product idea you can't build alone?
One strategy call. Bring the idea and we'll tell you honestly what it takes to build it.
Book a Strategy Call