AI + Snowpal API: Reduce Time to Market

Podcast

Africa, AI, and the Future of Global Talent — on Apple and Spotify.

Introduction

Holland, who lives in Melbourne, Australia, but runs operations out of Johannesburg, Durban, Cape Town, Nairobi, and Addis Ababa, didn’t set out to build an Africa-focused talent company. His path started in international education, building an internship placement platform that he took from Australia to the UK and Canada. Everything changed in 2020, when he was introduced to the continent through Zondwa Mandela, a grandson of Nelson and Winnie Mandela.

“I’d never been to Africa, but it definitely ignited something inside of me, an interest and that entrepreneurial flair, you could call it,” Holland recalled. He flew into Ethiopia first, then Rwanda, Kenya, and South Africa. What he found didn’t match his expectations at all: “I was completely blown away by the talent that is on the continent, the level of English proficiency, the tech capability, education levels, the infrastructure that’s happening in Africa. It wasn’t what I expected in my head.”

Talent Match Africa was born from that trip. Today the company places people in tech, finance and accounting, sales support, customer service, legal support, logistics, and operations roles with companies across the US, Australia, Canada, the UK, France, and China — and increasingly, in AI-related work.

The Demographic Case for Africa

Holland’s pitch for Africa starts with numbers most business leaders haven’t encountered. By 2035, every second person entering the global workforce will live on the African continent. By 2050, the continent’s population is projected to reach two billion. The driver is age: the average age in Africa is 19, compared to the 40s in the US and 72 in Monaco. That young population is now flooding into the workforce, backed by millions of university graduates every year.

Crucially, that talent pool is largely untapped. “India has become very congested and saturated,” Holland said. “The US went in the 70s and 80s and helped India become this tech powerhouse. But now it’s very saturated because everyone’s there. Whereas people haven’t quite worked out yet that there’s amazing talent in Africa. So you don’t have that competitive pressure. Price becomes more favorable, access to really good talent.”

He also pointed to a retention advantage Africa currently holds over the Philippines, where job-hopping has become endemic. “You don’t have people moving around as much... We’re not having those issues in Africa. Not yet anyway. We’re probably five years away from when that may become a problem.”

“Africa Is Not One Country”

Palaniappan pushed back with an obvious question: Africa is a continent of more than fifty countries, spanning enormous cultural and linguistic differences. Isn’t that a barrier for companies trying to figure out where — and how — to hire?

Holland pointed to a book that shapes his own thinking: Africa Is Not One Country. “A lot of people do sometimes think about Africa as being a country, when it’s like saying Europe is a country,” he said. “People in Germany are very different to people in France. And they’re next to each other.” A company that wants French-speaking talent needs to look at specific regions; language, accent, and business culture all vary sharply from country to country.

Accents, in particular, have become a bigger consideration than Holland expected. “I’m finding more and more that accent is even more important, particularly for a lot of USA companies. I’ll often get calls from businesses saying, ‘Look, Gerard, we really want people, but just so you know, we need really neutral accents.’ Where if they’re talking to clients, we don’t want people to know that they’re from another country — Americans want to deal with Americans.” South African, Kenyan, and Nigerian accents are all distinct, he noted, and clients increasingly specify which they’re comfortable with.

For companies looking to enter the continent, Holland recommends South Africa as an entry point: “It’s probably the most westernized of a lot of the countries in Africa. So a lot of businesses will get a foothold in South Africa and then they might work up into different parts of the continent.”

The Affordability Equation — And Why It’s Shifting

Palaniappan asked Holland directly whether Africa’s core value proposition, like India’s before it, ultimately comes down to cost. Holland didn’t dodge the question.

“India has become a lot more expensive now,” he said. “Eight, nine years ago, India was still very, very affordable. With all the demand on talent, people know what they’re worth and they can ask to be paid more, which then costs go up.” He described clients who saw quarterly price increases of 15% just to keep pace with local wage inflation. Africa, by contrast, is earlier in that cycle — global demand hasn’t yet driven up local wages the way it has in India, though Holland noted that large employers like Google and Amazon are already establishing a presence on the continent.

He also pointed to a cultural shift in how openly companies discuss offshoring. “Pre-COVID, it was almost like businesses when they talked about offshoring, it was a bit taboo... Now, post-COVID, people are like, ‘Yeah, I’ve had 20 people in Bangalore for 10 years.’” Rising costs of living in the US, UK, and Australia have made the math increasingly unavoidable for businesses trying to stay profitable: “If you can get someone doing the exact same job, but it costs 70% less, then businesses are saying, well, I’m going to do that.”

Underlying all of it, in Holland’s view, is a shift in trust that COVID accelerated. “What COVID made everyone appreciate... is that I can trust my people working remotely to do their job if we’re tracking the outcomes of what they do. If I’m in Boston and I’ve got a team member in Boston that’s working from home anyway, well why can’t I have a team member in Johannesburg or Bangalore doing the same work?”

The AI Question: Does Cheaper Labor Even Matter Anymore?

The most pointed exchange of the conversation came when Palaniappan raised what he called playing “devil’s advocate.” If AI is allowing companies to do the same work with a fraction of the headcount — he cited an example of a company that reportedly went from 52 employees to eight — does the whole premise of chasing cheaper labor abroad start to break down? If you only need eight people, why not just hire eight people locally?

Holland’s answer was refreshingly candid about the uncertainty in the room. “I don’t think anyone has the answer yet. Every business I speak to now has a different perspective on it.” He described playing golf with a business owner who’d cut his team from 22 to 12 while becoming more profitable than ever, driven by AI efficiency — and, in the same breath, other businesses that tried to cut headcount with AI and had to reverse course and rehire because “the AI wasn’t the efficiency they thought they would get.”

Holland laid out two divergent futures he sees as plausible. On one end: mass unemployment. “We actually need way, way less people across the entire economy, and we end up at 25, 30 percent unemployment globally. That’s a pretty drastic position. It’s not impossible. I think it’s a low probability, but it’s not impossible... The USA cannot possibly survive with more than 20 percent unemployment. The country will implode on itself.”

On the other end is a more optimistic scenario, and it’s the one Holland is building his business around: AI as an equalizer for the developing world. “If we can have people that are based in South Africa, Kenya, Philippines, Colombia — doesn’t matter — and you upskill them with the latest tools... they can perform at two to three times higher than what they otherwise would have three years ago. And then all of a sudden you can have lower-cost resources doing the same work but at a higher level than previously possible.” For a business owner, he added, “this is amazing — I can get people that are much more affordable, doing work at a really high level because they’re using AI tools.”

He offered a concrete example: a client in Toronto had built out 20-25 AI agents running parts of their business, with the CEO and CFO each managing some directly. But agents need constant supervision. “You have to actually manage them. They break, something’s not working, you need to fine-tune it... it’s not a ‘you do it once, you leave it there, and happy days, you go sit on a beach while your business makes all this money.’” TMA now has two people in Johannesburg dedicated to managing that client’s AI agents — a role that didn’t exist a few years ago.

He also shared a striking data point from a French airline-software client: “Of their thousand engineers, no one writes code anymore. Literally no one writes a line of code. They’re all reviewing code. They’re all on their phones watching the code build.” That shift, Holland argued, is changing the profile of the talent companies need — not less experienced people, but more experienced ones who can supervise AI output. “So rather than getting very early-stage grads who don’t have the experience yet, it’s actually targeting the people who do have a lot of experience... We can go and target the top 10 percent. It’s harder to do in India now because the top 10 percent are getting paid a lot of money. We don’t have that saturation in these markets at the minute.”

Summing up the uncertainty, Holland offered one of the conversation’s sharper lines: “There’s this saying that you’ve probably heard — AI won’t take your job, but someone using AI will take your job.”

Beyond the Bottom Line: Culture, Trust, and Why Remote-Only Failed

Palaniappan raised a challenge that goes beyond skill or price: the fatigue that comes with building trust across cultural and geographic distance. Holland admitted TMA learned this the hard way. “When we first took the business into Africa... we did a work-from-home model, and it was a disaster. It didn’t work 98 percent of the time.” The fix was physical offices: pristine, well-equipped spaces in each city where TMA’s talent works alongside other engineers, marketers, and business professionals, creating a sense of team and accountability that pure remote work didn’t provide. It also lets TMA intervene directly when something’s off: “We’ve got managers on the ground that can actually go and sit next to them and have a coffee and say, what’s happening? Your performance has dropped off. Is there something we need to know about?”

But Holland was clear that the deeper responsibility for culture sits with the client, not the vendor. “That always comes down to treating people no different if they’re based in Johannesburg or they’re based in Seattle. It’s how they bring them into team meetings, how they speak to them the same as they would speak to any employee. If you foster a nice culture like that, you get loyalty and longevity, and then you get better results as well. But it does take effort.”

Entrepreneurship and Creativity: Is Africa Just Playing Catch-Up?

One of Palaniappan’s more provocative questions was whether developing economies are destined to remain in a support role — providing affordable labor to execute someone else’s vision — rather than originating new ideas themselves. Holland pushed back, pointing to Africa’s fintech sector as evidence of homegrown innovation. “MPESA was actually developed before WeChat, and it’s a full financial system that sits on an app on your phone... Nigeria has a huge tech entrepreneurial startup scene.” He described a grassroots hustle culture across the continent: “Most Africans I meet have a side hustle. By nature, there’s this hustle entrepreneurship mentality.”

He does concede the obvious gap: Africa isn’t attracting Silicon Valley-scale venture capital. “There’s not like the unicorn VC money — people aren’t putting five billion dollars into a company like you are in Silicon Valley.” But he sees AI tools lowering the barrier to entry for African founders in a way that could change that calculus over time: “Now you don’t need capital to go and build a startup. You don’t need to go and hire engineers to build an idea that you’ve got. You can get a license to Claude Code, put a certain amount in per month, and go build it.”

The Perception Problem

Asked about political stability, Holland said he’s personally never run into trouble operating in the countries where TMA works. His bigger concern is reputational, not operational — specifically, how migration coverage in Western media shapes perceptions of Africa as a business partner. “I think what the bigger issue is now is what’s happening in the media around migrants... it’s too often being pointed at — it’s someone from Africa, it’s someone from Morocco. And it’s only telling part of the story... That’s not the real Africa that I know.”

He argued that this narrative directly complicates his sales pitch: “It makes my life more difficult because I’m convincing businesses to look to Africa for their global resourcing. But if all they’re seeing on the news is that migrants are causing problems in their own country, and those migrants are from Africa, then that subconsciously or consciously changes their view as to whether they want to engage with people from the continent.” He turned the lens back on the US as well, noting the political polarization he’s observed there: “I’ve never seen — I mean, the US — I’ve never experienced before, the last probably four years, is almost a hatred between political parties... there’s a lot of things simmering underneath the surface in America.”

Krish’s Own Playbook

Toward the end of the conversation, Holland turned the tables and asked Palaniappan why he wouldn’t look to Africa when adding resources to his own US-based company. Palaniappan laid out his personal decision hierarchy: local talent within driving distance first, for the value of in-person connection; then talent elsewhere within the US; then, if cost becomes the deciding factor, international markets — where he’s worked with people in the Czech Republic and Ukraine, and extensively with talent in India, drawing on his own upbringing there to navigate regional differences in colleges, credibility, and culture.

His core caution about outsourcing to any new region, Africa included, wasn’t about talent quality — it was about the ongoing relational work required to make a distributed team function, even when AI is doing much of the technical heavy lifting. “Even if you’re building software, even if you’re using AI to build software, you don’t actually hire a developer like you did three years ago. There’s still a lot of conversation that needs to happen constantly so you’re building the best quality software... There’s got to be a connect, or lack of disconnect, between your team and that person or those people.”

He also named a practical awareness gap that Holland’s business exists to solve: most people, he noted, can probably name fewer than twenty of Africa’s roughly fifty-eight countries, let alone distinguish the talent, culture, working norms, and political context of South Sudan versus Mauritania versus Kenya. “If there’s a way to bridge that gap, I can see more people wanting to explore this as an option, so they don’t feel like they’re coming from a place of being ignorant about who they’re going to be potentially working with.”

Holland’s closing point tied the whole conversation together: the decision calculus for every business leader now runs through AI first. “A lot of decision-makers, well, how does — can AI automate it? If not, how do I have someone that can help me use AI to do it? If not, what’s the human I need to do it? And then how much does it cost? We all as business professionals are weighing that up all the time.”

Closing Thoughts

What emerges from the conversation isn’t a simple sales pitch for African outsourcing — it’s a picture of an industry in flux, where the old logic of “cheaper labor, same work” is being rewritten by AI in real time, and where the winners may be the regions that combine affordability with rapid AI adoption rather than those competing on cost alone. Holland’s bet is that Africa, still early in its global-talent journey and unburdened by the wage saturation now facing India, is positioned to make that leap.

Gerard Holland is the founder of Talent Match Africa. More information is available at talentmatchafrica.com.

Viktor Popovic has closed two very different kinds of impossible sales. The first was convincing an old-school pressure washer manufacturer, in 2003, that people would actually buy heavy equipment over the internet. The second, twenty years later, is convincing payment processors to compete against each other in real time for the same merchant. Between those two sales sits a masterclass in what it actually takes to sell something the market isn’t ready to buy.

AI + Snowpal API: Reduce Time to Market

Podcast

How One Founder Cracked Two Impossible Sales — on Apple and Spotify.

The first sale is never the one you planned for

Viktor didn’t set out to sell pressure washers. He’d built a list of roughly 40 products tied to the aviation industry — his original field of study — but a keyword analysis run by his business partner turned up an unexpected signal: “pressure” had unusually high search volume. One of the aviation-adjacent items on his list happened to be a pressure washer used for cleaning hangar floors. That accident of keyword research became a 21-year business.

“A friend asked me if I wanted to start a business. Without a second thought — yes, I'm ready. Why not?"

But finding the product was the easy part. The real sales problem was upstream: getting manufacturers to trust an unproven sales channel. In 2003, the standard model was regional reps who drove vans full of equipment around town, pulled machines off the truck, hooked up a garden hose, and demoed them live. Viktor was asking manufacturers to abandon that entirely and hand their equipment to a stranger promising to sell it through a browser. It took him six months to land his first vendor, a company called Cam Spray out of Iowa. The first actual sale — a cold-water diesel-powered pressure washer to a U.S. military base in San Diego — came down to a simple phone call and a fast, confident shipping quote.

The lesson he draws from it: the hardest sale often isn’t to the end customer. It’s convincing the party one step removed — the vendor, the partner, the gatekeeper — that a new way of doing business is worth the risk.

The second time around, he was wrong about what would be hard

When Viktor started Avendo, a fintech SaaS company that lets credit card processors compete for merchant transactions in real time, he assumed the sales motion would be straightforward. Merchants would obviously want lower processing rates. Processors would obviously want to compete for that business. “Why wouldn’t they love this idea?”

He was wrong. Payment processors have run the same playbook for 50 to 60 years: evaluate a merchant, assess risk off their statements, quote a flat rate, done. Avendo was asking them to shift into a model where they compete for the same merchant’s business transaction by transaction. That’s not a product objection — it’s an identity objection. It took Viktor seven or eight reworked pitches to find language that got processors past their blind spots and objections before the idea started to click.

“I thought the sales process would be where I need to worry, that everybody would be on board because the idea is great — why not? Man, was I wrong. It's actually the hardest part: getting payment processors to change the way they think, because they've been doing business this same way for the last 50-60 years.”

Notably, once it did click, it clicked fast — because the pitch to merchants and referral partners is genuinely simple: save 1% on a million-dollar-a-year processing volume, and that flows straight to net margin. Decision-makers get it in one sentence. The friction isn’t in the value proposition. It’s in getting the party whose behavior has to change to actually change it.

Referral partnerships beat cold outreach — but only after the failures teach you why

Before landing on what works, Avendo ran seven or eight different marketing motions in parallel: cold email, referral partnerships, paid advertising, and more. Viktor is candid that most of it didn’t work on the first try. One cold-email platform was pulling leads from what turned out to be a stale database — they were spending real money generating zero responses before they figured out the list itself was the problem. Email deliverability issues meant learning to run domain warm-ups, rewrite subject lines, and rebuild sender reputation from scratch.

What eventually worked was narrowing to three referral partner types who already understand net margin economics well enough to sell on Avendo’s behalf without much friction: business consultants and coaches, fractional CFOs, and accounting firms. These partners refer their clients into Avendo, and Avendo reciprocates leads back to them with client approval — a two-way referral loop built on partners who don’t need convincing on the math.

The broader point: there’s no way to know in advance which channel will work. The only path is running several simultaneously, tracking results honestly, and being willing to kill a channel that isn’t converting rather than defending the plan for its own sake.

80% planning, 20% execution — and still 70% wrong

A mentor once told Viktor that a well-run initiative is 80% planning and 20% execution — get the plan right and the execution mostly takes care of itself. He believes it, and he still spent months in heavy planning before launching Avendo. And yet roughly 70% of that original plan changed once reality intervened.

That’s not a contradiction. The planning wasn’t wasted just because the specifics changed — it forced him to actually understand the payment industry’s layers (network fees, acquiring banks, issuing banks, card types, government and gift cards) instead of assuming his merchant-side experience had already taught him the business. Planning, in his framing, isn’t about predicting the future correctly. It’s about doing the homework deep enough that when the plan breaks, you know enough to fix it fast.

Resilience is a skill, not a personality trait

Viktor doesn’t describe himself as naturally thick-skinned. He describes himself as built that way by repetition — pitching processors seven or eight different ways, absorbing rejection after rejection, and treating each “no” as information about a blind spot rather than a verdict on the idea. His practical advice for staying in a sales grind that isn’t paying off yet: celebrate small wins deliberately. Hiring the right person, closing one meaningful account, hitting a minor milestone — mark it, even briefly, because the wins that matter get lost if you’re only measuring against the ten-million-dollar outcome still years away.

The takeaway for anyone selling something the market doesn’t understand yet

Two sales, two decades apart, same underlying pattern: the product wasn’t the obstacle. The obstacle was convincing someone whose business model, habits, or risk tolerance had to change. Viktor’s approach to both is the same — treat every rejection as a missing data point, keep reworking the pitch until it lands, lean on partners who already understand your economics, and measure progress in small wins rather than waiting for the finish line to feel good.

“It's just trial and error, I think that's the bottom line. I don't think there's a secret to it, or a crystal ball you can look at.”

As he put it on the podcast: don’t get discouraged. “Not him — let’s go tweak something, do it this way.” That, more than any framework, is what got two very different sales across the line.

Summary

For sales engineers evaluating go-to-market motion design: the core signal from this conversation is that objection surface area scales with how entrenched the incumbent workflow is, not with product complexity — Viktor’s hardest technical sell wasn’t a feature gap, it was displacing a 50-60 year old risk-assessment heuristic (flat-rate quoting off a merchant’s statements) with a real-time, transaction-level competitive bidding model, which required rebuilding the champion’s mental model before any pricing conversation could land; his resolution path was iterative pitch-architecture testing (seven to eight distinct framings) to identify and patch objection blind spots rather than optimizing a single script, paired with a channel-attribution pivot away from cold outbound (killed by stale list decay in a purchased database, undetectable until response-rate analysis surfaced it) toward a referral-partner model selecting for partners who already carry the requisite domain literacy — fractional CFOs, accounting firms, consultants — so the value prop (basis-point margin capture at the transaction level) requires zero re-education before it converts, which is the throughline: reduce time-to-comprehension for the buyer by routing through intermediaries who’ve already internalized your unit economics, rather than trying to compress that education into the pitch itself.

In this episode, ⁠Krish Palaniappan⁠ speaks with ⁠Brian Samson⁠, founder of ⁠Plugg Technologies⁠, about the evolving landscape of remote work, particularly in the context of nearshoring and offshoring. Brian shares insights on the benefits of hiring talent from Latin America, the cultural nuances that affect remote collaboration, and the importance of a rigorous hiring process to mitigate risks associated with international hiring. The conversation delves into the value of talent beyond cost savings and the challenges faced when hiring from different countries.

• Originally featured on the Snowpal Podcast with Krish Palaniappan

• Guest: Brian Samson, Founder of Plugg Technologies

Most companies weighing nearshore hiring ask the wrong question first. They ask how much cheaper it is, when the question that actually determines whether the decision pays off is how much value they are getting for that lower cost. Host Krish Palaniappan spent much of his conversation with Brian Samson pressing on exactly that gap, playing devil’s advocate at nearly every turn, and the exchange produced one of the more rigorous breakdowns of nearshore economics available on any podcast. Krish did not let Brian get away with vague claims about savings; he wanted the actual math.

What emerged is a framework that treats nearshoring less like a discount and more like an arbitrage calculation, one where a company can save 50 percent on cost while absorbing only a 10 to 20 percent dip in output quality, netting a real gain in value rather than just a lower invoice. That distinction, cost savings versus value creation, is the thread running through the entire episode.

Samson has built his career around proving that math out in practice. He has spent 11 years in nearshoring, made more than 500 placements, and built three separate companies to $4M ARR each. He moved to Buenos Aires with two suitcases, grew a software development team there to 80 engineers, and later exited that business. Today he runs Plugg Technologies from Hawaii, placing senior Latin American developers, DevOps engineers, QA specialists, and data engineers with U.S. companies.

The Real Math Behind Nearshoring

Krish Palaniappan pushed Samson to defend nearshoring on grounds other than price, asking directly whether there was any reason to hire nearshore or offshore that had nothing to do with the dollar amount being saved. Samson’s answer reframed the entire conversation around labor arbitrage rather than simple cost cutting. Using Mexico as an example, he walked through the numbers: a U.S. based technical role paying a $150,000 base salary actually costs a company closer to $200,000 once benefits, FICA, and employer taxes are factored in. The equivalent role in Mexico, once local benefits like the aguinaldo (a mandatory 13th month salary) are included, runs closer to $100,000 all in.

