Snowpal AI + API: Build Apps Faster, Cheaper, Better

From SEO to AEO: How to Optimize Your Website for AI Agents (feat. Frank Vitetta)

Krish Palaniappan — Thu, 14 May 2026 04:55:44 GMT

A conversation between Krish Palaniappan, CEO of Snowpal, and Frank Vitetta, CEO of Orchid Box, LLM Scout, and CodeScout.

Podcast

Your Website Is Invisible to AI: Here’s How to Fix It — on Apple and Spotify.

The SEO Crisis No One Saw Coming

For decades, the rules of search engine optimization were clear: rank high on Google, drive traffic, convert visitors. That playbook is now being rewritten at speed.

According to Frank, a digital marketing expert and founder of LLM Scout, his agency is seeing average traffic drops of 30–35% year over year across clients — and some are experiencing drops as steep as 80%. The culprit isn’t a Google algorithm update. It’s the rise of AI.

“Google and LLMs — ChatGPT, Claude, and others — they tend now to reply directly to the user,” Frank explains. “So there is no reason for people to go and browse websites. For my clients, that’s a big problem.”

Combined with stricter GDPR enforcement in Europe, which requires explicit user consent before analytics fires, marketers are flying increasingly blind. But the story isn’t as bleak as those numbers suggest.

Is SEO Dead? Not Exactly — But It’s Transforming

Despite falling click-through rates, SEO remains foundational — because LLMs still rely on it.

Frank points to a striking statistic: roughly 18% of Google’s traffic today comes from LLM bots. When you ask ChatGPT or Claude a question they can’t answer from training data, they perform live Google searches to gather information. They break your prompt into multiple search queries — a process called “query fan-out” — then crawl the top results in real time to synthesize an answer.

“If you’re still number one in Google, the LLM will recommend you,” Frank says. “The user isn’t clicking the link, but the company is still being discovered.”

The shift, then, isn’t from SEO to something else. It’s from SEO to AEO — Answer Engine Optimization — a discipline focused on making your content readable, trustworthy, and accessible not just to humans, but to AI agents acting on their behalf.

Introducing the Third Web: Markdown Pages for AI Crawlers

One of the most practical strategies Frank recommends is creating a markdown (.md) version of your key web pages alongside the standard HTML version.

Here’s the problem markdown solves: when an LLM crawls your site in real time, it only processes a limited amount of content — approximately the first 100 kilobytes of a page. A typical HTML page is bloated with JavaScript calls, CSS, navigation menus, footers, image tags, third-party scripts, and other “noise” that has nothing to do with the actual content. By the time all that noise is cleared, the meaningful content may never make it into the AI’s context window.

Markdown strips all of that away. It retains only the essential structure — headings (H1, H2, H3), bold text, links, and tables — in a lightweight format that LLMs are deeply familiar with, since most of them were trained on markdown-rich datasets.

How to Implement Markdown Pages

The implementation is simpler than it sounds. For each important page, you:

Create a parallel .md file at a predictable URL (e.g., /blog/article-name.md)
Add a single directive in your HTML tag:

This tells AI crawlers that a cleaner, machine-readable version of the page exists. The HTML page continues serving human visitors and Google’s traditional crawler without any changes.

Frank’s client at elsewhen.com already has this in production. You can verify it by taking any blog post URL, removing the trailing slash, and appending .md — a stripped-down, content-only version of the article appears instantly.

An Important Caution on Content Parity

Frank flags a critical risk: the markdown version must be substantively identical to the HTML version. Search engines like Google will screenshot your HTML page and compare it to what they can scrape. If the two versions differ meaningfully, you risk a cloaking penalty — the same kind applied to sites that historically hid white text on white backgrounds to game keyword rankings.

Agent-Centric Design: Rethinking How Websites Are Built

Markdown pages address how AI crawls your content. But there’s a second, equally important challenge: how AI agents interact with your pages when they’re taking actions on a user’s behalf.

When a user instructs an agent to “find me a course provider in this space,” the agent doesn’t read your HTML. It visually “sees” your page — essentially taking a screenshot and interpreting what’s there. This is where most modern websites silently fail.

Frank describes a client whose course catalog page had 80% of its content hidden behind tabs. A human visitor instinctively clicks the tabs. An AI agent sees a screenshot, identifies only what’s visually open, and reports back to the user as if the rest doesn’t exist. Entire product lines become invisible.

“We need to have this in mind when designing,” Frank explains. “If I screenshot this page and send it to someone, would they be able to understand that there is a button here, that they need to press something to watch a video?”

Design Principles for Agent Accessibility

The shift Frank advocates isn’t a complete redesign — it’s a new lens applied to existing design decisions:

Avoid hiding content behind interactive elements. Tabs, carousels, accordions, and modals are human-friendly but agent-hostile. If a piece of content matters, make it visible without requiring a click.

Use high contrast and clear visual hierarchy. Agents interpret pages visually. Background images underneath text, low-contrast buttons, and decorative styling can obscure meaning. Black text on white backgrounds, with clear structural hierarchy, performs best.

Redesign mega menus for dual audiences. Interestingly, the mega menu — once dismissed as dated UX — is making a comeback. Frank notes that well-structured mega menus give agents fast access to a site’s most important content areas without requiring deep navigation. EY Parthenon’s site is cited as an example: services and subsections laid out clearly, accessible in one visual sweep.

Carousels are a liability. A carousel only ever shows one item at a time. An agent seeing a screenshot sees one item. Everything else on those slides, for all practical purposes, does not exist.

JSON-LD and Schema Markup: Speaking the Machine’s Language

Long before AI agents arrived, SEOs were enriching web pages with structured data using the schema.org vocabulary and JSON-LD (JavaScript Object Notation for Linked Data). Now, that practice is more valuable than ever.

Schema markup allows you to define entities — companies, products, events, people, reviews, courses, FAQs — in a standardized format that machines parse directly, without hunting through prose for the information. Instead of an AI agent trying to find your phone number or office address buried somewhere in paragraph text, you declare it explicitly:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "telephone": "+1-800-000-0000",
  "address": { ... }
}

Frank explains that a modern page might carry multiple overlapping schema types: an event, a product listing, an FAQ section, a course, and company information — all described in structured JSON alongside the visual HTML, all invisible to the reader, all immediately legible to an AI.

Google Search Console now surfaces errors in your rich metadata — missing required fields, type mismatches, formatting issues — making it easier to audit and maintain this layer of your site.

LLM.txt: The AI-Native Sitemap

Traditional XML sitemaps tell crawlers what pages exist and when they were last updated. LLM.txt — a newer convention Frank describes — takes a different approach. Rather than listing URLs, it explains how a website is structured in plain language.

An LLM.txt file might say: “This is a B2B consulting firm. Service pages live under /services. New blog content appears at /blog/[slug]. All product pages follow /products/[category]/[product-name].”

It’s less a directory and more a set of orientation instructions — the kind you might give a new employee on their first day.

The adoption of LLM.txt is still uneven. Anthropic has pushed for it; OpenAI has not committed. Frank acknowledges that in practice, most LLMs appear to rely primarily on what’s on the page itself rather than reading either sitemaps or LLM.txt. But the emerging consensus among AEO practitioners is to implement it anyway — the cost is minimal and the potential upside is real.

Citations: The New Backlinks

In traditional SEO, authority was built through backlinks — other websites linking to yours. In the AI-discovery era, the equivalent is citations: your brand name appearing on other credible platforms, even without a link.

LLMs are trained on massive corpora of online text, and sites with high human-generated authority — Reddit, LinkedIn, trusted review platforms — carry disproportionate weight.

“There was a rush on getting your name on Reddit,” Frank recalls. “People found that LLMs loved Reddit and LinkedIn because they have strong spam policies and self-moderating communities. It was seen as human opinion.”

The predictable result followed: marketers flooded those platforms with AI-generated content, platforms adapted their moderation, and the SEO lift faded. But the underlying dynamic remains: authentic presence on authoritative third-party platforms signals trustworthiness to AI systems evaluating which sources to cite.

The lesson isn’t to game Reddit. It’s to build genuine presence where humans actually discuss your industry — because that’s still where AI goes to learn what’s credible.

The Bigger Shift: From Websites to APIs and MCPs

Beneath all the tactical optimizations lies a more fundamental transformation. As Frank and Krish explore in their conversation, the future of software distribution may not be websites or apps at all — it may be APIs and Model Context Protocols (MCPs).

Platforms like Claude’s Cowork already demonstrate the pattern: rather than switching between a dozen separate applications, users interact with one AI interface that connects to all their tools via connectors. Salesforce, HubSpot, Slack — their data and functionality become accessible through a single, personalized layer.

In this world, having a beautiful website matters less than having a well-documented, accessible API. The agent doesn’t visit your homepage. It calls your endpoint.

Frank’s own roadmap reflects this: “My next step is to create an MCP server so that becomes accessible to other tools. You tell the other tools: we exist, this is how you authenticate, this is what you can do. People use our services using other services seamlessly — without even knowing they’re using us.”

Krish echoes this at Snowpal: building an MCP server so AI agents across industries can consume their APIs generically, without needing to know the specific endpoints, with industry-specific sample agents demonstrating the integration model.

AI + Snowpal API: Reduce Time to Market

The Economic Undercurrent: What AI Is Doing to Jobs

No discussion of AI optimization is complete without confronting its broader consequences. Frank speaks plainly about the UK’s youth unemployment — the highest rate for under-25s in over a decade — and links it directly to AI displacing entry-level roles.

