How to do this: RECOMMENDED
Hi! In this series, I’m sharing daily-basis wisdom about simple yet underestimated things that managers and owners stumble upon. Some get stuck on the logic; others battle with retention and UX
Today’s idea: The logic of the “Recommended” function. For free
As always — JUST COPY ME and you’ll prosper. The logic, side cases, and architecture are already considered
What is it?
It’s a feature where a user sees an entity (product, content, service) suggested specifically for them
Why do you need it? If you’re an e-commerce store or a content platform, this is a must-have
Why? Retention and TTV (Time to Value). It keeps users engaged and increases the average check
The Core Logic: Matching vs. Similar
Here is where most people fail. Let’s take e-commerce as an example:
*Result:* The user is confused and keeps browsing
*Result:* A satisfied customer and a bundle proposal that hits a 10/10 NPS
The Rule: Focus on what *matches* the current need, not just what *looks like* the current item. Think about the user's intent
*Example:* A book about a single mom in her 30s. Don't just recommend another "fiction" book. Recommend a book about building a home business or psychological self-help. See the pattern?
Implementation & UX: The "Side Quest" Rule
1. Placement: The "Recommended" section is a side quest
Never put it in the way of the core user flow. Place it when the target event is either finalised or nearly finished (e.g., in the cart or right after a purchase). Keep your core metrics safe
2. UI: Keep it simple. Use a carousel with the same entity components but under a different title. Give the user an option to choose without leaving the page
3. The Database (Code): Less code = less bugs
1. Reusable Components: Use the same UI card but with different props
2. Joint Tables: Don't mess up your main product table. Create a separate table for "Recommendations" that maps Product IDs to Recommended IDs with priority parameters
Gaps and Forgotten Moments
Nowadays, building a SaaS over a weekend is easy, but proper testing, UX, and CustDev are often forgotten
This logic is built on 8+ years of experience
You can just copy this, or ask me to help. I’ve been doing this for a long time
