Hey, so I have been working with AI tooling for some time and I love your content. I have been a follower for a very long time now. For this project, I would love to get more details, but from what I understand, an AI system will not help you that much in the sense of recommendations, since you already have a system to get laptop prices and handle different cases to see if a laptop is at a good price or not. You can’t really account for all the different if cases in the world, so maybe this is where the gap is that an AI system can help with.
I would imagine this scenario: you are a software engineer, but you require certain hardware. Let’s say you need at least 48GB of memory for your use case.
You don’t really have a classification on your website for a software engineer that needs that much memory on a laptop, then the AI can handle that case.
It can search the DB for certain laptops that the user may find useful. It can also make a tracker, so a cron job or something that searches for that particular deal type and notifies the user somehow when there is a good deal. Or it can help the user look at other options, maybe things they may not have seen.
So I am thinking of an agent here. This agent can use MCP tools to get the data, maybe look at prices, send messages or whatever.
Then you would have your actual agent.
A pro tip: focus on evals. These should be your first priority if you want consistency and soundness of answers from the LLM.
So it really depends on your approach. I wouldn’t advise rolling your own LLM, that will be complicated, at least for a start.
What you should get correct is the harness. You probably have data and scrapers for the laptops and their price changes. You will have to define some rules on which laptops at which prices are good. You kind of already have that on your site, as you are flagging good and bad deals.
So start with the evals, then move to the harness. This should help you develop a good direction while developing your system, then you can start optimizing it.