“Junior engineers, junior lawyers — that first job, second job — I think those have completely been replaced by AI,” he says. “The problem is those people are not going to climb the ladder, which means eventually there will be no mid-level, no senior. There will be a gap.”

Both Frank and Krish describe an irony shared by many in technology: the tools that increase individual productivity also compress the on-ramps through which expertise is built. Senior developers still manage and review. But without juniors learning by doing, who becomes senior?

Frank’s advice, when pressed, circles back to something almost old-fashioned: find what you genuinely love and pursue it with adaptability as your core skill. “If you have a passion for something, you will make it happen. It won’t become a job you do for money — it becomes your identity.”

How Few People Are Actually Building With AI

Perhaps the most grounding data point in the conversation comes from a graphic Krish shares — sourced, Frank believes, from Diary of a CEO — breaking down global AI adoption:

84% of the world population has never used AI
16% use a free AI chatbot
0.3% pay for a subscription
0.04% are actively building with AI

At 8.1 billion people, that 0.04% represents roughly 3.2 million builders. For anyone steeped in the AI conversation — reading newsletters, attending podcasts, refreshing LinkedIn — that number is a useful corrective. The urgency feels total because of algorithmic echo chambers. The reality is that the overwhelming majority of the world hasn’t yet clicked “sign up.”

“I’ve been living in AI anxiety,” Frank admits. “As soon as I go to LinkedIn, everything is about AI. I’m constantly bombarded. But then that graph came along and I thought — I need to breathe.”

The Mechanics of AI Crawling and Query Fan-Out

When a user submits a prompt to an LLM like ChatGPT or Claude, the model doesn’t perform a single search — it decomposes the query into multiple targeted sub-queries, a process called query fan-out. Each sub-query hits a search engine independently, returning a set of ranked URLs. The agent then crawls those pages in real time, parsing the raw HTML to extract relevant content. Because most LLMs cap their page ingestion at roughly the first 100 kilobytes, any content buried beneath heavy JavaScript bundles, third-party script calls, and navigation boilerplate may never enter the model’s context window at all. This is why rendering order in the DOM matters: content that appears early in the HTML source has a structurally higher probability of being ingested than content loaded dynamically via JavaScript after the initial parse.

Structured Data and the JSON-LD Signal Layer

Beneath every well-optimized page lies a machine-readable signal layer built on JSON-LD and the schema.org vocabulary. Unlike prose content, which requires natural language processing to extract entities and relationships, JSON-LD declares them explicitly — a product’s price, an organization’s phone number, an event’s start time — in a standardized format that search engines and AI crawlers can parse deterministically. Modern pages often carry multiple overlapping schema types simultaneously: an Organization block in the site header, a Course or Product block in the body, an FAQPage block in the footer. Each additional schema type expands the surface area of structured facts an AI can confidently extract without inference, reducing hallucination risk and increasing the likelihood that your entity is accurately represented when an LLM synthesizes an answer citing your content.

Key Takeaways for Marketers and Builders

If you’re managing a website or building a digital product in 2025, here are the actionable priorities that emerge from this conversation:

Audit your pages for agent accessibility. Take a screenshot of each important page and ask: could an AI agent understand what’s on this page and what actions are available? If the answer involves clicking tabs or swiping carousels, you have work to do.

Add markdown versions of your highest-value content pages. Use the directive to point crawlers to a clean, noise-free version. Keep the content identical to the HTML version.

Implement or expand JSON-LD schema markup. Every entity type your pages represent — company, product, event, FAQ, course, review — should have corresponding structured data. Audit using Google Search Console’s rich results report.

Write an LLM.txt file. Explain your site’s structure in plain language. It costs almost nothing and may provide meaningful upside as LLM adoption of the standard grows.

Build for citations, not just backlinks. Authentic presence on credible third-party platforms still matters. Focus on genuine value — useful content, honest engagement — rather than volume plays that platforms will quickly detect and discount.

Start thinking in APIs. If you’re building anything new, design it to be consumed by agents, not just browsers. An MCP server or well-documented REST API may ultimately drive more distribution than a polished homepage.

FAQ: Optimizing Your Website for AI Agents

Q: Is SEO dead now that AI answers questions directly?

No — but it’s transforming. LLMs still rely on search engines to find information. Roughly 18% of Google’s traffic today comes from AI bots performing real-time searches on behalf of users. If you rank well on Google, AI is still likely to discover and cite you. The difference is that users no longer click through to your site — the AI summarizes the answer for them. SEO remains the foundation; Answer Engine Optimization (AEO) is the layer you now need to build on top of it.

Q: What is Answer Engine Optimization (AEO)?

AEO is the practice of optimizing your website so that AI systems — ChatGPT, Claude, Gemini, and the agents they power — can find, understand, and accurately represent your content. Where traditional SEO focused on ranking signals for human searchers, AEO focuses on machine readability, structured data, agent accessibility, and authoritative citations across the web.

Q: How much traffic are websites actually losing to AI?

On average, sites are seeing traffic drops of 30–35% year over year. Some are experiencing drops as high as 80%, particularly in Europe where GDPR consent requirements have further reduced trackable traffic. The cause isn’t purely AI — privacy regulations are compounding the problem — but AI-generated answers replacing click-throughs is the dominant factor.

Q: What is a markdown page and why do I need one?

A markdown (.md) page is a stripped-down, plain-text version of your web page that contains only the essential content — headings, body text, links, and tables — with none of the HTML noise (JavaScript, CSS, navigation menus, image tags, footers). LLMs were largely trained on markdown-formatted data, so they parse it faster and more accurately. Creating a markdown version of your key pages gives AI crawlers a clean, high-signal file to ingest instead of fighting through a bloated HTML document.

Q: Will having a markdown page hurt my Google rankings?

Not if the content is identical to your HTML page. The critical rule is content parity: the markdown version must reflect the same information as the HTML version. If the two differ meaningfully, search engines may flag it as cloaking — a tactic historically used to show different content to crawlers than to users — and penalize your site. Keep them in sync and you’re safe.

Q: How do I tell AI crawlers that a markdown version of my page exists?

Add a single line to your HTML :

This directive signals to AI crawlers that a machine-readable alternative is available. Your HTML page continues to serve human visitors and traditional search bots without any changes.

Q: How much of my page does an AI actually read?

Most LLMs cap page ingestion at around the first 100 kilobytes of content. On a typical HTML page loaded with scripts, stylesheets, and third-party calls, the actual article content can sit well past that cutoff. A markdown page resolves this by putting only the content — nothing else — in a file that’s almost always well under that limit.

Q: What is agent-centric design?

Agent-centric design means building your website so that an AI agent — which perceives pages visually, like a screenshot — can understand what’s on the page and what actions are available, without needing to click, swipe, or hover. It’s the AI equivalent of accessibility design for humans with disabilities.

Q: What website elements are most dangerous for AI agents?

The biggest offenders are: tabbed content (agents only see what’s open), carousels (agents see one slide, everything else is invisible), content loaded by JavaScript after page render (agents may not trigger it), and buttons or CTAs that rely on animation or hover states to be understood. If a screenshot of your page wouldn’t make the content and actions obvious to a stranger, it won’t be obvious to an agent either.

Q: Do I need to completely redesign my website?

Not necessarily. The goal is to apply a new lens to existing design decisions — asking “would an agent understand this from a screenshot?” at each step. In many cases, the changes are incremental: making tabs visible by default, ensuring buttons are clearly labeled, avoiding background images underneath critical text. A full redesign is only warranted if the site’s structure is fundamentally agent-hostile.

Q: What is JSON-LD and why does it matter for AI?

JSON-LD (JavaScript Object Notation for Linked Data) is a standardized format for declaring structured facts about a page — your company name, phone number, product price, event date, FAQ answers — in a way machines can parse directly without inference. Rather than an AI trying to extract your phone number from somewhere in paragraph text, you declare it explicitly in a JSON block. This reduces hallucination risk and ensures AI accurately represents your entity.

Q: Which schema types should I prioritize?

Start with the types that match your page content: Organization for company pages, Product for product pages, Course for educational content, Event for events, FAQPage for FAQ sections, and Review or AggregateRating for review content. A single page can carry multiple schema types simultaneously. Use Google Search Console’s rich results report to identify errors and missing required fields.

Q: What is LLM.txt?

LLM.txt is a plain-language file you place at the root of your site (e.g., yoursite.com/llm.txt) that explains how your website is structured — not by listing every URL, but by describing where different types of content live. Think of it as orientation instructions for an AI: “Service pages are under /services. Blog posts follow /blog/[slug]. Product pages are at /products/[category]/[name].”

Q: Is LLM.txt widely supported yet?

Not universally. Anthropic has pushed for its adoption; OpenAI has not committed. In practice, most LLMs currently appear to rely primarily on on-page content rather than reading LLM.txt. However, implementation costs almost nothing, and adoption is expected to grow. It’s worth adding now.

Q: Should I still maintain my XML sitemap?

Yes. XML sitemaps remain important for traditional search engine crawlers and indirectly benefit AI discovery through Google rankings. LLM.txt is a complement, not a replacement — the two serve different audiences and purposes.

Q: What replaces backlinks in the AI era?

Citations — your brand name appearing on credible third-party platforms, with or without a link. LLMs are trained on vast corpora that weight authoritative sources heavily. If your company or product is mentioned genuinely and frequently on trusted platforms (industry publications, community forums, professional networks), AI systems are more likely to surface and recommend you.

Q: Is it worth trying to get mentions on Reddit or LinkedIn?

