13
33 Comments

I built an AI that finds the right product for your customers

Hey IH! I'm Nicola, founder of LimTech and AI developer from Italy.

While buying and searching for products online, I kept noticing
the same problem over and over: ecommerce stores losing customers
simply because they couldn't find the right product. Sometimes the
search bar doesn't work properly, categories are unclear, or you
don't even know exactly what you need to solve your problem.

So I decided to fix it. Here's what I built, why, and honestly —
how hard it was.


We've all been there.

You land on an ecommerce store looking for something specific.
You type in the search bar. You get hundreds of results but maybe
none of them is what you're actually searching for. You filter,
scroll, filter again. Ten minutes later you give up and leave.

Or worse — you find something close, but you're not sure if it
fits your needs. There's no one to ask. You're forced to send an
email or call. If you're lucky there's a chat that says "we'll
reply within 24 hours." So you close the tab — because you wanted
to buy right now, not tomorrow.

This frustrated me every single time. Not just as a customer,
but as someone who builds tech for businesses. I kept thinking:
why is this still a problem in 2026?

The technology to solve it exists. But nobody had applied it
properly to small and medium ecommerce stores.


So I started testing. And after months of work, I built Nexus.

Nexus is an AI assistant that reads your entire product catalog
via API — prices, availability, variants, categories — and helps
customers find exactly what they're looking for through a natural
conversation.

Customer: "I'm looking for a running shoe under €100, waterproof, size 42"
Nexus: here are the 3 products that match, with prices and
availability. Which one interests you?

No more endless scrolling. No more lost customers.
Like talking to a real shop assistant — but available 24/7.


The honest part: it was much harder than I expected.

I want to be real about this, because I see too many "I built X
in a weekend" posts. This took me several months, and there were
moments I genuinely wasn't sure it would work.

Problem 1: The server never slept

The first big challenge was automation. Nexus needs to update
its knowledge every night automatically — reading new products,
prices, availability from the catalog. Setting up reliable
server-side automation that actually runs at 2am without failing
was way more painful than I expected. Cron jobs, error handling,
retry logic, monitoring — things that sound simple but eat weeks
when you're building solo.

Problem 2: Hallucinations nearly killed the project

This was the real nightmare. Early versions of Nexus would
confidently recommend products that didn't exist, invent prices,
or suggest sizes that were out of stock. For a generic chatbot
that's annoying. For an ecommerce assistant, it's catastrophic —
imagine a customer ordering something the AI made up.

I spent weeks on this. The solution was moving to a full RAG
(Retrieval-Augmented Generation) architecture — instead of letting
the AI generate answers from general knowledge, it can only respond
based on the actual catalog data it has retrieved. If a product
doesn't exist in your store, Nexus says so clearly and suggests
real alternatives.

Zero hallucinations. Every answer is grounded in verified data.

Problem 3: Token costs almost made it unviable

The third wall I hit was cost. Every customer conversation uses
tokens — and with a large product catalog, the early versions were
sending huge amounts of data to the LLM with every single query.
The costs were unsustainable.

I had to completely rethink how Nexus retrieves and filters
information before sending it to the model. Better vector search,
smarter context windowing, aggressive filtering before the LLM
even sees the data. It took weeks of optimization to get the cost
per conversation to a level that made business sense.

Looking back, these three problems taught me more about building
real AI products than any tutorial or course ever could.


Where we are now

  • Live at limtech.ai — you can try the demo right now
  • Two plans: Web (reads your website content) and Ecommerce
    (full catalog API integration)
  • Compatible with Prestashop, WooCommerce, and other platforms
  • Live in 24 hours from setup, no technical team required
  • GDPR compliant, servers in Europe

Currently onboarding our first customers and actively looking
for feedback from ecommerce store owners.


What's next?

Honestly, this is the part where the real work begins.

The product works. The product is live. But building something
and selling it are two completely different skills — and I'm
starting the second one now.

Right now I'm focused on three things:

  • Finding the first paying customers

  • Growing organic search. I've spent the last weeks optimizing
    limtech.ai for SEO — building the right pages, fixing technical
    issues on the server (more painful than expected), and trying
    to rank for the right keywords. Early days but the foundation
    is there.

  • Learning to sell. After months of heads-down building, I now
    have to get out there and talk to real customers. If you've
    been through this transition from builder to seller, I'd love
    to hear how you approached it.

If you have suggestions, feedback, or just want to try the live website — I'm here in the comments.

What's the hardest part of going from "product is ready"
to "first paying customer"? Would love to hear your experience.