That is a 50 percent cost reduction. But Samson was careful to note that quality does not drop by the same percentage. In his experience, the quality gap between a well vetted nearshore hire and a U.S. based one runs closer to 10 to 20 percent, which means the net effect is closer to a 30 percent gain in value once cost and output are weighed together. This is the calculation Samson wants hiring managers to run before they dismiss nearshoring as a race to the bottom on price. It is not about finding the cheapest person available, it is about finding where the value curve actually bends in a company’s favor.

The Cultural Question Most Hiring Managers Get Wrong

Krish Palaniappan raised a pointed objection that many hiring leaders quietly share: if a company already trusts a domestic hire’s resume, LinkedIn history, and legal accountability without a second thought, why should international hiring require extra scrutiny? “I’m not worried that Brian Samson is Brian Samson. I’m not worried that Brian’s resume is any different from what Brian purports that resume to be. I go to LinkedIn’s profile. I know Brian’s been doing this and I trust everything that Brian says,” said Krish Palaniappan, framing the deeper issue as one of unfamiliar geography and legal systems rather than talent quality itself.

Samson’s response separated two distinct kinds of culture that often get conflated. There is the surface level culture of customs and communication style, and then there is what he called startup culture, the shared experience of solving hard problems under real constraints. He argued that the attributes most hiring managers actually want, critical thinking, resourcefulness, grit, and humility, are becoming harder to find in populations that have not had to navigate real adversity. Latin American professionals who have lived through hyperinflation, labor strikes, and menu prices that change so often they are written in chalk develop those traits out of necessity. Samson pointed to the growth of venture capital ecosystems in Argentina, Brazil, and India as evidence that this same startup pressure is now producing a deep bench of talent that has been tested the same way U.S. founders have been tested.

The One Time a Candidate Was Not Who They Said They Were

Krish Palaniappan’s skepticism about international hiring risk was not abstract, and Samson met it with a real story rather than a reassurance. Over five years running Plugg Technologies, there was exactly one instance where the person who showed up for the first day of work did not appear to be the same person who had completed the interview process. “So in other words, Brian, you hired somebody and then the person who showed up to the job was different from the person who actually took the interview initially,” said Krish Palaniappan, confirming the detail before moving on.

Samson’s takeaway was not that international hiring is inherently riskier, but that hiring rigor matters more than geography. Companies that skip background checks, reference calls, and video interviews in a rush to fill a seat are the ones most exposed to this kind of problem, regardless of where the candidate is based. A disciplined process, video verification, reference checks, and a structured interview loop, catches this before it becomes a first day surprise. This is a useful reminder for any company evaluating nearshore staffing partners: the safeguard is not avoiding international talent, it is building a hiring system rigorous enough to trust regardless of where the candidate lives.

AI Is Not Killing Nearshoring, It Is Multiplying Its Value

The most forward looking exchange in the episode centered on whether AI tools make nearshoring less necessary, since companies can now do more with fewer people. Krish Palaniappan pushed this scenario hard, citing a founder who went from 50 employees to eight and asking whether the savings from AI adoption might simply replace the savings companies used to get from hiring abroad.

Samson’s answer was that the two are not competing forces, they compound. A company that combines a nearshore team with AI tooling gets what he called a double bonus arbitrage: the labor cost savings of nearshoring layered on top of the productivity gains from AI, rather than one canceling out the other. He was careful to note that AI is not a U.S. exclusive advantage; nearshore talent is adopting the same tools just as quickly, so the productivity gap does not disappear, it compounds in the buyer’s favor on both sides of the equation.

Why the Engineering Org Chart Is About to Look Different

Both Samson and Krish Palaniappan agreed that the makeup of engineering teams is shifting in ways that are hard to predict from historical hiring templates. Samson argued that mid-level engineering managers, people too senior for day to day coding but not senior enough to operate at an executive level, are increasingly exposed as companies flatten their organizational structures. He pointed to a pattern he first observed at a San Francisco unicorn: engineers overwhelmingly prefer leads who are still writing code themselves, and professionalized management layers that pull people away from hands on work tend not to last.

Krish Palaniappan extended the argument beyond engineering, noting that software developers are far from the only role that could be affected by AI driven efficiency gains. “I don’t know why it’s just software engineers that everyone seems to come after. I think there are a lot of roles that are going to disappear. It’s not just us,” said Krish Palaniappan. Both agreed that the traditional formula of one architect, three developers, one product manager, and one tester is unlikely to hold, and that team composition going forward will need to be built role by role rather than templated from past hires. Samson closed the thread on a striking note about how far this shift has already gone: “You’re building a software company, you’re building software, but you actually don’t have a technical co-founder, which is a statement that you one could not have made a year ago or maybe two years ago,” said Krish Palaniappan, reacting to Samson’s point that AI tools now let non-technical founders get a product to the validation stage before ever hiring an engineer.

How to Get Started

For companies weighing whether and how to bring nearshore talent into their hiring mix, the conversation points to a few concrete next steps.

1. Run the actual arbitrage math before deciding. Compare the fully loaded cost of a domestic hire against the fully loaded cost of a nearshore hire, then weigh the realistic quality gap, not the assumed one, before making a call.

2. Tighten the hiring process rather than avoiding international candidates. Video verification, reference checks, and a structured interview loop reduce risk far more effectively than staying domestic out of caution.

3. Pair nearshore hiring with AI adoption rather than choosing between them. The two produce compounding value when used together, not competing savings.

4. Rebuild team composition role by role. Do not assume the engineering org chart that worked two years ago still applies. Start from the specific problem being solved and staff accordingly.

The Bottom Line

The core insight from this conversation is that nearshoring, done with real rigor, is not a shortcut around quality, it is a way to buy more value for the same dollar. Samson’s own path from a San Francisco talent recruiter to a founder running nearly 100 people across Latin America shows what happens when that math is applied consistently over a decade.

Summary

🌎 Brian’s Background & Business Focus

• Former head of talent in SF tech

• 10+ years operating in Latin America

• Plug Technologies founded in 2022

• Focus: Matching U.S. companies with Latin American tech talent

• Value: Same or similar time zones → better collaboration & cultural proximity

🧠 Offshoring vs Nearshoring vs Onshoring (Key Definitions)

Outsourcing: Contracting work outside your core team

Offshoring: Hiring across oceans (e.g., US → India)

• Lower cost, follow-the-sun model

  Nearshoring: Hiring in nearby countries, same or close time-zone (e.g., US → LATAM)

• Cost savings + real-time collaboration

  Onshoring: Hiring in your country

• Shared culture, fewer risks, highest cost

💸 Labor Arbitrage & Value Equation

• Offshoring/nearshoring isn’t only about cost reduction

• Value focus:

  • Example: $200K US engineer → $100K LATAM engineer

  • ~50% savings with maybe 10–20% difference in quality

  • Net value gain ~30%

💼 Cultural & Skills Considerations

• LATAM talent described as:

  • Resourceful, gritty, clever, hardworking, loyal

• Result of real-world economic pressures & scrappy startup environments

• “Top talent exists everywhere — location is less relevant now”

👀 Trust, Vetting & Hiring Challenges

• Global hiring challenge: fake candidates & misrepresentation

• Rise in impersonation cases with remote interviews

• Solution: rigorous hiring process

  • structured interviews

  • video calls

  • references

  • background checks

🤖 AI’s Impact on Talent Models

• AI lowers cost of building software

• Teams can be smaller & more efficient, wherever they’re located

• Future = nearshoring + AI → double efficiency advantage

• Core leadership team still valuable close-by

• Supplemental talent can be global

🚀 Entrepreneurship in the AI Era

• Lower barriers to start companies than ever

• Offshoring + nearshoring + AI → “multi-order efficiency boosts”

• More global entrepreneurs, less need for huge seed capital

👷 Future of Engineering & Workforces

• Composition of engineering teams will change

• Fewer engineers needed, but higher-quality roles

• Rise of lean teams

• Mid-level managers at risk (trend already visible in Big Tech)

• ICs and senior leaders remain crucial

🎓 Education & Young Talent

• Universities lag behind tech evolution

• Students must self-learn AI and modern tools

• Product-thinking engineers become more valuable

🔮 Predictions on AI & Jobs

• AI won’t replace developers wholesale yet

• But team structure, workflow, and required knowledge will reshape

• “Everyone must re-learn how to build software”

Frequently Asked Questions

What is nearshoring in business terms?

Nearshoring means hiring talent in a nearby country that shares a similar time zone to the hiring company, as opposed to offshoring, which sends work to a distant, often lower cost region regardless of time zone overlap. Brian Samson of Plugg Technologies describes nearshoring for U.S. companies as hiring across Latin America, where teams remain available for real time collaboration during the U.S. workday.

Why do U.S. companies choose Latin America over Asia for nearshoring?

Time zone alignment is the primary reason. Brian Samson explains that Latin American countries fall on U.S. time zones or close to them, enabling same day collaboration on tools like Slack and Jira, whereas offshoring to Asia typically sacrifices that overlap in exchange for deeper cost savings.

What roles can be nearshored to Latin America?

Software developers, DevOps engineers, QA specialists, and data engineers are the roles Brian Samson places most often through Plugg Technologies. He notes that non-core functions like finance and accounting can also be outsourced regardless of location, while core technical roles benefit most from the time zone alignment that nearshoring specifically provides.

How much can a company save by nearshoring instead of hiring domestically?

Brian Samson estimates roughly 50 percent cost savings when nearshoring a technical role to a country like Mexico, once fully loaded U.S. costs like benefits and employer taxes are factored in. He argues the quality difference is much smaller, closer to 10 to 20 percent, which results in a net value gain rather than a simple discount.

Does AI reduce the need for nearshore hiring?

According to Brian Samson, AI does not replace the value of nearshoring, it compounds it. Companies that combine nearshore talent with AI tooling get layered savings, since nearshore teams are adopting the same AI tools as quickly as U.S. based teams, meaning the productivity gains apply on both sides of the equation rather than eliminating the need for nearshore staffing.

What does Plugg Technologies do?

Plugg Technologies is a nearshore staffing company founded by Brian Samson that connects software developers, DevOps engineers, QA specialists, and data engineers across Latin America with U.S. companies. The company has made more than 500 placements over 11 years and is led by Samson and his partner Ruben, both former expats in Latin America. More information is available at plugg.tech.

Brian Samson is the founder of Plugg Technologies and host of The Nearshore Cafe Podcast. This post is based on his appearance on the Snowpal Podcast.

AI + Snowpal API: Reduce Time to Market

AI + Snowpal API: Reduce Time to Market

Podcast

The People Who Spent 20 Years Becoming Experts Are About to Find Out That Experience Has Been Democratized - on Apple and Spotify.

The People Who Spent 20 Years Becoming Experts Are About to Find Out That Experience Has Been Democratized

Generative AI isn’t just automating tasks — it’s distributing the very thing that made experienced leaders valuable. For decades, seniority meant accumulated intelligence. You knew things others didn’t. You’d seen cycles, patterns, failure modes. That institutional knowledge was the moat.

Kelly’s argument is that the moat is filling in. “Most leaders are where they are today because of their expertise,” she says, “but what happens when that becomes democratized?” When a junior employee with the right prompt can surface the same analysis a 20-year veteran could, the value equation changes completely. What leaders offer can no longer be just what they know. It has to be something harder to replicate — judgment, trust, the willingness to be accountable for decisions made in ambiguity.

That shift is why Kelly insists we’re not in a technology moment. We’re in a leadership moment.

AI + Snowpal API: Reduce Time to Market

Middle Managers Aren’t Obsolete — They’re Just Being Asked to Do Something They Were Never Trained For

The tech industry has a running fantasy: flatten the org, cut the middle, let AI coordinate what managers used to. Kelly thinks this is a mistake, and she’s blunt about why.

Middle managers are already the most burned-out segment of the workforce. They’re sandwiched between a C-suite selling an AI vision that isn’t fully real yet, and a workforce eager to use tools their companies haven’t figured out how to deploy. “The tools are not quite where some of the C-suite and board thinks they are,” she says. Meanwhile, managers are expected to execute a transformation that hasn’t been designed.

The role isn’t disappearing, but it is changing in a specific direction. The old job — relay information up, execute instructions down — is shrinking. The new job is orchestration: figuring out which work gets done by humans, which by AI agents, and how to hold that hybrid accountable to outcomes. It’s messier, more political, and more human than ever. The managers who survive won’t be the ones who master the tools fastest. They’ll be the ones who can navigate the parts of organizations that AI genuinely cannot touch.

That said, Kelly draws an important distinction between product companies and everyone else. In a product company, middle managers typically contribute directly — they’re in the codebase, the architecture, the design decisions. Their expertise justifies their seniority. In government agencies or traditional consulting hierarchies, where tenure drives promotion more than output, the calculus is different. If your job is coordination without contribution, AI makes it very difficult to justify that role.

Nobody Actually Knows How Many AI Agents Their Company Needs, and That’s the Problem

Krish put a question to Kelly that she called “a billion-dollar question for consulting companies”: who decides how many AI agents a company deploys, and how do you separate the ones every team shares from the ones that are specific to a single function?

The honest answer right now is: nobody has figured this out cleanly. What Kelly is seeing in practice is experimentation without governance — teams spinning up agents independently, in parallel, without coordination. The result isn’t efficiency. It’s complexity. “I have more complexity, not efficiency, because of all these AI agents I’m trying to manage,” is the phrase she keeps hearing from inside organizations.

Her prescription is a shared leadership agenda anchored at the C-suite level. The CHRO needs to be in the room, not just the CTO and CIO. HR, which has historically been left out of technology decisions, has the exact expertise this moment demands: how do you design work, structure spans of control, and build organizations around outcomes? Those questions don’t have technical answers. They have human answers. And HR is where that knowledge lives.

The principle Kelly keeps returning to is simplification. Before adding more agents, define what you need at the enterprise level and at the functional level, and be ruthless about eliminating overlap. The companies winning with AI aren’t the ones running the most experiments. They’re the ones that have decided what they’re actually trying to accomplish.

CEOs Are Saying “AI” 17 Times Per Earnings Call While Their Dev Teams Are Still Figuring Out the Tools

There’s a gap between the AI story being told and the AI reality being lived, and Kelly names it directly. Leaders know that positioning their company as AI-enabled can mean a two-to-three times valuation lift. The incentive to overclaim is enormous. And so they do.

Meanwhile, the teams actually building things are still working through which tools are ready for production, which workflows have genuinely changed, and which “AI transformation” initiatives are really just rebranded pilots that haven’t shipped. The board gets the aspirational version. The engineers get the uncertainty.

This isn’t always cynical — some of the gap is genuinely a lag between where the technology is heading and where it is right now. But Kelly doesn’t let leaders entirely off the hook. The fundamental problem is that most companies have invested heavily in AI tools without doing the hard downstream work: redesigning the job, rebuilding the workflow, doing the change management that actually makes transformation stick. She’s seen what that takes in consulting. It’s an 18-to-24 month roadmap, minimum. Most executives are measuring progress by next quarter.

The SaaS Apocalypse Is Probably Overblown — But the Market Doesn’t Seem to Have Decided Yet

Krish raised the SaaS conversation with something real: Atlassian went up 40% on earnings, then added another 5% the next day. Workday, Salesforce, Asana, Monday — companies that had been hammered for a year — are bouncing. The market keeps changing its mind.

Kelly’s read is that this whiplash is structural. Most of the broader economy is in a low-to-no-growth environment. That’s not purely an AI story — macroeconomic complexity is doing a lot of work here. But it means that AI stocks are essentially holding up the equity markets, which creates an outsized sensitivity to any signal about AI’s actual progress. Jensen Huang’s position — that SaaS companies need to evolve but aren’t going away — is closer to Kelly’s view than the doom narrative. These companies have distribution, customer relationships, and institutional trust that takes years to build. AI doesn’t make those irrelevant overnight. It does, however, require them to rethink what they’re selling and how they’re delivering it.

The Consulting Industry Built Its Junior Pipeline on Tasks That AI Now Does Better, Cheaper, and Faster

Kelly grew up in consulting. She knows the model: junior staff spend two years learning the craft through PowerPoint decks and memos, billing at a premium while absorbing industry knowledge from senior partners. That pipeline produces the partners of the future.

The problem is that AI has made the first half of that equation untenable. “You don’t need that junior consultant anymore to do that deliverable,” she says. AI can produce a polished analytical deck faster and cheaper than a first-year analyst, without the overhead. If the business case for hiring junior consultants was always partly about developing future partners, that calculus just got a lot harder.

The second challenge is more fundamental. What you hire McKinsey or Deloitte for is intelligence — the framework, the insight, the perspective accumulated across hundreds of engagements. That is precisely what generative AI is democratizing. The consulting model has to move toward problems that are genuinely hard: change management, human dynamics, the ethics of automation, the decisions that require judgment that can’t be offloaded. Firms that keep selling software implementation and document production are going to feel the pressure first.

Managed services faces an even steeper reckoning. The large-scale outsourcing model — teams in the Philippines and India handling operations at volume — maps almost directly onto what AI automates. Kelly is candid that she worries about what this means for countries where those jobs represent significant economic opportunity. The question of responsibility — who thinks through these consequences before making the switch — isn’t a business question. It’s an ethical one.

The Economy Looks Fine Until You Realize It’s Being Held Up by One Sector

The K-shaped economy isn’t a metaphor. It’s a description of what’s actually happening: returns to capital and highly-skilled knowledge work are accelerating, while pressure mounts on everyone else. The upper tier keeps spending. Luxury travel, airlines, fine dining — demand stays strong. Spirit Airlines goes bankrupt. Both things are true at the same time.

Kelly isn’t panicking, but she’s watching the lagging indicators that don’t show up immediately: credit card debt rising, spending rotating toward necessities, the compounding effect of price pressure on anyone living without a significant financial cushion. Q3 and Q4 of this year, she thinks, will be telling. The part of consumer spending that looks healthy right now may be masking a delayed adjustment.

The deeper point she makes is about interconnection. The U.S. economy is not an island. Supply chains, outsourcing relationships, oil markets, demographic shifts in Asia — all of it connects back. When companies automate away managed services jobs in India, that has consequences that eventually ripple through trade, through goods, through prices here. “The bagel you go get for breakfast has tremendous world economic consequences,” Kelly says — and most of us haven’t thought about the chain that produced it.

The New Skill Isn’t Learning to Code — It’s Learning to Unlearn

The most surprising advice Kelly offers doesn’t come from a workforce development framework. It comes from a long look at what AI actually can’t do. Empathy, wisdom, ethical judgment, creativity, the ability to hold complexity and act in ambiguity — these aren’t soft skills. They’re the hard ones. They’re the ones nobody has systematically developed, because the STEM premium made everything else feel optional.

Her read: the professions most immune to AI automation aren’t the ones that sound impressive on a LinkedIn profile. They’re healthcare, education, skilled trades. There are already labor shortages in all three. The culture hasn’t caught up — it’s still glamorizing the path of the YouTube influencer, the vibe coder, the growth hacker. But the plumber and the electrician may end up significantly better positioned in the economy that’s actually forming.

Krish offered his own version of the same idea from the builder’s perspective. The new skill, in his words, is not any particular language or algorithm. It’s “how do I solve this problem better using the current suite of people, agents, technologies, and the changing dynamics of the larger world?” The muscle memory that made experienced engineers valuable — the deeply ingrained patterns of how software gets built — is now partly a liability. The engineers who thrive will be the ones who can unlearn it.

Kelly loved that framing: “That might be your snippet for social sharing.”

The Decisions We Make About AI Today Will Shape Things for Generations

Kelly’s closing wasn’t hedged. She believes this moment is genuinely consequential — not in the hype-cycle sense of transformative technology, but in the sense that the choices leaders make right now about how to use AI, and how to treat the people displaced by it, will compound.

Her book, Reclaim the Plot, is written as fiction, drawing on real patterns she’s observed across tech and consulting without naming anyone. The central argument is that leaders keep chasing new technologies at the expense of people, and that this moment requires something different: an active rewriting of the story, not just an optimization of the current one.

The session ended the way all good conversations do — a little open, a little unresolved, with more questions raised than answered. Kelly’s dinner order was sushi, steak, and New York cheesecake. Krish’s assessment: she’s not saving that thousand dollars a month.

Listen to the full conversation on the Snowpal Podcast. Check out Dr. Kelly Monahan’s new book, Reclaim the Plot: How Leaders Rewrite the Story When AI Rewrites Work.

AI + Snowpal API: Reduce Time to Market

Podcast

Who Needs Developers? (Everyone, Actually) - on Apple and Spotify.

From Moscow to the World: A Founder’s Journey

Asia Solnyshkina did not plan to become a global founder. In March 2022, when war broke out between Russia and Ukraine, she left Moscow with little more than her laptop and her two children. There was no plan, no destination, no certainty about what would come next.

“I left Russia with just my laptop and two kids,” she recalls. “Basically with no plan of what I will be doing, how I will be managing my company.”

What followed was a journey across continents. First Georgia, then three years in Mexico City — “a brilliant, beautiful place” — and now an attempt to settle in the United States. Her company, ProSense Digital, builds custom software for businesses worldwide: ERP systems, CRMs, websites, and complex automation tools. Clients range from the United States to Latin America to Australia.

The eight-year-old company was remote from the start, which softened some of the disruption. But rebuilding a business across countries, time zones, and cultures forged something more durable than any office could: resilience paired with agility.