Authentic mentions on these platforms still carry value — both rank well on Google and feed into LLM training data. However, both platforms actively moderate AI-generated spam, and LLMs themselves are increasingly able to detect low-quality, synthetic content. The strategy that works is genuine participation: useful content, honest answers, real engagement. Volume plays and AI-written posts are quickly discounted.

Q: Do websites even matter if the future is AI agents?

In the short to medium term, yes — websites remain the primary surface AI agents crawl for information. But the longer-term trajectory points toward APIs and Model Context Protocols (MCPs) as the primary distribution layer. If your product or service can be consumed directly by an agent via API, you bypass the website layer entirely. Building both — an optimized web presence and an accessible API — is the safest path for the next few years.

Q: What is an MCP and why should I care?

A Model Context Protocol (MCP) is a standardized way for AI agents to authenticate with and call external services. Rather than an agent browsing your website to find information, it calls your MCP endpoint directly: “What services do you offer? What’s the pricing? Book this.” Companies that expose MCP servers become natively accessible to any AI platform that supports the protocol — without the user ever visiting a website.

Q: How urgent is all of this?

More urgent than most businesses realize. Traffic declines are already happening — 30–80% drops are live, not theoretical. At the same time, only 0.04% of the world’s population is actively building with AI right now. Early movers who optimize for AI discoverability have a significant window before the rest of the market catches up. The companies that act in the next 12–18 months will be the ones AI recommends by default.

Frank Vitetta, is the founder and CEO of Orchid Box, LLM Scout, and CodeScout. LLM Scout monitors how brands are cited and represented across major AI platforms. Krish Palaniappan is the CEO of Snowpal, an API platform helping businesses build software faster.

Macroeconomic impacts of AI adoption (feat. Dr. Kelly Monahan)

Krish Palaniappan — Wed, 06 May 2026 22:37:03 GMT

If you’ve been losing sleep wondering whether your job will survive the AI revolution, congratulations: you’re already doing more strategic thinking than most C-suites. That, in essence, is the bracing message Dr. Kelly Monahan brought to a recent Snowpal podcast conversation with founder Krish Palaniappan. Kelly, who studies the future of work and has done time in the research trenches at Deloitte, Accenture, and Meta, has the rare distinction of having started her HR career by laying people off because of robotic process automation. It is, as career origin stories go, the equivalent of a firefighter whose first day on the job involves lighting a match. Twenty years later, the technology is more polite about it (chatbots are nothing if not cheerful), but the underlying question is the same: what is a human worker actually for?

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.

Governing Intelligence: How AI Is Reshaping Public Sector Software (feat. Andrew Stockwell)

Krish Palaniappan — Wed, 06 May 2026 03:41:05 GMT

Deploying AI in regulated, mission-critical environments is a challenge of a different order from shipping a consumer app. Where most AI practitioners enjoy the freedom to iterate quickly and fail cheaply, public sector software vendors must satisfy procurement regulations, legal liability constraints, and a profound obligation to public trust. Andrew Stockwell, VP of AI at Euna Solutions — a leading provider of cloud-based software for government bodies across the United States and Canada — has spent years operating at this intersection. In a wide-ranging conversation on the Snowpal Podcast, Stockwell walked through the technical decisions, architectural patterns, and organizational strategies his team uses to ship production-quality AI responsibly in one of the world’s most demanding verticals.

AI + Snowpal API: Reduce Time to Market

Sections

Augmentation over automation — why human-in-the-loop is a legal necessity, not timidity
LLM Ops in practice — how Arise, test sets, and iterative prompt tuning enforce reliability
Base LLMs, RAG, and differentiation — where the moat actually lives (and how it evolves)
The AI gateway — multi-tenancy, PII removal, prompt injection guards, and model flexibility
Token economics and ROI — the 3× budget overrun and how departmental accountability replaced centralised approval
SDLC transformation — halved time-to-merge, citizen developers, and the guardrail standardization challenge
The SaaS landscape — why trust and compliance posture compound into a durable moat
Context windows and the horizon — what becomes possible as context limits expand

Podcast

Trust the Guardrails: Building AI That Governments Can Actually Use — on Apple and Spotify.

1. Augmentation Over Automation: The Public Sector Constraint

The starting point for any AI deployment at EUNA Solutions is a deliberate philosophical choice: keep a human in the loop. This is not timidity — it is a response to the legal and regulatory realities of government procurement, grants, and budget management.

“There’s a strong bias for augmentation instead of automation... It’s about trust, explainability and transparency. We cannot roll out any agentic solution that we have not tested thoroughly.”

Stockwell’s concrete example — Euna Solutions’ AI solicitation agent — illustrates the principle sharply. The agent analyses Request for Proposal (RFP) documents and suggests categories a procurement officer may have overlooked. For a fire engine RFP, the system might prompt an official to specify hose diameter or wheel size. But it stops there deliberately.

“We cannot say to them the hose diameter needs to be X or Y, because then we kind of hold liable.”

The boundary between recommendation and prescription is not a product design preference; it is a legal firewall. Every guardrail, every observability hook, and every evaluation run exists to enforce that line in production, not just in staging.

2. LLM Ops in Practice: Building Confidence Before Go-Live

With liability stakes this high, Euna Solutions treats LLM observability as a first-class engineering discipline, not an afterthought. The team uses Arise — an LLM ops and observability platform — alongside alternatives such as LangSmith and LangFuse, to evaluate agents outside production before release.

“We have the system prompt, we have the agent, and then we run a standardised test set through Arise and we have an expected result that we want. And we have the actual output that was outputted from the LLM. And then we were able to see the difference between the two, adjust the system prompt and rerun those evaluations again to make sure we’re getting the level of accuracy that we want.”

The same observability loop runs in production. Drift in model output — inevitable as underlying models are updated by providers — is caught early and corrected by updating system or guardrail prompts before customers are affected.

The Guardrail Feedback Loop

Guardrails at Euna Solutions are product-specific rather than generic. For each feature, product managers and engineers define what the model must not output. The guardrail layer intercepts every agent response and re-prompts the model if the response violates a rule — iterating until the output is compliant before it is surfaced to the user.

“The guardrail reviews it. If it’s not [acceptable], it goes back to the agent and it keeps iterating until the response gets back. And then it’s populated in the front end for the customer to see.”

This architecture means that test coverage at the system-prompt level becomes a form of regression testing. QA engineers own the evaluation suites; software engineers own the prompts. The distinction matters because evaluation quality is ultimately a domain knowledge problem, not just a technical one.

3. Base LLMs, RAG, and the Question of Differentiation

A natural question arises: if the solicitation agent is powered by a base LLM with no proprietary fine-tuning, what stops a competitor from replicating it? Stockwell’s answer is pragmatic and instructive for anyone building in the LLM application layer.

“These large language models are trained on billions of parameters of data. So they have all those public RFPs that have been published in the past in them... The system prompt is probably the most important in this. That is a very, very long prompt, a lot of tokens where we give it examples of how we want it to output. We give it the wording that we want it to use. We give it different scenarios.”

The moat, in the near term, is prompt engineering depth, evaluation infrastructure, and the guardrail layer — not proprietary model weights. Over time, Stockwell anticipates a migration toward fine-tuned models or Retrieval-Augmented Generation (RAG) pipelines seeded with the company’s accumulated private data.

RAG as a Shared Capability

RAG is not just a customer-facing feature at Euna Solutions — it is an internal developer productivity tool. The team has built reusable RAG patterns that engineering teams can adopt by pointing their data at a managed vector store (currently AWS OpenSearch) and calling through the AI gateway.

“If you want a RAG agent, it’s a pretty easy thing to deploy, here’s the pattern. All you have to do is shift your data into this vector store, call it through the AI gateway, choose a large language model. Here’s Arise that you can use for testing. And that’s kind of enabled them.”

One illustrative internal application is developer tooling built on top of MCP (Model Context Protocol) servers, which give AI agents contextual knowledge about SharePoint, Salesforce, or role-based access control systems — reducing the friction of context-gathering in an engineering session.

4. The AI Gateway: Multi-Tenancy at the LLM Layer

Euna Solutions serves multiple government entities, each with their own data isolation requirements. The core architectural solution is a centralised AI gateway through which every LLM API call flows, regardless of which product line triggers it.

“Every single API call to a large language model goes to that AI gateway. And then we split the gateway by the different products. So we have like a procurement entry point, the grants entry point, a budget entry point broken up by the products. And we were able to see which customers are calling the model, what their token spend, what their limit is.”

Beyond multi-tenancy and billing visibility, the gateway serves as a unified enforcement point for cross-cutting concerns. Toxic language filtering, PII removal, SQL injection prevention, and prompt injection guardrails all live at this layer — applied consistently across every product without requiring each engineering team to re-implement them.

Model Flexibility and Cost Optimization

The gateway also enables provider-agnostic model selection. Engineering teams can evaluate expensive frontier models against cheaper, lightweight alternatives using the same evaluation harness and choose based on accuracy data rather than intuition.

“We can take an expensive large language model and we can take something like Gemini Flash and test it and see what the output is. And if they both give me the same accuracy, I’m going to take the cheaper one.”

In customer-facing contexts, this flexibility could eventually become a product feature — allowing government agencies to choose a model tier based on their accuracy requirements and budget, with pricing attached to that choice.

5. Token Economics and the ROI Question

Enabling Claude across the organization at Euna Solutions produced an immediate and instructive result: token spend ran to roughly three times the projected budget. The experience offers a candid case study in enterprise AI governance.

