Episode 150

LiLi Tile: Building the Self-Improving Ecommerce Site

Mory Katan
Mory Katan
Chief Technology Officer

In this episode we talked about:

  • Why Mory believes “context equals output” when it comes to AI
  • How WiseBird Systems’ Owl moves from analysis to decision, execution, deployment, and feedback
  • How LiLi Tile is using AI across CRO, CRM, inventory, financials, and warehouse operations
  • How AI can dramatically reduce the time between an idea and a live website test
  • How lean teams can use AI to query and combine data that would normally require a dedicated analytics team
  • Why repetitive admin work is one of the clearest places to start with AI
  • How Noibu data can feed self-improving ecommerce workflows

🎧 Listen now on Apple Podcasts, Spotify, or YouTube

Episode highlights:

00:00 – Introduction

‍02:24 – Building A Self-Improving Ecommerce Website

‍06:17 – How AI Has Evolved Beyond Simple Tasks

‍09:46 – Connecting AI Across The Entire Ecommerce Business

‍13:40 – Redesigning A Website In Days Instead Of Months

‍16:28 – Turning Business Data Into Action With AI

Mory’s bottom line: AI is only as useful as the context you give it, and most businesses are giving it almost none. At LiLi Tile, that meant building a system that ingests session data, heat maps, CRM conversations, inventory, and financials before it makes a single recommendation, so that recommendations actually land. It also meant removing the handoffs: from idea to design to implementation to deployment in one flow, not four. The results — a site redesign in two days, 200% conversion lift, 500% more add-to-carts — aren’t from a better AI model. They’re from better context. His rule for all of it: context equals output.

FAQ

Mory Katan is the CTO of LiLi Tile, a design materials brand his family started in 2018, and the founder of WiseBird Systems, the AI orchestration platform he built to power end-to-end ecommerce workflows. He started his career leading a development team at JPMorgan, overseeing digital projects with developers in the US and India, before moving into his own ventures. He describes himself as someone who has been deeply involved in machine learning long before the current AI wave, and who built Owl, WiseBird's AI brain, because the existing tools required too many handoffs between evaluation, decision, and deployment.
It's Mory's central rule for AI: the quality of what you get out is directly determined by how much relevant context you put in. Most AI implementations underperform not because the model is wrong but because it's working from thin, fragmented, or missing context — a blank canvas with no knowledge of the business. Owl is built around this principle: before making any recommendation, it ingests session data, heat maps, CRM conversations, inventory levels, financials, and purchasing history, so that its decisions are grounded in the actual state of the business rather than general inference.
Owl is WiseBird's AI orchestration system, built to take ecommerce operations from evaluation to deployment in a single flow. Where most AI tools return an answer and hand the work back to a human, Owl derives a decision, acts on it, deploys it, tests it, and reports back. It learns continuously from its conversations, logging preferences and corrections so it doesn't repeat the same mistakes. Noibu is the behavioral data layer that feeds Owl: session data, real user metrics, heat maps, and add-to-cart signals that give Owl the context it needs to make site speed, CRO, and A/B testing decisions that are grounded in actual shopper behavior.
LiLi onboarded Noibu on a Thursday afternoon. By Saturday, Owl had made its initial decisions. Sunday night they launched. Within 30 days, site speed dropped from 3 seconds to 1 second, add-to-carts increased 500%, and overall conversion rose nearly 200%. Mory attributes the speed of those results to having the right data layer in place: once Owl could read LiLi's real session behavior through Noibu, it could act on specific signals rather than general assumptions.
The traditional redesign process at LiLi required a developer, a designer, a project manager, and leadership oversight, and took at least two months from ideation to deployment. A lot of the decisions within it were gut feelings: where to put a button, what layout looked better. With Owl connected to Noibu's behavioral data and heat maps, a single project manager completed a full website redesign in two days — design, approval, implementation, and live launch on Shopify. No developer. No graphic designer. Mory's point is that the bottleneck was never the ideas; it was the handoff chain between them.
A year ago, AI was useful for menial tasks: drafting emails, creating documents, basic text work. The math and visual reasoning came later. What changed in the past year, according to Mory, is the ability to organize and catalog context at scale: financial spreadsheets, inventory levels, customer conversations, all kept as persistent pockets of context that the model can pull from to deliver more accurate and consistent results. Owl takes this further by learning from every conversation, so corrections and preferences are retained across sessions rather than starting from a blank canvas each time.
Quite a bit. After reading through LiLi's existing CRM, Owl recreated it as a custom system built for the specific nature of the business, tracking handmade tile variations, import demand factors, customer conversations, and marketing touchpoints. It built an inventory tool that logs stock and generates predictive purchasing decisions based on page views and add-to-cart signals from Noibu. It pulls in QuickBooks to produce simplified financial dashboards. It manages the pick, pack, and ship workflow across LiLi's warehouse, with monitors throughout the facility. Mory's framing is that Owl spans far beyond retail: any business where data lives across disconnected platforms and queries take too long to run can benefit from the same approach.
Because their data is spread across platforms that weren't designed to talk to each other. Mory describes customers with CRMs holding hundreds of thousands of records and no fast way to ask a simple question like how many people didn't receive an email in the last 30 days. Building those queries and automations takes time that most lean teams don't have, and the opportunity to act on the answer is gone by the time the answer arrives. He gives the example of a company that took four months to onboard Salesforce and three days to onboard Owl, and still couldn't cross-reference geographic data, pool density, and site visit frequency inside Salesforce the way they could inside Owl. His point is that being held hostage by your own data is one of the most common and least discussed bottlenecks in ecommerce.
Start by identifying workflows that take more than an hour a day and could be repeated by AI. Mory's advice is to have the conversation first: map the processes that are slow, repetitive, or dependent on manual handoffs, and work backward from there to where AI fits. He's direct that something like Owl took years of development and comes with a lot of embedded knowledge out of the box, so operators who want results quickly are better served reaching out to WiseBird than building from scratch. The critical integration layer, he says, is having good behavioral data to act on, which is where Noibu comes in: data, the ability to understand it, and action are the three components that have to come together.

Want to be featured on The Ecommerce Toolbox?

We feature senior ecommerce leaders with real things to say. If you've led something worth talking about, we want to hear from you.

Apply to be a guest →

Other episodes

See all episodes

Audit your site today

Understand the revenue impact of all errors on your site and how to swiftly reproduce and resolve.