“I do feel that right now I can adapt to the new world a lot,” she says, “because I’ve been traveling, I’ve been meeting different people, I’ve been working with different businesses, rebuilding the whole structure, the whole company, losing partners and all of this. I feel comfortable in this new AI era, which is pretty fast.”

What Good Design Actually Means

Working across Russia, Latin America, Australia, and the US revealed striking differences in how clients approach software. In Russia, Asia found, clients often arrived focused on aesthetics — the pretty button, the beautiful interface — sometimes at the expense of the underlying system.

“What I felt about building business in Russia was, it was all about, let’s do the pretty UI. And that’s it. We’re not thinking about the UX,” she explains. Her work became as much about education as engineering: helping clients see that beneath every button there must be a system that serves a real business goal.

This is where the conversation got pointed. What does “good design” actually mean to engineers who want specifics, not adjectives?

For Asia, the answer is unromantic: good design is design that converts. Amazon, with its dense interface and relentless commercial focus, is good design. Award-winning agency sites with floating parallax and ornate animations often are not. “I’m not thinking about how beautiful it is, I’m thinking about the goals. I’m thinking about what people are trying to achieve.”

That definition is debatable — and Krish pushed back. Plenty of well-designed products fail to find product-market fit, derailed by timing, capital, or distribution rather than craft. But the underlying point holds: design exists to serve business outcomes, not to win Dribbble shots.

The AI Inflection: Cheaper Software, More Software

A reasonable prediction, repeated for years, holds that AI will end software development as a profession. Asia’s lived experience contradicts it.

“I’ve been told for years in a row that software development will be dead like in a year, in a month or so. Right now what I’m experiencing with my exact business — it’s actually not just thriving, but my client base grew.”

This echoes the Jevons paradox: when something becomes cheaper to produce, demand often expands rather than contracts. Software is following the pattern. Businesses that once viewed custom development as expensive and slow now see automation as accessible — and they are bringing more problems to the table than ever.

Asia’s design and prototyping process has changed dramatically. Where her team once spent weeks in Figma, iterating through three or four rounds before showing clients anything tangible, they now prototype directly in tools like Lovable. By the time the polished design would have arrived under the old process, the market itself might have shifted.

“The main essence of what we’re doing is prompt engineering,” she says. “Creating a good task for AI so it could understand the problem we’re trying to solve. Not drawing beautiful buttons, but solving the real business problem.”

The Managed Services Question

If anyone with a credit card and a Lovable subscription can build software, what is a managed services provider actually selling?

Krish pressed on this directly. The traditional moat — knowing a particular language, framework, or architecture — has weakened as tools generate working code from natural language. So what does Asia’s company offer that a curious non-engineer cannot do alone?

Her answer pivoted away from the tool entirely. “I’m not using just the tool, because the tool is just the tool. I’m using my experience working 15 years in software development.” More importantly, she argues, ProSense Digital is not a body shop selling hours — it is a product company selling outcomes.

“We’re not trying to sell just the lines of code. We’re trying to sell the complete products that helps people with whatever they need.”

What AI changes for her company is leverage, not category. Experiments that once cost real money — A/B tests, prototype iterations, market probes — now cost almost nothing. That makes it easier, not harder, to do the thing she has always sold: understanding what users actually need versus what they say they need.

The honest concession: she may be wrong. “Probably in a year or two, I will have to go to some other business. But right now I do feel like this. We’re building products.”

What Founders Get Wrong

Asked what founders most often get wrong when scaling, Asia gave an answer rooted in the cost of conviction. Founders fall in love with their original idea and refuse to let market signal change their minds. “Sometimes founders stick to their ideas even though they are in the process of developing the product itself, they do understand that probably this idea is not right. But they’re investing a lot of time, a lot of money and a lot of everything.”

The discipline she advocates is experimentation as default. Talk to users, watch behavior, run tests, and accept that what people say they need is rarely what they actually need.

The conversation circled into a productive disagreement here. Krish raised the Henry Ford line — that customers asked for faster horses, not cars — and the iPhone launch, which Asia herself remembers as underwhelming at the time. Sometimes great products are not validated by initial reception. Sometimes the surveys say no and the founder presses on anyway.

The synthesis: even the giants get this wrong. Meta’s Metaverse spend, Google’s graveyard of canceled products, and the cool reception to Meta’s smart glasses all suggest that even well-resourced teams build products for ego, for investors, for narrative — not always for users. Asia’s framing: “Sometimes people are building products not to be successful.” It is a sharp observation about R&D, ego, and the pressure to appear ahead.

The Future of Software Development

Krish offered a candid read on his own field after more than two decades in it. Software has never been static, but the pace of change in the last two years is different in kind, not just degree. Several things have shifted:

The fundamental shift is that he no longer needs a developer to build software. After 20 years of always needing one, that assumption is gone.

Hiring is harder to think about, not easier. Yes, anyone can use these tools. But if a hire cannot reason from first principles about persistence layers, about why Postgres versus DynamoDB, about architecture trade-offs — then what value do they add beyond what the model already provides?

Architecture itself is changing. Engineers with muscle memory from the previous era have to actively unlearn old patterns. Newcomers have an advantage in flexibility but lack the scar tissue that distinguishes good decisions from bad ones.

The economics are commoditizing. Charging top dollar for code is over. Smaller teams shipping more software is the emerging shape. Founders report going from 54 people to 8. Yet layoffs are everywhere, and the gap between “AI made us more productive” and “we still have headcount” is closing painfully.

Production reality is more complicated than the demos suggest. AWS suffered outages that the company attributed to AI-generated code; senior architects must now approve generated changes there. Apple is rejecting vibe-coded apps from the App Store. Vibe coding is excellent for experiments and prototypes — Asia uses it actively — but production-grade systems still demand engineering judgment.

“I’m not comfortable pushing code to production that I’ve at least not seen one time,” Krish said. “I cannot have a tool generate code and then push it to production.”

Hiring in the New World

Asia’s hiring philosophy has quietly evolved into something unconventional. She does not run formal interviews. Instead, every manager keeps a stockpile of small, low-stakes tasks — the kind where a candidate failing would not damage anything important. When a CV catches her eye for curiosity and intelligence, the candidate gets one of those tasks.

“I’m observing how they are interacting in the real world setting.”

College degrees are not required. The trait she screens for, above all else, is curiosity — the willingness to engage with a world that is changing faster than any curriculum can keep up with. She is actively hiring vibe coders, not because they replace engineers, but because they extend her ability to run cheap experiments at scale.

On Jobs, Identity, and What Comes Next

Krish was direct when Asia asked whether he feared AI would take his job: “I’m not afraid because I know it is going to. I have no doubts about that. The job that I have done all these years — writing code, like every line of code — that job is gone. It’s not coming back.”

The dilemma is more subtle than replacement, though. Sometimes he sits down to write a line of code and hesitates because the tool can do it. Then the tool’s output is not quite right, so he rewrites it. At which point, why didn’t he just write it himself? The judgment about what to delegate and what to keep is a new skill, and it requires the engineering background he’s not yet willing to abandon.

“You want to use these tools to make yourself more productive, but I don’t want to use those tools to lose my agency. We are all born with a certain intellect, good, bad, or ugly. If you don’t end up using that, what is the point in living life?”

Asia’s view on AI’s broader employment impact is more optimistic. Yes, jobs will disappear. But new ones — for people who can think, adapt, and stay curious — will emerge. The transition rewards people who treat this as a moment to experiment, not a threat to defend against.

The Future of Managed Services

The managed services model for custom software development is undergoing a fundamental structural shift driven by AI-assisted code generation and rapid prototyping tools like Lovable. Historically, the value proposition of firms like ProSense Digital rested on deep technical expertise in specific stacks — React.js, Python, PHP — and the human capital required to translate business requirements into functional ERP or CRM systems over multi-month development cycles. Today, that cycle has compressed dramatically. Rather than spending two to three weeks on Figma prototyping followed by iterative design reviews, teams can now generate working UI prototypes through prompt engineering in a fraction of the time. The core competency has shifted upstream — away from implementation fluency and toward problem framing, requirements elicitation, and knowing what questions to ask the machine. Companies that continue to sell lines of code as a deliverable will face severe margin compression; those repositioning around product outcomes and experiment-driven iteration are finding, counterintuitively, that demand is actually growing as the Jevons paradox plays out: lower build costs are expanding the total addressable market for software.

The architectural risk introduced by vibe coding and LLM-generated codebases is becoming increasingly visible at scale. AWS’s recent production outages, attributed in part to AI-generated code reaching production without sufficient senior review, illustrate a critical gap: the speed at which code can be synthesized now far outpaces the institutional knowledge required to validate it. Key engineering decisions — selecting appropriate persistence layers (e.g., PostgreSQL vs. DynamoDB), designing for idempotency, managing stateful distributed workflows — require understanding that is not easily delegated to a generative model. Apple’s App Store rejections of vibe-coded submissions further underscore that AI-generated code often fails production-readiness criteria around security, performance, and platform compliance. The practical implication for engineering organizations is a bifurcated workflow: use AI-assisted generation aggressively in prototyping and experimentation phases, but ensure a senior architect with domain fluency reviews and approves anything moving toward production. The engineering background requirement hasn’t disappeared — it has simply migrated from writing code to governing the code that machines write.

A Final Thought on People

After a wide-ranging conversation, Asia closed with the observation that surprised her most across years of travel and work in Russia, Latin America, China, Singapore, Australia, and the US:

“All of us are people. We all are little children inside. We all have the same fears, the same joy, the same everything.”

Business cultures differ. Design preferences differ. Management styles differ. But under all of it, the people are remarkably the same — and the work, in the end, is for them.

Asia Solnyshkina is the founder and CEO of ProSense Digital, a product company building custom software for clients worldwide. Connect with her at prosense.digital or on LinkedIn.

AI + Snowpal API: Reduce Time to Market

Every company feels the pressure to go AI. Trade publications demand it. Investors expect it. And yet most AI pilots quietly fail — expensive experiments that produce dashboards nobody checks and chatbots nobody trusts. Sid Bharath, founder of Refound AI, has spent the past year helping companies move past that failure pattern. He builds AI agents for a living, runs his own business almost entirely on agents, and has a specific, repeatable framework for how he does it. In a wide-ranging conversation on the Snowpal podcast, he laid out the full playbook.

Podcast

How to Make Your Company AI-Native (Without the Hype) - on Apple and Spotify.

Let me guess. Someone in your leadership team has said the words “we need to be doing more with AI” in the last thirty days. Maybe it was a board meeting. Maybe it was a Slack message with a link to a TechCrunch article. Maybe it was you.

And so the team spins up a pilot. Buys a tool. Adds a chatbot to the website. Runs a few experiments. And three months later, the results are... fine. Not transformative. Not the productivity revolution the headlines promised. Just fine.

Sid Bharath has seen this movie dozens of times. As the founder of Refound AI — an AI consultancy that helps companies become genuinely AI-native — he spends his days cleaning up after exactly this pattern. And his diagnosis is always the same: you skipped the audit.

The Uncomfortable Truth About AI Adoption

Here is the thing nobody says out loud in AI vendor pitches: most AI projects fail not because the technology doesn’t work, but because companies deploy it without understanding their own operations first.

“The reason so many AI projects fail is you just try to do something and it doesn’t really make sense for your business,” Sid told Krish Palaniappan on the Snowpal podcast. “You can’t just pick a tool and hope it solves a problem you haven’t clearly identified.”

The FOMO is real. The pressure is real. But blindly adopting AI without understanding where your actual bottlenecks are is like hiring a team of consultants and sending them to the wrong office. The capability is there. The direction is missing.

Before you build anything, deploy anything, or buy anything — you need to know where your time is actually going.

What a Real AI Audit Looks Like

An AI audit is not a software scan. It is not a spreadsheet of your tech stack. It is a series of honest conversations with the people actually doing the work.

Sid’s team books one-hour sessions with every role in the organisation — product managers, engineers, designers, QA testers, salespeople, operations staff. The question is always some version of the same thing: walk me through your week. What takes the most time? What do you hate doing but have to do anyway?

That last question is the most revealing one. Because in every company, there is a category of work that everyone resents — the admin, the documentation, the status updates, the data entry — that nobody was actually hired to do but that somehow consumes enormous amounts of the day. That is where AI belongs.

“For some people, there’s a very clear thing they do every day where they’re like, ‘I hate doing this, but I have to do it and it takes up so much time — can you fix it for me?’” Sid said. “Those are the easiest ones.”

The audit maps the entire workflow: from how customer signals get collected and turned into product specs, through design and engineering and QA, all the way to how the product gets communicated to the market. The bottleneck is different for every company. For one it might be that product managers are drowning in Zendesk tickets and NPS surveys before they can form a single clear feature idea. For another it is that engineers ship fast but the sales team bleeds hours every day on proposal documents.

You do not know which one is you until you look.

A Concrete Example: The Sales Team That Was Losing 2 Hours a Day

Take a typical sales workflow. You have leads coming in, discovery calls being scheduled, proposals being drafted, contracts being sent, and CRMs being updated. The part that creates revenue is the conversation with the prospect. The part that eats up the day is everything around it.

Sid spoke to a sales team recently where every salesperson was spending at least two hours a day on admin — updating Salesforce, creating proposals, drafting follow-up emails, generating reports. Two hours. Out of an eight-hour day, 25 percent of each person’s capacity was going to work that a well-configured AI agent could handle in seconds.

Here is what happens when you fix that. The moment a sales call ends, an agent detects the completed meeting, reads the transcript, checks where the lead sits in the pipeline, generates a tailored proposal using the company’s existing templates, updates the CRM, and pings the salesperson on Slack with everything ready to review. Total time required from the human: thirty seconds to glance at the proposal and hit send.

The salesperson did not lose their job. They got two hours back every day to do the work they were actually hired to do — have more conversations and close more deals.

That is what a well-placed AI agent looks like. Not a chatbot on a website. An autonomous system that understands your workflow and handles the parts of it that don’t need a human.

Why Custom Agents Beat Off-the-Shelf Tools

At this point you might be thinking: can’t I just buy a tool that does this? There are plenty of AI-powered CRM integrations, proposal generators, and meeting summary tools on the market.

You can. And you will get 80 percent of the way there.

The problem is the other 20 percent. Every company has its own quirks — its own proposal format, its own CRM logic, its own approval process, its own exceptions. Off-the-shelf tools handle the generic case. They leave the specific, messy, exception-heavy details back on the human’s plate. And those details are usually the ones that mattered.

A custom agent built on your actual context — your SOPs, your templates, your business logic — can handle the full process. Not 80 percent of it. All of it.

This is what Sid calls the AI OS: an AI operating system. A single agent running on a server, connected to your existing tools, and loaded with a structured understanding of how your business actually works. The core architecture is reusable across clients. What changes is the context — the business-specific knowledge that makes the agent behave like someone who has worked there for ten years rather than something that just read your website.

The Meta-Point: Sid’s Own Company Runs on Agents

Here is where it gets interesting. Refound AI does not just build agents for clients. Sid runs his entire consultancy on the same system he sells.

When a prospect books a discovery call, an agent researches them and delivers a briefing before the meeting. When the call ends, the agent reads the transcript, drafts the proposal, and prepares the follow-up email. Every morning, Sid’s team wakes up to a digest in Discord: here is the state of the pipeline, here are the outstanding tasks for each client, here is what needs to happen today. When Sid finishes an audit interview, the agent turns the notes into a presentation deck ready for the client.

The result is a small team capable of running dozens of client engagements simultaneously. Sid cancelled most of his SaaS subscriptions. He lives primarily in his terminal, using Claude Code as his main development interface. The agents have access to Gmail, Google Drive, Discord, and a custom internal database. He does not log into most tools anymore — the agents do it for him.

“The only human work left,” he said, “is getting on a podcast, a discovery call, or doing an in-person audit interview. Everything else is agents.”

The Governance Question Nobody Wants to Skip

Running on agents sounds great until something goes wrong. And things do go wrong. Amazon made headlines recently when a series of outages were attributed to AI-generated code that bypassed engineering review. If your agents are writing to production databases, sending emails on your behalf, and updating customer records — you need to think carefully about what happens when they err.

Sid is direct about this: the answer is the human checkpoint. Every significant action an agent proposes is reviewed before it executes. The human can always abort. There is a meta-agent that monitors the operational agents and surfaces anomalies in the logs. When something goes wrong, the team diagnoses it and patches the agent’s instructions so the mistake does not happen again.

The key distinction he draws is between what he calls vibe coding — where a non-technical person tells an AI to build something and ships whatever comes out — and agentic engineering, where the agent produces the bulk of the output but a human with real technical judgment is reviewing every meaningful decision before it goes live. The first approach is how you get outages. The second is how companies like Anthropic build production systems that are 99 percent AI-generated and still reliable.

Agents are powerful. They are not magic. They still need human judgment at the critical moments. The goal is to make sure humans are only spending time at those critical moments, and not on everything else.

What This Means for Developers and Teams

One of the most honest parts of the conversation was when Krish noted the obvious: if Refound AI can provide software services without traditional developers on payroll, something structural has changed.

Sid agreed, but pushed back on the catastrophist framing. The role is not disappearing — it is shifting. Boris Cherny, the creator of Claude Code, put it plainly when someone pointed out that Anthropic keeps hiring engineers despite claiming 99 percent of its code is AI-generated. Cherny’s response: the work of engineering now looks a lot more like technical product management. It is about translating business requirements into precise instructions that allow AI systems to produce the right output — not writing every line yourself.

You still need to understand how code works. You need to make architectural decisions. You need to know how to evaluate what the AI produces and whether it makes sense. The craft is still relevant — it just expresses itself differently now.

Sid also raised a point about design that tends to get overlooked. Language models default to the average. They produce outputs that are generically competent but rarely distinctive. A person with a genuine sense of taste — not just visual design, but how interactions should feel, how an agent should behave, how a workflow should flow — is increasingly rare and increasingly valuable precisely because AI cannot reliably replicate it.

Where to Start

If you take one thing from this conversation, make it this: before you build, audit.

Before you pick a tool, spend a week having honest conversations with the people on your team about where their time actually goes. Ask them what they hate doing. Ask them what takes longer than it should. Ask them what they would eliminate if they could. The answers will tell you more about where AI can help than any vendor demo.

From there, the path is clearer than it looks. Identify the highest-leverage bottleneck. Build or commission a custom agent designed around your actual workflow and context. Keep a human in the loop at the moments that matter. Measure the time recovered. Then do it again.

Going AI-native is not about replacing your team with robots. It is about freeing your team from the work that was never really theirs to begin with — and giving them more time to do the things that only they can do.

Sid Bharath is the founder of Refound AI, an AI consultancy helping companies build AI agents and AI operating systems. Krish Palaniappan is the founder of Snowpal, a product and API platform. This article is adapted from their conversation on the Snowpal Podcast.

Tanvi Mittal (GitHub) has spent over 15 years in software quality — starting as a developer, moving into test automation, and now sitting at the sharp edge of a field being fundamentally reshaped by AI. In a recent conversation on the Snowpal Podcast, she offered a candid, street-level view of what’s actually happening inside engineering teams today.

AI + Snowpal API

Podcast

A conversation with Tanvi Mittal, AI Systems & Quality Engineering Expert — on Apple and Spotify.

The Speed Problem No One Is Solving

The shift is striking. AI coding tools have dramatically compressed development timelines, but quality assurance hasn’t kept pace. “The ship to production has increased because now we have a lot of tools which we can leverage to code faster,” Tanvi observed. “But that has not been taken care of so seriously compared to the development part of it.”

In other words: teams are shipping more, but not necessarily testing more. If a sprint that once yielded 10 features now yields 30, the test coverage isn’t automatically tripling with it. That gap — between velocity and validation — is one of the defining challenges of modern software development.

The Tester Is Not Disappearing — But the Job Is Unrecognizable

Ask Tanvi whether the role of the manual tester still exists, and she’ll answer without hesitation: it’s “going super fast.” The person who walks through UI screens page by page, checking boxes manually, is largely a relic. In its place is something harder to define but far more demanding.

The industry is converging on what she calls full-stack quality: developers writing their own functional tests, and QA engineers shifting their focus to end-to-end integration, cross-system behavior, and — increasingly — AI-specific testing. “We definitely need a lot of quality checks around that,” she said. “I don’t see that QA is going anywhere soon.”

What is changing is the nature of the work. QA teams at large enterprises are now expected to be the first responders when something breaks in production. They’re digging through logs, tracing root causes, and managing the complexity of systems where dozens of services interact. That’s a very different job from checking if a button works.

Testing AI Is Not Like Testing Anything Else

Here’s where the conversation gets genuinely new territory. When the thing you’re testing is itself an AI — an agent, a chatbot, a decision-making system — traditional test cases stop making sense.

“The outputs can be different,” Tanvi explained, “but the gist of the work done by that agent should be the same.” You can’t write a test that expects a single, deterministic output. Instead, you’re validating behavior: does the agent do what it’s supposed to do, across a wide range of inputs, without doing what it’s not supposed to do?

That second part is where prompt injection comes in — the AI equivalent of SQL injection. A well-designed financial chatbot, for instance, should calculate loan payments. It should not be coaxed into writing Python code for a user just because they asked nicely. “If it’s giving me that, then it’s unnecessary use of tokens,” Tanvi noted, “and all those kinds of testing and data validation needed to be done.”

This kind of behavioral testing requires a fundamentally different mindset. It’s less about deterministic pass/fail and more about probabilistic trust: does this system behave reliably and safely, at scale, over time?

AI-Generated Code Still Needs Human Eyes

One of the more nuanced points Tanvi made is about the limits of trusting AI-generated tests. When an AI tool auto-generates 100 test cases alongside the code it writes, around 30 of them may be useless — technically invalid in the real production environment, or simply missing the edge cases that matter.