“We enabled Claude and we thought our budget would be X and it’s like three times X because of the usage... We kind of narrow it in and we say, hey, you spent $5,000 on X this month. What did you use it for? Log it in the AI innovation hub and what’s the return on investment?”

Stockwell’s response was to build an AI Innovation Hub — an internal tool where employees log their AI projects, enabling leadership to tie token spend to concrete outcomes. The shift in governance model is noteworthy: rather than centralised approval for every use of AI, departmental leaders are accountable for demonstrating ROI within their own teams.

“I should not be approving your token usage if you’re in finance or if you’re in HR... it should be the leaders in those areas understanding what their employees are using AI for and making sure that they’re using it in a way that we are getting a positive ROI from it.”

One employee, for example, completed a documentation project in four months that would have taken twelve — a result that justified elevated token consumption. The AI enablement team’s role is not cost policing but process re-engineering: helping teams understand whether an AI automation is truly the right solution, or whether the underlying process should be redesigned first.

“Instead of just, ‘should we automate this?’, it’s like, ‘can we take a step back and let’s look at the entire process to see if this is really an AI automation, is it something that Claude should be doing, is it a software engineering process?’”

6. SDLC Transformation: Speed, Quality, and the Guardrail Gap

Euna Solutions has a dedicated team focused solely on SDLC transformation through AI. The headline metric is time-to-merge-request, which has dropped by approximately half as developer adoption of AI tooling has increased.

“It’s still two weeks [sprints], but we’re able to get through a lot more in those two weeks.”

Early adopters within engineering teams have begun building their own agent-based review pipelines — ad hoc solutions to code quality and risk concerns that arise naturally as AI-generated code enters production codebases. The challenge for the AI platform team is standardizing these patterns so their benefits are available to all engineers, not just those who built them.

“As our developers start using it, they start building up their own agents within the different solutions to mitigate the risks that they’re seeing — they’ll have a review agent, they’ll have this agent. And now what we kind of have to do is figure out how do we standardise that so that all developers have access to these different things.”

Claude Code has been central to this internal transformation. Non-technical staff in HR, marketing, legal, and finance are now building their own internal applications — a dynamic that is surfacing new questions about production readiness checklists, SDLC governance for citizen-developed apps, and how to enforce coding standards outside traditional engineering pipelines.

7. The SaaS Landscape: Threats, Opportunities, and the Adoption Curve

The conversation broadened to the macro question of what AI means for SaaS companies as a category. Stockwell’s view is nuanced: the threat is real, but the response is within reach of any company willing to move quickly and invest in AI capability.

“You can go get a Replit account or Lovable and vibe code something very, very quickly. Governments move in this space pretty slowly, and there’s definitely a trust component to this. So we’ve kind of built over years all the guardrails, not just from an AI perspective, but from a data and infrastructure perspective.”

The compound moat — compliance posture, data trust, customer relationships, and now AI platform depth — is harder to replicate than any individual feature. The risk is not that AI replaces Euna Solutions outright; it is that a nimbler competitor replicates enough functionality fast enough to win new contracts.

“If you kind of have a vision — instead of pushing out five product features a year, you can maybe push out ten because you’re using AI and you’re using more and more tokens to produce things.”

Stockwell’s broader framing of the adoption curve is a useful corrective to the hype cycle. The majority of potential users have not yet meaningfully engaged with AI tooling. Teams and organizations that move quickly across that curve — in Stockwell’s words, “as quickly as possible” — are building a lead that will compound as the curve steepens.

8. Looking Ahead: Context Windows, Vibe Coding, and the Horizon

Two technical constraints define the current ceiling of AI-assisted software development in Stockwell’s view: context window size and the maturity of evaluation infrastructure. Both are moving.

“What’s stopping a company right now from taking their current software application and giving it to an AI agent and saying, ‘take this and redo X, Y, and Z with these features and deploy it’ is context. The context window is too small. It cannot take all the tokens into account of your entire codebase. But if I have to look about this — maybe a year, maybe two years from now, maybe even sooner — that’s not going to be an issue.”

The implication is that organizations building strong AI posture now are positioning themselves for a qualitatively different capability in the near term. The teams and companies that have invested in observability, guardrails, prompt engineering depth, and developer education will be able to absorb larger context windows and more autonomous agents without starting from scratch on governance.

His advice to teams navigating the current pace of change is to resist the temptation to over-engineer.

“People try and sometimes overcomplicate things when you can do a very small pilot project. It’s very easy to build an agentic pattern and it’s very easy to productionize it once you have the capabilities — your LLM ops, your guardrails. And there’s a lot of value that we can already get to our customer just by embedding a basic LLM powered by an agentic solution.”

Technologies

At Euna Solutions, every LLM API call — whether targeting Claude, Gemini Flash, or any other provider — is routed through a centralized AI gateway that enforces rate limiting, token metering, PII redaction, toxic language filtering, and prompt injection guardrails before a single token reaches a customer-facing surface. Atop that gateway sits a stack of reusable agentic patterns: RAG pipelines backed by AWS OpenSearch vector stores, Lambda functions for serverless orchestration, and MCP (Model Context Protocol) servers that give agents contextual awareness of enterprise systems including SharePoint, Salesforce, and role-based access control environments. Each pattern is observable end-to-end through Arise, an LLM ops platform analogous to LangSmith and LangFuse, which runs standardized evaluation sets against expected outputs both in pre-production and live environments — enabling the team to detect prompt drift, adjust system prompts or guardrail prompts, and rerun evals before any degradation surfaces to users. The guardrail layer itself operates as a feedback loop: agent responses are intercepted, evaluated against product-specific constraint rules, and re-submitted to the model iteratively until compliant output is produced, at which point it is passed to the front end.

On the developer productivity side, Euna Solutions has embedded Claude and Claude Code across engineering, HR, marketing, legal, and finance, producing a measurable 50% reduction in time-to-merge-request without shortening two-week sprints — the same cycles now yield significantly higher throughput. Engineers across product lines, spanning AWS, Azure, and GCP infrastructure inherited through acquisition, are building bespoke dev-side MCP servers and autonomous review agents to validate AI-generated code against production readiness checklists, effectively creating team-local SDLC guardrails that the AI platform team is now working to standardize organization-wide. Model selection is treated as an empirical rather than intuitive decision: the AI gateway enables side-by-side evaluation of frontier models against lightweight alternatives like Gemini Flash, with accuracy benchmarked against the same Arise test sets used in production monitoring, so cost optimization is grounded in observed performance deltas rather than vendor claims. Fine-tuning and expanded RAG coverage — augmenting base LLMs already trained on billions of public parameters including historical RFP corpora — remain the planned evolution path as private data assets mature and context window constraints, currently the binding limit on whole-codebase agentic refactoring, continue to expand.

Conclusion

The technical story that emerges from Andrew Stockwell’s experience at Euna Solutions is less about any single model or framework and more about infrastructure discipline. The companies and teams succeeding with AI in regulated, high-stakes environments are not doing so because they have access to better models — they are doing so because they have invested in the layers that make models trustworthy: rigorous evaluation pipelines, purpose-built guardrails, centralised observability, and a culture of measured experimentation over speculative automation.

As Stockwell put it in his closing remarks:

“Don’t look at it from a negative point of view. Look at it from a positive point of view and just have the right vision and strategy to execute on it. Anyone can do anything now. I can take anyone who’s never coded and they can vibe code an app or an idea. So there’s so many opportunities.”

The technical foundations Euna Solutions has built — an AI gateway, reusable agentic patterns, LLM observability, and a governed AI innovation hub — are a blueprint for any software organization trying to ship AI responsibly at scale. The tools are largely available. The discipline is the differentiator.

About the Guest

Andrew Stockwell is VP of AI at Euna Solutions, a cloud-based software provider for public sector organizations in the United States and Canada. His background spans actuarial economics, data science, and a Master’s degree in Computer Science. He has led AI platform, enablement, and LLM ops initiatives across multiple organizations, with a focus on responsible deployment of generative AI in regulated environments.

About the Snowpal Podcast

The Snowpal Podcast explores the intersection of technology, software architecture, and entrepreneurship. Episodes feature practitioners sharing hands-on experience building and deploying software at scale. Hosted by Krish Palaniappan, founder of Snowpal.

From Wall Street to Her Street: How to Close the Financial Confidence Gap (feat. Jessica Perrone)

Krish Palaniappan — Wed, 29 Apr 2026 22:32:52 GMT

Jessica Perrone, founder of Her Financial IQ, shares insights on financial education for women, addressing unique challenges, investment strategies, and the importance of financial literacy. Discover how tailored education can empower women and transform financial decision-making.

What happens when a former Wall Street fintech co-founder decides to stop building products for institutions and start building them for people — specifically, for women who’ve been told, in one way or another, that finance just isn’t for them?

You get: Her Financial IQ.

I recently had the pleasure of sitting down with Jessica Perrone, founder of HerFinIQ.com, for a wide-ranging conversation on financial literacy, investing anxiety, the role of culture in money habits, and where AI fits into all of it. It was one of those conversations that was genuinely hard to cut short — and I promised Jessica we’d do a follow-up to go even deeper.

Here’s a recap of what we covered.

AI + Snowpal API: Reduce Time to Market

Podcast

Making Finance Less Scary — on Apple and Spotify.

Why Women? Why Now?

The first thing I asked Jessica was the obvious question: why focus specifically on women when financial illiteracy affects everyone?

Her answer was thoughtful. She runs a co-ed platform called FinIQ.edu too — because the topics of finance are the same for everyone. But the way those topics land is often very different.

