<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/rss-styles.xsl" type="text/xsl"?><rss version="2.0"><channel><title>Vijayanta Gupta. Writing.</title><description>Essays, board memos, and notes on growth, pricing, AI, and the commercial side of building software. Published when there is something to say, not on a calendar.</description><link>https://vijayantagupta.com</link><language>en-gb</language><item><title>AI roadmap theatre: why most B2B software AI strategies will not move the growth curve</title><link>https://vijayantagupta.com/writing/note/ai-roadmap-theatre</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/ai-roadmap-theatre</guid><description>Most software boards treat an AI roadmap as an AI strategy, but the first two years of disclosed shipping show the feature inventory has not moved revenue, retention, margin, or category position.</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>investors</category><category>moat</category><category>margin</category><category>pricing</category><category>diligence</category></item><item><title>Software multiples in the agentic era</title><link>https://vijayantagupta.com/writing/note/software-multiples-in-the-agentic-era</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/software-multiples-in-the-agentic-era</guid><description>The SaaS multiple framework assumed durable recurring revenue, low cost to serve, and 80-point gross margins, and agentic AI tests all three at once, splitting the category into three cohorts that should be priced separately.</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>multiples</category><category>investors</category><category>margin</category><category>pricing</category><category>moat</category></item><item><title>The difference between using AI and operating AI-natively</title><link>https://vijayantagupta.com/writing/note/using-ai-vs-operating-ai-natively</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/using-ai-vs-operating-ai-natively</guid><description>A field note drawing the line between using AI through licences and features and operating AI-natively by rebuilding workflow, hiring, pricing, product, and capital around the model.</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>AI-native</category><category>operating-model</category><category>workflow</category><category>margin</category><category>leadership</category></item><item><title>Why product, go-to-market and pricing must be rebuilt together</title><link>https://vijayantagupta.com/writing/note/why-product-go-to-market-and-pricing-must-be-rebuilt-together</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/why-product-go-to-market-and-pricing-must-be-rebuilt-together</guid><description>AI transitions fail when product, go-to-market and pricing are run as sequential workstreams rather than one integrated reset, because AI changes value capture first and value capture is a pricing variable.</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>go-to-market</category><category>pricing</category><category>product</category><category>operating-model</category><category>CEO</category></item><item><title>The workflow obsolescence risk</title><link>https://vijayantagupta.com/writing/note/the-workflow-obsolescence-risk</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/the-workflow-obsolescence-risk</guid><description>The AI risk most software boards still misprice is not feature-level competition but workflow-level disintermediation, where AI removes the workflow a product currently monetises.</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><category>workflow</category><category>investors</category><category>diligence</category><category>moat</category></item><item><title>What six people can now attempt</title><link>https://vijayantagupta.com/writing/note/what-six-people-can-now-attempt</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/what-six-people-can-now-attempt</guid><description>A field note from building AI-native, arguing that lower marginal cost of code widens the scope of problems a small team will rationally attempt, not just its speed.</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><category>AI-native</category><category>small-teams</category><category>software</category><category>venture</category><category>operating-model</category></item><item><title>Your first AI hire may be the wrong one</title><link>https://vijayantagupta.com/writing/note/your-first-ai-hire-may-be-the-wrong-one</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/your-first-ai-hire-may-be-the-wrong-one</guid><description>The reflex when a board asks about AI is to hire someone with AI in their title, but in most B2B software companies the first constraint is the operating model, not model capability or engineering bandwidth.</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><category>hiring</category><category>CEO</category><category>operating-model</category><category>AI strategy</category><category>boards</category></item><item><title>Five questions every software board should ask in 2026</title><link>https://vijayantagupta.com/writing/memo/five-questions-every-software-board-should-ask</link><guid isPermaLink="true">https://vijayantagupta.com/writing/memo/five-questions-every-software-board-should-ask</guid><description>Five board-level questions that re-anchor the AI conversation from the product roadmap onto the business model, each answered with operating evidence.</description><pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate><category>boards</category><category>AI-native</category><category>pricing</category><category>switching-costs</category><category>go-to-market</category></item><item><title>Five AI questions to ask in software diligence</title><link>https://vijayantagupta.com/writing/note/five-ai-questions-to-ask-in-software-diligence</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/five-ai-questions-to-ask-in-software-diligence</guid><description>An investor-grade reframe of the board memo questions, tuned to underwriting choices across workflow disintermediation, switching cost, pricing survival, margin, and go-to-market exposure.</description><pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate><category>diligence</category><category>investors</category><category>moat</category><category>pricing</category><category>margin</category></item><item><title>The AI roadmap is not the moat</title><link>https://vijayantagupta.com/writing/note/the-ai-roadmap-is-not-the-moat</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/the-ai-roadmap-is-not-the-moat</guid><description>A reframe of what counts as defensible in AI-native software, arguing investors should diligence the moat layer of data, integration, and switching cost rather than the roadmap layer.</description><pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate><category>moat</category><category>investors</category><category>diligence</category><category>multiples</category></item><item><title>Where AI creates margin expansion and where it destroys it</title><link>https://vijayantagupta.com/writing/note/where-ai-creates-margin-expansion</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/where-ai-creates-margin-expansion</guid><description>The specific configurations that raise software gross margin under AI economics, set against the ones that destroy it, and how each lands inside the contract envelope.</description><pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate><category>margin</category><category>pricing</category><category>investors</category><category>diligence</category><category>multiples</category></item><item><title>AI-native is not a product strategy. It is an operating model.</title><link>https://vijayantagupta.com/writing/ai-native-is-not-a-product-strategy</link><guid isPermaLink="true">https://vijayantagupta.com/writing/ai-native-is-not-a-product-strategy</guid><description>Treating AI as a product strategy puts it inside the roadmap. Treating it as an operating model puts it inside how the company decides, allocates capital, prices, and builds.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><category>AI-native</category><category>operating-model</category><category>pricing</category><category>margin</category><category>boards</category></item><item><title>The SaaS company after SaaS</title><link>https://vijayantagupta.com/writing/the-saas-company-after-saas</link><guid isPermaLink="true">https://vijayantagupta.com/writing/the-saas-company-after-saas</guid><description>The next decade is not a feature cycle for SaaS but the construction of a different kind of company, built on AI economics rather than seat economics, on top of SaaS.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><category>SaaS</category><category>AI-native</category><category>pricing</category><category>margin</category><category>operating-model</category></item><item><title>The second growth curve</title><link>https://vijayantagupta.com/writing/the-second-growth-curve</link><guid isPermaLink="true">https://vijayantagupta.com/writing/the-second-growth-curve</guid><description>The first growth curve of B2B software, from on-premise to SaaS, is ending. The second, from SaaS to AI-native, has begun. A business-model reset, not a feature cycle.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><category>AI-native</category><category>SaaS</category><category>growth</category><category>pricing</category><category>boards</category></item><item><title>The SaaS-to-AI-native transition risk</title><link>https://vijayantagupta.com/writing/memo/the-saas-to-ai-native-transition-risk</link><guid isPermaLink="true">https://vijayantagupta.com/writing/memo/the-saas-to-ai-native-transition-risk</guid><description>A board-language view of the SaaS-to-AI-native transition risk across product, go-to-market, pricing, services, and capital, with one diagnostic per line.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><category>boards</category><category>AI-native</category><category>pricing</category><category>margin</category><category>go-to-market</category></item><item><title>Your 2026 growth plan is modelled on a buyer that no longer exists</title><link>https://vijayantagupta.com/writing/memo/your-2026-growth-plan-buyer-no-longer-exists</link><guid isPermaLink="true">https://vijayantagupta.com/writing/memo/your-2026-growth-plan-buyer-no-longer-exists</guid><description>Most software growth plans for 2026 still assume the prior go-to-market motion, pricing, and unit economics while the product becomes an AI product.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><category>boards</category><category>growth</category><category>pricing</category><category>margin</category><category>go-to-market</category></item><item><title>AI is a business model reset, not a feature roadmap</title><link>https://vijayantagupta.com/writing/ai-is-a-business-model-reset</link><guid isPermaLink="true">https://vijayantagupta.com/writing/ai-is-a-business-model-reset</guid><description>Most B2B software CEOs are answering what AI features ship this quarter. The board question is what AI is doing to the business model that ships them.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>AI-native</category><category>SaaS</category><category>pricing</category><category>margin</category><category>boards</category></item><item><title>AI redesigns the C-suite before it redesigns the workforce</title><link>https://vijayantagupta.com/writing/ai-redesigns-the-c-suite</link><guid isPermaLink="true">https://vijayantagupta.com/writing/ai-redesigns-the-c-suite</guid><description>AI is being framed for CEOs as a workforce question. It is first a leadership-architecture question, and the C-suite operating model is being rewired before the workforce is.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>AI-native</category><category>C-suite</category><category>boards</category><category>operating-model</category><category>leadership</category></item><item><title>Pricing is the first AI-native lever</title><link>https://vijayantagupta.com/writing/pricing-is-the-first-ai-native-lever</link><guid isPermaLink="true">https://vijayantagupta.com/writing/pricing-is-the-first-ai-native-lever</guid><description>In the shift from SaaS to AI-native, pricing is the first lever to reset, because it is the only one that translates AI margin economics into recurring revenue structure.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>pricing</category><category>AI-native</category><category>margin</category><category>go-to-market</category><category>boards</category></item><item><title>When the go-to-market playbook stops working</title><link>https://vijayantagupta.com/writing/when-the-go-to-market-playbook-stops-working</link><guid isPermaLink="true">https://vijayantagupta.com/writing/when-the-go-to-market-playbook-stops-working</guid><description>Go-to-market signals lead product signals when a software business hits its growth ceiling, and boards usually see the break twelve months late because the dashboards smooth it.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>go-to-market</category><category>SaaS</category><category>pricing</category><category>boards</category><category>AI-native</category></item><item><title>Why AI is not yet showing up in the growth plan</title><link>https://vijayantagupta.com/writing/memo/why-ai-is-not-in-the-growth-plan</link><guid isPermaLink="true">https://vijayantagupta.com/writing/memo/why-ai-is-not-in-the-growth-plan</guid><description>Why AI does not appear in the growth numbers, and what would change that.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>AI</category><category>growth</category><category>boards</category><category>pricing</category></item><item><title>A CEO&apos;s 90-day AI-native reset agenda</title><link>https://vijayantagupta.com/writing/note/a-ceos-90-day-ai-native-reset-agenda</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/a-ceos-90-day-ai-native-reset-agenda</guid><description>Most AI programmes in B2B software fail in the third to sixth month when the feature backlog catches up with the operating model and nothing moves on the P&amp;L. This is the operator&apos;s ninety-day sequence.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>CEO</category><category>AI-native</category><category>pricing</category><category>operating-model</category><category>capital-allocation</category></item><item><title>Do not delegate AI strategy to the product roadmap</title><link>https://vijayantagupta.com/writing/note/do-not-delegate-ai-strategy-to-the-product-roadmap</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/do-not-delegate-ai-strategy-to-the-product-roadmap</guid><description>A CEO who delegates AI strategy to the CPO has chosen the smallest version of the AI question, because product roadmaps optimise inside the business model while the AI question is about the business model itself.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>CEO</category><category>CPO</category><category>AI strategy</category><category>pricing</category><category>operating-model</category></item><item><title>How to tell whether your AI strategy is theatre</title><link>https://vijayantagupta.com/writing/note/how-to-tell-whether-your-ai-strategy-is-theatre</link><guid isPermaLink="true">https://vijayantagupta.com/writing/note/how-to-tell-whether-your-ai-strategy-is-theatre</guid><description>Most software companies have an AI strategy on paper and few have one in the operating model. This is a ten-minute self-audit against five operating tells; three or more, and the strategy is theatre.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>CEO</category><category>AI strategy</category><category>diagnostic</category><category>pricing</category><category>gross-margin</category></item></channel></rss>