“You are not spending time on writing the code yourself. You are spending time to iterate through the code what is written by the AI and then updating that based on where it is not correct.” The same applies to tests.

This is a subtle but critical insight. The role of the QA engineer isn’t going away — it’s being elevated. The new job is judgment: knowing which tests are real, which edge cases an AI missed, and where the system’s behavior might diverge from expectation in the wild.

Governance, Observability, and the Rogue Agent Problem

As AI agents get more authority — taking actions, making decisions, operating autonomously inside complex systems — the stakes for getting testing wrong go up dramatically. A rogue AI agent might cause significant damage before anyone notices.

Tanvi’s answer to this is observability. Her focus has shifted toward log monitoring and production behavior analysis: catching anomalies early, before they become incidents. She’s even built an open-source tool called Log Miner to support this kind of proactive monitoring.

Tools like Datadog play a central role here — not just as passive log aggregators, but as active early-warning systems. Teams set custom alerts, monitor dashboards in real time, and treat unusual patterns as signals worth investigating before customers notice. “Before the customer points it out, there are a lot of checks and monitoring happening where you can figure out and change before it goes out of your control.”

Interestingly, she also flagged a gap: QA teams are rarely involved early enough in what gets logged and how. If logs are poorly structured, too noisy, or missing key traceable information, debugging production issues becomes exponentially harder. That’s starting to change — QA engineers are increasingly being brought into conversations about logging standards, not just the applications themselves.

FinTech Moves Slower, and For Good Reason

One of the more grounding moments in the conversation was Tanvi’s pushback on the narrative that AI is visibly transforming every software product. In regulated industries like banking and healthcare, that’s simply not what’s happening on the surface.

“FinTech is a sector where AI is not able to show a lot of impact because we have a lot of constraints,” she said. The improvements are real, but they’re mostly invisible to end users: faster deployment pipelines, automated backend processes, modernized APIs. A deployment that once took four to five hours now happens in two clicks. That’s meaningful progress — but you wouldn’t see it from your banking app.

The implication is important: the “AI is changing everything overnight” narrative is largely true for startups and smaller companies, not for enterprises operating in regulated spaces where trust, compliance, and stability rightly slow things down.

The Skill That Matters More Than Any Other

Near the end of their conversation, Tanvi was asked what she’d look for when hiring today that she wouldn’t have looked for two or three years ago. Her answer was unambiguous: prompt engineering.

“How good (they are) at prompt engineering — that is the one thing.” Combined with attitude and genuine dedication to the work, that’s the hiring filter she’d apply now.

It’s a telling signal. The ability to communicate precisely with AI systems — to construct clear, bounded, effective prompts — has become a professional skill, not just a party trick. It’s now table stakes for anyone working in or around software development.

Change Is the Only Constant (And Most People Are Lagging)

Perhaps the most honest thread running through the conversation was about the gap between what people say and what they actually do. Most parents — including Tanvi — are rethinking what success looks like for their kids in an AI-shaped world. Most professionals acknowledge that the skills needed to stay employable are shifting fast.

And yet. The same two-week sprints. The same college applications. The same job searches for traditional roles.

“We are in a world where every day we have to learn new stuff to be accommodating with the technologies shifting,” Tanvi said in her closing. “That’s it. We are learners every day.”

It’s a simple statement, but it cuts to the heart of what’s being asked of everyone in this industry right now — not just QA engineers. The people who will navigate this era well are the ones who treat learning not as a phase, but as a permanent condition of professional life.

Q&A with Tanvi Mittal

Q: Can you tell us a little about your background?

I have 15-plus years of experience in software. I started as a developer, then moved into quality engineering, working closely with large enterprises to build automation frameworks and test React and Angular-based applications. More recently, I’ve been focused on the AI side — how AI and AI agents are affecting software, and how we can carefully test them without leaking bugs into production.

Q: How has testing fundamentally changed with the rise of AI tools?

The biggest shift is that code is being shipped to production much faster because developers now have powerful tools to write code quickly. But the investment in testing hasn’t kept pace with that acceleration. If a lot of code is being generated in one week but we don’t allocate enough capacity for testing, that’s a serious gap. Speed without quality is a risk.

Q: Is the manual tester — someone who walks through UI pages by hand — still a relevant role?

That role is going away very fast. We’re moving toward what I’d call full-stack quality, where testers are also developers and developers are also testers. In smaller teams, that’s already the norm. In large enterprises, the shift is happening now. The QA focus is increasingly on end-to-end integration testing — where many systems interact — rather than checking individual pages manually.

Q: So is QA as a profession disappearing?

Not at all. The need is evolving, not shrinking. We now need people who can intelligently validate the behavior and output of AI agents and LLMs. That requires a very different skill set than traditional testing — but it’s very much in demand. I don’t see QA going anywhere soon.

Q: How do you test code that wasn’t written by a human?

For traditional software, we run it through the same test cases we’d apply to human-written code — plus a quality check on the generated code itself. For AI agents, it’s different. You’re doing behavioral testing: given a wide range of inputs, is the agent producing outputs that are consistent with its intended purpose? The outputs may vary, but the underlying behavior should be reliable.

Q: Can you explain prompt injection and why it matters for QA?

Prompt injection is to AI agents what SQL injection is to databases — it’s a way of manipulating a system into doing something it shouldn’t. For example, imagine a financial chatbot designed only to calculate loan payments. If a user can prompt it into writing Python code or revealing system instructions, that’s a security failure. Part of our job is to test that agents stay within their intended boundaries, no matter how creatively users phrase their requests.

Q: AI tools can auto-generate test cases alongside the code. Does that eliminate the need for human testers?

Not yet. In my experience, if an AI generates 100 test cases, around 30 of them may be impractical or invalid in a real production environment, and it often misses important edge cases. You still need a human to evaluate which tests are meaningful and which aren’t. The time saving is real — but the judgment required to use AI-generated tests responsibly still belongs to a person.

Q: How does QA fit into faster delivery cycles? Are two-week sprints still the norm?

In large enterprises, two-week sprints are still common. QA joins on day one — we sit with developers, understand what’s changing, assess the impact on other systems, and begin defining test cases. By day three we’re refining those cases. Developers handle about 80% of test automation, and our team focuses on the integration and end-to-end layer — making sure all the systems that touch the change are working together correctly.

Q: How are you seeing team structures change?

In startups, the change is dramatic — one person often covers product, development, and QA. In large enterprises, the shift is more gradual but visible. Product owners are managing three products instead of one. QA engineers are being asked to handle DevOps tasks like deployments and root-cause analysis. The days of narrowly defined, single-skill roles are fading. Everyone has to wear multiple hats.

Q: What does good AI governance look like in practice?

Observability is the foundation. You need to monitor production logs continuously so that when something goes wrong with an AI agent, you catch it before customers do. I built an open-source tool called Log Miner for this purpose. Tools like Datadog are central to this — you set up custom alerts, watch dashboards in real time, and treat anomalies as early warning signals rather than waiting for incidents to escalate.

Q: Why does FinTech seem slower to adopt AI visibly?

Because trust is everything in financial services. The customers’ data and money are on the line — that creates a high bar for introducing AI. A lot of progress is happening, but it’s behind the scenes: API modernization, automated deployments, internal tooling. Things that dramatically improve velocity for engineering teams but aren’t visible to the end user. That’s appropriate caution, not stagnation.

Q: Is a college degree in software still worth pursuing?

Honestly, it’s complicated. For fields like medicine or law, formal education is non-negotiable. For software engineering, the diploma is less critical than the skills — and the skills needed are changing faster than most curricula can keep up with. Personally, I wouldn’t push my kids toward software development the way previous generations were pushed. I’d want them to understand AI, not just code. That said, from a cultural standpoint, many families — including mine — haven’t fully made that mental shift yet.

Q: Are laid-off workers turning to entrepreneurship?

Most people are still looking for stable employment first. Business is not easy money — anyone who’s run a company knows that. Most people won’t leave a job until their business is already generating revenue. If someone gets laid off without a business plan, their first instinct is to find another job. Entrepreneurship tends to be the second choice, not the first.

Q: What’s the one skill you’d look for in a new hire today that you wouldn’t have cared about three years ago?

Prompt engineering. How well someone can communicate with AI systems — constructing precise, effective prompts — is now a core professional skill. Beyond that, I look for attitude: commitment, adaptability, and genuine dedication to the work. Those qualities matter more than ever in a world where the tools change every few months.

Q: Any final advice for people navigating this shift?

We are in a world where you have to learn something new every single day to keep up with how fast technology is moving. The people who will thrive aren’t necessarily the most experienced — they’re the most adaptable. Treat learning not as something you did in school, but as a permanent part of how you work.

Tanvi Mittal is an AI systems and quality engineering expert specializing in testing, reliability, and security in LLM-powered applications. This article is based on her appearance on the Snowpal Podcast, hosted by Krish Palaniappan.

Hydraulics — the technology that powers excavators, military vehicles, oil rigs, and factory floors — have been around since the 1800s. They work by pressurizing fluid to create force. They’re powerful. They’re proven. And according to Hiten Sonpal, CEO of RISE Robotics, they’ve hit their ceiling.

Hiten joined the Snowpal Podcast to talk about what his company is building, what he’s learned from shipping over 9 million units at iRobot, and why he raised $5.7 million from the crowd instead of from VCs. It’s a conversation worth your full attention.

Build Apps in Quick Time

Podcast

The Belt Revolution: How One MIT Startup Is Replacing Oil With Ingenuity - on Apple and Spotify.

The thing Rise Robotics actually built

Rise’s core technology is called Beltdraulic™ — and the name tells you most of what you need to know.

They took a hydraulic actuator (the cylinder that creates linear motion in heavy machinery), removed all the fluid, and replaced it with high-performance belts — the same kind used in elevators.

That swap sounds simple. The results are not.

Beltdraulic™ actuators are:

• 3× more efficient than hydraulics

• 3× faster

• 3× more durable

• Fluid-free — no leaks, no environmental contamination, no hydraulic oil fires

• AI-ready out of the box — they know their exact position, orientation, and load at all times

That last point matters more than it might seem. We’ll get back to it.

Who’s buying it

Rise has two primary customers right now: the Pentagon and the oil and gas sector.

The military angle makes intuitive sense. Soldiers working around traditional hydraulic equipment deal with diesel smoke, constant noise, and bases that eventually become environmental superfund sites from hydraulic oil leaks. Beltdraulic™ eliminates all of that. The Air Force and Army are already running programs with Rise focused on field readiness and reducing logistical complexity.

The oil and gas angle required more strategic thinking.

When Hiten joined Rise, the engineering team was excited about construction. Excavators, cranes — big, obvious applications. But construction moves slowly. The pain isn’t acute enough. Potential customers would hear the pitch and say: “Yeah, that sounds nice. Our customers aren’t really complaining though.”

Oil and gas was different.

Hydraulic systems in O&G run 24 hours a day, 7 days a week. Any downtime is expensive. Any leak is a liability. Any inefficiency compounds across years of continuous operation. Rise is now running pilots converting hydraulic natural gas pumps to belt-draulic ones — in a sector with an $11 billion addressable market, with oil pumps next on the roadmap.

“Our biggest enemy, since we don’t have any competitors, is inertia.”

— Hiten Sonpal

The lesson he took from this: don’t sell better. Find someone who’s in pain, and solve the pain.

What 9 million shipped units taught him

Before Rise Robotics, Hiten spent years at iRobot, leading teams that generated over $2 billion in revenue across 20 product lines.

The single most important thing he learned:

Every improvement you make costs exponentially more than the last one.

Whether you’re trying to cut cost, improve durability, increase speed, or extend battery life — each incremental gain takes more effort than the one before it. Start trying to improve five things at once, and you’ve built a project that won’t survive the next company reorganization.

His rule: pick three customer pain points, and only three.

Not the three coolest problems. The three problems your customer is loudest about, that no one else has solved, that you can actually ship a solution to within your runway.

For hardware companies, that runway is typically 18–24 months. For AI/SaaS, maybe 6–9. The timescale changes by industry. The principle doesn’t.

“You need to find out where your customer’s pain points are — and deliver a solution before the organization loses patience or you run out of money.”

This isn’t a compromise. It’s how you stay in the game long enough to solve the hard stuff later.

Why Beltdraulic™ and AI belong together

Here’s the AI angle that most people in the robotics space are underestimating.

Traditional hydraulic systems have what engineers call bang-bang control — you open a valve, fluid moves, something pushes. You don’t know exactly how far it moved, how much force it applied, or where it stopped without a separate sensor system. Closing that loop requires a trained human operator in the seat.

Belt-draulic actuators are different. Every actuator knows, at all times:

• Its exact position

• The forces it’s experiencing

• Its orientation

That’s a digital twin out of the box. And a digital twin is the foundation for everything autonomous: remote operation, semi-autonomy, full autonomy, predictive maintenance.

Hiten drew a comparison to the self-driving car industry. Meaningful autonomy didn’t arrive until vehicles switched to drive-by-wire — electronic control replacing mechanical linkages. Every serious autonomous vehicle platform had to make that switch before the AI could actually take over.

The same transition is coming to heavy equipment. Beltdraulic™ is the drive-by-wire layer for excavators, forklifts, military vehicles, and oil rigs.

The data angle is equally compelling. An actuator that knows how hard it’s working can tell you when a part is being overstressed — years before it fails in the field. It can tell you if a customer is consistently lifting half their rated load (maybe they’re over-engineered and overpaying). It can generate evidence for carbon credit claims after switching away from hydraulics.

The crowdfunding twist

When Hiten joined Rise, the VC market wasn’t interested on good terms. Everyone wanted humanoid robots and AI. A deep-tech industrial hardware company didn’t fit the narrative.

But Rise had 1,500 LinkedIn followers who kept asking how they could get involved.

Hiten noticed that, and remembered something: Regulation Crowdfunding — a law passed during the Obama administration — allows startups to raise up to $5 million from the public in a 12-month window, offering real equity, not just perks.

He ran a “testing the waters” campaign to gauge interest. Within a month: $800,000 in soft commitments.

So they launched a full campaign on WeFunder, the world’s largest crowdfunding platform.

The result: $5.7 million in reservations — $700,000 more than the legal cap. Rise had to turn money away.

A few things made it work:

The terms were the same as their institutional round. Third-party ratings firm King’s Crowd gave them 4.7 out of 5 stars specifically because retail investors were getting institutional terms — something almost unheard of in crowdfunding.

The investor base is strategic, not just financial. Rise now has 2,500 investors who introduce them to customers, suppliers, and future investors. Some are active military or veterans who work with hydraulic equipment and want to see it improved. Some are climate-focused. Some are just smart retail investors who’ve realized that the best returns in companies like SpaceX were captured long before any IPO — and they want in earlier.

The minimum investment is $250. Anyone can participate.

Hiten is opening another round to accommodate the $700K that didn’t fit last year.

The bottom line

Rise Robotics isn’t trying to build a humanoid robot or solve general AI. They’re solving a specific, expensive, widespread problem that has existed for a century — with technology they can manufacture today, deploy in existing equipment, and scale through a market worth three-quarters of a trillion dollars.

The strategy is clear: go wide until you find a vertical where the pain is acute, then go deep. Focus on three things. Ship. Repeat.

If you’re a founder, there’s a product development framework here worth stealing. If you’re an investor, there’s an opportunity worth looking at seriously — especially before the next institutional round.

Q&A with Hiten Sonpal

Q: Give us a quick intro — who are you and what does Rise Robotics do?

I’m the CEO of Rise Robotics. I’ve been with the company for less than two years, brought on board by the founders to help take the company to its next stage of growth — primarily through commercialization of their technology. The company is affiliated with MIT; three out of four founders went to school there.

What we do is build a new kind of linear actuator that replaces hydraulic systems. We call our technology belt-draulics. We’ve taken the oil out of hydraulic systems and replaced it with modern belts — the same kind used by the elevator industry. By doing that, we’ve created a technology that’s three times as efficient as hydraulics, three times as fast, three times as durable, and is AI and automation-ready out of the box.

Q: Who are your customers right now?

Our biggest customers currently are the Pentagon — specifically the Air Force and the Army. We’re developing hydraulic-free solutions to help improve their readiness and reduce the logistical footprint they deal with in the field.

We recently started commercializing our technology commercially. Our first commercial sale was in the second half of last year — a pilot in the oil and gas sector, which has an $11 billion addressable market. We’re converting hydraulic natural gas pumps to belt-draulic ones, which are completely fluid-free. After that, our next step is oil pumps. Further down the line we’re looking at construction, forestry, and maritime. We have a lot of interest from heavy industry in general, but those are our two primary customers right now.

Q: Do you have competitors?

We actually have no competitors in the traditional sense. Our competitors in one way are the incumbents — companies currently making hydraulic systems — but they’ve reached the ceiling of the S-curve in terms of what can happen with fluid-based actuation.

There are also companies that make linear actuators using screw-type technology — taking a ball screw and rotating it to push forward and backward. Those companies are more likely to be our partners than our competitors. Their stroke lengths are relatively small, their speeds are slow, and the forces they can apply are limited. We have longer stroke lengths, higher speed, and higher forces. We’re very complementary to screw-type actuators. So basically, we don’t have any direct competitors in this space.

Q: What has building deep tech taught you about product development?

The key insight for me came from my time at iRobot, where teams I led generated over $2 billion in revenue and shipped over 9 million units across 20 product lines.

What I learned is that when you’re trying to improve performance in any one axis — cost, reliability, speed, durability — the effort required increases exponentially with each increment. When teams try to tackle multiple axes at once, all those exponentials stack up very quickly. At some point the problem becomes intractable.

Most large organizations reorganize every 18 months. If your project isn’t making substantial traction, it won’t survive two reorganizations. The same is true for startups — 18 months of runway means you need milestones.

So my key insight has been to help engineering teams understand they don’t have to solve everything. Pick three key problems the customer doesn’t have a solution for, and focus on delivering those. If you can solve those three things, you’ll have a market and a successful product. Think of a spider chart with all these axes — how do you squish that chart down to something tractable within a given timeframe?

Q: How do you stay focused on those three things when the world keeps changing?

The timeframe needs to be sized to the rate of change in a particular industry. In consumer electronics, 18 months is right. For pure SaaS, maybe 9 months. For AI-driven companies, even 6 months. For heavy industry, maybe 24 months.

But the core tenet still holds: can you find your customer’s pain points and deliver on them before the organization loses patience or you run out of money?

The world is changing quickly — it is possible that while you’re pursuing those three pain points, something shifts. But keeping that focused tempo means if one thing changes, you still have two to work with. If you were trying to solve ten things, a third of them shifting throws away a massive amount of work. Focusing on a few things and getting them right works across sectors, across industries, whether it’s software or hardware.

Q: How do you bring hardware innovation into legacy industries? What’s the biggest challenge?

Our biggest enemy — since we don’t have any competitors — is inertia. Legacy industries have been doing things a certain way for a very long time. Their training, their processes, their entire operation has been optimized for the technology they already have. Bringing change is very challenging.

What I’ve found works well is identifying customers who have a specific pain point that really bothers them — and going to address that pain point directly. That causes industries to move. If we show up and say ‘this is better,’ it takes a long time to get traction. But if we show up and say ‘we can solve this particular problem you’ve been living with,’ that’s different.

When I first joined Rise, the engineering team was excited about construction. It’s a large market — but it’s slow moving. Customers there would say ‘yeah, this sounds nice, but our customers aren’t really complaining.’ Oil and gas was different. Hydraulic systems there run 24/7. Any durability problem, efficiency problem, or downtime is substantial. By shifting to a customer with a real pain point, we got more traction immediately.

Q: Did you go horizontal or vertical in your market approach?

We started horizontal, which made sense when I joined. We launched our second-generation cylinder — the first standalone unit we could actually ship — at Bauma in Germany, the world’s largest construction show. We had over 200 leads from that show, across construction, agriculture, distribution, and more.

When we came back, we evaluated all of them — understanding the problems of each, where we were as a company, and which customers could meet us where we are. When we discovered the oil and gas vertical, it became very clear that going broad had been the right move to find it. Once we identified a vertical that was compelling, we could stop going broad and go deep.

So the approach was: start horizontal until you find a vertical where the pain is acute and the margins are good, then commit. We still take joint development opportunities from customers in other sectors who come to us, but when it comes to where we put our own chips — we’re going vertical.

Q: Are your products AI-native, or do they work without AI?

We are AI enablers. We don’t have AI inside the actuators, and our customers don’t need AI tools to build a drive-by-wire system using our technology.

But if they choose to add semi-autonomy, teleoperation, or full autonomy, our systems enable all of that — without depending on it. The reason is that our actuators provide precise multi-position control out of the box. You know the position of every actuator, the forces it’s experiencing, and its orientation at all times. That’s a digital twin out of the box, which is the foundation for everything autonomous.

Traditional hydraulics have what’s called bang-bang control — you open the valve, the fluid moves, and you don’t have precise feedback. You need a trained human operator in the seat to close all those loops in their head. With our technology, an AI system gets everything it needs for a digital model — and you can implement safety policies that are mathematically calculated, not statistically guessed.

Q: How does your technology relate to the autonomy transition we’re seeing in vehicles?

The analogy to autonomous vehicles is almost exact. Meaningful autonomy at scale didn’t arrive until manufacturers switched to drive-by-wire platforms. Companies like Waymo and Hyundai couldn’t truly scale autonomous systems until the vehicle’s mechanical controls were replaced with electronic, software-addressable controls.

The same transition is coming to heavy equipment. As long as excavators, forklifts, and industrial machines rely on hydraulic systems, full autonomy remains out of reach. Our technology converts those hydraulic systems into drive-by-wire systems — which is the foundational layer that any autonomous or AI control system needs.