“Women have only had financial rights since the 1970s,” Jessica pointed out. “We don’t think about how recently women were given the right to own a credit card without the cosigning of their husband or their dad.”

That history, she argues, doesn’t just disappear. It gets passed down — in the form of anxiety, avoidance, and silence. When women are in mixed-gender rooms discussing money, they tend to go quiet. They defer. But in a room full of women, something shifts. It becomes more like a coffee talk than a lecture, and real questions get asked.

That’s the environment Jessica has spent six years creating.

Two Real-Life Examples That Tell the Story

I shared two Instagram videos I’d come across that stuck with me. In one, a young woman in her mid-20s had financed a Tesla for $94,000 — $1,000 a month for 90 months, plus a $4,000 down payment — on a car likely worth around $60,000. In another, a woman going through a divorce realized she had no idea what her family’s finances looked like because her husband had handled everything.

Jessica didn’t flinch. “These are two very real situations that I see frequently,” she said.

The root cause? No one’s having the money conversation at home. Nobody’s teaching the ratios — what percentage of your income should go to housing, to a car payment. “Loan officers and car salespeople are going to push you to think you can afford more than you really can,” she said. “Educating yourself on your budget and your credit score is so important.”

It’s not just a women’s issue, either. As Jessica put it — financial blind spots show up across genders. What matters is that someone starts talking about it.

Investing 101 (Before You Even Think About Stocks)

We spent a good chunk of our time on investing, and Jessica made a point that I think gets overlooked too often: you can’t talk about stocks until you talk about how to invest.

“Before you understand what a P/E ratio is, you have to understand what a stock is,” she said.

Her own story reinforced this. When she first had money to invest, she dove into self-directed trading — convinced she could learn by doing. It didn’t go well. She didn’t understand how stocks move with the economy, the difference between safer large-cap names and riskier plays like Bitcoin, or what kinds of accounts to use for what kinds of goals.

“If you want to buy a car next year, you don’t want your money in the markets,” she explained. “You want it in more liquid accounts — maybe a high-yield savings account.”

Her courses now start there: the buckets, the time horizon, the type of account, the risk level. Then, once those foundations are in place, you can start thinking about individual investments.

Diversification Is More Than Just “Don’t Put All Your Eggs in One Basket”

I pushed back a bit on the idea of diversification — citing Peter Lynch’s point that you can over-diversify to the point where your returns get diluted. Jessica’s response clarified something I found genuinely useful.

She’s not just talking about diversifying assets. She’s talking about diversifying risk levels.

“I have my self-directed account, which is more risky. I have my robo-advisor account, which is managed and in ETFs — less risky. And then outside the markets, I have real estate and cash.”

The idea is that you benchmark each account against something like the S&P 500. If your self-directed portfolio isn’t beating — or at least keeping pace with — the index, that’s information. If your robo-advisor isn’t protecting you on the downside, that’s information too. Multiple accounts give you data to work with, not just hope.

“That benchmarking allows me to not second-guess myself,” she said. “And to be more confident as a self-directed investor.”

Risk Tolerance Isn’t Fixed — It Grows With Education

I used my wife and myself as an example here. She’s conservative — ETFs, metals, savings accounts. I’m on the other end of the spectrum (I may or may not have had money on Meta going into earnings that afternoon). How do two people learn from the same curriculum and apply it so differently?

Jessica’s answer surprised me: “Your wife, after taking my courses, will have a risk tolerance that’s closer to yours.”

The point isn’t that everyone should become an aggressive investor. It’s that most people’s risk tolerance is artificially low — not because of their actual personality, but because of a lack of understanding. Once you understand how different assets work, what your time horizon is, and how to structure accounts accordingly, you can make choices that actually fit you. Her courses include real risk tolerance questionnaires that financial advisors use, and map those results to actual asset strategies.

“There’s no right or wrong,” she said. “It’s just about doing it the safest way that will give you the most growth for your risk tolerance.”

Culture, Community, and the Village

I asked Jessica about something I’ve observed firsthand: how much of financial behavior is cultural, not just educational? Growing up in India, I watched women in my family invest in gold not because they’d studied asset allocation, but because that’s what their mothers did.

Jessica’s answer was one of my favorites from the whole conversation.

“Women go into their communities and they teach their daughters, their husbands, their sons, their sisters, their brothers, their mothers, their fathers, their cousins, their neighbors. And then they lift up the whole community.”

She shared the example of working with refugees from Nepal who had never interacted with a formal financial system — not a bank account, not a budget, nothing. Education, she said, has to meet people where they are. That’s why her curriculum spans everything from basic banking and budgeting all the way through advanced investment strategies.

The App (and the Vision)

Here’s something I’ll call out specifically because it came up almost serendipitously in our conversation: Jessica is building an app.

When I floated the idea of a tool that could learn your risk profile from your behavior and allocate money algorithmically — essentially a pocket financial advisor — Jessica basically said: that’s what I’m building.

“I want to start with individuals’ finances, help them figure out where their buckets go, and then once they have their buckets and their budget, become an allocator,” she said. “I want to democratize allocation.”

The dream is an ecosystem where users can manage their personal finances, understand their risk tolerance, and then allocate to financial products — 529s, 401ks, investment accounts — with minimal friction, guided by their actual profile.

We heard it here first.

Final Thoughts

What struck me most about Jessica is that she talks about finance the way a good coach talks about their sport — with genuine excitement, no condescension, and a real belief that everyone can learn. Not everyone needs to trade individual stocks. But everyone deserves to understand their money, and everyone deserves to feel confident walking into a conversation with a financial advisor, a loan officer, or even a car dealership.

If you’re someone who gets anxious when the topic of money comes up — or if you know someone who is — check out HerFinIQ.com. There’s also a co-ed version of the curriculum at FinIQ.edu for anyone who wants to learn alongside a partner.

And yes, Jessica — I’ll tell my wife about the courses.

`Summary`

At Snowpal, we’ve been building a FinTech API because we kept seeing the same gap — people making financial decisions without the right tools, information, or infrastructure underneath them. Whether it’s a first-time investor who doesn’t know the difference between a brokerage account and a Roth IRA, or a platform trying to offer personalized financial guidance at scale, the plumbing just isn’t there. Our API is designed to change that: giving developers and product teams the building blocks to embed intelligent, personalized financial functionality directly into their apps — without starting from scratch.

That’s exactly why a conversation like the one we had with Jessica Perrone of HerFinIQ resonates so deeply with us. Jessica’s vision — an ecosystem that meets users where they are, understands their risk tolerance, and allocates their money intelligently across the right accounts — is precisely the kind of product our API is built to power. Financial education creates the awareness; the right technology closes the loop. Together, they turn knowledge into action. That’s the future we’re building toward at Snowpal, and we think it’s closer than most people realize.

Jessica Perrone is the founder of Her Financial IQ, a financial education platform for women. She offers online courses, corporate workshops, and group coaching programs. Find her at HerFinIQ.com or on LinkedIn.

Building Through Uncertainty: A Conversation on Resilience, AI, and the Future of Software (feat. Asia Solnyshkina)

Krish Palaniappan — Mon, 27 Apr 2026 22:37:52 GMT

A conversation between Krish Palaniappan and Asia Solnyshkina, founder of ProSense Digital — exploring what it means to build software in an era when the rules are being rewritten in real time.

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.

Inside the Rise of AI-Native Companies (feat. Sid Bharath)

Krish Palaniappan — Tue, 21 Apr 2026 00:10:09 GMT

In this episode, Sid Bharath, founder of ReFound AI, shares insights on how companies can leverage AI to become AI native through audits, creating AI operating models, and deploying AI agents. Discover practical frameworks and real-world examples of automating business processes with AI.

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.

AIOps and Modern IT Operations: Simplifying Multi-Cloud Operations (feat. Michael Nappi)

Krish Palaniappan — Wed, 08 Apr 2026 23:31:44 GMT

In this episode, Michael Nappi, Chief Product and Engineering Officer at ScienceLogic, shares insights into AI Ops, its role in modern IT management, and how it helps large enterprises and MSPs streamline their infrastructure monitoring and management. Discover how AI-driven automation and observability are transforming IT operations.

AI + Snowpal API: Reduce Time to Market

Podcast

AIOps: Turning Data into Action — on Apple and Spotify.

The AIOps Pipeline Diagram

Raw telemetry from across a hybrid IT estate flows into a unified data lake, where AI reasons over it to surface only what matters — routing each insight to either a human engineer or an autonomous remediation agent.

Q & A with Michael Nappi

1. What is AIOps and how does it differ from traditional IT operations?

AIOps extends traditional IT operations by applying AI/ML techniques to large volumes of telemetry data (metrics, logs, events, traces) generated across complex IT environments. While traditional IT ops relies on rule-based monitoring and manual intervention, AIOps enables automated correlation, noise reduction, anomaly detection, and actionable insights, helping teams understand system behavior and respond faster.

2. What core problem does IT operations aim to solve?

IT operations ensures that an organization’s compute, storage, and networking infrastructure runs reliably, efficiently, and continuously delivers services to the business. This includes maintaining uptime, performance, and availability while minimizing disruptions.

3. Who are the primary customers of AIOps platforms like ScienceLogic?

The primary customers are large enterprises, global 2000 organizations, government agencies (including DoD and civilian sectors), and MSPs. These customers typically operate large-scale, hybrid, and distributed IT environments requiring centralized visibility and control.

4. What role do MSPs play in this ecosystem?

