<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by satyam bansal on Medium]]></title>
        <description><![CDATA[Stories by satyam bansal on Medium]]></description>
        <link>https://medium.com/@satyambansal?source=rss-30b9ee35fc2e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*xBTvAW95lUJSh7iw.jpg</url>
            <title>Stories by satyam bansal on Medium</title>
            <link>https://medium.com/@satyambansal?source=rss-30b9ee35fc2e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:20:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@satyambansal/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From Siloed SaaS to an Agent-Ready Platform]]></title>
            <link>https://medium.com/@satyambansal/from-siloed-saas-to-an-agent-ready-platform-3ca8fb507625?source=rss-30b9ee35fc2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ca8fb507625</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[satyam bansal]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 22:17:06 GMT</pubDate>
            <atom:updated>2026-10-27T22:24:59.233Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rCj3xer0R65QOSGDPx47Lw.jpeg" /><figcaption>Back in my Evercommerce days in Denver</figcaption></figure><blockquote>Sep 27, 2026 · @Satyam Bansal</blockquote><h3>What modernizing a portfolio of vertical software taught me about building for the age of AI agents</h3><p>The hardest problem in enterprise software usually isn’t building something new. It’s getting a set of successful products, built by different teams for different customers, to start acting like one platform.</p><p>I spent a good part of my time at EverCommerce on exactly that. We served HVAC contractors, lawn-care companies, remodelers and many other small businesses, through products we’d built and products we’d acquired. Each had loyal customers and years of hard-won domain knowledge. Each had also grown up on its own. Scheduling had been built several times over. So had payments, messaging, reviews and invoicing.</p><p>That wasn’t anyone’s mistake. A plumber’s day doesn’t look like a landscaper’s, and the software reflected it. But behind the scenes, talented teams were solving the same problems in parallel.</p><p>So we kept coming back to one question: how do you protect what’s unique about each product while standardizing what sits underneath?</p><p>I’ve been thinking about that work again lately, because the answer turns out to be a pretty good blueprint for something few people were talking about back then: AI agents.</p><h3>Keep the experience, share the capability</h3><p>Think about three field-service businesses. One fixes broken air conditioners on short notice. One mows the same lawns every week. One spends months on a kitchen remodel. Their owners need very different screens and workflows. But all three need to know who the customer is, when the crew is free, how to get there, how to send an invoice and how to get paid.</p><p>When every product builds those pieces itself, each becomes another roadmap and another integration headache. And a great idea in one product stays stuck there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HMzBIOcYmuwjqdIrMGJTPg.png" /><figcaption>From siloed apps to services, events and agents</figcaption></figure><p>The rule we worked toward was easy to say and hard to do: products own the experience, the platform owns the shared capabilities. We carved the platform into business domains (scheduling, routing, crews, messaging, reviews, invoicing, payments, identity) and exposed each as a service any product could use.</p><p>The front ends didn’t become generic. A remodeler still got software built for remodelers. The difference was that when scheduling got better, everyone got the improvement.</p><h3>The org chart is part of the architecture</h3><p>The lesson that surprised me most wasn’t technical. A shared service with no owner becomes everybody’s dependency and nobody’s product. Before long, you’ve rebuilt the silos you set out to remove, just one layer down.</p><p>So we started organizing teams around capabilities, not only apps. The question shifted from “What does Product A need from us this quarter?” to “What should scheduling be able to do for every business we serve?” It’s a harder conversation for teams used to owning a product end to end. It’s also the one that makes the investment pay off.</p><h3>APIs weren’t enough</h3><p>Services gave products a way to ask for things: find me an available technician, charge this invoice. But much of what matters in a service business isn’t a request. It’s something that just happened. A technician is running late. A card is declined. A customer leaves a one-star review.</p><p>That’s where an event backbone like Kafka earns its keep. When a job is marked complete, the job service publishes a JobCompleted event and moves on. Billing sends the invoice, messaging thanks the customer, reviews asks for feedback, and analytics updates the numbers. The job service doesn&#39;t need to know any of them exist.</p><p>The way I explain it to non-engineers: an API says “I need something.” An event says “something happened.”</p><p>We did this to reduce coupling and scale the platform. Looking back, it did something else too. It gave intelligent systems something to listen to.</p><h3>Now add agents</h3><p>Picture a dispatcher at 10 a.m. One of her technicians just called in sick with a full day booked. She has to work out which appointments are affected, who else has the right skills, who’s close enough, and what to move. Then she has to call or text every customer, while the phones keep ringing.</p><p>Now picture an agent that hears the TechnicianUnavailable event the moment it fires. It checks the schedule, finds qualified technicians nearby, estimates drive times and drafts new assignments. For routine changes it makes them and texts the customers. For bigger calls, like moving a high-value job or approving overtime, it lays out a plan and asks the dispatcher to sign off.</p><p>The dispatcher doesn’t disappear. She stops doing the arithmetic and starts making the judgment calls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mD5rPqTqQ6JbeQ4vsfWocQ.png" /><figcaption>Agents decide. Workflows coordinate. Services execute.</figcaption></figure><p>None of this works without the earlier platform work. The agent isn’t replacing the services. It’s using them, and they’re what keep it safe.</p><h3>Your services are already skills</h3><p>There’s a lot of talk about giving agents tools and skills. Most established software companies already have them. They’re just locked inside applications.</p><p>A scheduling service already knows how to find availability and reassign a job. A payments service knows how to collect. A messaging service knows how to reach a customer. An agent shouldn’t reinvent any of that. It needs clear, governed access to it.</p><p>The model I keep coming back to: agents decide, workflows coordinate, services execute, events signal. And the boundaries matter. Nobody wants an AI improvising a tax calculation. Let deterministic software do what it’s good at, and bring in AI where there’s real ambiguity.</p><h3>What I’d do differently</h3><p>If I were starting today, I’d design every important capability for two kinds of users from day one: people and machines. That means clear naming, tight permissions, well-defined events and good audit trails. When an agent reschedules a customer, someone will eventually ask why, and the system should have an answer.</p><p>I’d also resist starting with the technology. “We need microservices” was the wrong opening line then, and “we need agents” is the wrong one now. Start with the business. Where are you building the same thing twice? What truly sets each product apart? Where do you need judgment, and where do you need the same answer every time?</p><p>For vertical software companies especially, don’t sand off the specialization. It’s usually why customers chose you. Standardize underneath it.</p><h3>Layers of leverage</h3><p>Platform modernization used to be justified by efficiency. That’s still true, but AI adds a new reason. Reusable services become tools. Events become triggers. Shared identity and permissions become guardrails.</p><p>For years, the main users of these services were web apps, mobile apps and integrations. Increasingly, they’ll be agents, working alongside the dispatchers, office managers and owners who run these businesses every day.</p><p>That’s why I don’t see siloed apps, services, events and agents as a string of trends. They’re layers of leverage. Get them right, and you’re ready for whatever interface comes next.</p><p><em>If you’re in the middle of a modernization like this, or figuring out where agents fit on top of what you’ve already built, I’d love to hear how it’s going in the comments.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ca8fb507625" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the Room: Rethinking the Economics of Hotel Booking]]></title>
            <link>https://medium.com/@satyambansal/beyond-the-room-rethinking-the-economics-of-hotel-booking-c3df6fc83a9d?source=rss-30b9ee35fc2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3df6fc83a9d</guid>
            <dc:creator><![CDATA[satyam bansal]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 04:24:34 GMT</pubDate>
            <atom:updated>2026-10-14T04:24:34.685Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How lessons from e-commerce and airline retailing helped us rethink what a hotel booking could become.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lvL8GWmiv11HtNOErrJ1Dg.png" /></figure><p>When I joined Sabre as GM and Vice President of Product for its hospitality software business, I inherited a platform that I often described as <strong>Shopify for hotels</strong>.</p><p>The idea was simple, but economically important. A hotel could have a beautiful website, but unless that website could turn a visitor into a paying guest, it remained dependent on third parties to complete the transaction. Online travel agencies have created enormous value for the hospitality industry by aggregating demand and providing global distribution, but that distribution comes at a price. Hotels can give up 20 to 30 percent of a booking in commissions. Just as importantly, when the booking happens elsewhere, the hotel risks ceding something even more valuable: the direct relationship with its guest.</p><p>Our technology helped hotels change that equation. It transformed their websites into sophisticated booking engines and, at the time, powered approximately <strong>$11 billion in annualized room bookings across roughly 12,000 hotels</strong>.</p><p>By any measure, this was already a substantial commerce platform. But coming from an e-commerce background, I found myself thinking less about what the platform was already doing and more about what it wasn’t.</p><p><strong>Why should the transaction end with the room?</strong></p><h3>Looking at hospitality through a different lens</h3><p>The airline industry had already demonstrated what a different model could look like. Buy an airline ticket and the seat is often only the beginning of the transaction. A traveler might pay for a preferred seat, additional legroom, another checked bag, a meal or priority boarding. Over time, airlines became increasingly sophisticated at understanding that the core product could serve as the anchor for a much broader retail relationship.</p><p>Hotels arguably have an even richer opportunity.</p><p>A traveler isn’t simply purchasing a bed for the night. They may be celebrating an anniversary, taking their children on vacation, attending a concert, arriving at an unfamiliar airport, spending a week at a resort or meeting friends for dinner. The room is important, but it is only one component of the experience the guest is actually buying.</p><p>Yet the digital transaction in hospitality had largely remained centered on three things: choose a room, choose the dates, and pay.</p><p>Coming out of COVID, my team and I began thinking seriously about how we could change that. What if the booking engine could become a retailing platform? What if, while reserving a room, a guest could add a bottle of champagne waiting on arrival, a birthday cake, a beach cabana, an airport ride, or tickets to a concert or sporting event?</p><p>The opportunity wasn’t simply to sell more. It was to allow the hotel to participate in more of the guest’s journey.</p><p>That distinction became central to how we thought about the product.</p><h3>Building beyond the hotel’s own inventory</h3><p>The idea became more interesting, and considerably more complicated, once we started thinking about the breadth of what a hotel might sell.</p><p>Some products and services naturally belonged to the property itself. A resort could offer a cabana. A hotel could arrange champagne or a cake in the room. Those were relatively intuitive extensions of the existing booking experience.</p><p>But why stop at inventory owned by the hotel?</p><p>We explored integrations with national platforms such as Uber and Ticketmaster. The underlying idea was that a hotel could eventually package transportation, entertainment and other services into the same commerce experience. A guest traveling for a concert, for example, shouldn’t necessarily have to think of the hotel room, transportation and event as three entirely disconnected transactions.</p><p>At the same time, we knew that much of what makes travel memorable is intensely local. There may be no sophisticated API connecting to the barbecue restaurant down the street, a neighborhood experience, or a small local business that guests love.</p><p>So the product also needed to give hotels the ability to configure and merchandise their own inventory of local products, services and experiences.</p><p>This became an important design principle. We wanted the <strong>scale of a platform without losing the personality of the individual hotel and its destination</strong>.</p><p>It also reflected something I had learned from my years in e-commerce: the catalog matters. Once you expand what can be sold, the product problem changes. You are no longer simply processing a transaction. You have to think about inventory, merchandising, relevance, configuration and where an offer belongs in the customer journey.</p><p>We began referring to the broader approach as <strong>intelligent retailing</strong>.</p><h3>Taking the idea into the real world</h3><p>With a platform serving roughly 12,000 hotels around the world, it would have been easy to build the capability, release it broadly and wait for the data to arrive. We chose a more deliberate path.</p><p>We handpicked a small group of hotels with whom we had strong relationships and invited them to help us harden the product. Importantly, we didn’t limit the pilots to the United States. We worked with properties across different markets, including Europe and Hong Kong, because we wanted to understand whether the assumptions we were making held up across geographies and different types of travelers.</p><p>Those hotels became more than early adopters. They became development partners.</p><p>That distinction matters when you are attempting something genuinely new. A good design team can anticipate a great deal. A good product team can construct thoughtful hypotheses. But once real customers begin using a product in real commercial environments, assumptions get challenged very quickly.</p><p>The pilot allowed us to learn before trying to scale. It helped us understand how hotels wanted to configure their offers, how ancillary products should appear within the booking journey, and where the experience created value versus simply adding friction.</p><p>And ultimately, customers gave us the signal that mattered most: they bought.</p><p>As we launched the capability, we saw <strong>ancillary attach rates approaching 20 percent</strong>. To me, that number was meaningful not simply because it represented additional commerce. It validated the underlying premise that guests were willing to buy more than a room when the offer was relevant to the journey they were already planning.</p><p>For hotels, that opened another economic opportunity. Instead of thinking about the booking engine simply as a mechanism for reducing dependence on intermediaries, it could become a platform for increasing the value of the direct relationship itself.</p><p>Intelligent retailing went on to become an important part of Sabre Hospitality’s product direction and, eventually, part of the strategic foundation of the hospitality business through its subsequent acquisition.</p><h3>Sometimes experience outside an industry is an advantage</h3><p>Looking back, one of the things I value most about this experience is where the idea came from.</p><p>We certainly didn’t invent ancillary retailing. Airlines had spent years becoming extraordinarily sophisticated at it, and e-commerce companies had long understood the economics of merchandising, cross-sell and upsell.</p><p>The opportunity was in looking at hospitality through those other lenses.</p><p>Every industry develops conventions. Over time, those conventions can quietly turn into assumptions about what the business is and what it isn’t. Hotels sell rooms. Airlines sell seats. Software companies sell subscriptions. Retailers sell products.</p><p>Eventually those definitions can become constraints.</p><p>Coming into hospitality with an e-commerce background meant that I didn’t necessarily see the boundaries in quite the same way. I saw a large digital commerce platform processing billions of dollars in transactions, and it seemed natural to ask why the product being sold had to stop at room inventory.</p><p>That experience reinforced something I have seen repeatedly over my career: <strong>some of the most interesting opportunities appear when you take a mental model that works in one industry and ask why it shouldn’t work in another.</strong></p><p>The answer isn’t always that it will. Context matters enormously, and blindly importing a playbook from somewhere else is rarely a good strategy. But asking the question can expose assumptions that people inside an industry have stopped noticing.</p><h3>When product leadership becomes business leadership</h3><p>There was another lesson in the experience that has stayed with me.</p><p>We often describe product leadership in terms of roadmaps, customer problems, technology choices and features. All of those things matter. But as the scope of the role gets larger, I think the question changes.</p><p>The question becomes: <strong>How can technology change the economics of the business for the customer?</strong></p><p>In our case, a better booking engine was useful. But helping a hotel move from selling a room to participating in more of the guest’s journey was potentially much more consequential.</p><p>Making that happen required far more than product management. It required technology, partnerships, commercial judgment, customer relationships, experimentation and teams across multiple functions and geographies working toward the same idea.</p><p>That last part is important to me. Looking back at work like this, it is easy to attach an executive’s name to a strategy. The reality is that ideas only become meaningful when talented teams turn them into products that customers actually choose to use. I remain enormously proud of the teams that took this idea, challenged it, improved it and ultimately brought it into the market.</p><p>For me, the enduring lesson from the experience is not really about hotels, airlines or ancillary revenue.</p><p>It is about how we define the business we’re in.</p><p>Sometimes the most valuable product opportunity isn’t another feature within the existing definition of the product. It is recognizing that the customer is trying to accomplish something larger than the transaction we happen to sell today.</p><p><strong>The room was the booking. The journey was the opportunity.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3df6fc83a9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why did we invest in Zeda.io?]]></title>
            <link>https://medium.com/@satyambansal/why-did-we-invest-in-zeda-io-560b5489688f?source=rss-30b9ee35fc2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/560b5489688f</guid>
            <category><![CDATA[zeda]]></category>
            <category><![CDATA[prashant-mahajan]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[saas-angel-investments]]></category>
            <category><![CDATA[satyam-bansal]]></category>
            <dc:creator><![CDATA[satyam bansal]]></dc:creator>
            <pubDate>Sun, 02 Jan 2022 20:43:30 GMT</pubDate>
            <atom:updated>2022-01-02T21:04:53.084Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Why did we invest in Zeda.io?</strong></p><p><strong>CORE IDEA</strong></p><p>Zeda.io was born to power and re-imagine what the future of product management tools might look like. Over last 12 months, there has been an explosion of startups in this area — Notion, Dragonboat, Coda claim to disrupt the way teams operate in complex modern product development environments. The capability which, with its due credit was probably created by Atlassian with its suite of products like Jira, Confluence, and Bitbucket (among others) has been a default goto tool for number of mature product management businesses. Not to mention, Github (now owned by Microsoft) also has various features that can do the job for companies that are looking for light processes.</p><p>Where we felt as product managers, the gap in the market was with integrations and a more intuitive UI. Collaboration is the central philosophy that drives everything at Zeda. It takes an integrations first approach, where it wants to port core functionalities through API connectivity from other providers and also index heavily on a seamless integration with Slack, Figma, Salesforce, Zendesk, and other services. A two way street that unlocks the power of collaboration and communication related to product management like never before. It was giving wings Product led growth through democratising influence of and on product by marketing, design, sales, customer support in addition to developers.</p><p>That we felt could be a true game changer and had the possibility of developing a moat that would define the next gen of collaboration.</p><p><strong>FOUNDER AND TEAM</strong></p><p>We’ve always believed that teams are almost more important than the idea and that a nimble, closely knit set of founders can navigate through anything that the market throws at them. We found that right spirit and combination in Prashant and Vaibhav. With just the right complimentary skill set and personality traits, they were fabulous in bringing onboard a compelling set of advisors, early investors and putting together a team that would help them build a product that could reimagine collaboration in the modern workplace. Prashant’s ability to communicate his ideas and rally people behind them is his superpower and he uses it to his maximum advantage.</p><p><strong>CONCERNS</strong></p><p>Few points of concern for us were:</p><ol><li>First time founders</li><li>Could a SAAS company out of India truly be a global player and what would it take to make that happen. We’ve seen that happening already with Freshdesk and Zoho and hundreds more in the pipeline are starting to have wide impact. Having the product and development in India would certainly present a cost and scale advantage, but the sales, product and connectivity to the markets in the US would be paramount for Zeda to be successful on a global stage, which is what it aspires to be.</li><li>Would the potential client base barely dabble with the product for few teams or could Zeda find wide adoption in fortune 500 companies or would it be targeted towards the mid-market segment? The positioning from the market segmentation standpoint was still unclear.</li></ol><p><strong>OUR VALUE</strong></p><p>When we make investments, we usually are looking at ourselves as assets that could help the company grow beyond just writing checks. Our assessment of the product, its development roadmap, as well as providing strategic connectivity to western markets is a value that we certainly want to bring to the table. Not only does it help us stay connected and understand the true fabric and challenges of the product, but also can help the founders (especially in other parts of the world) open doors to the most mature SAAS market on the planet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=560b5489688f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Angel investing and why I love it?]]></title>
            <link>https://medium.com/@satyambansal/angel-investing-and-why-i-love-it-e97fd6cf4e1c?source=rss-30b9ee35fc2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e97fd6cf4e1c</guid>
            <dc:creator><![CDATA[satyam bansal]]></dc:creator>
            <pubDate>Wed, 22 Sep 2021 22:17:45 GMT</pubDate>
            <atom:updated>2021-10-05T14:30:56.411Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Angel investing and why I love it?</strong></p><p>I started angel investing 6 years ago and it all happened by accident. At times, you might not find your calling, the calling might find you. Angel investing and me were paired by destiny. We met the first time when my cousin was getting going with his startup and was looking to raise some FFF funds (friends, family, and fools). I’m not sure what category I fell in but I was perfectly fine with any of those. Purely because the rush of of being part of something that was germinating was exciting and I was happy to help in anyway I could. Unfortunately, despite raising over $5 Mn over time from some marquee investors, his company had a firesale to a larger player without much of an outcome for any investor. It didn’t really bother me. Most of the times when i’ve been to a casino, I’ve lost money and if I dig deeper, that certainly leaves me feeling more foolish than I did investing in my cousin’s company. There was a sense of purpose and pride associated with supporting and helping a startup and there are always risks that come with that.</p><p>Soon after this experience, I met two entrepreneurs from Bengaluru who were struggling with an idea they were working on. Idea was to bring offline shopping inventory to an online platform through a marketplace model. Sounded brilliant but they were having some serious challenges. I was heading partnerships and growth at Flipkart at the time and was intimately familiar with the challenges of e-commerce. When I heard the idea and saw the product they had developed, the pitfalls they would face with scaling the supply side and maintaining the accuracy of inventory over time were apparent to me. But before I go any further, I want to talk about Veekshith and Vivek. They were brimming with energy, ideas, grit, and motivation. They were passionate about the history and future of tech and at times I felt that their mind was running faster than their tongue could keep pace with.</p><p>I honestly didn’t know what I had to offer them, but decided to go on with the ride and trust my instincts. Problem statement was that how could they fix the model of their idea to become scalable and remove the associated pitfalls. I decided to commit to 3-4 hours of brainstorming time to them every week till we could get to a solution to the problem they were looking to solve. First few sessions were spent asking a lot of hard questions and getting a deeper understanding of how they were running their business and areas where they were struggling more than the others. As I dug deeper, it started becoming clear to me that if I really wanted to help these talented entrepreneurs, I had to convince them of becoming more malleable and be open to exploring ideas that might either pivot their business to a tangential model or even be open to moving in a different direction altogether. For that I had to win their trust, which I could sense was cementing slowly.</p><p>After few weeks of brainstorming sessions, we jointly laid out a plan by way of which we would measure a few times before we cut. Whatever Veekshith and Vivek did next was going to be something that they would need to live through for next few years of their life, hail come storm, and that idea needed to be well thought through with the ‘i’s dotted and ‘t’s crossed. That also meant that we needed to be able to explore multiple possibilities and draw out a time bound plan by way of which we could collectively reach a decision point through a process driven approach.</p><p>So, here’s the process we laid out:</p><p><strong>Step 1:</strong> Pick 8–10 ideas of which their existing idea would be one in the list to give all the work they had put in a fair shot.</p><p><strong>Step 2:</strong> Lay out a set of criteria (that was important to the founders) that each of the ideas would need to meet. Example, not too capital intensive, nothing that would require building a supply chain and inventory mechanism, something that would have technology as a moat (given their strong software development background), etc.</p><p><strong>Step 3:</strong> Use the process of elimination to reduce the list to 3 ideas over time. Hopefully, at this point, the three finalists would be so strong and well thought through that they would each be contesting against each other.</p><p><strong>Step 4:</strong> Each of us would champion one of the ideas and create a pitch deck. With these three buttoned up pitch decks in hand, we’d go to real VCs and people in our network whose opinion truly mattered to us and ask them — “which one would you fund?”. Through that democratic process, one idea will emerge a winner and the founders will be off to the races.</p><figure><img alt="Veekshith and me on a hiking trip of Kalvantin Durg peak near Mumbai" src="https://cdn-images-1.medium.com/max/1024/1*phGyy6as45m60ysVwvxalQ.png" /><figcaption>Veekshith and me on a hiking trip to Kalvantin Durg peak in Maharashtra</figcaption></figure><p>Through the above process, that lasted for about 3 months, the idea of Finly was born. Finly is an Accounts Payable automation system that enables and empowers the finance and accounting teams at companies to automate their payments and provide rich analytics to manage the same. Automation of accounting is an area that started gaining some traction over last couple of decades with companies like Concur and Coupa but there is always incremental opportunity in streamlining and automating specific aspects of accounting, especially with increasing complexity around various new age business models. Finly over time found one such niche and focused the entire product upon that hence finding a market fit that gave them the needed traction to scale. It is important to note that none of us have an accounting or finance background, nor did we understand the SAAS business very well. Conventional wisdom might profess that most large changes are instrumented by entities with specialized knowledge and power in those industries. However, I have yet to see large tech driven changes coming from field experts and/or well capitalized corporations with the mindset of extrapolating their retrospective success to build a disruptive future. Those large corporations might rarely instigate that disruptive future, but might very well be the vehicles to scale and drive mass adoption.</p><p>Jump ahead 6 years, Finly has now been acquired by a Seattle based firm, Lockstep. As I say goodbye for now to my association with these founders, I’ll be rooting on the sidelines for their continued success and much larger impact that they are so capable of creating with being onboard a strong well capitalized vehicle like Lockstep. I’ve learnt that quality of people you associate with and mutual respect and consideration go a long way towards creating long lasting relationships.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e97fd6cf4e1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership in the new world]]></title>
            <link>https://medium.com/@satyambansal/leadership-in-the-new-world-16f66c4d9029?source=rss-30b9ee35fc2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/16f66c4d9029</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[modern-leader]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[satyam bansal]]></dc:creator>
            <pubDate>Tue, 09 Jun 2020 16:48:27 GMT</pubDate>
            <atom:updated>2020-06-09T16:48:27.612Z</atom:updated>
            <content:encoded><![CDATA[<p>There is so much talk about the need and importance of leadership in modern day organisations, business and otherwise that I had a do quick writeup to get my thoughts in. The relevance of the role and it’s perception over ages has changed so much, yet remained the same in so many ways. Same in the sense that people still want to be able to look up to someone who they can look up to and get inspired from, and so different in the manner that it requires leaders to be anything but dogmatic and authoritarian.</p><p>“Anyone can cook” were the famous words from one my favourite Pixas films, Ratatouille. I do believe that — anyone can lead. If you have ideas, dynamism, will to inspire, ability to take people along and hunger in the belly to execute, you can shine. Sounds simple — well, not quite!</p><p><strong>Need for leadership</strong></p><p>There is huge unmet need for effective leadership in the world today. Individuals who can inspire, bring about change and take people with them consistently are hard to come by and when they do, are invaluable. Effective and diligent leaders truly care about their people and consistently work towards developing and honing their skills and careers. Studies have repeatedly revealed that employees are motivated by the people they work with and the work they do than just the money they make. Monetary payback is important, but tap-dancing your way to office on a Monday morning is getting much higher up on people’s checklist than a fat paycheck. And their leaders have a huge role to play in making that happen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*5og1UPCoueJ4ZI6REnFK4A.jpeg" /></figure><p>Care for individual and professional development and the sense of daily challenge to solve interesting problems is what gets most star employees out of bed. With the advent of Artificial Intelligence, lot of jobs will be replaced with technology over time. Smart leaders in organisations will ensure investment in development of their workforce to skill them for jobs of future.</p><p><strong>The epiphany: No such thing as over-communication</strong></p><p>With every passing decade, the need and nature of leadership changes. What baby boomers wanted and expected of their leaders is quite different from what millennials want and that is different from the needs of gen Z and so on. Leadership styles have been evolving particularly due to the advent and connectivity of the internet. One way communication where leaders communicated with their followers in a one way stream is turned on it’s head through an open channel format where people are communicating with the leaders just as much and as frequently as they wish to. Their voice, opinions and inputs are more visible, more accessible and we have more tools now than ever to engage. We have evolved gradually and steadily from the world of telephone and town-halls to AMA (Ask me anything) on Slack and Twitter. Even conferences nowadays use Slido to allow for anonymous feedback and voting from audience. With access to all these tools and channels, it becomes ever more so important for plugged in leaders to have an open ear to feedback. The challenge of course is that this can become a massive distraction. The amount and kind of engagement that leaders find useful and fruitful really is an individual choice depending upon the style, personality, and frankly the nature of job and company. But most leaders can’t afford to not have open communication lines today — not only with their employees, but equally so with shareholders and customers. Lack of communication can make people ignored and not cared for.</p><p><strong>Dated to Updated lens of leadership: </strong>The dated lens of leadership is loaded with two broad characteristics:</p><ul><li>Care for ONLY revenue and profitability</li><li>Dictator-like hierarchical leadership</li></ul><p>Jury has spoken — it’s not only about the moolah; more importantly it is about Aarie, Rachel, Ravi, Chris, and Jafari. It is also about Mia who runs the “women in tech” group and Jay who runs the “continued education” forum. When companies care more about the people behind numbers, employees bring their best to work and innovate to deliver the numbers. The opposite is just as true.</p><p>The world and the new work environment (especially for global businesses) is so layered that it requires a leader that cherishes diversity in people, problems, customers and opportunities alike. It is through that diversity of point of views, great companies manage to solve problems which are seemingly impossible to navigate first. There is a fabulous article written by squadron commanding officer, Jack Curtis called <a href="https://fromthegreennotebook.com/2019/08/23/the-map-on-the-wall/">“Map on the wall”</a>. In this quick read, officer Curtis lays out the importance of strength in diversity, importance of dialog over process, and the impact of physical artefacts as a reminder of what certain leaders live by and emphasise as cornerstones of their leadership. A simple thing as a map with pins in places indicating where members of his team are dispersed represents his organisation and where those people come from - a celebration of trust, differences in ideologies, faiths, education, experiences and backgrounds with one thing bringing all of them together — unity of purpose.</p><p>Here are few outlooks I’ve seen effective leaders portray repeatedly for the benefit of their team and business:</p><ol><li><strong>They have the knack and ability to build and keep excitement among their people:</strong> ‘Inspiration’ equals ‘excitement’. All of us are looking to be inspired and need a periodic shot in the arm that sends that gush of blood flowing through our veins and we realise that higher sense of purpose and that bit of greatness that all of us were born to achieve during our time here on earth. Some of us need that shot more than the others..but there’s no doubt that all of us need it. As a leader in a modern day world, how do you get your teams that gush of blood regularly. Ability to get people to perform their ‘less than perfect’ but ‘scintillating’ best is what a leader aspires to achieve. Once that is done, results become almost immaterial. When individuals and teams bring their A game everyday with clarity of strategic goals and a sense of confidence, great movements happen.</li><li><strong>Have a growth and constant improvement mindset:</strong> One of the biggest things I’ve learnt from one of the greatest companies on earth, Amazon is building upon your success and experimenting relentlessly. Amazon’s incredible moves since it’s inception with the founder’s ability to convince the investors to bet on future for 13 years without any profit, to launching products and services like AWs, Kindle, and Echo to ancillary plays like Prime video and acquisitions of Twitch and Whole foods. These are all incredible examples of grit, smart planning, leadership at every level and relentless hunger to synergise and grow.</li></ol><p>Harvard Business Review lays it out more succinctly as the following important traits of effective leaders in the modern business world:</p><ol><li>uniting people around an exciting, aspirational vision;</li><li>building a strategy for achieving the vision by making choices about what to do and what not to do;</li><li>attracting and developing the best possible talent to implement the strategy;</li><li>relentlessly focusing on results in the context of strategy;</li><li>creating ongoing innovation that will help reinvent the vision and strategy; and</li><li>“leading yourself”: knowing and growing yourself so that you can most effectively lead others and carry out these practices.</li></ol><p>These six step rule has been widely published and spoken about. It is a quick and easy reference guide for leaders who can evaluate themselves on these dimensions and see where calibration might be needed.</p><p>Our world — business, tech, personal or political has never been and will never be static. There is so much happening constantly that things change rapidly by the time an organisation plans a product or initiative and the time when that undertaking is ready to see the light of the day. All of the above — business, tech, personal and political environments have today are so intertwined that deeper understanding of each of them have become more important than ever.</p><p>3. <strong>Lead to disrupt</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*u-45XR9DdU8_-4GWdnXmLQ.png" /><figcaption>Victims of disruption</figcaption></figure><p>These names use to be relevant once upon a time. The pace of change has increased with every passing decade and effective leaders and organisations are spending more time now than ever looking at data, micro and macro economic trends and using those insights to make bold bets to lead their companies into future. Data analytics is evolving so quickly into so many related fields that is it would be virtually ineffective to be a leader in any functional domain without appreciating the value of it. With all the talk about AI, ML, NLP being the next frontiers to push the tech envelop, traditional industries like manufacturing and banking are increasingly getting digitised and bringing data at the center of their transformation and growth strategy to stay relevant in future.</p><p><strong>Finally, I’d say that you can’t learn to swim by reading about it. </strong>Leaders know that within themselves. While articles on leadership might be available on the internet dime a dozen, true leaders understand the need of jumping in the cold waters and struggling through the rough tides. That’s bold dynamism.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16f66c4d9029" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flavors of Product Management]]></title>
            <link>https://medium.com/@satyambansal/flavors-of-product-management-df53e6b64418?source=rss-30b9ee35fc2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/df53e6b64418</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[satyam bansal]]></dc:creator>
            <pubDate>Sun, 28 Apr 2019 13:32:05 GMT</pubDate>
            <atom:updated>2020-06-02T21:52:01.077Z</atom:updated>
            <content:encoded><![CDATA[<p>Having been part of several tech companies in a diverse set of roles, I’ve had the opportunity to get up, close and personal with product development, and hence product management. One of the most interesting things I found as part of my journey was that every organisation looks at and manifests product management and the PM org within the company ecosystem in its own unique way. In this article, I’ll talk about few lenses related to Product management that industry has developed.</p><p>Technical product management and even more so, product management have become loosely used terms in the industry. We see numerous flavors of both of those across different companies. From managing technical architecture to managing partnerships with internal and external stakeholders — A PMs role can be up for grabs for anyone’s interpretation. Rightfully so, since it sits in the middle of so many functions and requires everything to fire in unison to deliver that mythical beast called “product” — a combination of user experience, data analytics, and marketing to deliver what turns out to be user delight or less desirably, consumer grievance.</p><p>So, how do you slice and dice and provide more definition to this role. Should there even be a “one size fits all” meaning to this or is it OK to naturally let the organism breathe and take its own shape within your company’s nest. Having lived through and seen many different settings and been part of successful and more importantly, not so successful journeys, I’d say — the sweet spot lies in doing a little bit of both. It’s critical that leaders at a successful company need to be deliberate about what they want their Product org to be, but also let the org evolve into what will fit the glove naturally. This is important, since your company’s product, DNA, and modus operandi is unique and the most effective way to function will inevitably be unique, provided there is someone at leadership to nurture, calibrate and hone it. Completely leaving it to its own may have grave ramifications right from hiring people with skill sets that are a mismatch to execution inefficiencies on day to day basis.</p><p><strong>LETS LOOK AT 2 AVATARS</strong></p><p><strong>Company A </strong>considers its product manager as general manager or if you will- a mini CEO of the Product. In this case, the technical decision making, from architectural choices, what data management system to use, Kubernetes v/s ECS, which out of the box CRM solution to consider v/s building one in-house are one among the many choices that PMs have to make and often those decisions are made more by relying on engineering and principal architects. While there is a point of view and objective opinion that you’re expected to have in that scenario, the final decision making lies elsewhere when it comes to making technical choices. This also means that it’s important to give engineering a crystal clear understanding of the product requirements, so they can analyse solutions and make the choices that best fit your vision and needs. Similar dynamics play out in your relationship with marketing, finance, data, etc. I know what you’re thinking — Jack of all. And that’s not completely incorrect. In this world view, Product managers are required to be jack of all and know enough to be able to engage meaningfully with all different orgs and departments that relate to your product. Basis that knowledge, they make decisions since what’s happening in one function might impact another and left hand might not know what right is doing. It’s a PM’s job to ensure that doesn’t happen and they can sew the entire story together for important decisions to be made. In other words, there is one single orchestrator who everyone can look to for making decisions. This orchestrator has to have knowledge of every instrument that is part of the band, but doesn’t necessarily need to play any.</p><p>This approach especially makes great sense for a company where there are multiple products, front end, back end or combination of all those in play. Most of these product verticals have clear KPIs around performance or revenue metrics that can be defined and the PM owns the delivery of those metrics through product launches.</p><p><strong>Company B</strong> looks Product management as an org whose job is to largely make technical architectural choices basis the need and layout as well as orchestrate best practices to deliver the product consistently and predictably. In this particular case, the role of Product manager is centred more around technical decision making — ownership of what will be built, why and the impact of that might not necessarily reside with the PM org. PMs are needed to evaluate the specs of different options lot more holistically and evaluate various choices available to them through calibrating parameters and prototyping early on before taking a call. Sharpening the axe before you start chopping the wood is an important part of your time investment. It’s imperative in this setting that there is another entity who owns the PnL and performance KPIs and product essentially becomes a means to achieve those goals for that entity who is the real owner of deliverables. Now, there could be multiple owners who are trying to achieve multiple things through their asks from the product org. Here are few examples:</p><ul><li>A sales org trying to sell advertising might be asking product to deliver more advertising formats on the front end platform because the clients are demanding for them which enables them to sell more. On the backend, they might be asking for a better attribution and tracking mechanism which doesn’t exist currently.</li><li>A partnerships stakeholder internally might be asking for an API integration between billing systems of a partner they are working with.</li></ul><p>But what ends up happening inevitably is that the ownership of the sales numbers or the P&amp;L that partnerships or biz dev is supposed to deliver doesn’t necessarily belong to product and hence the product team may or may not choose to prioritise the asks since they have to look at the engineering capacity and delivery of pipelines for oncoming quarters or PI cycles (Product increment cycles). Somewhere, this push-pull ensues and the incentives alignment might be fractured and often in these scenarios, we’ve seen top leadership needing to weigh in either to break the deadlock, help prioritise or often reorg to enable better orchestration.</p><p><strong>LETS COMPARE</strong></p><p>In structure A, which is more of a product ownership GM structure, the prod-engg. pods are split and aligned for specific products/P&amp;Ls. Even though other functions like sales and partnerships and engineering may or may not report into product, the pod lead by product leader is responsible for the KPIs, since there are cross functional dependencies on marketing, partnerships, sales, finance, etc.</p><p>As you can see, approach 1 and 2 are very different. One is wide and one is deep. Each has its own fallacies and benefits. Often the product org can fail when the expectations from management are set do both. It’s tough to be a mile wide and a mile deep, but it is important to choose areas where depth is important and the ones where one can rely on internal partners for the same. Top leadership in companies face constant challenge around calibrating the org structures as the company morphs itself through growth and different life-cycles.</p><p>The knowledge base needs to be lot closer to engineering in Company B’s case and the candidates should ideally have some coding experience and be comfortable with architecture of technical platforms, data flows, micro-services and containers. Additionally, they should have a deep interest in evolving technologies and frameworks around AI, ML, cloud, and what will create those disruptive breakthroughs in times to come. Their technical decision making should not be limited to the worldview today, but what will it evolve into tomorrow. Will your picks stand that test of time as supposed to needing an overhaul of systems down the line, which would be a terribly expensive outcome?</p><p>On the other hand, for Company A, the skill set requirement becomes more around high degree of comfort with ambiguity and ability to smartly make decisions with less than perfect or comprehensive information availability. Having a general sense of business from the lens of legal, finance, large amounts of data led decisioning, marketing, and corporate strategy is important. If you’re going to be in a room with marketing and not meaningfully be able to engage and lead them to reaching decisions, you’re not the right fit for company A’s Product team.</p><p>Having said all of the above, one skill which is non-negotiable for Product managers in any flavour is the ability to communicate. Ability to express your ideas not only verbally, but in effective written communication is table stakes. An equally important skill is to have a high EQ. Product managers need to be precise about what they communicate and what their expectations are from different teams. But if they do it in a manner that lacks empathy and makes other functions feel that they’re just being given marching orders, it is not going to create a healthy environment that can sustain speed and efficiency to ship out great product quarter after quarter. With machines taking over large parts of human roles, if there is one element that they’re still far from being able to replicate — it’s emotional intelligence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df53e6b64418" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bit of lifehack]]></title>
            <link>https://medium.com/@satyambansal/bit-of-lifehack-3197e86c5002?source=rss-30b9ee35fc2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3197e86c5002</guid>
            <dc:creator><![CDATA[satyam bansal]]></dc:creator>
            <pubDate>Sun, 05 Jul 2015 17:03:58 GMT</pubDate>
            <atom:updated>2015-07-05T17:03:58.923Z</atom:updated>
            <content:encoded><![CDATA[<p>My week nowadays comprises of handling 4 different PnLs for Flipkart, taking 5 to 6 interviews for various positions across the org, socializing internally to figure out where fires might be burning and putting a plan in action, meeting a startup or two to invest in, and ensuring I can spend enough time with family so they allow me to do all of the above.</p><p>What I do ensure however is to listen to a lot of music along the way. I use an app called RadioTunes that has stations with different music genre’s and I like Top Hits, Classic Rock and DaTempo Lounge depending upon whether I’m really listening or just need some music that I can ignore while I do something else in the foreground. This helps me stay calm, increase focus, and makes the otherwise possibly stressful journey lot more fun. Another thing that helps me deal with stress and enjoy the journey are my workouts. Simply put-I’d die without them! I’m a sweat junkie and love anything that gets the drench going.</p><p>All of us have felt sometime the insides of our mind looking like this —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/342/1*DdrCdWju_OhBq5aqjuFDTw.jpeg" /></figure><p>Then I discovered Evernote. What it has done is helped me put all my random thoughts in one pace when they come, as they come. So, if I thought it, I have it. Over time, I’ve come to believe, no matter how random the thought, it has consequence. When I refer back to it during my 3 monthly goal setting exercise, it helps put all my random neuron firings in perspective, and the culmination of all that turns into goals — life, work, family, and fun.</p><p>What I found over time was that there were 4 key priorities that I was going after outside of work. I’ll exclude my job since that is something that takes majority of my time, mindspace and bandwidth. The challenge really is that with your work, family, and other chores taking most of your time, how do you organize yourself to make time for everything else that you want to pursue.</p><p><strong><em>“Absorb what is useful, reject what is useless,<br>add what is specifically your own.”<br>– Bruce Lee</em></strong></p><p>My priorities range from sharpening my skill set to expanding my horizons, a hobby, investing smartly, and spending quality time with family. I found that was easy for me to drift from one priority to another at any given point in time without achieving depth with any of them. So, I decided to take only one thing at a time and completely commit myself to only that one thing for that time slab. I try to close any browser tabs that might be distracting me and surround my mind with only thoughts of task at hand. Its hard-very hard, especially to do it consistently and repeatedly for varied set of priorities. But with little discipline, gets the job done with higher quality and efficiency. Turns out that that there is an official name for this. Its called — <strong>Time blocking.</strong></p><p>That being said, do I follow my time blocked schedule to a ‘T’ every day? Almost never. But I’m always able to refer to it to know what I’ll have to sacrifice if I decide to go off course. For example, if I’m in the middle of writing a blog post, but I’m supposed to move on to working out, is it worth it to do a shorter work out so I can finish my post? Or is there a way I can rework a later activity? I am always sure to schedule in some “buffer” time in case a task takes longer than expected.</p><p>So, here are 4 things I try and do to be most productive</p><ol><li>Eliminate all distractions</li><li>Focus on being productive, not being busy</li><li>commit undivided attention to one thing at a time in 90 minute intervals</li><li>reply to emails, text messages in sprints— don’t be plugged in and accessible 24x7</li><li>stay obsessed and mildly paranoid</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3197e86c5002" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>