Waymo has even revealed they use remote operators in the Philippines and the US to help get Waymos unstuck from corner cases. The only reason that’s possible is they have a full digital model of the car and its environment. With a hydraulic excavator, that kind of remote situational awareness simply doesn’t exist.

Q: What do startups typically get wrong when scaling complex technology?

The most common mistake is trying to optimize across too many dimensions at once. Teams want to cut cost AND improve reliability AND increase runtime AND improve durability — all at the same time. Each of those improvements is exponentially harder than the last, and when you stack them all together, you’ve built something that can’t be delivered in the time you have.

The discipline required is brutal prioritization. You have to help your engineering team understand that they don’t need to solve every problem — only the three that the customer is actually crying out for. And you need to be honest about your timeframe. Whether it’s 9 months or 24 months, you have a clock. The project that survives is the one that ships something real within that window.

The second mistake is not finding customers early enough. We’re a B2B company, and the instinct in deep tech is to stay in the lab until the technology is perfect. But customer pull is what actually tells you which problems are worth solving — and it’s what gives the organization a reason to keep funding you.

Q: Tell us about your crowdfunding approach — what is Regulation Crowdfunding and why did you use it?

When I joined Rise, the VC market wasn’t offering us great terms. Investors were chasing humanoid robots and AI, and our terms as a deep-tech hardware company were unattractive.

But we had 1,500 LinkedIn followers who regularly asked how they could get involved. That gave me an idea. I was advising a couple of companies that had successfully raised using Regulation Crowdfunding — a law passed during the Obama administration that allows startups to raise up to $5 million from the public over 12 months, with real equity.

We ran a ‘testing the waters’ campaign first — people could express interest without committing money. Within a month we had $800,000 of interest. So we launched a full campaign on WeFunder, which is the number one crowdfunding platform in the world. To our surprise, we ended up with $5.7 million in reservations — $700,000 more than the legal cap. We had to turn money away.

What we didn’t expect was how strategic those investors would become. We now have 2,500 investors who introduce us to customers, suppliers, and future investors. Some want to be customers themselves. It’s been extraordinary.

Q: Do investors in your crowdfunding campaign get real equity in Rise Robotics?

Yes — the process has advanced significantly over the past few years. What happens is that an LLC ends up owning a chunk of the company. All the crowdfunding investors own a piece of that LLC. So it’s very straightforward equity ownership — just structured with one layer so that our cap table doesn’t get unwieldy.

This way we have one line on the cap table representing our 2,500 investors, which institutional VCs are comfortable with for future rounds.

We can also take very small checks — the minimum investment in Rise Robotics is $250. Anyone can participate. And one of the reasons our campaign had so much traction is that the terms we offered retail investors were the same terms we offered institutional investors. The ratings firm King’s Crowd gave us 4.7 out of 5 stars specifically because of that.

Q: Who else is investing in Rise, beyond just technology enthusiasts?

We’re getting three distinct types of investors. First, there are impact investors — people in the armed services who work with hydraulic equipment and see firsthand what belt-draulics could do for soldiers. With our tech, they can stop inhaling diesel smoke, stop being around loud equipment that damages hearing, and stop dealing with hydraulic oil leaks that eventually turn military bases into environmental superfund sites. Those people invest because they believe in the mission.

Second, there are climate-focused investors who like the clean energy angle — removing fluid leaks and improving energy efficiency across heavy industry at scale.

Third, there are savvy retail investors who are starting to think like VCs. They look at our $750 billion addressable market, see that we’re disrupting something real, and recognize that companies like SpaceX are going to IPO at $1.5–2 trillion — meaning most of the money has already been made by the time a retail investor could buy in. Reg CF gives retail investors the chance to get in early, on institutional terms.

Interested in Rise Robotics? Visit riserobotics.com or explore their investor campaign at invest.riserobotics.com.

Listen to the full episode on the Snowpal Podcast.

Want to Invest in RISE Robotics?

The discussion cuts through common misconceptions around growth, marketing, and technology, emphasizing a core principle: businesses must fix internal friction before attempting to scale externally. Drawing from real-world examples and candid exchanges, Kathy highlights how founders often become the “glue” in their organizations—and why that becomes a bottleneck. Together, they explore how aligning messaging with customer problems, clarifying expectations, and building process-driven systems can create sustainable growth.

This conversation is especially relevant for founders, operators, and product leaders navigating today’s rapidly evolving landscape shaped by automation and AI.

Snowpal API on AWS Marketplace

Podcast

Fix Systems First Before Scaling Marketing and AI Growth — on Apple (Part I, Part II) and Spotify.

Fix the System Before You Amplify It

One of the most critical mistakes founders make is pouring time, energy, and money into marketing before addressing the underlying inefficiencies in their business. As discussed in the conversation, amplifying a broken system does not solve problems—it magnifies them. When marketing efforts increase visibility, they also increase exposure to friction, gaps, and inconsistencies that already exist. The result is not growth, but chaos at scale. Before investing in outreach, advertising, or automation, founders must ensure that what they are amplifying is actually worth amplifying.

The Founder as the Bottleneck

Many founder-led businesses are built on deep expertise, often developed in a specific domain such as engineering, product development, or consulting. However, expertise in one area does not translate into mastery across all business functions. In corporate environments, specialized departments handle sales, marketing, customer success, and operations. When founders step out on their own, they unknowingly inherit all of these roles. Over time, they become the “glue” holding everything together—filling gaps manually, compensating for missing processes, and bridging communication breakdowns. While this may work in early stages, it fundamentally limits scalability. A business cannot grow efficiently if it depends entirely on the founder’s constant intervention.

The Illusion of Knowing Versus Doing

A subtle but pervasive challenge is the gap between awareness and execution. Founders often understand, at least conceptually, that they need better sales processes, clearer messaging, and defined systems. However, knowing this does not automatically translate into implementation. Muscle memory, habits, and day-to-day pressures push them back into reactive behaviors—focusing on product features instead of customer problems, or jumping into tactics without strategic alignment. This disconnect is not due to incompetence but to the complexity of running a business where multiple unknowns compete for attention simultaneously.

Shifting From Solutions to Problems

One of the most powerful shifts founders can make is moving from a solution-centric mindset to a problem-centric one. Businesses naturally fall in love with their products—their features, capabilities, and technical sophistication. However, customers do not buy solutions; they buy relief from pain. A restaurant owner, for example, is not looking to “build software”—they are trying to serve customers better, increase orders, and replicate in-person experiences digitally. When founders focus on the customer’s starting point—their frustrations, constraints, and goals—they position their offering as a bridge rather than a product. This reframing is essential for effective communication, positioning, and conversion.

Conducting a Friction Audit

Before scaling any business activity, founders must conduct what can be described as a “friction audit.” This involves analyzing the entire customer journey—from initial awareness to final delivery—through the customer’s perspective. Where do prospects lose interest? Where does confusion arise? Where are expectations misaligned? Every point of friction represents a leak in the system. Without addressing these leaks, additional traffic or leads will simply flow through and be lost. The goal is to create a seamless, intuitive experience that moves customers forward without unnecessary resistance.

The Role of Expectations in Delivery

A significant portion of business breakdowns stems from mismatched expectations. When what is promised differs from what is delivered, dissatisfaction is inevitable—even if the product itself is high quality. Clear documentation, defined processes, and explicit communication are essential to ensure alignment between provider and customer. This reduces scope creep, eliminates ambiguity, and creates a predictable experience. In many cases, customers do not require perfection—they require consistency and clarity. Delivering exactly what was promised, in the way it was promised, builds trust and long-term loyalty.

Qualification: Not Everyone Is Your Customer

Another key insight is the importance of qualification. While it may be tempting to assume a large addressable market, not everyone is a viable customer at any given time. Some prospects lack urgency, others lack budget, and some simply do not align with the offering. Effective systems filter and qualify leads early, ensuring that time and resources are focused on those most likely to convert. This requires understanding not just who your customers are, but when they are ready to act. Without this clarity, businesses waste effort chasing unqualified opportunities.

Tools Do Not Replace Strategy

Modern tools, including AI, automation platforms, and sales software, have dramatically lowered barriers to entry. Founders can now build, market, and scale faster than ever before. However, tools are not a substitute for strategy. A tool applied to a broken system will only accelerate dysfunction. The effectiveness of any tool depends on how well it is integrated into a coherent process. Rather than searching for a single “all-in-one” solution, successful founders assemble ecosystems of tools that align with their workflows and objectives. The focus remains on process design, not tool selection.

AI as an Amplifier, Not a Fix

Artificial intelligence represents a powerful force in modern business, but it is not a cure-all. AI excels at amplifying existing systems—whether they are efficient or flawed. If a sales process is unclear or a customer journey is fragmented, AI will scale those issues just as effectively as it scales successes. Therefore, foundational clarity must precede technological adoption. Businesses that invest in AI without first addressing structural weaknesses risk accelerating their own inefficiencies.

Building Systems That Scale

Ultimately, sustainable growth comes from transforming implicit knowledge into explicit systems. Founders must externalize what exists in their heads—documenting processes, defining workflows, and creating repeatable structures. This shift reduces dependency on individuals and enables consistent execution. When systems are well-designed, they not only support growth but also enhance the customer experience, making it easier for clients to engage, buy, and succeed.

Conclusion

The path to scalable growth is not paved with more marketing, more tools, or more activity. It begins with clarity—understanding the customer, identifying friction, aligning expectations, and building systems that work independently of constant human intervention. Only after these foundations are in place does amplification make sense. At that point, marketing, automation, and AI become powerful accelerators rather than sources of compounded problems.

Q & A

1. Why shouldn’t businesses invest in marketing too early?

Marketing amplifies whatever already exists. If your systems have gaps or inefficiencies, you’ll scale problems instead of results.

2. What is a “friction audit”?

It’s a systematic review of the customer journey to identify where prospects get confused, drop off, or experience delays.

3. What role do founders often play unintentionally?

Founders often become the “glue,” manually filling gaps between systems instead of building processes that run independently.

4. Why is being the “glue” a problem?

It limits scalability because growth becomes dependent on the founder’s time, attention, and ability to manage everything.

5. What is the difference between knowing and executing?

Founders may understand what needs to be done but struggle to consistently implement it due to habits and operational pressure.

6. What is a common messaging mistake founders make?

They focus on features and solutions rather than clearly articulating the customer’s problem and desired outcome.

7. Why should businesses focus on customer problems first?

Customers engage when they feel understood; framing around their pain points makes your solution more relevant and compelling.

8. What causes most client dissatisfaction?

Misaligned expectations—when what is delivered doesn’t match what the customer thought they were buying.

9. How can businesses reduce scope creep?

By clearly defining deliverables, documenting processes, and ensuring both sides agree on expectations before execution begins.

10. What does “qualified lead” mean?

A prospect who not only fits your target profile but also has the urgency, budget, and readiness to make a decision.

11. Why isn’t everyone a potential customer?

Because timing, need, budget, and priorities vary—targeting everyone leads to wasted effort and poor conversion.

12. Are tools enough to fix business problems?

No. Tools are enablers, but without a clear process, they can create more complexity rather than solving issues.

13. What is the risk of relying too much on tools?

You may automate broken workflows, making inefficiencies faster and harder to detect instead of eliminating them.

14. How does AI impact business systems?

AI accelerates execution, but it mirrors your system quality—strong systems improve, weak systems deteriorate faster.

15. What is the foundation of scalable growth?

Well-defined processes, clear messaging aligned to customer needs, qualified leads, and systems that reduce dependency on individuals.

In today’s rapidly evolving digital landscape, artificial intelligence (AI) is no longer a futuristic concept—it is a present-day catalyst reshaping how businesses operate. Organizations across industries are increasingly integrating AI-driven tools to optimize workflows, enhance productivity, and unlock new levels of efficiency. What once required teams of specialists and months of development can now often be achieved in days—or even minutes.

This transformation is particularly evident in operational roles, where professionals are expected to manage complex systems, coordinate across functions, and drive outcomes efficiently. AI is not replacing these roles; instead, it is amplifying human capabilities. By automating repetitive tasks and enabling smarter decision-making, AI allows individuals to focus on strategic, high-impact work.

Podcast

AI Tools That 10x Your Output — on Apple and Spotify.

From Manual Processes to Intelligent Automation

Traditionally, business operations involved significant manual effort—building reports, updating systems, and coordinating across multiple tools. Employees often juggled dozens of applications simultaneously, leading to inefficiencies and fragmented workflows.

Today, automation platforms and AI integrations are streamlining these processes. Instead of manually transferring data between systems, organizations can implement automated workflows where updates in one tool trigger actions across others. This interconnected ecosystem reduces redundancy, minimizes errors, and ensures real-time alignment across teams.

Moreover, AI-powered assistants are redefining accessibility to information. Employees can now retrieve insights, generate reports, and execute tasks through simple conversational interfaces, dramatically reducing the time required to access critical data.

The Human Edge in an AI-Driven World

Despite the rapid advancement of AI, human judgment remains indispensable. While AI excels at speed, scale, and pattern recognition, it lacks the nuanced understanding of human behavior, emotional intelligence, and contextual decision-making.

The true differentiator in this new era lies in how individuals leverage AI—not just whether they use it. Professionals who combine technical fluency with strategic thinking and empathy will stand out. They can interpret AI outputs, refine them, and align them with real-world needs, creating solutions that are both efficient and meaningful.

As highlighted in the discussion, the future workforce will not be defined solely by technical skills but by adaptability, curiosity, and the ability to continuously learn and evolve.

Technologies Driving the Shift

One of the most impactful developments in recent years is the rise of integration and automation platforms. Tools like workflow automation systems enable seamless communication between applications, eliminating the need for custom-built integrations. These platforms allow even non-engineers to design sophisticated workflows, connect data sources, and automate business processes with minimal technical overhead.

In parallel, AI-enhanced tools are evolving from simple automation engines into intelligent orchestration systems. They can now act as virtual assistants—retrieving data, generating reports, and even executing multi-step tasks across platforms. Combined with collaborative tools and knowledge management systems, these technologies create a unified digital workspace where information flows effortlessly and decisions can be made faster than ever before.

Navigating the Challenges

While the benefits are substantial, the widespread adoption of AI also introduces challenges. Over-reliance on automation without understanding underlying processes can lead to errors and inefficiencies. Additionally, as AI-generated outputs become more prevalent, maintaining quality and accuracy requires careful oversight.

Organizations must strike a balance—leveraging AI to enhance productivity while ensuring that human expertise remains central to critical decisions. This includes implementing review processes, fostering a culture of continuous learning, and encouraging employees to question and refine AI-generated results.

Technologies

Modern AI-driven operations rely on a stack of interconnected tools that streamline workflows, enhance collaboration, and automate decision-making. Platforms like Zapier serve as the backbone of automation by enabling seamless integrations across thousands of applications. Instead of building custom APIs, teams can create automated workflows (“Zaps”) that trigger actions between systems—such as syncing CRM updates, generating reports, or notifying teams in real time. Increasingly, these platforms are incorporating AI capabilities, allowing users to build intelligent agents that not only move data but also interpret it and take contextual actions.

Collaboration and knowledge management tools such as Notion and Slack play a critical role in centralizing information and enabling real-time communication. Notion acts as a unified workspace for documentation, task management, and strategic planning, often enhanced with AI features for summarization and content generation. Slack, on the other hand, becomes the operational command center when integrated with automation tools—hosting AI chatbots that can fetch reports, answer queries, and trigger workflows directly from conversations. Together, these tools reduce friction in day-to-day operations and create a more responsive, data-driven work environment.

On the development and prototyping side, platforms like Lovable represent a new wave of “vibe coding” tools that allow users to rapidly build applications without deep engineering expertise. These tools can generate functional websites or applications within minutes, enabling faster experimentation and iteration. While they may not yet replace full-scale engineering for complex systems, they significantly lower the barrier to entry for building MVPs and communicating product ideas. Complementing these are AI assistants such as ChatGPT, which help users learn new skills, generate code, and solve problems interactively—making them indispensable across both technical and non-technical workflows.

Finally, the power of these tools is amplified when used together as an integrated ecosystem. Automation platforms connect data sources, collaboration tools provide visibility and communication, and AI assistants enhance decision-making and execution. The result is a highly efficient digital infrastructure where individuals can accomplish what previously required entire teams—while still relying on human judgment to guide strategy, creativity, and meaningful outcomes.

The Road Ahead

We are currently in a transitional phase—a “wild west” of AI adoption—where experimentation is high and best practices are still emerging. Over the next few years, we can expect a recalibration as organizations learn how to use AI more effectively and responsibly.

The future belongs to those who can navigate this evolving landscape with both technical proficiency and human insight. AI will continue to advance, but the ability to think critically, adapt სწრაფly, and connect with people will remain uniquely human strengths.

In the end, the question is not whether AI will change the way we work—it already has. The real question is how we choose to work alongside it.

Q & A

1. Who is featured in the episode and what perspective does he bring?

   Jeremy Hass, founder of Prefix Ops, shares a practitioner’s perspective on how AI is transforming business operations, offering real-world insights on tools, workflows, and how individuals can stay competitive.

2. What is the central theme of the episode?

   The episode focuses on how AI can significantly increase productivity in operations, while emphasizing that success depends on combining AI capabilities with human judgment and strategic thinking.

3. How is AI changing the way businesses operate today?

   AI is enabling companies to automate repetitive processes, streamline workflows, and make faster, data-driven decisions—often reducing tasks that once took weeks to just hours or minutes.

4. Is AI replacing jobs in operations?

   No, AI is primarily augmenting roles rather than replacing them, allowing professionals to focus less on manual work and more on high-impact, strategic initiatives.

5. What were some inefficiencies in traditional operations workflows?

   Teams often relied on manual data entry, disconnected tools, and constant context-switching, which led to delays, errors, and fragmented processes.

6. How do automation platforms improve operational efficiency?

   They connect different tools and systems so that actions in one platform automatically trigger updates in others, reducing manual effort and ensuring consistency across workflows.

7. What role do AI-powered assistants play in modern work environments?

   They allow users to retrieve information, generate reports, and execute tasks through simple prompts, making complex operations more accessible and faster to perform.

8. Why is human judgment still critical despite AI advancements?

   While AI excels at processing data and identifying patterns, it lacks context, emotional intelligence, and nuanced reasoning—making human oversight essential for meaningful decisions.

9. What differentiates top performers in an AI-driven workplace?

   Individuals who can effectively interpret AI outputs, refine them, and apply them strategically—while also demonstrating adaptability and continuous learning—stand out the most.

10. What are intelligent orchestration systems?

    These are advanced AI tools that go beyond simple automation by managing multi-step workflows, making decisions, and coordinating actions across multiple platforms.

11. How do collaboration tools like Notion and Slack fit into AI-driven operations?

    They centralize knowledge and communication, and when integrated with AI and automation, they become hubs where teams can access insights, trigger workflows, and collaborate in real time.

12. What are “vibe coding” tools and why are they important?

    Tools like Lovable enable users to quickly build applications or prototypes without deep coding knowledge, accelerating experimentation and lowering the barrier to product development.

13. What risks come with increased reliance on AI?

    Over-reliance without understanding underlying processes can lead to errors, poor decision-making, and reduced accountability, especially if outputs are not properly reviewed.

14. How can organizations responsibly adopt AI?

    By combining automation with human oversight, implementing quality checks, and fostering a culture of continuous learning and critical evaluation of AI-generated outputs.

15. What does the future of work look like in an AI-driven world?

    The future will favor individuals who blend technical fluency with human skills like critical thinking, adaptability, and empathy, as AI becomes a core collaborator in daily work rather than just a tool.

AI + Snowpal API for Faster Development

Podcast

Digital Transformation in the Oil & Gas Industry: Where Data Meets Deep Domain Expertise — on Apple and Spotify.

The oil and gas industry is often perceived as traditional—anchored in physical infrastructure, field operations, and decades-old engineering practices. But beneath that surface, a significant shift is underway. What used to be a largely mechanical and intuition-driven industry is steadily becoming one of the most data-intensive sectors in the global economy.

Conversations with leaders like Steve Senterfit reveal that this transformation isn’t primarily about adopting new tools. It’s about rethinking how decisions are made, how operations are run, and how value is created across the lifecycle of energy production.

Transformation Starts With the Business, Not Technology

A common misconception is that digital transformation begins with technology selection—AI platforms, analytics tools, or automation systems. In reality, especially in oil and gas, it starts with the business itself.

As highlighted in your discussion , early transformation efforts—often called the “digital oil field”—were focused on a simple but powerful objective: improving production outcomes. The goal was to extract resources more efficiently, reduce costs, and enhance safety. That fundamental objective hasn’t changed. What has changed is the sophistication of the tools available to achieve it.

But technology alone doesn’t transform an organization. Companies often struggle not because their strategy is flawed, but because they underestimate the complexity of execution—aligning teams, managing change, and ensuring adoption.

Why Oil & Gas Is Fundamentally Different

One of the reasons transformation in oil and gas is so challenging is that the industry itself is deeply specialized. Unlike software-driven sectors where solutions can be reused across domains, oil and gas operations are tightly coupled with physical environments and geological realities.

A well in Texas behaves differently from one in Pennsylvania. Offshore drilling introduces an entirely different set of constraints compared to onshore operations. Even when processes appear similar at a high level, the underlying conditions—temperature, pressure, chemical composition—require tailored approaches.

This is why domain expertise matters so much. You can’t simply apply a generic transformation playbook. The systems, the data, and even the decision logic are often unique to the field, the basin, or the asset.

The Hybrid Nature of Transformation