MSPs manage IT infrastructure on behalf of other businesses, providing services like monitoring, incident detection, and remediation. They abstract operational complexity for their clients and are accountable for maintaining service availability and performance.

5. What value does ScienceLogic provide to MSPs and enterprises?

ScienceLogic provides a unified observability and operations platform that discovers infrastructure, aggregates telemetry, correlates signals, identifies issues, and enables both guided and automated remediation, effectively replacing multiple fragmented tools with a single system.

6. How does infrastructure discovery work in such platforms?

The platform detects all assets within an IT environment (anything with an IP address), including servers, network devices, applications, and services, using protocols like SNMP, SSH, APIs, and others. This creates a comprehensive, real-time inventory of the IT estate.

7. What are collectors and why are they used?

Collectors are lightweight Linux-based agents deployed within a customer’s environment that gather telemetry data locally and forward it to the central platform. They act as edge caches, improve resiliency, support secure communication behind firewalls, and enable operation in restricted or air-gapped environments.

8. Why not collect all data directly from the cloud without collectors?

Collectors provide architectural benefits such as reduced latency, improved reliability via store-and-forward mechanisms, compliance with security constraints (e.g., firewalls, air-gapped systems), and efficient data filtering before transmission, which is especially important in sensitive or distributed environments.

9. What types of data are collected and analyzed?

The platform ingests metrics, logs, events, and traces from infrastructure and applications. This telemetry may originate from cloud services (e.g., AWS CloudTrail), APIs, or system-level monitoring and is normalized and correlated for analysis.

10. How does the platform handle noisy or high-volume data?

It uses filtering, sampling, and intelligent ingestion strategies to avoid overwhelming the system with unnecessary data, focusing instead on meaningful signals that contribute to actionable insights.

11. Is the platform cloud-agnostic and how does it support multi-cloud environments?

Yes, it is fully cloud-agnostic, capable of monitoring workloads across AWS, Azure, GCP, on-prem systems, and virtualized environments, providing a unified “single pane of glass” view across all environments.

12. How is the platform deployed and hosted?

It can be deployed on-premises, hosted by ScienceLogic as a SaaS offering, or deployed within a customer’s or MSP’s cloud environment. The architecture is flexible to support various operational and compliance needs.

13. How does onboarding work for MSPs and their customers?

ScienceLogic provisions and configures the platform for MSPs in a SaaS environment. MSPs then onboard their customers into a multi-tenant system by deploying collectors, configuring integrations, and assigning user roles.

14. How does the platform model services instead of just infrastructure?

It maps underlying infrastructure components (servers, databases, APIs, etc.) to business services, enabling visibility into service health, performance, and risk. This allows teams to understand not just system status but business impact.

15. How does AIOps enable proactive rather than reactive operations?

By analyzing trends and patterns in telemetry data, the platform can detect early warning signs of degradation, predict potential failures, and alert teams before issues impact services, enabling proactive remediation instead of reactive firefighting.

The QA Revolution: How AI Is Rewriting the Rules of Software Quality (feat. Tanvi Mittal)

Krish Palaniappan — Tue, 07 Apr 2026 02:16:50 GMT

There’s a quiet crisis unfolding inside software engineering teams everywhere. Code is being written faster than ever — in some cases, features that once took weeks now take a single day. But here’s the uncomfortable question nobody is asking loudly enough: who’s checking the work?

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.

No Hydraulics, No Problem: How Rise Robotics Is Quietly Disrupting a $750 Billion Industry (feat. Hiten Sonpal)

Krish Palaniappan — Tue, 07 Apr 2026 02:16:01 GMT

Here’s a question worth sitting with: when was the last time anyone fundamentally rethought how a hydraulic system works?

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?

Fix Systems First Before Scaling Marketing and AI Growth (feat. Kathy Baldwin)

Krish Palaniappan — Sat, 04 Apr 2026 00:24:33 GMT

In this episode, Krish sits down with Kathy Baldwin, Founder and CEO of Finally Business Infrastructure, for a deeply practical conversation on what it really takes to scale a business. Kathy brings decades of experience in sales, systems thinking, and customer psychology, working closely with founder-led businesses to transform the knowledge in their heads into structured, scalable processes.

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.

kathybaldwin.me & snowpal.com

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.

Leveraging AI and Automation: The New Frontier of Workforce Productivity (feat. Jeremy Hass)

Krish Palaniappan — Thu, 02 Apr 2026 01:39:14 GMT

In this episode, Jeremy Hass, founder of Prefix Ops, shares insights on leveraging AI in business operations, the importance of human judgment, and how to differentiate oneself in an AI-driven world. Discover practical examples, tools, and strategies to stay ahead in the rapidly evolving tech landscape.

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

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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.

The Hidden Lever in Capital Markets: Why Communication Determines IPO Success (feat. Jeffrey Goldberger)

Krish Palaniappan — Thu, 02 Apr 2026 01:31:00 GMT

In this interview, Jeffrey Goldberger, Managing Partner at KCSA Strategic Communications, shares expert insights on the nuances of going public, effective communication strategies, and the impact of technology on investor relations. Perfect for founders, investors, and industry enthusiasts eager to understand the complexities of public markets and corporate reputation management.

Snowpal API on AWS Marketplace

Podcast

From Earnings to Expectations: The Real Driver of Valuation — on Apple and Spotify.

From Private Momentum to Public Scrutiny

For growth-stage companies, the transition from private to public markets is often framed narrowly as a financial inflection point defined by revenue scale, valuation benchmarks, and liquidity events. In practice, however, the shift is far more structural and behavioral. A company moving into the public domain is no longer evaluated solely on its ability to execute operationally; it is continuously assessed on how effectively it explains that execution to an external audience that has limited context but significant capital at stake. Many growth-stage companies reach IPO readiness with strong fundamentals—product-market fit, recurring revenue, and expanding customer bases—yet remain relatively unknown in broader capital markets. This asymmetry creates a critical vulnerability: they lack an established narrative, and therefore lack control over how they are perceived when scrutiny intensifies.

What changes most dramatically post-IPO is not the business itself, but the cadence and transparency of its obligations. Quarterly disclosures, forward guidance, analyst interactions, and real-time market reactions introduce a level of accountability that most management teams have never experienced. Founders and operators who were previously insulated from external pressure must now operate as stewards of shareholder capital, where every strategic decision is interpreted through the lens of value creation. Without a deliberate communication strategy in place prior to this transition, companies often find themselves reacting to narratives instead of shaping them.

Communication as a Financial Instrument

In capital markets, communication functions as an extension of financial performance rather than a supplement to it. Investors do not consume earnings releases as static reports; they interpret them as signals embedded with intent, confidence, and risk. The numerical outputs—revenue growth, margins, earnings per share—are only one dimension of the evaluation process. The accompanying commentary, tone, and framing of those numbers determine how markets price future expectations. This is why two companies with identical financial results can experience materially different stock price reactions based solely on how those results are communicated.

The forward-looking component of communication is particularly influential. Guidance, whether explicit or implied, establishes a baseline against which future performance is judged. When management communicates with precision and consistency, it reduces uncertainty and compresses perceived risk, often supporting higher valuation multiples. Conversely, ambiguous or overly optimistic messaging expands uncertainty, increasing volatility even in the presence of strong historical performance. In this sense, communication operates as a mechanism for risk management, directly influencing the cost of capital.

The Multi-Stakeholder Reality

Public company communication is inherently multi-dimensional because it serves a heterogeneous audience with competing priorities. Institutional investors seek clarity on long-term growth drivers and capital allocation discipline. Sell-side analysts focus on model inputs, comparability, and incremental data points that refine forecasts. Employees interpret the same messages for signals about job security, strategic direction, and cultural stability. Partners and customers evaluate implications for supply chains, pricing, and product continuity.

This convergence creates a structural complexity: a single earnings call must simultaneously satisfy technical rigor and broad accessibility. Overly technical language risks alienating non-financial stakeholders, while excessive simplification can undermine credibility with sophisticated investors. The most effective companies resolve this tension by developing layered communication—clear core messages supported by detailed disclosures—ensuring that each stakeholder group can extract relevant insights without misinterpretation. Failure to achieve this balance often results in fragmented understanding, where different audiences derive conflicting conclusions from the same information.

The Cost of Inconsistency

Credibility in public markets is cumulative, built through repeated alignment between what management communicates and what the company ultimately delivers. This alignment forms a reservoir of trust that can materially influence how investors respond during periods of underperformance or external disruption. Companies that consistently meet or exceed their communicated expectations establish a reputation for reliability, which in turn stabilizes their investor base and reduces sensitivity to short-term volatility.

In contrast, inconsistency—whether through missed guidance, shifting narratives, or reactive disclosures—erodes this trust rapidly. Markets tend to penalize not just the deviation itself, but the perceived lack of control or foresight that it signals. Once credibility is compromised, even strong subsequent performance may be discounted, as investors require sustained evidence before recalibrating their expectations. This asymmetry underscores a fundamental principle: it is significantly easier to preserve trust than to rebuild it.

Preparing for the Public Narrative

IPO preparation must therefore extend beyond financial reporting systems and regulatory compliance to include the construction of a coherent and durable narrative. This involves articulating a clear investment thesis that connects the company’s historical performance with its future growth trajectory, supported by measurable drivers and realistic assumptions. Management teams must align internally on this narrative to ensure consistency across all communication channels, from investor presentations to earnings calls and media interactions.