posted to Icon for group Artificial Intelligence
Artificial Intelligence
on August 5, 2026
  1. 1

    The same challenge faced by every fellow founder. Building and selling are two different skills.

  2. 1

    Interesting concept. Choice overload is a real problem these days. If AI can actually narrow the options without feeling biased, that's a pretty valuable experience. Curious how you're measuring whether the recommendations are actually helping users decide.

  3. 1

    I really liked your point that building and selling are two different skills. I think a lot of founders assume that once the product works, growth becomes a traffic problem, when it's often an activation problem.

    As you start onboarding your first customers, I'd pay close attention to where they get stuck between "this looks interesting" and "I can't imagine running my store without this." Those conversations, onboarding friction points, and even the questions people ask before buying will probably teach you as much as analytics.

    Looking forward to seeing the before-and-after conversion numbers once you've got a few stores using Nexus. Wishing you the best!

  4. 1

    I like the server never sleeps problem - the next day runs for me and catching up or putting out agent fires is always fun lol !

  5. 1

    The RAG approach to keeping product recommendations grounded is especially interesting. GeekyAnts has also been working around AI product engineering, and this is a good example of why the retrieval layer matters as much as the model.

    1. 1

      Thanks Arjun for the comment. Yes RAG approach was exactly the way to reach my target, even if is not easy to set up

  6. 1

    Really enjoyed the transparency in this post, especially the part about hallucinations and token costs. A lot of AI product posts skip those challenges and make it sound like everything worked on the first try.

    I also think your point about "building something and selling it are two different skills" resonates with many founders. That's probably the hardest transition.

    One question: have you considered tracking the percentage of conversations that end in a product click or purchase? It seems like that metric could become one of your strongest selling points if you can show Nexus improves conversion compared to traditional search.

    Wishing you the best with your first paying customers! Looking forward to seeing how the product evolves.

    1. 1

      Thanks Aman for your comment! Yes i considered to use a metric before and after introducing the Bot, because for sure a customer will want to know if this service worth the investment or not. If there is no difference it will be difficult to justify the cost, then i can track interactions with the bot.

  7. 1

    This is the right problem to be working on. The pattern I keep seeing from the visibility side: AI assistants only recommend products they can describe confidently, and confidence comes from consistency. If your product data, pricing, and positioning match across your site, your reviews, and every directory or marketplace you appear in, the model treats you as a safe answer. One inconsistency and it hedges or skips you entirely. Curious how you handle that on the data side: do you normalize the product info from merchants yourself, or rely on what they feed you?

    1. 1

      Thanks for your comment Jonathan! I have 3 ways to interact with datas: manually, automated using API selecting which datas to use, hybrid using API and choosing / adding informations on request of the customer. In this way i can cover all kind of websites, it depends on what the customers has already available and how much is accurate.

  8. 1

    This is a great premise I think

    1. 1

      Thanks for your comment!

  9. 1

    Nobody buys an AI product finder. They buy a conversion number, so pick five stores on one platform, install it free for 30 days, and measure one thing: revenue from sessions that used site search, before and after. I started Henson Group doing free migrations for months and those companies became my first paying clients, so I would park the SEO work until you have those five numbers, because a case study with a percentage sells this and a keyword ranking will not.

    1. 1

      Many thanks for your opinion! Is a really good advice, yes i'm agree with you because people want numbers or real returns on their own business, then if they try (even for free initially) they could become customers.

  10. 1

    Really enjoyed the honest breakdown, especially the part about hallucinations and token optimization. I think many people underestimate how much engineering goes into making AI products reliable, not just intelligent. Good luck with getting those first paying customers!

    1. 1

      Thanks so much for your comment! Exactly, a developer should think also to the cost of the final service because if is too high the customer could complain about it, is crucial

  11. 1

    So amazing and educative

    1. 1

      Thanks for your comment! I tried to describe all my feelings on this work, like everyone who think and develop an idea there are good and bad time, noghing is easy, i thought was nice to show to everyone this process

  12. 1

    The ecommerce store owner discovery challenge is really the funnel problem in disguise. You built for what you thought the problem was (product search), but customer acquisition through cold outreach feels like spam to them because you're broadcasting without proof.

    What if the first customers come from places where store owners already hang out solving this problem? Shopify forums, theme communities, WooCommerce subreddits. You're still cold-reaching but the signal is different - they're already in the mindset of fixing catalog issues, not being sold to by random people.

    The conversion gap arises from approaching buyers in broadcast mode (here's my solution) vs showing up where the buying signal already exists (here's how others solved this in your community).

    Keep pushing on this - the product is solid but customer discovery shapes everything.

    1. 1

      Totally agree, thanks for your comment and suggestion! I will have a look on communities of CMS where maybe there could be already some potential customers

  13. 1

    I enjoyed reading this because you talked about the hard parts instead of making it sound effortless.

    The section about hallucinations stood out the most. I think many AI products underestimate how quickly trust disappears when the system confidently gives an incorrect answer. Moving to a RAG-based approach seems like the right trade-off for an ecommerce assistant where accuracy matters more than creativity.

    One thing I'm curious about is your onboarding process with store owners. Once they see Nexus working, what has been the biggest reason they don't move forward? Is it trust, integration effort, pricing, or simply that they don't yet feel the pain strongly enough?

    I think the answer to that question could end up shaping your go-to-market strategy more than any feature at this stage.

    Wishing you the best with your first customers.

    1. 1

      Thanks for your comment!

      I'm totally agree with you, at the early stage i made several test but the bot didn't reply always very well, had several hallucinations and i understood was the biggest weak, i had to fix. If the customer can't get the right answer is an useless tool, then my main focus was about it. There are several way to improve but i have to consider also speed of answers (no one want to wait too long) and costs (every question / answer costs token), then also find the right balance had been quite hard.

      About your question i can't reply now because i just released a few weeks ago, then i hadn't request yet. When i will have some request i can understand better if there will be problem and i will find the way to fix (if price, trust or whatever it is).

      Now i'm searching the way to promote it and let people discover the tool

      1. 1

        Thanks for the detailed reply. I think you're approaching it the right way by solving reliability before trying to scale distribution.

        One thing I've been realizing recently is that finding people isn't usually the hardest part—finding the people who already feel the problem is. Promotion gets you attention, but conversations with the right customers are what really shape the product.

        It'll be interesting to see what patterns emerge once you start speaking with your first ecommerce customers. Those conversations often reveal things we never expected while building.

        1. 1

          Yes, i really will care about first conversations and see request from customers.

  14. 1

    Hello Nicola, I could relate to the last part of your post the most.

    Building the product has actually been the easier part for me. I'm only at the beginning of promoting and selling my own products, and I'm already realizing it's a completely different challenge. Writing code has clear answers. Marketing and sales feel much less predictable, and there's a lot more trial and error.

    I also appreciated that you shared the problems you hit along the way instead of making it sound like everything came together effortlessly. Those are the kinds of posts I find the most useful.

    Good luck with finding your first customers - I hope that part starts gaining momentum soon.

    1. 1

      Many thanks for your comment Tatiana, i really appreciate. Yes the "easiest" part is the creating part maybe because we have already in our mind the target and what we want to obtain, then everything is on us, but about finding customers depends not only from you then is more difficult (especially at the beginning)

  15. 1

    The shift from building to selling is probably where the assumptions get tested differently.

    As you've started talking to ecommerce owners, are they responding to the same problem that originally made you build Nexus, or are they describing a different reason they'd actually pay for it?

    1. 1

      Actually is difficult to find ecommerce owners to approach, this is my biggest problem. If you reach them online they target you as Spam, i need then to be discovered from them.
      People who i talked with are agree with my idea to build Nexus, then probably it could be a good product, I prepared it to be versatile for any type of business, to adapt to the customer's needs.

      1. 1

        That’s helpful context. The gap between people agreeing with the idea and actually reaching the right buyers is an interesting one.

        I’d like to continue the conversation outside the thread. What’s the best email to reach you on?

        1. 1

          you can reach me at [email protected], feel free to contact me

          1. 1

            Thanks! I’ve just sent it over.

            Looking forward to hearing your thoughts whenever you have a chance.

  16. 1

    The transition from builder to seller is the hardest reset. You spend months thinking the product is the problem — then it works, and you realize you have no idea how to sell. Talking to customers before the product is ready is the only thing that actually helps.

    1. 1

      Thanks for your comment, i really appreciate! I always like to hear other opinion and experiences, especially about this hard topic

Trending on Indie Hackers
I built a startup-idea scanner. It just told me none of my 3,400 ideas are easy wins. User Avatar 85 comments I Just Discovered My Analytics Numbers Are Mostly Fake. Here Is Why. User Avatar 80 comments “I’ll just post on Upwork” is not a client strategy. Here’s what I built instead. User Avatar 63 comments Co-founders suck… User Avatar 61 comments The Capture Trap User Avatar 35 comments