
Action's Antidotes
From Cybersecurity to Fashion Tech with Harish Chandramowli
What happens when a cybersecurity engineer walks into a fashion boutique? For Harish Chandramowli, it sparked an idea that’s now helping small fashion brands save time, money, and sanity. A chance observation in a New York store became a mission to untangle problems in inventory, communication, and operations many brands struggle with. In this episode, I speak with Harish, founder of Flair Software, about how he went from working at Bloomberg and MongoDB to building a platform that fixes the messy back-office problems fashion brands face. Harish explains why seasonal inventory is a high-stakes game, how communication breakdowns can cost thousands, and why he built his solution to integrate with Shopify instead of competing against it. Tune in now to learn more. --- Listen to the podcast here: From Cybersecurity to Fashion Tech with Harish Chandramowli Welcome to Action’s Antidotes, your antidote to the mindset that keeps you settling for less. We have a lot of technological advances, a lot of digital technology, and a lot of the efforts around it have been used primarily around digital products, primarily around some of the platforms and everything else, but there’s also an aspect that I’m hopeful around that really takes some of the digital technology that we have and uses it to enhance the physical products and the actual life that we have outside of our computers in real life. My guest today, Harish Chandramowli, is the founder of Flaire Software and he has some interesting solutions for the fashion industry and other kind of inventory-related pursuits. --- Harish, welcome to the program. It’s a pleasure to be here. Thank you for joining us. Now, first of all, kind of have your feet in both worlds, whether it be kind of our technological world as well as the world of fashion, the world of some of these in-real-life types of pursuits. Tell me a bit about your story, where you started and how you came up with the idea, what you observed that led to Flaire Software. Yeah. Just taking a step back, I am not from fashion industry. It’s all pretty new to me. I did my master’s in cyber security actually in Johns Hopkins, then I worked as security engineer in a bunch of very data-related platforms like Bloomberg, MongoDB. And MongoDB was my last gig where I primarily started as cloud security engineer but moved on to like an Atlas dedicated team where you see how lot of different people use databases. And, interestingly, there are a lot of retail companies using databases very heavily. That made me more and more curious on how software is being used in retail industry and why database is like one of the biggest line expenditures. On top of that, when I was looking into ERPs, Oracle is one of the biggest player in the ERP market, which made me even more curious on what this space is. What happens around here? Why is a database company spending so much on an ERP, on like a data workflow? Yeah. This kind of made me curious but, again, it was more like I don’t think I was into fashion or any of those things. I went to this store called ONS in Soho. It’s a great store you should check out if you are ever in like downtown area in New York. What’s the store called again? ONS. Okay. Orange, Naples, San Diego. So if you go to Soho and like downtown in the fashion districts, you will notice a lot of these small, small brands which is not your typical H&Ms or Zara. Yeah. So I was there, I was actually listening to their team meetings, talking a lot with their founder. I was looking at how they are operating in the back office. The first thing that stood out to me is that fashion as a whole uses a lot of software. One aspect of it which we are all familiar with is designing the fashion, like the threading, modeling and like the cut and everything. Another easier to relate option is like e-commerce site, where you list, sell products, and then there is a big piece of back office operation which kind of brings together your design teams to your sales team, your customer service team, which is ERP. And what I really noticed is that, especially in fashion, T-shirts are looked at size and colors, whereas a female swimwear product has cup size, torso length, color, and regular sizes. That means everyone looks at product in a very different way, and, often, people spend 100k, 200k hiring software engineers to customize the product structure on how they look at their business in the back office, how they analyze is my orange color moving faster than my red color, or is this torso length moving more than the other length? And it was very expensive, and having worked at MongoDB, having seen how a schemaless database, how giving the power to user to define schema can help people, it just stood out to me that why haven’t we done that in ERP? And that’s what led to Flaire. Essentially you looked at what happens at a lot of these smaller fashion companies and figured out a way that you could really kind of simplify their operation. Yes. You didn’t originally come from the fashion industry. Does the fashion industry have a special meaning to you or is this just the industry that you happened to observe this retail issue where you’re going to be taking this to kind of other components of retail? So I was looking at different retail things. One of the things that really stood out for me in fashion industry is the season. One, even within our customers, I have seen some of our customers go bankrupt just because they had one bad season. So the need for inventory planning, the need to analyze your business comes very early in your life cycle compared to other businesses.Share on X You need to move fast. You can’t sit on a lot of inventories. At the end of every four months, you need to decide do I sell my inventory at 50 percent loss or do I sit on it for the next season? Sitting on it for the next season means your cash is locked up, you can’t buy new products for the next season, and you are not making profit on it. So, all this decision making and all the need for an ERP or need for a workflow automation platform comes very early in the cycle. That’s one of the reason I took fashion industry. Apart from that, I was always curious. Because when I grew up, I grew up in a place where all these manufacturing happens, so we used to buy clothing in kgs and pounds. You don’t go and buy a t-shirt, you buy a pound of t-shirt. Oh, yeah. Oh my gosh –– –– the factory. So I was always curious on how things have changed between factories and how you buy clothes to here. So there was a bit of curiosity. But the main reason I picked fashion is because the need for these kind of innovative solutions comes very early in your business life cycle. So you alluded to like right now or before your solution, most of these companies were essentially hiring data scientists to comb through all this data, seeing what color was moving, probably looking at factors like month of the year, trends in style and stuff like that, right? Primarily, more than that, people use engineers to push into some kind of like a data store where they can do the analysis. But then at mid-level, people are not even doing that. They are trying to handle everything in spreadsheet because they don’t have the money to hire those engineers so they were literally doing that in spreadsheets. When you looked at these organizations, what are the size? How many total employees would one of these brands that you see in Soho, one of these kind of stores have? If I look at our customer profile, various customer profile, it varies anywhere from like 6 to 7 employees to 25, 30 employees, based on the size. $30 million brands, which is like one of our lower end of the customer base would be like 5 to 10 employees, whereas the $60, $70 million brands have like 20 employees. When I think about companies around that size, there’s certain hyper-specialized positions that not necessarily being hired out unless it’s like specific to industry, so when I think about a company that’s a thousand people, say, almost every one of them is going to have data engineers, data scientists, something even for just their operations, whereas the smaller ones probably not. So, these companies, let’s say one of them has 15 employees in your end, what is that makeup of the employees? Is it just like kind of a marketing person, a CEO, and a bunch of, you know… Exactly. Most of them are tech savvy. One, they know what information they need to make decisions, but they have no idea how to get those information. That’s where they look up to us and be like, “Hey, if I have this information, I can make a better business decision on how to plan, how much inventory to buy, when to expect an inventory, when to book a marketing campaign,” whereas they have no idea how to get those information because your CRM is very decoupled from your ERP which is very decoupled from the interactions that a purchase manager is having with a factory on, “Can we produce this? Can we not produce this? When this can be produced?” So, they are looking to us and be like, “Hey, I have all these separate information, how do I bring these things together? Can you make a software that can help us and give us the detail in the simplest possible way?” Typically, if I just look at what the situation would be, a CRM would have, say, I don’t know, the number of a certain item that’s selling each day. That information would be there, right? Two things, most of often than not, CRM, especially in this industry, happens is with B2B businesses, so what would happen is that you will –– so you are sitting in July and you will be selling your winter clothes as bulk orders. So you will be negotiating with other shops on like, “Hey,...