Equally critical is the development of institutional capabilities around investor relations. This includes establishing processes for regular engagement, preparing for earnings call dynamics—including anticipated questions and scenario responses—and ensuring that disclosures are both comprehensive and comprehensible. Companies that treat these elements as strategic priorities, rather than procedural requirements, are better positioned to enter public markets with confidence and control over their narrative.

Leadership as Signal

In the public market context, leadership communication becomes a primary signal through which investors assess not just strategy, but execution capability. The demeanor, clarity, and responsiveness of executives during earnings calls and public appearances are scrutinized as indicators of underlying business health. Subtle factors—hesitation in answering questions, inconsistencies in messaging, or lack of specificity—can introduce doubt, even when financial results are strong.

Effective leaders understand that their role extends beyond reporting outcomes; they must interpret those outcomes within a broader strategic context. This requires balancing transparency with conviction—acknowledging challenges without amplifying concern, and expressing optimism without overstating certainty. Achieving this balance is not intuitive; it is the result of rigorous preparation, disciplined messaging, and a deep understanding of how markets process information.

Conclusion: The Intangible That Drives Valuation

For finance professionals, the instinct is often to prioritize quantifiable metrics as the primary drivers of valuation. While these metrics are undeniably important, the IPO journey reveals that perception—shaped largely through communication—plays an equally critical role. Markets do not operate on data alone; they operate on interpreted data, filtered through narratives that influence expectations and risk assessments.

Communication, therefore, should be viewed not as a peripheral function, but as a core component of financial strategy. It shapes how performance is understood, how risks are evaluated, and ultimately how value is assigned. Companies that recognize this interplay early, and invest in building disciplined, transparent, and consistent communication frameworks, position themselves to not only achieve a successful IPO but to sustain credibility and performance in the long term.

Q & A on IPO Communication and Capital Markets

Understanding IPO Readiness and Communication

Q1. Why do growth-stage companies struggle with IPO readiness despite strong business fundamentals?

Growth-stage companies often assume that operational success—such as revenue growth, product-market fit, and customer traction—naturally translates into IPO readiness. However, the gap lies in their lack of experience operating as public entities. They are typically “lesser known” in capital markets and have not built a communication infrastructure to engage investors, analysts, and broader stakeholders. This absence of visibility and structured messaging creates a disconnect between business performance and market perception, making communication a critical missing layer.

Q2. What is the most common mistake companies make before going public?

The most frequent mistake is underestimating the importance of communication. Many companies delay building a communication strategy until late in the IPO process, treating it as a secondary function rather than a core capability. This leads to inconsistent messaging, unclear expectations, and confusion among stakeholders—including employees, investors, and partners—at a time when clarity is most essential.

Communication as a Driver of Market Behavior

Q3. Why does communication impact stock price even when financial results are strong?

Financial results represent historical performance, but markets are forward-looking. Communication—especially tone, guidance, and narrative—shapes expectations about the future. Investors analyze not just what was achieved, but what management believes will happen next. Even with strong earnings, cautious or unclear messaging can introduce uncertainty, leading to negative market reactions.

Q4. Can poor communication outweigh strong numbers?

Yes, it can. Markets interpret signals beyond raw data. During earnings calls, investors and analysts evaluate every word, tone, and hesitation. If leadership appears uncertain, overly optimistic, or inconsistent, it can undermine confidence—even if the underlying numbers are solid. In this sense, communication acts as a multiplier (positive or negative) on financial performance.

Stakeholders and Messaging Complexity

Q5. Who are companies really communicating to during earnings calls?

While earnings calls are designed primarily for the investment community, the audience is much broader. Investors, analysts, employees, partners, and even customers consume the same information simultaneously. Each group interprets the message differently based on their interests—financial returns, job security, operational continuity, or strategic alignment—making communication inherently multi-layered.

Q6. Why is it difficult to balance messaging across stakeholders?

Because each stakeholder group seeks different insights from the same message. Investors want clarity on growth and margins, employees look for stability and direction, and partners assess operational implications. Effective communication must therefore be both technically precise and broadly understandable, avoiding jargon while maintaining credibility.

The Role of Leadership in Communication

Q7. What role does the CEO play in shaping investor perception?

The CEO is not just a business operator but also the primary storyteller of the company. Their tone, confidence, and clarity signal how the business is performing and where it is headed. A CEO must balance realism with optimism—acknowledging challenges while reinforcing long-term potential. Investors are often evaluating leadership quality as much as business performance.

Q8. Is enthusiasm important in leadership communication?

Absolutely. Investors expect leadership to demonstrate conviction in their strategy and business. A lack of enthusiasm can signal weak internal confidence, while excessive optimism without substance can damage credibility. The balance lies in presenting a truthful narrative with clear plans for addressing risks and capturing opportunities.

Consistency, Trust, and Market Confidence

Q9. Why is consistency in communication so critical in public markets?

Consistency builds “trust capital.” When companies repeatedly set expectations and meet them, investors develop confidence in management’s ability to execute. This trust reduces volatility and provides resilience during difficult periods. In contrast, inconsistent messaging or missed expectations quickly erodes credibility, which is difficult to rebuild.

Q10. Can companies recover from communication or operational failures?

Yes, but recovery depends on speed, transparency, and execution. Companies that acknowledge issues quickly, communicate clearly about corrective actions, and demonstrate measurable improvements can regain trust. Crisis situations—such as product failures or security breaches—are often less damaging than prolonged ambiguity or delayed responses.

External Factors and Market Interpretation

Q11. How do external factors influence market reactions beyond company control?

Even strong company performance can be overshadowed by macroeconomic conditions, geopolitical events, or industry-wide trends. For example, rising costs, regulatory changes, or global instability can alter future expectations. Investors incorporate these external variables into their interpretation of company guidance, often leading to unexpected market reactions.

Q12. Why do markets react more to forward guidance than past performance?

Because valuation is based on discounted future cash flows, not historical results. While past performance validates execution, forward guidance shapes the assumptions investors use to model future growth. Any change in guidance—whether explicit or implied—can significantly impact valuation.

Preparing for Public Market Expectations

Q13. What should companies do before going public to improve communication?

They should build a structured communication framework early. This includes defining clear messaging, identifying key stakeholder groups, aligning leadership narratives, and preparing for recurring disclosures such as earnings calls. Companies should also practice simplifying complex business models into investor-friendly language to reduce misinterpretation.

Q14. How important is investor relations in the IPO process?

Investor relations is critical. It serves as the bridge between the company and the market, ensuring consistent, transparent, and strategic communication. A strong investor relations function helps attract long-term investors, manage expectations, and maintain credibility over time.

Communication as a Strategic Advantage

Q15. Is communication domain-specific, or does it follow a universal playbook?

While each industry has nuances—such as specific metrics or regulatory considerations—the core principles of communication are universal. Clarity, consistency, transparency, and credibility apply across sectors. Leaders who master these principles can often succeed regardless of industry.

Q16. What ultimately determines long-term success in public markets?

Long-term success is driven by a combination of execution and perception. Companies must deliver results, but they must also communicate those results effectively. Over time, those that align performance with clear, credible communication build enduring investor trust, stronger valuations, and a more stable shareholder base.

Final Perspective

Q17. What is the single most important takeaway for finance professionals?

Communication is not a support function—it is a financial lever. It directly influences valuation, investor confidence, and market stability. Companies that treat communication as a strategic discipline, rather than an afterthought, gain a meaningful advantage in navigating public markets.

Human + Machine: The Real Story of AI in Oil & Gas: From Rigs to Real-Time Intelligence (feat. Steve Senterfit)

Krish Palaniappan — Wed, 01 Apr 2026 01:20:51 GMT

In this insightful interview, Steve Senterfit, President of SmartBridge, shares his extensive experience in digital transformation, especially within the oil and gas industry. The discussion covers industry-specific challenges, the role of AI, and practical strategies for successful technology adoption.

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

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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 in Marketing: Why Adoption Is Easy but Advantage Is Rare (feat. Harjiv Singh)

Krish Palaniappan — Wed, 01 Apr 2026 01:20:33 GMT

Marketing has evolved significantly over the last few decades, particularly with the introduction of digital tools and platforms. But with this evolution comes complexity, making it challenging for marketers to navigate. In this post, we’ll explore how AI native marketing platforms are addressing these challenges and transforming how marketing teams operate. We’ll break down insights from a recent discussion with Harjiv Singh, founder and CEO of CambrianEdge, who shares valuable perspectives on leveraging AI in marketing.

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

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.
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.
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.
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.
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.
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.
Why is measuring everything not always beneficial?
Because not all measurable actions contribute to meaningful outcomes—data without context can lead to misguided decisions.
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.
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.
What foundational principle of marketing remains unchanged?
Marketing still centers on understanding customer needs, communicating value clearly, and building trust over time.
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.
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.
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.
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.
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.
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.
How does AI impact creativity in marketing?
It amplifies the importance of creativity, as differentiation increasingly depends on original thinking, storytelling, and strategic insight.
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.
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.
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.
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.

When Everyone Can Build Software using AI, What Still Matters (feat. AJ Bubb)

Krish Palaniappan — Wed, 01 Apr 2026 01:20:04 GMT

The conversation between Krish Palaniappan and AJ Bubb offers a sharp lens into how AI is reshaping not just software development, but the very nature of work, differentiation, and expertise. At its core is a grounded but often misunderstood idea: AI is not replacing human capability, it is amplifying it. AJ frames this as “human plus AI,” where machines accelerate execution while humans remain responsible for direction, intent, and judgment. This distinction becomes critical in the context of “vibe coding,” where AI takes over much of the mechanical effort of building software.

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