Another distinguishing feature of oil and gas is that transformation isn’t purely digital. It exists at the intersection of physical and digital systems.

Modern operations rely on sensors embedded deep within wells, fiber optics capturing real-time data, and drones inspecting pipelines across vast geographies. These physical technologies feed into software systems that analyze, interpret, and act on the data.

This creates a layered ecosystem where operational technology and information technology converge. Transformation, therefore, isn’t about upgrading software alone—it’s about orchestrating an entire system that spans the field and the cloud.

AI: Evolution, Not Revolution

There’s a tendency to frame AI as something entirely new, but in oil and gas, that’s not quite accurate. Machine learning and predictive models have been in use for years, particularly in areas like equipment maintenance and production forecasting.

What’s changed recently is accessibility. With the rise of generative AI and more user-friendly platforms, the barrier to entry has lowered significantly. Organizations can now experiment and deploy solutions faster than before.

A compelling example from your discussion is chemical injection optimization. Traditionally, engineers relied on experience and historical data to decide how to treat wells for issues like corrosion or scaling. Today, AI systems can analyze years of sensor data and lab results simultaneously, generating recommendations that are far more comprehensive than what a human could process alone.

And yet, the final decision still rests with people.

The Enduring Role of Human Judgment

This is where one of the most important insights emerges. Despite advances in AI, human expertise remains central.

AI systems can identify patterns, generate recommendations, and even automate certain workflows. But they are not infallible. They depend on data quality, can drift over time, and occasionally produce incorrect outputs. In a high-stakes environment like oil and gas, where decisions can have safety and financial implications, that margin of error matters.

The most effective approach, as emphasized by Steve Senterfit, is to keep humans in the loop. AI augments decision-making rather than replacing it. Over time, feedback from human decisions helps improve the system, creating a continuous learning cycle.

The Real Bottleneck: Adoption

Interestingly, the biggest challenge isn’t building these systems—it’s getting people to use them effectively.

Organizations often invest heavily in technology but fall short on training and integration. Tools are deployed, but workflows remain unchanged. Employees revert to familiar methods, not because they resist innovation, but because they haven’t been shown how to incorporate new tools into their daily work.

This gap between capability and usage is where many transformation efforts stall. It’s not enough to provide a tool; companies must also build the skills and habits required to use it.

Alignment and Execution

Another recurring theme is the difficulty of maintaining alignment within large organizations. Transformation initiatives typically span multiple functions—engineering, operations, IT—and each comes with its own priorities.

Even when leadership agrees on a roadmap, execution can drift. Teams may interpret priorities differently, or short-term pressures may override long-term goals. Without strong governance and clear ownership, progress slows and outcomes fall short.

This is particularly pronounced in oil and gas, where operations are complex and interdependent. Success depends not just on technology, but on coordination across the entire organization.

Looking Ahead

The future of oil and gas is not about replacing traditional operations but enhancing them. We are moving toward systems that are more connected, more predictive, and more adaptive.

Data will continue to play a central role, but it will be the combination of data, technology, and human expertise that defines success. Companies that understand this balance—those that invest not just in tools but in people and processes—will be the ones that lead the next phase of transformation.

Q & A

1. Who is featured in this interview and what expertise does he bring?

   Steve Senterfit, President of SmartBridge, brings deep experience in digital transformation, particularly within the oil and gas industry, offering practical insights on technology adoption and operational change.

2. What is the main focus of the discussion?

   The conversation centers on how digital transformation is reshaping the oil and gas industry, including the role of AI, domain expertise, and strategies for successful implementation.

3. How is the oil and gas industry evolving today?

   While traditionally rooted in physical infrastructure and engineering practices, the industry is becoming increasingly data-driven, with decisions and operations guided by advanced analytics.

4. Where does digital transformation actually begin in oil and gas?

   It starts with business objectives—such as improving production, reducing costs, and enhancing safety—rather than with selecting new technologies.

5. Why do many transformation efforts struggle?

   Organizations often underestimate execution challenges, such as aligning teams, managing change, and ensuring that new technologies are properly adopted.

6. What makes digital transformation in oil and gas uniquely challenging?

   The industry is highly specialized, with operations varying significantly by geography and environment, requiring tailored solutions rather than one-size-fits-all approaches.

7. Why is domain expertise critical in this industry?

   Because each asset, basin, and operation has unique conditions, deep knowledge of the field is necessary to design effective systems and make informed decisions.

8. What does the “hybrid nature” of transformation mean in oil and gas?

   It refers to the integration of physical systems (like sensors and equipment) with digital systems (like analytics and software), creating a connected ecosystem across field and cloud.

9. How has AI traditionally been used in oil and gas?

   AI and machine learning have long been applied to areas like predictive maintenance and production forecasting, supporting operational efficiency.

10. What has changed recently in AI adoption?

    AI has become more accessible due to user-friendly platforms and generative tools, enabling faster experimentation and broader adoption across organizations.

11. Can you give an example of AI in practice within oil and gas?

    AI can optimize chemical injection in wells by analyzing large volumes of sensor and lab data, providing more comprehensive recommendations than manual analysis.

12. Does AI replace human decision-making in this context?

    No, AI supports decision-making, but final judgments remain with human experts, especially in high-stakes environments.

13. Why is human oversight still essential when using AI?

    AI systems can produce errors, depend on data quality, and may drift over time, making human validation critical to ensure accuracy and safety.

14. What is the biggest barrier to successful transformation?

    Adoption—many organizations implement tools but fail to integrate them into daily workflows or properly train employees to use them.

15. What will define success in the future of oil and gas transformation?

    The ability to balance data, technology, and human expertise—investing not just in tools, but also in people, processes, and organizational alignment.

AI + Snowpal API for Faster Development

Podcast

From Noise to Signal: Winning in AI-Driven Marketing — on Apple and Spotify.

The New Reality of Marketing in an AI-Driven World

Marketing has always evolved alongside technology, but the current shift driven by AI is not incremental—it is structural. What began decades ago as a discipline centered around a few channels like television, print, and radio has transformed into a highly fragmented ecosystem of platforms, data streams, and performance metrics. Today’s marketer is expected to manage not only messaging and brand but also analytics, attribution, personalization, and continuous experimentation across dozens of channels. As noted in the discussion, the explosion of tools has introduced more complexity than clarity, forcing marketers into operational overhead rather than strategic thinking. AI enters this landscape as both a unifier and a disruptor, promising to consolidate workflows and enhance decision-making, yet simultaneously risking further fragmentation if layered blindly onto already complex systems. The paradox is that while AI is easier than ever to adopt, meaningful differentiation through AI remains rare because most organizations mistake access for advantage.

The Fragmentation Problem Marketers Must Confront

The fragmentation of the marketing stack is not merely a tooling issue—it is a cognitive one. Over time, marketers have been pulled away from core creative and strategic responsibilities into a cycle of managing dashboards, interpreting metrics, and optimizing micro-performance indicators. The rise of search engines, followed by social media and then performance marketing, created an environment where every action could be measured, but not necessarily understood. This distinction is critical. Just because something can be quantified does not mean it contributes to meaningful outcomes. AI has the potential to reverse this trend by abstracting complexity and enabling marketers to operate from a more unified layer, but only if it is implemented with intent. Otherwise, it becomes yet another layer of abstraction that distances teams further from clarity. The real opportunity is not to add AI to the stack, but to use AI to collapse the stack into something more coherent and strategically aligned.

The Illusion of Productivity in AI-Powered Marketing

AI has dramatically increased the speed at which marketing outputs can be generated, creating an illusion of productivity that can be dangerously misleading. Content can now be produced at scale—blogs, social posts, ad variations, campaign ideas—often in minutes. However, this abundance of output does not inherently translate into effectiveness. In fact, it often leads to saturation, where channels are filled with content that lacks differentiation, depth, or strategic coherence. The result is not engagement, but fatigue. Many marketing teams fall into the trap of optimizing for volume because it is easy to measure, while neglecting the harder question of whether the content actually resonates or builds trust. AI amplifies whatever intent it is given; if the intent is shallow, the output will be shallow at scale. The challenge for marketers is to resist the temptation to equate speed with value and instead focus on whether their efforts are creating meaningful connections with their audience.

Marketing Still Starts with Fundamentals

Despite the rapid evolution of tools and technologies, the foundational principles of marketing remain unchanged. At its core, marketing is about understanding customer needs, communicating value clearly, and building trust over time. One of the most common mistakes, particularly among product-driven and engineering-led teams, is delaying marketing until the product is “ready.” As emphasized in the conversation, marketing should begin in parallel with product development, not as a downstream activity. Early marketing efforts are not about scale but about signal—understanding how the market responds, refining messaging, and validating assumptions. A simple website, clear positioning, early content, and initial customer feedback can provide invaluable insights long before a product reaches maturity. AI can accelerate these efforts by reducing the cost and time required to create and test messaging, but it cannot replace the need for clarity of thought. Without that clarity, even the most sophisticated tools will produce noise rather than insight.

Content as the Foundation of Modern Marketing

Content remains the central pillar of marketing, particularly in the early stages of a business, but its role has evolved significantly. It is no longer sufficient to create content solely for human consumption or traditional search engines. Increasingly, content must also be structured in ways that are interpretable by AI systems that mediate discovery. This includes formats such as FAQs, clearly articulated problem-solution narratives, and authoritative explanations that can be easily parsed and surfaced by AI-driven interfaces. The implication is that content strategy must now account for both human readability and machine interpretability. As discussed, creating content has become easier than ever with AI, but the challenge lies in ensuring that it reflects the brand’s voice, maintains consistency, and delivers genuine value. The role of the marketer shifts from content creator to content curator and strategist, guiding AI outputs to align with broader business objectives and brand identity.

The Rise of AI-Driven Discovery

The way users discover information is undergoing a fundamental transformation. Traditional search engines provided a list of options, requiring users to navigate and interpret results themselves. AI-driven systems, by contrast, aim to provide direct answers, synthesizing information from multiple sources into a single response. This shift changes the dynamics of visibility. It is no longer enough to rank highly on a search results page; brands must now be recognized as credible sources that AI systems choose to reference. Credibility, therefore, becomes a critical asset. Signals such as media mentions, expert commentary, customer testimonials, and consistent messaging across platforms play a significant role in how AI systems evaluate and surface information. Public relations, thought leadership, and external validation are no longer peripheral activities—they are central to discoverability. Marketing, in this context, becomes less about capturing attention and more about earning trust at scale.

Why Most Marketers Misuse AI

The misuse of AI in marketing often stems from a failure to rethink underlying processes. Instead of reimagining workflows, many organizations simply layer AI onto existing systems, using it to generate more content, more reports, and more campaigns without addressing fundamental inefficiencies. This results in increased activity without improved outcomes. Another critical issue is the lack of behavioral change. While organizations may mandate AI adoption, individuals often continue to operate using familiar habits and mental models. The tools evolve, but the mindset does not. As observed in practice, a significant number of organizations have AI initiatives in place, yet only a small percentage leverage these tools in ways that meaningfully transform their operations. True adoption requires not just technical integration but a shift in how teams think, collaborate, and make decisions.

Creativity in the Age of Automation

Contrary to popular belief, the rise of AI does not diminish the importance of creativity—it amplifies it. When execution becomes commoditized, differentiation must come from insight, originality, and storytelling. If every competitor has access to the same tools and can produce similar outputs, then the quality of thinking behind those outputs becomes the defining factor. AI can generate ideas, but it cannot replace the nuanced understanding of audience psychology, cultural context, and brand voice that experienced marketers bring to the table. The role of the marketer evolves from executor to orchestrator, guiding AI to produce outputs that are not just efficient but meaningful. In this sense, AI does not replace human creativity; it raises the bar for it.

Building Marketing That Compounds Over Time

Effective marketing is not the result of isolated efforts but of consistent, compounding actions that build over time. Early-stage activities such as creating foundational content, gathering customer testimonials, and establishing thought leadership may appear incremental, but they create a cumulative effect that strengthens brand presence and credibility. Each piece of content, each mention, and each interaction contributes to a larger narrative that defines how a brand is perceived. AI can accelerate this compounding process by enabling faster production and distribution, but the underlying strategy must remain disciplined and focused. The goal is not to do everything at once, but to build a system where each effort reinforces the next, creating a flywheel of visibility and trust.

From Adoption to Advantage

The widespread availability of AI has lowered the baseline for execution in marketing, making it easier for more teams to operate at a higher level of efficiency. However, this also means that differentiation is harder to achieve. Advantage no longer comes from simply using AI, but from using it with intent and precision. Marketers who focus on clarity, strategy, and customer understanding will leverage AI to amplify their strengths, while those who rely on it as a shortcut will generate volume without value. The distinction between adoption and advantage lies in how thoughtfully AI is integrated into the broader marketing strategy.

The Path Forward for Marketers

The future of marketing will be defined by those who can balance the speed and scale of AI with the judgment and insight of human decision-making. As tools continue to evolve, the temptation to prioritize efficiency will remain strong, but the true opportunity lies in using AI to enhance, not replace, strategic thinking. Marketers must remain grounded in fundamentals while embracing new capabilities, ensuring that every action contributes to a coherent and meaningful brand narrative. AI can accelerate execution, but it cannot determine what matters. That responsibility remains firmly in the hands of those who understand not just how to market, but why it matters.

Q & A

1. Who is featured in this discussion and what expertise do they bring?

   Harjiv Singh, founder and CEO of CambrianEdge, shares insights on how AI is transforming modern marketing, with a focus on strategy, execution, and leveraging AI-native platforms effectively.

2. What is the main theme of this piece?

   It explores how AI is reshaping marketing by addressing complexity, improving workflows, and challenging teams to rethink how they operate in a fragmented digital landscape.

3. How has marketing evolved in the AI era?

   Marketing has shifted from a few traditional channels to a highly fragmented ecosystem of platforms, data streams, and performance metrics, increasing both opportunity and complexity.

4. What major challenge do modern marketers face today?

   They are overwhelmed by fragmented tools and data, often spending more time managing systems and metrics than focusing on strategy and creativity.

5. How does AI both help and complicate marketing?

   AI can unify workflows and improve decision-making, but if added without intention, it can increase fragmentation and operational complexity.

6. What is the “fragmentation problem” in marketing?

   It refers to the proliferation of tools and metrics that pull marketers away from core strategic work into managing dashboards and optimizing isolated performance indicators.

7. Why is measuring everything not always beneficial?

   Because not all measurable actions contribute to meaningful outcomes—data without context can lead to misguided decisions.

8. What is the “illusion of productivity” created by AI?

   AI enables rapid content generation, which can create the appearance of productivity, but high output does not necessarily lead to effective or impactful marketing.

9. Why can AI-generated content lead to saturation?

   Because it allows teams to produce large volumes of similar content quickly, often lacking differentiation, depth, and strategic alignment.

10. What foundational principle of marketing remains unchanged?

    Marketing still centers on understanding customer needs, communicating value clearly, and building trust over time.

11. When should marketing begin in a company’s lifecycle?

    It should start alongside product development, not after, to gather early feedback, refine messaging, and validate assumptions.

12. How has the role of content evolved in modern marketing?

    Content must now serve both human audiences and AI systems, requiring it to be structured, clear, and easily interpretable by machines.

13. What is changing about how users discover information?

    AI-driven systems are replacing traditional search lists with direct answers, shifting the focus from ranking to being a credible, referenced source.

14. Why is credibility becoming more important in marketing?

    Because AI systems prioritize trusted sources, making signals like media mentions, testimonials, and consistent messaging critical for visibility.

15. How do most organizations misuse AI in marketing?

    They layer AI onto existing processes without rethinking workflows, leading to more activity but not necessarily better outcomes.

16. Why is mindset change important for AI adoption?

    Because tools alone don’t transform results—teams must change how they think, collaborate, and make decisions to fully leverage AI.

17. How does AI impact creativity in marketing?

    It amplifies the importance of creativity, as differentiation increasingly depends on original thinking, storytelling, and strategic insight.

18. What role does the marketer play in an AI-driven environment?

    The marketer shifts from executor to orchestrator, guiding AI outputs to ensure they align with brand voice, strategy, and audience needs.

19. What does it mean for marketing to “compound over time”?

    Consistent efforts like content creation, thought leadership, and customer engagement build cumulative value, strengthening brand presence and trust.

20. What distinguishes AI adoption from true competitive advantage?

    Adoption is simply using AI tools, while advantage comes from using them thoughtfully with clear strategy and deep customer understanding.

21. What is the key takeaway for the future of marketing?

    Success will come from balancing AI’s speed and scale with human judgment, ensuring that efficiency enhances—rather than replaces—strategic thinking.

AI + Snowpal API for Faster Development

Podcast

AI Didn’t Kill Engineering: It Changed It — on Apple and Spotify.

Vibe coding compresses the distance between idea and execution. What once required coordinated engineering effort over weeks can now be prototyped in days, sometimes hours. This shift has dramatically lowered the barrier to entry, enabling both developers and non-developers to bring products to life. But in doing so, it has also commoditized the very act of building. If anyone can create software, then creation itself is no longer a differentiator. The competitive edge moves upstream—toward problem definition, clarity of thought, and the ability to shape solutions that reflect real-world nuance rather than generic outputs.

Krish raises a subtle but important concern: when people rely on AI too early in the process, they risk outsourcing not just execution, but thinking. Without a clear mental model of the problem, the tool begins to influence direction, introducing bias and often converging outcomes across users. AJ acknowledges this tension directly when he notes that AI will only do what it is asked to do—if the user lacks clarity, the output reflects that gap. This creates a paradox: the more powerful the tool, the more important it becomes to know what you’re doing before you use it.

Experience, therefore, still matters—but in a more nuanced way. It is less about knowing how to code and more about understanding the domain you are operating in. A seasoned practitioner brings context, pattern recognition, and an instinct for what questions to ask. AI can accelerate answers, but it cannot compensate for poorly framed problems. As highlighted in the discussion, someone with decades of experience in a field will always guide the tool more effectively than someone encountering the domain for the first time, even if both have access to the same technology.

A deeper risk emerges as AI-generated output becomes abundant: the erosion of human thinking. Instead of creating, experts increasingly find themselves reviewing and validating machine-generated content. AJ points out that a significant portion of senior expertise is already shifting toward proofreading “AI slop,” a trend that, if unchecked, could lead to the atrophy of critical thinking skills. When individuals stop exercising judgment and rely too heavily on automation, they risk losing the very capabilities that make AI valuable in the first place.

At the same time, there is a powerful upside for those who remain curious. AI rewards individuals who ask better questions, probe deeper, and iterate thoughtfully. Rather than using AI as an answer engine, AJ emphasizes using it as a discovery tool—something that helps identify blind spots and uncover the “corners” of a problem space. This reframing shifts the value from knowing answers to knowing how to explore, a skill that becomes increasingly important in an AI-driven environment.

These changes extend into hiring and team design. The rise of AI-enabled workflows is pushing organizations toward hybrid roles, where individuals are expected to operate across disciplines. Engineers must think in terms of product and user experience, while product managers must engage more deeply with technical possibilities. The modern contributor begins to resemble a one-person cross-functional team. However, this shift introduces tension between breadth and depth. While generalists can move quickly and adapt, they may lack the deep expertise required to navigate complex or high-stakes challenges.

As building becomes easier, differentiation shifts toward trust and proximity to the customer. In a world where multiple teams can produce similar solutions, the deciding factor is no longer just what is built, but who is building it and how well they understand the user. AJ highlights that success increasingly depends on being close to the customer—engaging directly, iterating with feedback, and building credibility through interaction. Founder-led storytelling and community presence begin to matter as much as, if not more than, the product itself.

Ultimately, the conversation reinforces a simple but powerful idea: tools do not determine outcomes—people do. AI expands what is possible, but it does not replace the need for clarity, judgment, or responsibility. The starting point is still the problem—what you are trying to solve and for whom. Everything else, including the tools you use, follows from that. The future that emerges is not one where humans are sidelined, but one where their role becomes more intentional. The real challenge is not keeping up with AI, but maintaining the discipline to think clearly, ask the right questions, and stay grounded in purpose as the tools around us continue to evolve.

AJ’s Company Links

• Convia Studio

• MXP Studio

• Facing Disruption Podcast

The journey of building a company is rarely linear, but when technology and human behavior intersect, the complexity multiplies. In a recent conversation on the Snowpal podcast, Anil Kumar, founder of Jodi365, offered a deeply reflective look into what it takes to build and sustain a product in a rapidly evolving landscape—one shaped equally by code and culture.

AI + Snowpal API for Faster Development

Podcast

Beyond Features: The Real Product Advantage — on Apple and Spotify.

Identifying the Problem Before the Product

Every meaningful product begins with a problem that refuses to be ignored. In the case of Jodi365, the inspiration came from observing a gap in the matchmaking ecosystem. Traditional matrimonial platforms were outdated in both design and intent, often driven by family involvement rather than individual agency. Meanwhile, emerging dating platforms lacked the seriousness required for long-term relationships.

This disconnect created an opportunity. The idea was not to replicate what already existed but to build something that resonated with a new generation—independent, career-focused individuals seeking meaningful connections without abandoning cultural context. The vision was a hybrid platform that balanced structure with autonomy.

The Reality of Building Technology Over Time

Technology evolves relentlessly, and staying relevant requires constant adaptation. One of the most candid admissions from Anil was the acknowledgment of early technical missteps. The initial versions of the platform were built quickly, prioritizing speed over scalability. This resulted in accumulated technical debt, clunky user experiences, and limitations that constrained product evolution.

As the platform grew, these early decisions became bottlenecks. Rebuilding while operating a live product proved to be one of the toughest challenges. Transitioning from basic content management systems to more sophisticated architectures, including graph databases, marked a turning point. It enabled more efficient matchmaking and significantly improved performance.