Building a Startup at the Intersection of Technology and Culture (feat. Dr. Anil Kumar)

Krish Palaniappan — Wed, 01 Apr 2026 01:19:44 GMT

In this insightful interview, Dr. Anil Kumar, Founder of Jodi365, shares his journey from India to the US, his entrepreneurial ventures in online matchmaking, and his perspectives on technological and cultural changes in India. We explore the evolution of India’s tech landscape, societal shifts, and the impact of education and culture on business and innovation. In this engaging conversation, Anil Kumar shares insights on societal perceptions, cultural influences, personal growth, and the impact of technology on careers and society. He reflects on India’s evolving identity, the influence of colonialism, and the future of work in a rapidly changing world.

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

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.
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.
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.
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.
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.
How did the platform evolve technologically over time?
It transitioned to more advanced architectures, including graph databases, which improved matchmaking efficiency and overall performance.
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.
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.
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.
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.
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.
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.
How did Jodi365 differentiate itself from competitors?
By focusing on a specific underserved segment and building for local context rather than copying global platforms.
What unconventional decision did Anil Kumar make regarding funding?
He chose to turn down venture capital, prioritizing sustainable growth and control over rapid scaling.
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.

The Illusion of Progress in AI-Driven Development: Speed Is Cheap, Insight Is Rare (feat. Rob Wright)

Krish Palaniappan — Wed, 01 Apr 2026 01:19:25 GMT

In this in-depth interview, Rob Wright, Co-founder of Waffl, a West Point graduate and former special operations leader turned tech founder, shares insights on AI adoption, building software, and navigating the rapidly changing tech landscape. Discover practical advice on leveraging AI for small businesses, the importance of trust in client relationships, and how large corporations approach innovation.

For software developers, the current AI wave feels like a cheat code. Tools can scaffold APIs, generate documentation, write tests, and even suggest architectural decisions. What once took days can now be done in hours, sometimes minutes. On the surface, this looks like undeniable progress. But beneath that speed lies a subtle trap: doing more is not the same as creating value.

As one insight from the conversation captures, “AI adoption is easy depending on your size…you can just log into tools and get efficiencies out of it.” That accessibility is precisely the problem. When something is this easy to adopt, it becomes just as easy to misuse.

Developers are increasingly surrounded by tools that promise leverage, yet many teams end up layering AI onto workflows without questioning whether it meaningfully improves outcomes. The result is often noise disguised as productivity.

AI + Snowpal API for Faster Development

Podcast

AI Adoption Is Easy. Creating Advantage Is Not. — on Apple and Spotify.

From West Point to Waffle: The Unlikely Entrepreneur

Rob Wright didn’t set out to be an entrepreneur. He grew up in East Tennessee, graduated from West Point in 2014, and spent the better part of a decade in the military. But even before high school, his mind worked a certain way.

“When I walk into a Tropical Smoothie Cafe,” he explains, “my mind starts going — this is how many people are on the assembly line, this is how much they’re getting paid, the rent is this much, this is how many orders they have to do to break even.” That instinct to see the business inside every business eventually led him to co-found Waffle, an AI-powered platform designed to help small businesses build real competitive advantage — not just bolt on AI for the sake of it.

When Tools Start Driving the Process

A common anti-pattern emerging across engineering teams is the force-fitting of AI into workflows. Instead of starting with a problem and identifying where AI fits, teams start with the tool and look for ways to use it.

Consider something as simple as requirements gathering. Traditionally, ideas might evolve through informal notes, discussions, or quick iterations. Introducing AI into that process can seem like a natural upgrade—convert voice notes into structured documents, generate detailed specs, and standardize outputs.

But what actually happens?

The output becomes bloated. A single idea expands into pages of over-structured documentation. Signal gets buried under verbosity. What once enabled clarity now introduces friction.

This is the paradox: AI can make processes more “complete” while making them less useful.

Efficiency vs. Advantage

There is a fundamental distinction developers must internalize: efficiency is not advantage.

Efficiency means doing the same things faster. Advantage means doing things others cannot easily replicate.

Most AI usage today falls into the first category. Generating code snippets faster, automating documentation, or improving internal workflows—these are valuable, but they are not defensible. If everyone has access to the same tools, then efficiency gains are quickly commoditized.

As discussed in the conversation, “If it is not replacing something that you do or generating something that you already don’t do, it’s not giving you a competitive advantage.”

This is the crux. Developers are not competing on how fast they can write boilerplate anymore. They are competing on how effectively they can solve meaningful problems.

The FOMO Trap in Developer Ecosystems

There is also a psychological dimension at play. The developer ecosystem is heavily influenced by trends, and AI has amplified this effect. Every new tool claims to replace entire workflows. Every announcement suggests that not adopting it immediately puts you at risk.

This creates a constant sense of urgency—an artificial pressure to integrate tools before understanding their value.

But chasing tools is not the same as building systems.

The more disciplined teams are doing the opposite. They are slowing down, identifying bottlenecks, and selectively introducing AI where it creates measurable impact. They are not asking, “How do we use this tool?” but rather, “Where does this tool actually matter?”

Why Small Teams Struggle More

Interestingly, smaller teams and startups often struggle more with AI adoption than larger organizations—not because they lack capability, but because they lack structure.

Large companies assign ownership. They define metrics. They evaluate outcomes. Even if their processes are slower, they are deliberate. There is accountability tied to adoption.

Small teams, on the other hand, operate with fluid roles. The same developer might be building features, handling infrastructure, and experimenting with AI tools—all at once. In such environments, AI becomes an unstructured layer added on top of already complex systems.

The result is fragmentation. Tools get adopted inconsistently. Workflows become harder to reason about. And ironically, productivity can decline.

Building vs. Selling: The Hard Truth

Another hard lesson for developers is that building something impressive does not guarantee that anyone will pay for it.

AI has lowered the barrier to building software. More people can create products now than ever before. But this has also increased competition dramatically. The real challenge is no longer building—it is validating demand.

As highlighted in the discussion, a product can receive strong positive feedback and still fail commercially because no one is willing to pay for it.

This forces a shift in mindset. Developers must think beyond implementation and consider distribution, user behavior, and willingness to pay. AI can accelerate development, but it cannot create demand.

Letting Go of the Wrong Things

One of the most difficult skills for developers and founders alike is knowing when to stop.

There is a natural tendency to persist, especially after investing significant time and effort. But persistence without validation leads to sunk cost fallacy—continuing a path simply because of past investment.

The more effective approach is iterative validation. Build small, test quickly, and measure real-world outcomes. If the signal is weak, pivot. Not because the idea is bad, but because the market is indifferent.

AI makes iteration faster, which should make decision-making faster as well. But that only works if teams are willing to act on feedback.

Rethinking What It Means to Build Software

The role of a software developer is evolving. It is no longer just about writing code—it is about orchestrating systems, making judgment calls, and understanding where automation fits.

AI is not replacing developers. It is exposing gaps in how developers think.

Those who rely solely on tools will produce more output, but not necessarily better outcomes. Those who focus on problem clarity, system design, and user value will use AI as leverage rather than a crutch.

Closing Thoughts: Evaluate Before You Implement

Rob’s closing comment distills everything into a single sharp principle:

“Really evaluate what you’re doing. Because AI doesn’t fix what’s already broken.”

Before implementing any tool — AI or otherwise — ask whether it replaces something you do or generates something you couldn’t do before. If it does neither, you don’t have an AI problem. You might have a process problem. And the solution to a process problem is building a better process, not stacking more technology on top of broken foundations.

The businesses that will win with AI aren’t the ones who adopt the most tools. They’re the ones who adopt the right tools, in the right places, at the right time — and build the kind of trust and judgment that no tool can replicate.

Rob Wright is the co-founder of Waffle, an AI platform for small and medium businesses. You can learn more at gowaffl.com.

Bridging the Competency Gap: Why Tech Leaders Need Strong External Communication (feat. Shayna Davis)

Krish Palaniappan — Thu, 26 Mar 2026 00:03:24 GMT

In this insightful interview, Shayna Davis, CEO of Executive Signals, shares expert advice on how tech leaders can enhance their external communication, build trust, and establish credibility in a competitive landscape. Discover practical strategies for leadership branding, content creation, and navigating reputation management to drive business success.

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.

What Listening Reveals About Great Leadership (feat. Dr. Anthony Giannoumis)

Krish Palaniappan — Tue, 24 Mar 2026 20:39:55 GMT

In this insightful interview, Dr. Anthony Giannoumis shares profound lessons on leadership, cultural intelligence, and the importance of empathy in diverse environments. Discover how listening, curiosity, and understanding different perspectives can transform teams and personal growth.

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.

Real-World Lessons in Software Transformation and Execution (feat. Sridhar Ravilla)

Krish Palaniappan — Tue, 24 Mar 2026 01:29:04 GMT

In today’s business world, transformation has become one of the most overused and misunderstood terms. Companies often describe everything from a website redesign to a software upgrade as “transformation.” But true transformation is much deeper than surface-level change. It reshapes how a business operates, how customers experience its products, and how leaders make decisions in a fast-changing environment. As Sridhar Ravilla explains, transformation is not about making temporary improvements. It is about creating lasting change that an organization cannot simply reverse.

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.

One is to go deep in one area, investing heavily to transform a single product, service, or operational function.
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

Transformation That Lands: A practical guide to making organizational change stick by turning strategy into measurable, lasting business outcomes.
Humans at Scale: A leadership-focused look at why human judgment, ownership, and accountability matter even more in the age of AI.
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.