Yet, even with these improvements, the lesson remained clear: technology is an enabler, not the product itself. Users do not care about frameworks or databases; they care about outcomes. In this case, the outcome was finding meaningful matches quickly and reliably.

The Trade-offs That Define Product Decisions

One of the most insightful aspects of the conversation was the emphasis on prioritization. In a resource-constrained environment, not every improvement is worth pursuing. Decisions like delaying an iOS app or ignoring minor UI inconsistencies were deliberate, grounded in the understanding that not all enhancements drive real value.

This reflects a broader principle in product development: focusing on what moves the needle. The 80/20 rule becomes essential. Perfection is often the enemy of progress, and chasing it can divert attention from core value creation.

Cultural Evolution as a Moving Target

While technology presents one set of challenges, cultural change introduces another layer of complexity. Over the past decade, societal norms in India have shifted dramatically. Increased economic independence, urbanization, and exposure to global ideas have reshaped how relationships are formed.

Young professionals today operate differently from previous generations. They seek compatibility beyond traditional filters, prioritize personal choice, and navigate relationships with greater autonomy. Platforms like Jodi365 must continuously adapt to these shifts, ensuring they remain relevant without losing their foundational identity.

This dual challenge—keeping pace with both technological and cultural change—requires a deep understanding of users, not just as customers, but as evolving individuals.

Competing in a Globalized Digital Economy

The rise of global platforms introduced another dimension of competition. When apps like Tinder entered the Indian market, they brought with them refined user experiences and significant capital. Many local startups attempted to replicate these models, often with substantial funding, but struggled to sustain momentum.

The insight here is subtle but important. Markets like India do not always favor local clones of global products. Instead, success often comes from differentiation rooted in local context rather than imitation. Jodi365’s approach—focusing on a specific, underserved segment—allowed it to survive and grow without chasing scale for its own sake.

Rethinking Success Beyond Venture Capital

In an ecosystem that often equates success with venture funding and rapid scaling, Anil’s perspective offers a refreshing counterpoint. Turning down investment, especially from prominent firms, is unconventional. Yet, it reflects a disciplined approach to growth—one that prioritizes sustainability over valuation.

Building a profitable business, funding growth through revenue, and maintaining control over strategic direction are choices that require patience and conviction. They also challenge the dominant narrative of what a successful startup should look like.

Lessons for Builders Navigating Complexity

The story of Jodi365 is not just about matchmaking; it is about navigating complexity in its many forms. It highlights the importance of starting with a clear problem, embracing iteration, and making pragmatic decisions in the face of constraints.

It also underscores a deeper truth: building products for humans requires more than technical expertise. It demands empathy, cultural awareness, and the ability to evolve alongside the very people you serve.

In a world where both technology and society are in constant flux, the most resilient products are those that understand this interplay—and design for it.

Q & A

1. Who is featured in this interview and what is his background?

   Dr. Anil Kumar, founder of Jodi365, shares his journey from India to the US, his experience building an online matchmaking platform, and his perspectives on technology, culture, and entrepreneurship.

2. What is the central theme of the conversation?

   The discussion focuses on building products at the intersection of technology and human behavior, emphasizing how cultural and societal shifts influence innovation.

3. What problem was Jodi365 designed to solve?

   It aimed to bridge the gap between traditional matrimonial platforms, which were often family-driven, and casual dating apps, by creating a platform for serious, modern relationships.

4. What made Jodi365’s approach unique?

   It combined structure with individual autonomy, catering to independent, career-focused users seeking meaningful connections within a cultural context.

5. What early technical challenges did the company face?

   Initial versions prioritized speed over scalability, leading to technical debt, poor user experience, and limitations that hindered growth.

6. How did the platform evolve technologically over time?

   It transitioned to more advanced architectures, including graph databases, which improved matchmaking efficiency and overall performance.

7. What key lesson did Anil Kumar highlight about technology?

   Technology is only an enabler—users care about outcomes, such as finding meaningful matches, not the underlying systems.

8. Why is prioritization critical in product development?

   Resources are limited, so teams must focus on features that deliver real value rather than pursuing perfection or minor improvements.

9. How does the 80/20 rule apply to product decisions?

   It helps teams concentrate on the small set of efforts that drive the majority of results, avoiding wasted effort on low-impact enhancements.

10. How have cultural shifts in India impacted matchmaking platforms?

    Increased independence, urbanization, and global exposure have changed relationship expectations, with users seeking compatibility and autonomy.

11. Why is understanding cultural change important for product success?

    Because user needs evolve over time, and products must adapt to remain relevant while staying aligned with their core purpose.

12. What competitive challenges did global platforms introduce?

    Apps like Tinder brought polished experiences and funding, making it harder for local startups to compete without differentiation.

13. How did Jodi365 differentiate itself from competitors?

    By focusing on a specific underserved segment and building for local context rather than copying global platforms.

14. What unconventional decision did Anil Kumar make regarding funding?

    He chose to turn down venture capital, prioritizing sustainable growth and control over rapid scaling.

15. What broader lesson does this story offer to builders?

    Successful products require more than technology—they demand empathy, cultural awareness, and the ability to adapt to both technological and societal change.

In today’s rapidly evolving tech landscape, leadership is no longer confined to building great products or managing internal teams. As highlighted in the conversation with Shayna Davis, tech leaders are increasingly expected to step outside their organizations and represent their companies to a broader audience. This shift has exposed a critical “competency gap” — the difference between technical expertise and the ability to communicate effectively with external stakeholders.

Podcast

Why Great Products Alone Don’t Win Anymore — on Apple and Spotify.

Understanding the Competency Gap

Traditionally, many technical leaders—especially those in engineering or product roles—focused primarily on execution. Their responsibilities revolved around building, scaling, and optimizing systems. External communication was often limited to founders or dedicated PR teams.

However, this expectation has fundamentally changed. Today, leaders across the organization—from CTOs to heads of product—are expected to engage with investors, customers, potential hires, and even the media. As Shayna Davis explains, this shift creates a gap because communication has become a required skill, but not one many leaders were trained for.

Why External Communication Matters

Building Trust

In an era where skepticism is at an all-time high, trust has become a competitive advantage. Stakeholders want to believe in the people behind the product—not just the product itself. Leaders who clearly articulate their vision, values, and perspective are more likely to earn that trust.

Attracting Talent

The competition for skilled professionals is intense. Candidates are no longer evaluating companies solely based on compensation or technology—they are evaluating leadership. A compelling external presence can inspire confidence and attract top-tier talent.

Navigating Rapid Change

Technology evolves at a breakneck pace. Leaders must demonstrate not only that they understand these changes but also that they have a perspective on where the industry is heading. This ability positions them as credible voices in their space.

The Changing Landscape of Leadership

According to Shayna Davis, three major forces are driving the need for stronger external communication. Companies today are operating in intense talent wars, competing aggressively for skilled professionals. At the same time, they are facing growing trust gaps, as public confidence in institutions and organizations continues to decline. Adding to this challenge is rapid technological disruption, where new innovations constantly reshape the competitive landscape.

These forces mean that having a strong product and a capable team is no longer enough. Perception, reputation, and narrative now play a critical role in success.

Moving Beyond Product-Centric Communication

One of the most common mistakes leaders make is focusing too heavily on product features when communicating externally. While product details are important, they are rarely memorable.

The most impactful leaders are those who go beyond surface-level messaging. They share their unique point of view about the industry, explain why they are building what they are building, and offer insights that cannot simply be found on their website. This shift transforms communication from transactional to meaningful. Instead of sounding like a product brochure, leaders begin to sound like thought leaders.

Real-World Illustration

Consider a panel discussion where multiple leaders present similar products. Most speakers might describe features, benefits, and use cases in a predictable manner. However, the standout speaker is often the one who shares a personal story, connects industry trends to real-world experiences, and explains the broader mission behind their work.

That individual becomes memorable—not because of their product alone, but because of their perspective and authenticity.

Practical Strategies for Tech Leaders

Develop a Clear Leadership Narrative

Leaders should take the time to define who they are, what they believe about their industry, and why their company exists. This narrative becomes the foundation for all external communication and helps ensure consistency across different interactions.

Practice Intentional Communication

Communication is not about changing one’s personality but about being intentional. Leaders should consciously decide how they want to show up and what they want to be known for, ensuring that their messaging aligns with their values and goals.

Balance Product and Perspective

Effective communication requires a balance between perspective and product messaging. Perspective helps build trust and credibility, while product messaging ensures clarity and drives action. Focusing too heavily on one at the expense of the other can limit impact.

Leverage Content Thoughtfully

Content creation, especially on professional platforms like LinkedIn, serves as a digital footprint. Even a small amount of consistent, high-quality content can reinforce credibility, showcase thought leadership, and build trust before direct conversations even begin.

Start Small but Stay Consistent

For startups and smaller teams, communication efforts do not need to be overwhelming. Even dedicating a short amount of time each month to refining messaging, aligning on perspectives, and improving online presence can create meaningful progress over time.

Communication as a Competitive Advantage

One of the most important insights is that communication is not just a supporting skill—it is a strategic advantage. When leaders communicate clearly and authentically, they build stronger relationships with customers, investors, and employees. This, in turn, drives trust, engagement, and long-term success.

Conversely, a lack of effective communication can erode trust, even if the product itself is strong.

Conclusion

The modern tech leader must evolve beyond technical excellence. While building a strong product and team remains essential, it is no longer sufficient.

Bridging the competency gap in external communication is now a critical leadership skill. By developing a clear narrative, sharing authentic perspectives, and engaging intentionally with external audiences, leaders can build trust, differentiate themselves, and position their companies for success in an increasingly competitive market.

In a world where many companies offer similar products, the leaders who communicate effectively are the ones who truly stand out.

In this engaging conversation, Dr. Giannoumis shares insights on learning from diverse perspectives, the importance of humility, and the value of kindness in a polarized world. Krish Palaniappan explores topics from cultural diversity to personal growth, offering a rich tapestry of stories and lessons.

Snowpal API on AWS Marketplace

Podcast

The Leaders Who Listen Lead Better — on Apple and Spotify.

Turns Out Every Leadership Lesson Comes With a Plot Twist

Here’s a list of some of the things discussed in this podcast.

• The student who said, “I made a list of all the things you did wrong today”

• The lecture that felt brilliant until honest feedback changed everything

• Learning to sit with criticism instead of shutting it down

• Why feedback feels like an attack before it feels like a gift

• The Norway classroom and the culture of challenging authority

• What changes when feedback crosses cultures

• Why some teams only open up after dinner, drinks, or informal trust-building

• The Indian classroom story: when authority threw the exam paper out the window

• Why “culture fit” is often just comfort in disguise

• The UN hackathon where the unexpected student team won top prize

• Seeing the whole person: the Costa Rica PhD story

• The leadership failure of assuming someone else’s transition looks like yours

• Why confidence is overrated and curiosity matters more

• The 18-year-old mentor who changed a professor’s career

• The quiet leadership mistake that kills great teams

• How listening becomes a competitive advantage

• Why inclusion is not just moral, but practical

• What great leaders learn from the people they least expect

The Student Who Tore Up His Ego and Made Him a Better Leader

Some leadership lessons come from boardrooms. Others come when a student walks up after class, opens a notebook, and says, “I made a list of all the things you did wrong today.” That moment became one of Dr. Giannoumis’s most important lessons in leadership. A professor, entrepreneur, keynote speaker, and author focused on inclusive leadership, Dr. Giannoumis has worked across countries and industries, but one of his clearest insights is simple: if you are not listening, you are not really leading.

Early in his teaching career, he thought he had delivered a brilliant lecture. Students praised him afterward, and he was feeling proud, until one student stayed behind and bluntly told him everything he had done wrong. His first reaction was defensive. He felt offended, angry, and ready to reject it. But instead, he listened. Some of the feedback stung, some felt unfair, and some turned out to be exactly what he needed. Looking back, he says that moment made him a better professor, teacher, researcher, and leader. The point was not that great leaders never feel threatened. The point was that they notice the feeling and do not let it control their response.

Why Feedback Feels Personal — and Why Culture Changes How It’s Heard

Dr. Giannoumis is clear that listening is not the same as instantly agreeing. Feedback often feels like an attack before it feels like a gift. He describes the physical reaction first: your heart races, your mind speeds up, and your instinct is to fight or flee. That is why self-awareness matters. If leaders can recognize those triggers, they can create enough distance to actually hear what is being said. Sometimes the job is simply to stay quiet long enough to understand, then decide what is useful and worth acting on.

That becomes even more important across cultures. In Norway, where Dr. Giannoumis lives and works, students are encouraged to challenge authority, and flatter hierarchies make direct feedback more normal. In more collectivist or hierarchical settings, the same style can be inappropriate or ineffective. Feedback may need to travel through trusted intermediaries, private conversations, or carefully created spaces where people feel permission to speak. He has seen this in places like China and Mozambique, where honest input depends less on asking for it publicly and more on building trust and context first. Listening may be universal, but the path to getting honest feedback is not.

Why Hiring for “Culture Fit” Often Builds Weaker Teams

This same idea shows up in hiring. Giannoumis argues that “culture fit” is often one of the laziest decisions leaders make because it usually means comfort, not contribution. People hire those who feel familiar, who sound right, act right, and match the environment they already know. But teams do not get stronger by maximizing familiarity. They get stronger by adding perspective. A person contributes more than what is written on a résumé. They bring a worldview, a lived experience, and a way of seeing problems that others in the room may miss. That difference is often exactly what creates better decisions.

He learned that lesson sharply during a UN expert hackathon. Invited to participate, his instinct was to bring experienced colleagues he already trusted. Instead, his boss insisted he bring three students. He assumed the opportunity was wasted. But those students, each with different backgrounds and perspectives, ended up winning the top prize. They succeeded not because they looked like the obvious all-star team, but because they challenged each other, brought different viewpoints, and built trust quickly enough that disagreement made the work stronger. What felt less comfortable turned out to be far more effective.

Leadership 101: “See the Whole Person”

One of his most painful leadership stories comes from his book, The Sins and Wins of Inclusive Leadership, in a section called “See the Whole Person.” He met an impressive woman from Costa Rica at a UN event in New York and later invited her to pursue a PhD under his supervision in Norway. She moved there with her family, but during a difficult season in his own life, he became unavailable and brushed off her requests for help getting settled. When he returned, she told him she was leaving the program. The loss was not just professional. It forced him to confront the fact that he had viewed her transition through his own lens rather than hers. He had moved countries before, but under completely different conditions. He had failed to see the full reality of her experience. That was the lesson: leadership requires more than seeing talent. It requires seeing the whole person.

When the conversation turned to confidence and humility, Giannoumis offered a different answer than many leaders might expect. He did not argue that confidence should be the goal. He argued for curiosity. In his view, confidence is overrated, while curiosity is what actually helps leaders grow. Curious people ask how things work, why they work, and what others know that they do not. That mindset keeps leaders open, adaptable, and grounded. It also helps explain why Giannoumis has learned so much not only from peers and mentors, but from students, younger people, and those outside traditional power structures.

The Leadership Trap: When Experience Replaces Learning

That is why he says one of the leadership mistakes that quietly kills teams is the failure to keep learning. Teams weaken when leaders stop being teachable, when seniority turns into certainty, and when expertise becomes a trap. He shared the example of getting career advice from an 18-year-old who had dropped out of high school, a young man who encouraged him to start recording short videos about his research and posting them online. It was not the sort of advice a senior academic would have given him, but it opened a new direction in his work and public voice. The real lesson was not about social media. It was about being willing to learn from unexpected places.

Summary

Across all these stories, the lesson is the same. Leadership is not about always having the answer. It is about making sure better answers can reach you. That means listening when feedback stings, adapting how feedback flows across cultures, hiring for perspective instead of comfort, and noticing when someone else’s experience demands a different kind of support. Listening is not soft. It is strategic. Curiosity is not passive. It is powerful. And inclusion is not just a moral value. It is a competitive advantage.

The conversation explores how strong leadership depends less on authority or confidence and more on listening, self-awareness, curiosity, and the ability to learn from others. It highlights the idea that feedback is often uncomfortable but necessary, and that the best leaders are the ones who can sit with criticism, manage their reactions, and turn difficult moments into opportunities for growth. It also emphasizes that communication, trust, and leadership styles are shaped by culture, so what works in one setting may not work in another. More broadly, the discussion challenges the habit of choosing familiarity over difference, showing how diverse perspectives strengthen teams, improve decision-making, and create better outcomes. At its core, the conversation argues that effective leadership comes from staying open, seeing people fully, and remaining willing to learn from unexpected places.

Snowpal API on AWS Marketplace

Podcast

Practical Wisdom for Modern Business Change — on Apple and Spotify.

What a Transformation Executive Really Does

A transformation executive plays a critical role in bridging the gap between strategic vision and real-world execution. This role goes beyond managing projects or overseeing technology upgrades. It involves helping organizations navigate major shifts in systems, processes, and customer experience. According to Sridhar, a true transformation changes the way people work and the way customers interact with the business. It leaves a permanent impact, much like a major shift in the physical world changes the landscape itself.

What makes this role especially valuable is its ability to connect leadership ambition with operational reality. Boards and executive teams often have bold visions for modernization, but someone must translate those ambitions into practical decisions, measurable outcomes, and sustainable change. That is where the transformation executive becomes essential.

Why Companies Feel Pressure to Transform

Many organizations do not begin transformation from a place of clarity. Instead, they are pushed by outside pressure. Sometimes it is hype around a new technology. Sometimes it is panic that competitors are moving faster. In other cases, it is fear of missing out. Companies see their peers experimenting with AI, cloud migration, or digital modernization and feel compelled to act before fully understanding whether the move is right for them.

Sridhar points out that leaders often fall into predictable postures during these moments. Some are driven by hype and believe the latest technology will change everything. Others act from panic, afraid of becoming irrelevant if they do not move immediately. Still others respond with denial, assuming the latest trend will pass. And finally, many organizations are motivated by FOMO, simply wanting to be seen as innovative because others are doing the same. These reactions can create urgency, but not always wisdom.

Transformation Is Not About Chasing Trends

One of the biggest mistakes companies make is pursuing change for appearance rather than value. A business may decide to move from one technology stack to another, not because the shift improves outcomes, but because it sounds current or satisfies pressure from leadership, vendors, or the market. In some cases, organizations spend heavily on modernization without clearly understanding whether the current system is actually failing them.

This is where strong transformation leadership matters. A good transformation executive does not simply encourage change. They challenge assumptions. They ask whether the move creates real value for customers, improves operational efficiency, or strengthens the business in a lasting way. If the answer is no, then “transformation” may just be expensive motion rather than meaningful progress.

The Missing Piece: Human Experience and Context

Sridhar emphasizes that many leaders focus on what he calls “270-degree visibility.” They look at data, speed to market, competitors, and predictive power. These are all important. But they often miss the final 90 degrees: human experience and context. That missing piece determines whether transformation will actually succeed.

A company can invest in better systems, smarter tools, and faster processes, but if it does not understand how customers experience the product or how employees interact with the changes, the transformation remains incomplete. Human judgment, adoption, and behavior are what turn a technical rollout into a real business outcome. Without that lens, even sophisticated transformation efforts can fail to stick.

How Leaders Should Approach Transformation

The first step in any transformation is to understand both the current state and the intended future state. Leaders need clarity on what is working, what is broken, and what they are trying to achieve. That means evaluating existing systems honestly, defining measurable goals, and deciding where limited resources should go. No organization has unlimited time, money, or talent, so prioritization becomes one of the most important leadership decisions.

There are generally two broad approaches.

1. One is to go deep in one area, investing heavily to transform a single product, service, or operational function.

2. The other is to make shallower improvements across multiple areas, improving the overall business experience without betting everything on one part of the organization.

Each approach can work, depending on the company’s size, goals, and constraints. Large organizations often prefer spreading investment across several initiatives to show broader results, while startups or growth-stage businesses may need to focus narrowly on the one area most likely to drive survival and revenue.

Why So Many Transformations Fail

A striking theme in Sridhar’s perspective is that transformations rarely fail because of strategy alone. In many cases, the plan itself is reasonable. The real breakdown happens in execution, ownership, and leadership. Accountability becomes diffused. Risks get buried in dashboards, committees, and status updates. What looks green on paper may still be red underneath. Teams may quietly reduce scope, shift timelines, or make tradeoffs that make reports look better without actually solving the core problem.

This is why leadership must create what Sridhar calls authentic resistance. Leaders should ask hard questions without aggression. They should not accept green dashboards at face value. Instead, they should look for what changed, what was deprioritized, and who is truly accountable for closing the gap between expectation and outcome. Transformation succeeds when ownership is clear and decisions are grounded in reality rather than presentation.

The Importance of ROI and Value Realization

Transformation cannot be justified by activity alone. It must create value. Organizations often begin with strong business cases and attractive ROI projections, but those projections mean little if no one tracks whether the promised value is actually being realized over time. Sridhar argues that value realization is not a one-time exercise at the approval stage. It must be continuously measured through real-time dashboards, outcome tracking, and clearly assigned ownership.

This is especially important because many digital and AI initiatives fail to deliver meaningful business value. Success requires more than funding and enthusiasm. It requires leaders to revisit assumptions, identify gaps between expected and current outcomes, and assign one accountable owner for each initiative. Without that accountability, blame shifts to the technology, the tool, or the team that is no longer around to defend itself. With accountability, transformation becomes a disciplined effort rather than a vague aspiration.

AI, Automation, and the Role of Humans

As organizations accelerate AI adoption, another misconception emerges: that technology reduces the importance of people. Sridhar’s view is the opposite. The more powerful technology becomes, the more human judgment matters. AI can generate predictions, automate workflows, and support decisions, but it cannot own consequences. That remains a human responsibility.

This is the heart of the “humans at scale” idea. AI does not create leadership gaps; it exposes them. If ownership is weak, automation scales avoidance rather than efficiency. If no one is willing to stand behind a process when it fails, automating that process only makes the failure larger and faster. That is why transformation in the AI era must strengthen human accountability, not weaken it.

Authorship

Sridhar brings a practitioner’s voice to authorship, drawing on more than 25 years of experience in technology, telecom, and large-scale business transformation. Rather than writing from a purely theoretical lens, he writes from the perspective of someone who has worked closely with executive leadership, managed large organizations and P&Ls, and seen firsthand why many transformation efforts succeed or fail. His books reflect that real-world grounding, focusing on the intersection of strategy, execution, leadership accountability, and human judgment in an era increasingly shaped by digital change and AI.

Sridhar Ravilla's Books on Amazon

1. Transformation That Lands: A practical guide to making organizational change stick by turning strategy into measurable, lasting business outcomes.

2. Humans at Scale: A leadership-focused look at why human judgment, ownership, and accountability matter even more in the age of AI.

3. AI 360: A big-picture exploration of AI’s full business impact, from systems and strategy to accountability, context, and decision-making.

Conclusion

Transformation is not a buzzword, a trend, or a technology purchase. It is a disciplined effort to create meaningful, lasting change in how a business operates and delivers value. A transformation executive helps organizations make that change real by bringing together strategy, execution, customer understanding, and human accountability.

For leaders navigating cloud migration, AI adoption, product modernization, or operational redesign, the lesson is clear: transformation works best when it is grounded in purpose, shaped by context, and owned by people who are willing to make difficult decisions. Technology can accelerate the journey, but leadership is what determines whether the transformation actually lands.

Bonus: Q & A

Here’s the crux of the conversation in a Q & A format.

Q: Who is Sridhar Ravilla?

Sridhar Ravilla is a technology and transformation leader with more than 25 years of experience in tech and telecom, focused on connecting executive vision with real-world execution.

Q: What does he mean by a “transformation executive”?

He defines a transformation executive as someone who leads deep, lasting change that reshapes systems, customer experience, and how people work, not just surface-level updates.

Q: What is true transformation according to Sridhar?

True transformation means changing current systems into something new with long-term impact, where the organization cannot simply go back to the old way.

Q: Why do companies pursue transformation?

Companies often pursue transformation because of hype, panic, denial, or fear of missing out, especially when competitors or boards are pushing for visible innovation.

Q: What is the first thing he looks at when advising a company?

He looks at the full business picture, especially the missing “final 90 degrees”: human experience and context, alongside data, speed, competition, and predictive power.

Q: How does he decide where a company should focus?

He helps leaders decide where limited resources will create the best ROI, whether by going deep into one product or making broader but lighter improvements across several areas.

Q: What approach works better: deep focus or broad improvements?

He says both can work. Larger companies often spread transformation across multiple areas to show broader results, while startups usually need to focus deeply on what drives survival and revenue.

Q: What causes most transformations to fail?

He argues that most transformations do not fail because of bad strategy, but because of weak ownership, diffused accountability, and leadership gaps during execution.

Q: What does he say about dashboards and project reporting?

He warns that dashboards may look green even when the real situation is not, because teams may change timelines, reduce scope, or make tradeoffs that hide deeper issues.

Q: What is “authentic resistance”?

It is a leadership habit of asking honest, curious questions and challenging assumptions without aggression so teams stay intellectually honest about progress and risk.

Q: What is his view on ROI and value realization?

He believes ROI should not live only in the original business case. Leaders must track expected outcomes versus actual outcomes continuously and assign one clear owner to every initiative.

Q: Why is accountability so important in transformation?

Without a named owner, failures get blamed on tools, technology, testers, or former team members. Accountability is what turns transformation into a real operating discipline.

Q: What is his view on AI and jobs?

He argues that AI does not replace the need for humans at the center. Instead, it exposes leadership, judgment, and accountability gaps that already existed.

Q: What does he say about automation?

He says automation without ownership scales avoidance, not efficiency. If nobody owns a process, automating it only makes the underlying problem bigger and faster.

Q: What books has he written?

He discusses three books: Transformation That Lands, Humans at Scale, and AI 360, each focused on transformation, leadership, accountability, and AI’s business impact.

Q: What is Transformation That Lands about?

It focuses on how to move beyond hype and make transformation stick in complex organizations so it produces measurable, lasting value.

Q: What is Humans at Scale about?

It explores why people remain essential in the AI era and how leadership must keep pace with technology to avoid a widening “fracture zone.”

Q: What is AI 360 about?

It looks at AI’s broader business impact, including systems, accountability, judgment, and the missing human and contextual dimensions leaders often overlook.

Q: What is his core message overall?

His core message is that successful transformation depends less on technology alone and more on leadership, human judgment, ownership, and disciplined execution.

Q: How do Snowpal’s products fit into this transformation conversation?

Snowpal’s products are used in the discussion as real examples of transformation choices, especially around updating user interfaces, modernizing backend APIs, enabling AI-agent access, and deciding where to focus effort for the best business impact.

Snowpal API on AWS Marketplace

Software founders often talk about solving problems. Fewer talk about redesigning the environment in which those problems exist in the first place. In a recent podcast, Krish Palaniappan sat down with Sarbojit, founder and CEO of Baanda, for a discussion that moved well beyond the usual startup talking points. What began as a conversation about SaaS quickly expanded into a broader reflection on how software platforms might evolve in the coming years: not as isolated apps for isolated tasks, but as connected systems built around people, context, and adaptability.

Podcast

Beyond SaaS: Building Platforms Around People, Not Just Products — on Apple and Spotify.

At the center of Sarbojit’s thinking is a simple critique of the modern software landscape. Traditional SaaS, he suggested, often forces users to navigate a maze of disconnected tools, each built for a narrow use case. For small businesses and non-technical users especially, that can create unnecessary complexity. His company, Baanda, is trying to move in a different direction. Its current product, Bazaar, is not meant to stand alone, but to serve as one part of a larger software ecosystem. In Sarbojit’s framing, Bazaar is to Baanda what a flagship product is to a larger platform company: an entry point into a more expansive vision.

Software Platform As A Service

That vision is what he calls “software platform as a service.” The phrase is intentionally broader than SaaS. Instead of giving users one specialized tool at a time, the goal is to offer an integrated digital environment where different business functions can work together behind the scenes. A boutique owner might need a storefront and payments. A handyman may care more about marketing and customer acquisition. A shipping-heavy business might primarily need logistics support. In Baanda’s ideal model, each of those users can operate within the same platform while benefiting from shared systems such as accounting, checkout, and transaction management. The software becomes less a collection of subscriptions and more an operational foundation.

Three Pillars

What makes the conversation especially interesting is that Sarbojit does not stop at product design. He organizes his longer-term thinking around three pillars:

1. Humanoid AI

2. Decentralized economy

3. Dynamic cooperation chemistry score

Humanoid AI

These are not presented as isolated features, but as foundational ideas supporting the platform itself. The first, humanoid AI, is his attempt to describe a system that understands people in a more contextual and individualized way. Rather than treating users as generic profiles inside a workflow, he imagines AI that can recognize differences in ability, motivation, background, and need. In his telling, that has implications not just for commerce, but for education, service delivery, and the broader question of how systems should adapt to the people inside them.

Decentralized economy

The second pillar, decentralized economy, reflects a challenge to conventional financial infrastructure. Sarbojit argues that today’s economic systems remain too dependent on centralized authorities and inherited assumptions about how value should move. He points to blockchain and algorithmic models as potential building blocks for a more distributed transactional system, one less reliant on traditional gatekeepers. Whether one agrees with that outlook or not, it reveals the scale of his ambition: Baanda is not merely trying to become another business software platform, but a framework that could eventually rethink how value itself is managed and exchanged.

Dynamic cooperation chemistry score

Then there is the most unusual of the three pillars: dynamic cooperation chemistry score. Sarbojit describes it almost as a contextual trust or compatibility engine. Like a credit score, it would attempt to generate a probability-based measure, but instead of assessing repayment likelihood, it would estimate whether two people or entities are likely to work well together in a specific setting. Two individuals may be a poor match for one kind of collaboration and an excellent fit for another. A system that can account for personality, timing, skill, and context could, in theory, help guide partnerships, teams, and opportunities more intelligently. It is an abstract idea, but also a revealing one: much of Sarbojit’s worldview centers on the belief that human systems fail when they flatten people into static categories.

Technology Stack

Krish’s questions then grounded the discussion in software engineering reality. What does it actually look like to build a platform with such expansive ambitions in 2026? Sarbojit’s answer was more pragmatic than philosophical. Baanda, he explained, is built primarily on the MERN stack and integrates with tools and services such as AWS, Google, Stripe, EasyPost, Twilio, and SendGrid. The architecture is modular by design, built to evolve over time rather than lock the company into a rigid technical foundation. Even the distinction between the company website and the underlying application matters here: the public-facing site acts as a billboard, while the application itself is structured as a progressive web app meant to support gradual enhancement and long-term change.

That led naturally into one of the most current questions in software: how much of modern development can AI actually take over? Sarbojit’s answer was measured. He did not dismiss AI coding tools; in fact, he credited them with dramatically increasing what a small team can build. But he also argued that there is still a meaningful difference between generating code and designing a living system. AI, in his view, is highly effective at producing fragments, snippets, and functional components. Where it still falls short is in preserving the coherence of a large architecture over time, especially when systems are distributed, interconnected, and subject to constant change. In other words, AI may be a powerful amplifier, but not yet a substitute for architectural thinking.

How AI Is Changing Hiring

The hiring discussion pushed that idea further. If AI can generate code, summarize research, and support cross-functional work, what should companies actually look for in new hires? Sarbojit argued that rigid role definitions are beginning to erode.

Formal credentials matter less, he suggested, than curiosity, problem-solving, and the capacity to respond to ambiguity. Even interviews, in that framework, should become more adaptive. A company may miss great candidates if it relies too heavily on fixed formats that reward quick responses over deeper thought.

Purpose of the Podcast

One of the strongest moments in the conversation came near the end, when Sarbojit turned the tables and asked Krish about the purpose of the podcast itself. Krish responded with a thoughtful reflection on learning in public. Too much startup storytelling, he noted, focuses on polished success narratives. What gets lost are the mistakes, uncertainties, and failed experiments that actually shape builders over time. His hope for the podcast is to make that less visible part of the journey more accessible: not just what people built, but how they thought, struggled, adjusted, and learned while building it.

That answer also serves as a fitting way to understand the larger conversation. This was not simply a founder describing his company. It was a conversation about what software might become when the goal is not just feature delivery, but system design at a human level. Sarbojit’s ideas range from practical to speculative, from current product architecture to future models of intelligence and trust. Not every vision this ambitious will unfold as imagined. But that is almost beside the point. What matters is the direction of the thinking: away from fragmented tools, toward adaptive platforms; away from static roles, toward dynamic capability; away from software as product, toward software as environment.

Summary

The podcast explores a vision for moving beyond traditional SaaS toward a broader “software platform as a service” model. Instead of forcing users to manage multiple disconnected tools for storefronts, payments, marketing, accounting, and logistics, the discussion presents the idea of a unified platform where these functions work together behind the scenes. The conversation also introduces three conceptual pillars supporting that vision: a more human-centered form of AI that adapts to individuals in context, a decentralized economic model that rethinks how value is exchanged, and a “dynamic cooperation chemistry score” designed to estimate how well people or entities might work together in different scenarios. Together, these ideas frame software not just as a collection of apps, but as an adaptive environment built around human needs and relationships.

The conversation then shifts into the practical realities of building such a platform. It covers the use of a MERN-based architecture, modular system design, and integrations with services like payments, messaging, shipping, and cloud infrastructure. A major theme is the role of AI in software development: AI tools are seen as highly useful for generating code snippets and accelerating implementation, but still limited when it comes to preserving the coherence of large, evolving systems. The podcast also examines how hiring is changing in response to these shifts, arguing that companies should increasingly value curiosity, adaptability, and context-driven problem solving over rigid job definitions or static credentials. In the end, the discussion becomes a broader reflection on how software, work, and collaboration may evolve together in an AI-shaped future.

If that shift does happen, the most important software companies of the future may not be the ones that build the most features. They may be the ones that understand people most deeply, connect systems most thoughtfully, and create the most coherent spaces for human work, exchange, and collaboration. That is the wager underneath Baanda’s vision, and it is what made this conversation worth paying attention to.

This move also has clear implications for competitors, particularly manufacturers of Windows-based machines such as HP and Microsoft. A product from Apple at this price point introduces a new level of competition, forcing other companies to reassess their offerings and pricing strategies. Beyond just affordability, the MacBook Neo appears to combine Apple’s ecosystem advantages with sufficient performance for everyday tasks, making it a compelling alternative for a wide range of users.

The device is reportedly powered by an A18 Pro chip, similar to those used in iPhones, and is designed primarily for students and light users. This includes activities like browsing, media consumption, content creation, and general productivity tasks. While it may not be intended for heavy-duty software development, it still supports tools like Xcode, meaning users can technically build apps on it. This opens the door for aspiring developers who previously found the cost of entry into the Apple ecosystem prohibitive.

Historically, one of the barriers to developing for Apple platforms has been the requirement of owning a Mac device, which often came with a high price tag. By lowering this barrier, Apple is not just selling more hardware—it is potentially growing its developer base and strengthening its ecosystem. More developers mean more apps, which in turn increases the value of Apple’s platforms, creating a reinforcing cycle of growth.

Ultimately, the MacBook Neo could prove to be more than just a new product; it may represent a strategic inflection point. Its impact is likely to extend beyond direct revenue from device sales, influencing software adoption, ecosystem expansion, and competitive dynamics across the industry. By making its ecosystem more accessible, Apple positions itself to benefit not only from increased unit sales but also from the broader, long-term value generated by new users entering its platform.

Snowpal API on AWS Marketplace

Podcast

The Strategic Role of Marketing and Communications in Modern Businesses — on Apple and Spotify.

Introduction: Building a Great Product Is Not Enough

In B2B companies, founders often begin with the belief that the hardest problem is building the product itself. For engineering-led businesses, this assumption is understandable. Reliability, scalability, security, and performance are all difficult problems. But once a product is launched, another challenge emerges: making sure the right buyers understand it, trust it, and see why it matters to their business.

That is where marketing and communications become essential. In B2B, growth rarely happens because a product simply exists. It happens because a company can clearly explain its value, consistently communicate its story, and build confidence with decision-makers over time. Communications is not separate from growth; it is part of the infrastructure that makes growth possible.

Marketing vs. Communications in a B2B Context

In a B2B company, marketing is often associated with lead generation, pipeline growth, and demand creation. Communications, however, plays a broader and more foundational role. It shapes how the company is perceived internally and externally, how its value proposition is understood, and how trust is built with customers, prospects, investors, partners, and employees.

This distinction matters because B2B buying is rarely impulsive. Buyers are evaluating risk, fit, credibility, and long-term value. Communications supports sales and marketing by giving them the messaging, positioning, and trust foundation they need to be effective. In that sense, communication is not just a support function; it is part of the architecture of the business itself.

Why Communications Matters in B2B Companies

For B2B companies, communications matters because the audience is often harder to win. Buyers are more selective, sales cycles are longer, and multiple stakeholders may be involved in a single decision. A business buyer may need to justify a purchase internally, compare alternatives, and return to your company several times before taking action.

That means your messaging must do more than attract attention. It has to reduce uncertainty. It has to explain what the product does, why it matters, and why your company is credible. It also has to remain consistent across the website, product materials, demos, sales conversations, onboarding, leadership updates, and customer-facing content. When that consistency is missing, friction appears. When it is present, the business becomes easier to understand and easier to trust.

Storytelling as a B2B Growth Tool

Storytelling is sometimes dismissed in B2B because it sounds too soft or consumer-oriented. In reality, it is one of the most practical tools a B2B company has. A good story helps a prospect understand what problem exists, why it matters, and how the company solves it. It also makes the company more memorable in markets where many offerings sound similar.

A useful B2B story is not fiction or hype. It is a structured way of connecting product capabilities to customer pain points and business outcomes. The strongest companies move from raw facts to a narrative, and from narrative to a recognizable brand. That process makes their product easier to explain, easier to remember, and easier to sell. This is especially important in software and services, where the product may be intangible and the value may not be obvious at first glance.

Content as a Trust Engine, Not Just a Traffic Engine

In B2B, content should not be viewed only as a traffic play. Its deeper role is to build familiarity and trust over repeated interactions. Buyers may encounter a company through a LinkedIn post, a founder interview, a webinar clip, a podcast appearance, a case study, or an email. Each piece of content acts as a touchpoint that helps the audience understand the company a little better.

This makes content especially valuable for B2B firms with complex offerings. A project management platform, a workflow tool, a consulting service, or an enterprise software product may all require explanation before a sale can happen. Content helps educate the market before the first sales call and reinforces confidence after the call. In that sense, content is not separate from sales; it supports the sales process by preparing the buyer to engage.

Technologies Powering B2B Marketing and Communications

Technology plays a central role in modern B2B communications because it enables companies to create, distribute, measure, and refine messaging at scale. Customer relationship management systems help teams organize leads, track buyer interactions, and personalize outreach. Marketing automation platforms make it possible to nurture prospects over time through segmented email journeys, event follow-ups, and product education sequences. Analytics tools help teams understand which messages, channels, and formats are contributing to awareness, engagement, and conversion.

AI tools are increasingly important in this stack, particularly for research, drafting, analysis, and workflow acceleration. But in B2B, technology works best when it supports strategy rather than replacing it. The tool can speed up execution, but it cannot decide what story should be told, how a category should be framed, or where credibility must be built. That still depends on judgment. For that reason, the most effective B2B companies use technology to amplify expertise, not substitute for it.

The Most Effective B2B Channels

For many B2B companies, the most effective channels are not the loudest or most viral ones. They are the channels where business buyers already spend time and where trust can be built steadily. LinkedIn is especially valuable because it is designed around professional identity, industry context, and business relevance. Facebook can also matter more than many B2B teams expect, especially for small businesses and operators making purchasing decisions. Email remains highly effective when the list is targeted, permission-based, and filled with useful content rather than noise.

This mix reflects a practical B2B reality: not every platform needs to be treated equally. Companies should focus on the places where their buyers actually pay attention and where the message can be repeated over time. A narrow but relevant audience is often far more valuable than broad reach without intent.

LinkedIn as a Core B2B Platform

Among B2B channels, LinkedIn stands out because it is well suited for thought leadership, company updates, industry commentary, and product education. It is not necessarily where the sale closes, but it is often where credibility begins. Buyers may not purchase directly from a post, but they may remember a company, follow its page, engage with its content, or respond to outreach more positively after repeated exposure.

For B2B teams, the most effective LinkedIn content often includes videos, carousels, and posts that clearly explain useful ideas. Timing and frequency matter, but not as much as substance and consistency. The goal is not simply to post often; it is to stay present with material that helps the audience understand the business and its expertise. Over time, that repeated exposure supports the longer, multi-touch nature of B2B buying.

Building a High-Quality B2B Email List

Email remains one of the most durable B2B communication channels because it gives companies direct access to an audience they own. But its value depends on list quality. A smaller opt-in list of relevant prospects is more valuable than a larger list of disinterested contacts. In B2B, the strongest email lists are built through product signups, demo requests, waitlists, webinars, downloadable resources, and cross-channel invitations from places like LinkedIn.

This matters because B2B communication is cumulative. The email list becomes a place where the company can continue educating, nurturing, and reinforcing trust over time. It is not just for promotions. It is for sustaining the conversation after the first point of contact.

Product Messaging Must Match Product Reality

One of the most important communications principles in B2B is alignment between what is promised and what the product actually delivers. If messaging overstates capability, buyers notice quickly. In software, this can be especially damaging because expectations are formed before the demo, before onboarding, and before expansion discussions.

That is why effective B2B communications must be grounded in the product itself. Teams need to understand how the product is experienced, whether the narrative matches the actual workflow, and whether customers interpret the value the same way the company intends. Good communication does not decorate the product; it clarifies it. When messaging and product experience align, the result is trust. When they diverge, the result is confusion.

Internal Communications Also Matter in B2B

B2B companies often think of communications as something customer-facing, but internal communication is just as important. Sales enablement, product roadmap updates, team alignment, all-hands meetings, and policy communication all influence how consistently the company presents itself. If internal teams are unclear about priorities, language, or direction, that confusion eventually reaches customers.

For growing B2B firms, internal communication becomes especially important because multiple functions must work together to support the buyer journey. Product, engineering, sales, customer success, and leadership all need a shared understanding of what the company stands for and how it talks about its work. Strong internal communication makes strong external communication possible.

The 50/50 Reality in B2B Growth

A hard truth for many B2B founders is that building the product is only part of the job. A substantial share of effort must go toward communicating the value of what has been built. In practice, this can mean that a surprisingly large amount of business energy needs to go into marketing, communications, and growth, not just product development.

This does not mean engineering becomes less important. It means the company must balance creation with communication. A strong product without visibility struggles to grow. A clear story without a strong product also fails. B2B success depends on doing both well enough, and doing them together.

Conclusion

For B2B companies, marketing and communications are not optional finishing layers added after the product is built. They are strategic functions that help the market understand the product, trust the company, and move toward a buying decision. The companies that perform best are often not just the ones with strong offerings, but the ones that explain those offerings clearly, repeatedly, and credibly.

In B2B, communication is what turns capability into comprehension and comprehension into trust. That is why it matters so much.