<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[The First Principles]]></title><description><![CDATA[Engineering systems, products, and ideas from the ground up]]></description><link>https://blog.navneetsingh.name</link><image><url>https://blog.navneetsingh.name/img/substack.png</url><title>The First Principles</title><link>https://blog.navneetsingh.name</link></image><generator>Substack</generator><lastBuildDate>Sat, 11 Apr 2026 19:32:06 GMT</lastBuildDate><atom:link href="https://blog.navneetsingh.name/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Navneet Singh]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[navneetsinghlall@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[navneetsinghlall@substack.com]]></itunes:email><itunes:name><![CDATA[Navneet Singh]]></itunes:name></itunes:owner><itunes:author><![CDATA[Navneet Singh]]></itunes:author><googleplay:owner><![CDATA[navneetsinghlall@substack.com]]></googleplay:owner><googleplay:email><![CDATA[navneetsinghlall@substack.com]]></googleplay:email><googleplay:author><![CDATA[Navneet Singh]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Software is about to stop looking like software]]></title><description><![CDATA[The product interface is going through its biggest shift since desktop to web. Most builders are looking the wrong way.]]></description><link>https://blog.navneetsingh.name/p/software-is-about-to-stop-looking</link><guid isPermaLink="false">https://blog.navneetsingh.name/p/software-is-about-to-stop-looking</guid><dc:creator><![CDATA[Navneet Singh]]></dc:creator><pubDate>Sun, 05 Apr 2026 05:38:19 GMT</pubDate><content:encoded><![CDATA[<p><em>This is Part 2 of the Future of Software series. <a href="https://blog.navneetsingh.name/p/software-is-a-proxy-ai-makes-it-obsolete">Read Part 1: Software Is a Proxy. AI Makes It Obsolete.</a></em></p><p>&#8220;AI will replace all software UIs with a chat window.&#8221; Open a text box, type what you want, get an answer. No dashboards. No navigation. No buttons.</p><p>Sounds elegant. Also wrong.</p><p>The opposite take is equally wrong. That AI just means adding a chatbot sidebar to your existing Salesforce instance and calling it transformation. I&#8217;ve seen four enterprise clients do exactly this in the last 18 months. Users ignore the chatbot within two weeks. Every time.</p><p>The product interface isn&#8217;t dying. It&#8217;s going through the biggest shift since desktop to web. And most builders are getting it wrong because they think it&#8217;s a binary choice. Chat or dashboard. Pick one.</p><blockquote><p>The future is neither.</p></blockquote><div><hr></div><h2>Why pure chat fails</h2><p>Before I get into where things are going, it&#8217;s worth understanding why the &#8220;just a chat box&#8221; pitch falls apart the moment someone tries to use it.</p><p><strong>Humans think visually, not sequentially.</strong> A business owner asks &#8220;how is my company doing?&#8221; and they don&#8217;t want 500 words back. They want to see revenue trending up, one project turning red, cash reserves stable. A well designed visual communicates in 2 seconds what takes 2 minutes to read. We built a project management tool for a healthcare client last year. First version had a conversational interface. Client&#8217;s project managers hated it. They needed to see the sprint board AND team capacity AND client deadline all at once. Not one at a time through a chat window.</p><p><strong>Chat has no persistent state.</strong> Ask &#8220;show me overdue tasks.&#8221; Get a list. Close the chat. Where&#8217;s the list? Gone. Ask again tomorrow, get a new list. Humans need spatial anchoring. The feeling that information lives somewhere stable, not summoned from thin air each time you ask.</p><p><strong>Chat can&#8217;t handle parallel attention.</strong> A project manager needs four data streams in peripheral vision while focusing on one. Chat forces everything into a single sequential thread. That&#8217;s a downgrade, not an upgrade.</p><p>So pure chat is out. But traditional dashboards are also increasingly inadequate. They show everything to everyone, all the time, regardless of what actually matters right now. They make humans come to the information instead of bringing information to the human.</p><p>What&#8217;s left?</p><div><hr></div><h2>Four stages of product interface evolution</h2><p>This transition isn&#8217;t a single leap. It&#8217;s a progression through four stages. Each one changes the fundamental relationship between the user and the product. I&#8217;ve been building B2B software for 18 years and we&#8217;re watching this play out in real time across our client base.</p><h3>Stage 1: Static dashboards (where most products are today)</h3><p>You navigate to information. The product has a fixed structure. Tabs, sidebars, pages, settings. The same dashboard shows the same layout to everyone, every time.</p><p>This is how Salesforce, Jira, HubSpot, Tally, and virtually every B2B tool works today. The UI is the product. Learning the UI is learning the product. The skill is in navigation.</p><p>We operate at this stage with most of our enterprise clients still. About 80% of the custom software we build in any given quarter is Stage 1. It works. It&#8217;s just not where things are heading.</p><h3>Stage 2: Conversational hybrid (where the progressive products are heading)</h3><p>You ask for information, the system responds with both text and visual context. The dashboard still exists but it&#8217;s increasingly secondary.</p><p>&#8220;What should I focus on today?&#8221; returns a prioritised list with context about why each item matters. Not because you navigated to a &#8220;priorities&#8221; page, but because the system synthesised across your tasks, calendar, team status, and deadlines to generate an answer.</p><p>We started building Stage 2 interfaces about eight months ago. A healthcare client wanted their clinical coordinators to be able to ask &#8220;which patients need follow up today&#8221; instead of navigating through four different screens to compile the list manually. The coordinator&#8217;s daily workflow went from <strong>45 minutes of screen navigation to a 3 minute conversation</strong>. Same data, same decisions, completely different interaction model.</p><p>Most users in Stage 2 products spend 80% of their time in conversation mode and 20% in dashboard mode. The inverse of today.Stage 3: Ambient intelligence (where things get interesting)</p><p>The system doesn&#8217;t wait for you to ask. It proactively delivers the 2 or 3 things that need your attention, through whatever channel you&#8217;re already on. WhatsApp, Slack, email, push notification.</p><p>8 AM, your phone buzzes: &#8220;Two items need attention. One team member is blocked. Reply 1 or 2 to choose an approach and unblock them. One deadline is at risk. Approve a scope adjustment or extend the timeline. Everything else is on track.&#8221;</p><p>You reply &#8220;2&#8221; and &#8220;approve.&#8221; Twelve seconds. Your entire morning interaction with what used to be a complex software product.</p><blockquote><p>The design principle inverts: if the system hasn&#8217;t contacted you, everything is fine. Silence is the signal that things are working. This is how a great executive assistant operates. They don&#8217;t hand you a 50 page report every morning. They tell you the three things that need your judgment. Everything else is handled.</p></blockquote><p>We&#8217;re prototyping this for a logistics client right now. Their operations manager currently spends 90 minutes every morning reviewing dashboards across three different systems. The goal is to bring that down to under 5 minutes of notification responses. We&#8217;re about halfway there.</p><h3>Stage 4: Generated interfaces</h3><p>No pre-built screens exist at all. When you want to see something, you describe what you want and the system generates a visualisation on the fly. Perfectly tailored to your question, your role, and your context.</p><p>&#8220;Show me how the team is doing&#8221; generates a completely different view for a CEO than for a team lead. The CEO sees cross-team velocity trends and budget utilisation. The team lead sees individual contributor output and blocker resolution times. Same question, different generated interface, because the system understands who&#8217;s asking and what they actually need.</p><p>&#8220;Compare this quarter with last quarter&#8221; doesn&#8217;t load a pre-built comparison page. It generates a side by side analysis highlighting specifically what changed, what caused the change, and what actions might address it. The visualisation is ephemeral. It exists for this moment, for this question, and then dissolves.</p><p>There is no &#8220;analytics page&#8221; with 15 pre-configured charts that someone built once and nobody updates. Every view is generated on demand, contextual to the user, and disposable after use.</p><p>We haven&#8217;t built a full Stage 4 system for a client yet. But we&#8217;ve built pieces. A government reporting module where the interface generates different compliance views depending on which regulatory body is requesting the data. Same underlying dataset, completely different presentation. That&#8217;s a taste of where this goes when it matures.</p><div><hr></div><h2>Five properties of the future interface</h2><p>Regardless of stage, the direction is clear. Future interfaces share five properties that are fundamentally different from today&#8217;s software.</p><h3>1. Exception based, not comprehensive</h3><p>Today&#8217;s products show you everything. All tasks, all deals, all transactions. The user&#8217;s job is to scan through comprehensive views and find what matters. That&#8217;s an enormous cognitive tax.</p><p>Future products show you only what needs attention. Three items are red. Everything else is fine. The 200 transactions that reconciled correctly are invisible. The 3 that didn&#8217;t are surfaced.</p><blockquote><p>The metric for a well designed future product is not &#8220;time spent in app.&#8221; It&#8217;s &#8220;decisions made per minute of attention.&#8221; If a user can process their entire daily workload in 90 seconds of interaction, that&#8217;s a triumph. Not a retention problem.</p></blockquote><p>I keep having this argument with product managers who are worried about engagement metrics dropping. If your users accomplished everything they needed and left in 45 seconds, you won. If they spent 20 minutes browsing dashboards and left without taking an action, you lost. The engagement model of the future is the opposite of consumer social media.</p><h3>2. Multi-modal, not screen bound</h3><p>Today&#8217;s products live on a screen. You open the app, use it, close it.</p><p>Future products exist across multiple channels simultaneously. Morning summary arrives as a WhatsApp message. Time sensitive approval pops up as a push notification. Deep analysis request generates a visual in the web app. Quick status check answered by voice assistant.</p><p>The product meets you where you are, in the format appropriate for the interaction&#8217;s complexity. Channel selection isn&#8217;t a user preference to configure. It&#8217;s a decision the system makes based on urgency, complexity, and context.</p><p>We&#8217;re seeing this with our own internal tools. Our marketing system runs across 10 tracks with automated alerting. When ad spend drifts more than 15% overnight, the alert goes to Slack. When a review drops below 3 stars, the notification goes to the responsible person&#8217;s phone. When someone wants to dig into campaign performance, they open the dashboard. Different channels for different urgency levels. Nobody configured that. The system decides.</p><h3>3. Conversation first, visualisation second</h3><p>The primary interaction model is natural language. But the response isn&#8217;t always text. That&#8217;s the nuance the &#8220;just a chat box&#8221; crowd misses.</p><p>When you ask &#8220;how are we doing on revenue?&#8221; the best answer is a chart. When you ask &#8220;who&#8217;s falling behind?&#8221; the best answer is a ranked list. When you ask &#8220;what happened last Tuesday?&#8221; the best answer might be a timeline.</p><p>The AI should know when to respond with words, when to respond with a visualisation, and when to respond with an action. The interface is generated in response to the question, not pre-built awaiting it. Pre-built dashboards assume the designer knows what the user will want to see. Generated visualisations assume the system can figure it out in real time. The latter is almost always more useful, because what matters changes every day.4. Progressively deep. Glanceable to explorable</p><p>The initial response should be absurdly simple. A traffic light. A single number. A one sentence summary. &#8220;Everything&#8217;s on track&#8221; or &#8220;Two things need your attention.&#8221;</p><p>But depth should be instantly available. Tap on &#8220;two things need attention&#8221; and you get the specifics. Tap on a specific issue and you get the full context. Conversation history, timeline, root cause analysis, recommended actions. Tap further and you get the raw data.</p><p>The design principle: <strong>the top layer should be understandable in 3 seconds</strong>. Every deeper layer is opt in. Most days, most users never go past the first layer. That&#8217;s success, not failure.</p><p>Think of it like a newspaper versus a research library. Today&#8217;s software is a research library. Everything is there, find what you need. Tomorrow&#8217;s software is a newspaper with a library behind it. The headlines tell you what matters, and you can always dig deeper.</p><h3>5. Action oriented, not information oriented</h3><p>This might be the most underappreciated shift. Today&#8217;s products end at &#8220;here&#8217;s the information.&#8221; The user then has to decide what to do and go somewhere else to do it. See a problem in the dashboard. Think about the solution. Switch to email to communicate it. Switch to the task tool to update it. Switch back to verify.</p><p>Future products end at &#8220;here&#8217;s the recommended action. Approve?&#8221;</p><p>&#8220;A team member is blocked on a decision. Here are both options with trade offs. Reply 1 or 2 to unblock them.&#8221; That&#8217;s not information delivery. That&#8217;s a decision point with pre-packaged execution. The user makes a judgment call, the system handles everything else. Communicating the decision, updating records, adjusting timelines, notifying stakeholders.</p><p>Every interaction should conclude with the work being done, not with the user having more information to act on manually.</p><div><hr></div><h2>What this means if you&#8217;re building</h2><p>If you&#8217;re building a B2B product right now, or redesigning one, a few things follow from this.</p><p><strong>Your home screen should not be a dashboard</strong>. It should be &#8220;What needs your attention right now.&#8221; Two or three cards, maximum. Everything on track is invisible.</p><p>Your primary interaction model should be conversational. A text input at the centre, not a navigation menu. &#8220;What&#8217;s behind schedule?&#8221; gets an intelligent answer. &#8220;Reassign the homepage task to Sarah&#8221; is executed, not routed to a form.</p><blockquote><p>Your notification layer is your most important surface. More users will interact through notifications than through your app. The notification isn&#8217;t a pointer to the app. The notification is the app for 90% of interactions.</p></blockquote><p><strong>Build zero permanent analytics pages</strong>. Every chart should be generated on demand in response to a question. Kill the &#8220;Analytics&#8221; tab with its 15 pre-built charts that 3% of users visit monthly.</p><p>Every piece of information should end with a suggested action. Don&#8217;t show &#8220;3 invoices are overdue.&#8221; Show &#8220;3 invoices are overdue. Payment reminders drafted. Send all three?&#8221;</p><blockquote><p>Measure <strong>decisions per minute, not time in app</strong>. Less time in your product means more value from your product.</p></blockquote><div><hr></div><h2>The uncomfortable bit</h2><p>Most B2B products being built today, including products that call themselves &#8220;AI-powered,&#8221; are designed around Stage 1 assumptions. They have dashboards. They have navigation menus. They have settings pages and configuration wizards. They&#8217;ve added an AI chat sidebar. That&#8217;s decoration.</p><p>The products that win the next decade will be designed around Stage 3 and Stage 4 from the ground up. They&#8217;ll feel less like &#8220;software&#8221; and more like &#8220;a team member who happens to be omniscient and tireless.&#8221; The interface won&#8217;t be something you learn or navigate or spend time in.</p><p>It will be something that works for you. Mostly in the background, occasionally surfacing for your judgment, always concluding with the work actually getting done.</p><p>The dashboard is dead. Not because screens are dead or because visual information is dead. But because the idea that a human should spend time navigating pre-built screens to find information and then separately act on it. That idea is dead.</p><p>What replaces it is better. Faster. Quieter. And, paradoxically, more visual than ever. Because when the system generates exactly the right visualisation for exactly the right question at exactly the right moment, the visual impact is far greater than a permanent dashboard full of charts nobody looks at.</p><p>The future of product UI isn&#8217;t no interface. It&#8217;s the right interface, at the right time, for the right person, generated in the moment it&#8217;s needed, and gone the moment it&#8217;s done.</p><blockquote><p>We&#8217;re building some of this right now. The early results are encouraging. And honestly a little unsettling. When the first thing your client says after using the new system is &#8220;I don&#8217;t feel like I&#8217;m using software anymore,&#8221; you know something fundamental shifted.</p></blockquote><div><hr></div><p><em><a href="https://www.linkedin.com/in/navneetsinghlall/">Navneet Singh</a> is the Founder &amp; CEO of Webority Technologies. He writes about engineering-first approaches to building technology companies.</em></p>]]></content:encoded></item><item><title><![CDATA[Software Is a Proxy. AI Makes It Obsolete.]]></title><description><![CDATA[Why dashboards, workflows, and "products" as we know them won't survive the next decade.]]></description><link>https://blog.navneetsingh.name/p/software-is-a-proxy-ai-makes-it-obsolete</link><guid isPermaLink="false">https://blog.navneetsingh.name/p/software-is-a-proxy-ai-makes-it-obsolete</guid><dc:creator><![CDATA[Navneet Singh]]></dc:creator><pubDate>Sun, 29 Mar 2026 14:06:20 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!VrRv!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!VrRv!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!VrRv!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png 424w, https://substackcdn.com/image/fetch/$s_!VrRv!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png 848w, https://substackcdn.com/image/fetch/$s_!VrRv!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png 1272w, https://substackcdn.com/image/fetch/$s_!VrRv!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!VrRv!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png" width="1200" height="675" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:675,&quot;width&quot;:1200,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:85204,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://blog.navneetsingh.name/i/192507356?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!VrRv!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png 424w, https://substackcdn.com/image/fetch/$s_!VrRv!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png 848w, https://substackcdn.com/image/fetch/$s_!VrRv!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png 1272w, https://substackcdn.com/image/fetch/$s_!VrRv!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb807e613-9cef-47fa-a260-cb7cbc3c8a58_1200x675.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image"><svg role="img" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg"><g><title></title><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Every piece of B2B software ever built exists for one reason: humans can&#8217;t hold enough information in their heads.</p><p>A project manager can&#8217;t track 500 tasks, their dependencies, their statuses, and their blockers simultaneously. So we built Jira. A salesperson can&#8217;t remember every interaction with every prospect. So we built CRM systems. Accountants, HR teams, marketers, all the same story. We kept building structured tools to compensate for the limits of human memory and attention.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://blog.navneetsingh.name/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The First Principles! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Every SaaS product is fundamentally a structured information proxy for humans. The UI, the database schema, the workflow engine, all of it exists because humans need structure to process information.</p><p>Now ask the uncomfortable question: what happens when AI doesn&#8217;t have those limitations?</p><p>An AI can hold the entire context of 500 tasks, their dependencies, every conversation that created them, every commit that relates to them, and every team member&#8217;s workload. Simultaneously. In memory. Without a database UI. It doesn&#8217;t need a kanban board to &#8220;see&#8221; the work. It doesn&#8217;t need a pipeline view to &#8220;understand&#8221; the sales funnel. It doesn&#8217;t need a trial balance to &#8220;know&#8221; the financial position.</p><blockquote><p><strong>The proxy becomes unnecessary</strong>. And that means the product as a category starts to dissolve.</p></blockquote><div><hr></div><h2>Three eras of software</h2><p><strong>Era 1 (1980&#8211;2010): Software as a tool.</strong></p><p>You operate it. Excel. Photoshop. Tally. AutoCAD. The human does the work, the software is the instrument. A master of Excel is more productive than a novice. You pay for what the software can do.</p><p><strong>Era 2 (2010&#8211;2025): Software as a system.</strong></p><p>You configure it. Salesforce. Jira. HubSpot. Workday. The human designs workflows, sets up automations, defines rules. The software executes them at scale. The skill shifts from operating to configuring. An entire consulting industry emerges around &#8220;Salesforce implementation&#8221; and &#8220;Jira administration.&#8221;</p><p>You pay for processes the software runs.</p><p><strong>Era 3 (2025&#8211;???): Software as an agent.</strong></p><p>You direct it. State the outcome. The AI figures out the process, executes the work, reports back. No configuration. No workflow design. No administration.</p><blockquote><p><strong>You pay for work done</strong>.</p></blockquote><p>We&#8217;re at the very beginning of Era 3. Most of the industry hasn&#8217;t figured out what that means yet.</p><p>I run a technology company. I&#8217;ve spent the last year watching our own clients ask for AI-native rebuilds of tools they&#8217;ve used for a decade. Not &#8220;add a chatbot.&#8221; Rebuild it. That&#8217;s the signal.</p><div><hr></div><h2>The Proxy Stack</h2><p>I think about this as layers. Every piece of software sits somewhere on what I call the Proxy Stack: how much stands between a human&#8217;s intent and the outcome they want.</p><ul><li><p><strong>Layer 4 &#8212; Thick Proxy.</strong> You do the work, software is the instrument. Excel, Tally, Photoshop. (Era 1)</p></li><li><p><strong>Layer 3 &#8212; Structured Proxy.</strong> You configure workflows, software executes. Salesforce, Jira, HubSpot. (Era 2)</p></li><li><p><strong>Layer 2 &#8212; Assisted Proxy.</strong> You operate the system, AI helps at the edges. Chatbot in the sidebar, auto-generated summaries. (<strong>Era 2.5</strong>)</p></li><li><p><strong>Layer 1 &#8212; Thin Proxy.</strong> You approve and direct, AI does most of the work. (Early Era 3)</p></li><li><p><strong>Layer 0 &#8212; Zero Proxy.</strong> You state the outcome, AI handles everything. (Full Era 3)</p></li></ul><p>Most of the SaaS industry right now is fighting over the move from Layer 3 to Layer 2. They&#8217;re calling it transformation. It&#8217;s <strong>a one-layer improvement while the market is heading to zero</strong>.</p><blockquote><p>The interesting question for any software product becomes simple: what layer are you on, and how fast are you moving down?</p></blockquote><div><hr></div><h2>The Era 2.5 trap</h2><p>Right now, every SaaS company is bolting AI onto their existing product. A chatbot in the sidebar. An &#8220;AI insights&#8221; panel. Auto-generated summaries. Content suggestions.</p><blockquote><p>They&#8217;re calling this &#8220;AI-powered.&#8221; It&#8217;s not. It&#8217;s <strong>Era 2 software with Era 3 marketing</strong>. Layer 3 products wearing a Layer 2 costume.</p></blockquote><p>The fundamental architecture hasn&#8217;t changed. The database schema is the same. The UI is the same. The workflow engine is the same. The user still needs to create records, update statuses, configure automations, and navigate dashboards. The AI is a feature, not the foundation.</p><p>I call this <strong>Era 2.5</strong>. And it&#8217;s a trap, because it gives incumbents the illusion of transformation while leaving them structurally vulnerable to genuine Layer 1 and <strong>Layer 0</strong> products.</p><p>The pattern is familiar. When the web emerged, most software companies built a &#8220;web portal&#8221; on top of their existing client-server architecture. It looked modern. It wasn&#8217;t. Salesforce, a true web-native architecture, ate their lunch. When mobile emerged, most companies built &#8220;responsive&#8221; versions of their desktop UIs. Instagram, Uber, WhatsApp didn&#8217;t do that. They were mobile-native from the ground up and created entirely new categories.</p><p>The same structural displacement is beginning now. It&#8217;s already starting. Klarna replaced 700 customer service agents with AI and reported the same satisfaction scores. Harvey is handling legal research that junior associates used to do. Cursor and similar tools are writing production code that ships without human review. These aren&#8217;t experiments. They&#8217;re early Layer 1 products eating into Layer 3 territory.</p><div><hr></div><h2>What Layer 0 products actually look like</h2><h3>The UI collapses</h3><p>A <strong>Layer 0</strong> product might not have a traditional UI at all. Not &#8220;minimal UI,&#8221; potentially no persistent visual interface. The interaction model is conversational plus notifications plus generated artifacts.</p><p>You don&#8217;t &#8220;open the project management tool.&#8221; You ask &#8220;what should I focus on today?&#8221; and get an answer that pulls from projects, calendar, team capacity, and deadlines. The answer IS the product.</p><p>You don&#8217;t &#8220;check the CRM.&#8221; The CRM tells you, unprompted, that your biggest prospect hasn&#8217;t responded in 12 days and drafts a follow-up referencing their Q3 budget cycle.</p><p>The entire concept of &#8220;logging into software&#8221; becomes as archaic as &#8220;dialling up the internet.&#8221;</p><p>Now, &#8220;no UI&#8221; taken literally is an overcorrection. Humans are visual. Even at <strong>Layer 0</strong>, people will want to see their financial position, see their project timeline. The difference is that these visualisations are generated on demand, not pre-built dashboards you navigate to. You won&#8217;t click through &#8220;Reports &gt; Financial &gt; P&amp;L &gt; FY 2026.&#8221; You&#8217;ll say &#8220;show me how we&#8217;re doing financially&#8221; and get something tailored to your context. The UI isn&#8217;t dead. It&#8217;s generated, not designed. Ephemeral, not permanent.</p><h3>The database becomes invisible</h3><p>At Layer 3, users interact with structured data through forms and views. Create a contact. Update a deal stage. Change a task status. Every interaction is a human translating reality into a structured record.</p><p>At <strong>Layer 0</strong>, the AI maintains structured data as a side effect of understanding unstructured reality. A conversation happened on WhatsApp, the AI extracted a task, identified the owner, estimated the effort, slotted it into the sprint. A payment arrived in the bank account, the AI matched it to an invoice, updated receivables, adjusted the cash flow forecast.</p><p>The database still exists. But no human ever touches it directly. It&#8217;s the AI&#8217;s memory, not the user&#8217;s interface.</p><p>This single shift eliminates the number one complaint about every B2B tool in existence: <strong>the overhead of keeping it updated</strong>. Nobody hates managing projects. They hate maintaining the project management tool. Nobody hates tracking sales. They hate updating the CRM. The administrative tax of structured data entry is universal friction. <strong>Layer 0</strong> removes it entirely.</p><h3>Products merge into agents</h3><p>If the UI is conversational and the database is invisible, what actually separates a &#8220;PM tool&#8221; from a &#8220;CRM&#8221; from an &#8220;accounting system&#8221;?</p><p>At Layer 3, they&#8217;re different products because they have different UIs, different data models, different workflows. You switch between applications. You export from one and import into another. You build integrations to connect them.</p><p>At <strong>Layer 0</strong>, they&#8217;re different capabilities of the same agent. &#8220;Follow up with the client&#8221; is a CRM action. &#8220;Create the invoice for that deal&#8221; is an accounting action. &#8220;Assign the implementation to the engineering team&#8221; is a PM action. But to the user, it&#8217;s one continuous conversation with one system that understands the full context.</p><p>The concept of &#8220;software categories&#8221; dissolves. CRM, ERP, HRM, PM become capabilities, not products. And the company that assembles the most comprehensive set of capabilities into a single coherent agent wins the entire enterprise software market.</p><p>Though I&#8217;d push back on myself here: some domains will resist this merger for a long time. Finance, HR, legal, healthcare, anywhere errors carry regulatory or legal consequences, the trust curve is steep. An engineer might accept AI auto-creating tasks from Day 1. A CFO won&#8217;t trust AI to auto-file tax returns until it&#8217;s proven correct for 12 consecutive months. That&#8217;s not irrational resistance. It&#8217;s appropriate caution with real stakes.</p><div><hr></div><h2>The moat shifts from product to data</h2><p>At Layer 3, the moat is the product: features, integrations, ecosystem, brand. Salesforce&#8217;s moat is its AppExchange ecosystem and millions of trained admins. Jira&#8217;s moat is deep integration with the Atlassian suite and the inertia of enterprise workflows built around it.</p><p>At <strong>Layer 0</strong>, the product layer commoditises. AI can generate UIs dynamically. Workflows configure themselves. Integrations are just API calls that an agent handles. The traditional product moat erodes.</p><p>What replaces it is accumulated domain intelligence.</p><p>An AI that has processed 10,000 Indian SMB accounting datasets understands GST edge cases that a generic AI never will. An AI that has managed 5,000 engineering sprints predicts blockers with precision a new entrant can&#8217;t match. Features can be copied overnight. Domain intelligence compounds over years.</p><blockquote><p>The implication for builders: your first 1,000 customers aren&#8217;t revenue. They&#8217;re your dataset. The competitive distance between you and a new entrant is measured in accumulated learning, not feature parity.</p></blockquote><div><hr></div><h2>The interaction frequency inverts</h2><p>This one challenges every SaaS metric we&#8217;ve been taught to worship.</p><p>Layer 3 products optimise for engagement. Daily active users. Time-in-app. Sessions per day. Product teams celebrate when users spend more time in their tool. Growth teams optimise for habit formation. The entire product strategy assumes that a &#8220;sticky&#8221; product is a good product.</p><p><strong>Layer 0</strong> inverts this completely.</p><p>The best AI agent is the one you interact with the least, because it&#8217;s handling everything autonomously. A project management system that requires zero daily interaction beats one that requires 30 minutes. An accounting system that needs one approval per day beats one demanding 2 hours of data entry.</p><p>Success is measured by the absence of human involvement, not its presence.</p><p>This breaks every SaaS business metric. DAU becomes meaningless. Time-in-app becomes a failure indicator. The companies that figure out new metrics (tasks autonomously completed, decisions made without human intervention, exceptions per 1,000 transactions) will build the products that actually matter.</p><blockquote><p>The north star for <strong>Layer 0</strong>: how much valuable work happened without anyone touching the product today?</p></blockquote><blockquote><p>And if engagement metrics break, pricing does too. Per-seat makes no sense when AI does the work of five people. The model shifts to outcomes: per transaction processed, per ticket resolved, per project managed. <strong>You pay for work done</strong>, not tools provided.</p></blockquote><div><hr></div><h2>What this means if you&#8217;re building</h2><p>If you&#8217;re building B2B software today, the strategic question isn&#8217;t &#8220;what features should we add?&#8221; It&#8217;s where are you on the Proxy Stack, and how fast are you moving down?</p><p>Sitting at Layer 3? Your window is closing. Not today, not this year, but within 3-5 years, Layer 1 alternatives will begin displacing products that require manual data entry, workflow configuration, and dashboard navigation.</p><p>Moving from Layer 3 to Layer 2? You&#8217;re buying time, not building a moat. The AI chatbot in your sidebar doesn&#8217;t change the fundamental architecture. Use the time well. Start rebuilding the foundation, not the facade.</p><p>Building for <strong>Layer 0</strong> from scratch? You have the structural advantage but face the distribution disadvantage. Incumbents have millions of users, thousands of integrations, and decades of trust. Your product needs to be dramatically better on the one dimension that matters most: <strong>elimination of human effort</strong>.</p><p>And if you&#8217;re not building software but running a business on it? Start asking your vendors a different question. Not &#8220;what features are on the roadmap&#8221; but &#8220;when does your product stop needing me to operate it?&#8221;</p><p>The transition will be slow and messy. Spreadsheets didn&#8217;t kill paper ledgers in a year. SaaS didn&#8217;t kill on-premise in a year. <strong>Layer 0</strong> won&#8217;t kill Layer 3 in a year either. Hybrid products will dominate the market for a while. Pure autonomous products will work for some use cases and fail for others.</p><p>But the direction is clear. The human-in-the-loop isn&#8217;t going away, it&#8217;s moving up. Instead of entering data and configuring workflows, humans do work that actually requires human judgment: setting strategy, making ethical calls, building relationships, evaluating ambiguity. The AI handles the structured, repeatable, process-driven layer. The human handles everything else.</p><blockquote><p>Every software category will be rebuilt around this principle. The only question is who rebuilds it first.</p></blockquote><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://blog.navneetsingh.name/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The First Principles! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><div><hr></div><p><em>Part 2 of this series is now live: <a href="https://blog.navneetsingh.name/p/software-is-about-to-stop-looking">Software is about to stop looking like software</a></em></p><p><em><a href="https://www.linkedin.com/in/navneetsinghlall/">Navneet Singh</a> is the Founder &amp; CEO of Webority Technologies. He writes about engineering-first approaches to building technology companies.</em></p>]]></content:encoded></item><item><title><![CDATA[CRED’s Identity Crisis: How a Premium Club Became a Platform Still Searching for Its Purpose]]></title><description><![CDATA[When CRED launched in 2018 under founder Kunal Shah, it carried the aura of a modern black card moment for Indian consumers.]]></description><link>https://blog.navneetsingh.name/p/creds-identity-crisis-how-a-premium</link><guid isPermaLink="false">https://blog.navneetsingh.name/p/creds-identity-crisis-how-a-premium</guid><dc:creator><![CDATA[Navneet Singh]]></dc:creator><pubDate>Sun, 14 Dec 2025 05:23:30 GMT</pubDate><content:encoded><![CDATA[<p>When CRED launched in 2018 under founder Kunal Shah, it carried the aura of a <strong>modern black card</strong> moment for Indian consumers.</p><p>When CRED launched, access was restricted to individuals with a <strong>credit score of 750+</strong>, reinforcing the idea that this was a genuine club for India&#8217;s most financially disciplined consumers.</p><p>The pitch felt simple and powerful:</p><blockquote><p>If you are financially disciplined, have a high credit score, and pay on time, you belong to an exclusive club. We&#8217;ll reward you for it.</p></blockquote><p>In spirit, it evoked the mythology of the iconic Amex Black Card: a quiet signal that you&#8217;ve &#8220;made it&#8221; financially and now get access to a different world of benefits.</p><p>CRED&#8217;s early positioning was clear:</p><ul><li><p>Aggregate India&#8217;s high&#8209;credit&#8209;score, financially responsible consumers.</p></li><li><p>Give them an elegant, reward&#8209;driven experience for paying credit card bills on time.</p></li><li><p>Build a community with trust, high spending capacity, and strong brand appeal.</p></li></ul><p>On paper, that is a powerful thesis. Capture a subset of consumers who are trusted by banks, have high scores, spend more, and likely have higher disposable income. then build premium financial services around them. The underlying bet: <strong>this audience should be monetizable at much higher margins than the typical mass&#8209;market user.</strong></p><p>In practice, CRED built something quite different.</p><h2>My Personal Experience with CRED: Why I Could Not Fully Trust It</h2><p>I signed up for CRED when it launched, partly out of curiosity and partly because I fell squarely into their target segment. I wanted to see what this &#8220;exclusive club&#8221; actually felt like from the inside.</p><p>At one point, CRED requested access to my Gmail account so it could scan card statements and provide personalized insights. I granted it briefly. just to evaluate the experience. but very quickly revoked access. The idea of giving a private company full visibility into all my emails didn&#8217;t sit well with me. It felt like too much trust, too early, without enough clarity on how my data would be used.</p><p>That moment stayed with me. It highlighted a deeper issue that ties directly into CRED&#8217;s business model:</p><blockquote><blockquote><p>If the value offered isn&#8217;t truly premium, users will hesitate to offer premium&#8209;level access.</p></blockquote></blockquote><blockquote><p>Trust is the currency of financial products. And for a platform attempting to position itself as a premium financial ally, trust must be earned with substance. not just sleek design or clever marketing.</p></blockquote><h2>Feature Timeline: How CRED Shifted Directions Over the Years (and What Each Shift Tells Us)</h2><p>To understand CRED&#8217;s <strong>identity crisis</strong>, it helps to look at its major product launches <strong>chronologically</strong>. The pattern reveals a platform trying multiple paths, each time nudging away from its original promise.</p><h3><strong>2018: The So&#8209;Called Exclusive Credit Card Bill Payment Club</strong></h3><p>CRED launches as an invite&#8209;only app for people with a <strong>750+ credit score</strong>, advertised as a premium club. although in reality, nothing inside felt genuinely exclusive.**.</p><ul><li><p>Simple value: Pay your credit card bill &#8594; earn CRED coins &#8594; redeem rewards.</p></li></ul><h3><strong>2019: Gamification Takes Over (The First Visible Drift)</strong></h3><p>CRED begins layering gamified mechanics. kill&#8209;the&#8209;bill, scratch cards, jackpots. These shifts moved the product away from being a disciplined financial club and closer to a dopamine&#8209;driven engagement app.<br>CRED starts introducing:</p><ul><li><p>&#8220;Kill the bill&#8221; games</p></li><li><p>Scratch cards</p></li><li><p>Jackpot&#8209;style campaigns</p></li></ul><h3><strong>2020: Launch of CRED Store</strong></h3><p>A marketplace redeemable through coins. but lacking anything truly exclusive. Instead of premium financial value, users saw repackaged discounts available elsewhere, weakening the club narrative.**<br>A curated marketplace of brands redeemable through coins. but almost nothing about it was truly premium. The supposed club offered no exclusive access, no elite experiences, and no member&#8209;only advantages.</p><h3><strong>2020: Introduction of CRED RentPay (Useful, But Not Premium)</strong></h3><p>A creative tool for rent payments via credit cards, but unrelated to premium benefits. It expanded utility, not exclusivity.**<br>Users could pay rent using a credit card by paying a fee.</p><h3><strong>2021: CRED Cash (Short&#8209;Term Credit That Premium Users Didn&#8217;t Need)</strong></h3><p>A lending product offering instant credit. But high&#8209;credibility users typically already access better rates from banks, making this feel misaligned with their needs.**<br>Instant credit lines offered through partner NBFCs.</p><h3><strong>2021: CRED Mint (Risky, Not Exclusive, and Not Tailored to High&#8209;Credibility Users)</strong></h3><p>Peer&#8209;to&#8209;peer lending opened a new avenue, yet introduced risk without delivering premium&#8209;grade wealth management. It felt experimental, not curated.**<br>Allowing users to lend money and earn interest.</p><h3><strong>2022: CRED Pay (Checkout Integration)</strong></h3><p>A merchant&#8209;checkout layer that positioned CRED as a payment facilitator. Useful for brands, but added no distinctive value for premium users.**<br>CRED partners with merchants to enable payment via CRED at checkout.</p><h3><strong>2022: Happay Acquisition (A Move Completely Outside the &#8220;Elite Club&#8221; Narrative)</strong></h3><p>A major entry into B2B expense management. A sharp turn away from the consumer&#8209;focused, premium&#8209;club identity.**<br>A major expansion into B2B financial operations.</p><h3><strong>2023&#8211;2024: Diversification Wave</strong></h3><p>Travel deals, dining offers, insurance, utilities. a scatter of features that broadened the platform but diluted the original promise even further.**<br>CRED begins offering:</p><ul><li><p>Travel deals</p></li><li><p>Dining experiences</p></li><li><p>Utility payments</p></li><li><p>Insurance&#8209;related products</p></li></ul><div><hr></div><h2>What CRED Actually Built: Features and Revenue Streams</h2><p>To understand the gap between promise and monetization, it helps to map what CRED has built and how it makes (or claims to make) money.</p><h3>Features and user experience</h3><p>Over the years, CRED has evolved from &#8220;pay your credit card bill and earn coins&#8221; to a broader fintech and commerce platform. The major pieces:</p><ul><li><p><strong>Credit&#8209;card bill payment hub</strong>: A single place to track multiple cards, get reminders, pay on time, and see basic analytics.</p></li><li><p><strong>Rewards and &#8220;CRED coins&#8221;</strong>: Every bill payment earns coins that can be redeemed for offers, discounts, and experiences.</p></li><li><p><strong>&#8220;Members&#8209;only&#8221; positioning</strong>: Eligibility based on credit score and branding around financial responsibility created a club&#8209;like feel.</p></li><li><p><strong>Additional verticals layered on top:</strong></p><ul><li><p>Rent payments via credit card (CRED RentPay) with convenience fees.</p></li><li><p>Short&#8209;term credit lines (CRED Cash / Stash) and peer&#8209;to&#8209;peer style products (CRED Mint).</p></li><li><p>A curated e&#8209;commerce &#8220;Store&#8221; and brand&#8209;offers marketplace.</p></li><li><p>Corporate and expense&#8209;management capabilities via acquisitions like Happay.</p></li></ul></li></ul><h3>Revenue and monetization channels</h3><p>Publicly, the monetization story looks something like this:</p><ul><li><p><strong>Brand/merchant listing fees and commissions</strong>: Brands pay to list offers, get visibility, and access this high&#8209;credit&#8209;score audience. CRED earns fees or commissions when users redeem.</p></li><li><p><strong>Transaction and processing fees</strong>: On flows like RentPay and certain payments, CRED charges convenience or service fees.</p></li><li><p><strong>Lending and interest income</strong>: From credit lines, lending products, and partnerships with banks/NBFCs.</p></li><li><p><strong>Data and user&#8209;insight monetization</strong>: In theory, enabling highly targeted access to a premium user base within regulatory bounds.</p></li></ul><h3>The financial picture in brief</h3><p>Even with growing revenue and a multi&#8209;billion&#8209;dollar valuation at its peak, CRED has consistently reported substantial operating losses. The topline is scaling; the bottom line still hasn&#8217;t convincingly followed.</p><p>So the natural question arises: <strong>If you&#8217;ve aggregated some of the country&#8217;s most creditworthy consumers, why is monetization still this hard?</strong></p><div><hr></div><h2>The Core Problem: Premium Audience, Non&#8209;Premium Value</h2><p>CRED&#8217;s thesis is straightforward: a user who is credit&#8209;worthy is more monetizable. Banks want them, brands want them, and advertisers love them.</p><blockquote><p>The catch is this: <strong>premium users expect premium value.</strong></p></blockquote><p>If what they receive, after clearing the &#8220;exclusive&#8221; bar, is an endless feed of discounts on consumer products, the experience quickly starts to feel less like a black card and more like a glorified coupon engine.</p><h3>1. The premium audience is valuable only if they feel they&#8217;re treated as premium</h3><p>The entire club narrative works only if <strong>the club feels different</strong>.</p><p>Instead of:</p><blockquote><p>&#8220;Because you&#8217;re financially solid, we&#8217;ll help you build more wealth, access better credit, and unlock superior financial opportunities.&#8221;</p></blockquote><p>the user journey often becomes:</p><blockquote><p>&#8220;Because you&#8217;re financially solid, here are some offers and cheap stuff you can buy if you redeem enough coins.&#8221;</p></blockquote><p>That&#8217;s a <strong>fundamental mismatch</strong>. You attract strong, disciplined financial profiles and then mostly nudge them to consume more, not necessarily to become <strong>richer, more secure, or more empowered</strong>.</p><h3>2. The margin economics of &#8220;cheap deals&#8221; is weak</h3><p>If your core loop is:</p><blockquote><p>pay bill &#8594; earn coins &#8594; redeem discount,</p></blockquote><p>then your economics are tied to the economics of discounts.</p><p>Deals are typically:</p><ul><li><p>Low&#8209;margin.</p></li><li><p>Often subsidized by brands as marketing spends.</p></li><li><p>Weakly linked to long&#8209;term loyalty or deep financial engagement.</p></li></ul><p>This can drive engagement and app opens, but it rarely produces <strong>high&#8209;margin, defensible revenue</strong>. You end up playing in the same arena as any rewards app or offer aggregator, just with better branding.</p><h3>3. The shift to real financial services is necessary: and difficult</h3><p>The only way to truly monetize a high&#8209;quality, high&#8209;trust user base is through <strong>financial products</strong>:</p><ul><li><p>Credit lines.</p></li><li><p>Investment products.</p></li><li><p>Insurance.</p></li><li><p>Wealth and advisory services.</p></li></ul><p>These products can deliver meaningful margin. But they also come with:</p><ul><li><p>Risk (credit risk, market risk).</p></li><li><p>Regulatory complexity.</p></li><li><p>The need for strong underwriting and data models.</p></li><li><p>Longer product cycles and slower, more disciplined growth.</p></li></ul><p>CRED has taken steps into this territory, but it&#8217;s still not clear that these initiatives have scaled to match the size and promise of the user base.</p><h3>4. Exclusivity vs scale: the strategic tension</h3><p><strong>Exclusivity is a differentiator</strong>. but it&#8217;s also a constraint.</p><p>If you insist on only the highest scores, your audience is relatively small. That&#8217;s fine <strong>if</strong> your monetization per user is strong. If it isn&#8217;t, exclusivity becomes a liability rather than a moat.</p><p>You&#8217;re then trapped between two unattractive choices:</p><ul><li><p>Loosen eligibility and dilute the premium narrative to chase volume.</p></li><li><p>Stay exclusive and accept thin monetization for a long time.</p></li></ul><p>Neither fully honors the original &#8220;elite club&#8221; story.</p><h3>5. The marketing and burn&#8209;rate trap</h3><p>Reward&#8209;driven businesses burn capital quickly:</p><ul><li><p>You subsidize user acquisition.</p></li><li><p>You subsidize rewards.</p></li><li><p>You spend on brand and advertising.</p></li></ul><p>If the monetization machine lags behind, you end up in a cycle of chasing ever more volume to justify ever more spend. without a clear path to sustainable profitability.</p><div><hr></div><h2>Where CRED Missed the Opportunity</h2><p>In my view, the real miss is simple:</p><blockquote><p>CRED figured out how to <strong>aggregate</strong> highly credible, disciplined financial users.<br>It did <strong>not</strong> figure out how to <strong>monetize</strong> them in a way that matches their profile.</p></blockquote><p>These are precisely the users who would respond to:</p><ul><li><p>Better investing options.</p></li><li><p>Sophisticated wealth&#8209;building tools.</p></li><li><p>Access to unique financial products.</p></li><li><p>Ways to optimize taxes, debt, and long&#8209;term planning.</p></li></ul><p>Instead, the experience has largely centered around:</p><ul><li><p>Games of chance.</p></li><li><p>Lucky draws.</p></li><li><p>Flashy campaigns.</p></li><li><p>A catalogue of offers that often look like the same promotions available elsewhere, repackaged inside a premium wrapper.</p></li></ul><p>It&#8217;s an <strong>emotional mismatch</strong>: for a user who sees themselves as financially solid and responsible, the platform often feels more like a gamified shopping feed than a serious financial ally.</p><div><hr></div><h2>What CRED Could Have Built Instead</h2><p>If I were building a business around high&#8209;credibility users, the design would tilt more towards <strong>wealth, leverage, and long&#8209;term value</strong>, and less towards <strong>discounts and dopamine</strong>.</p><h3>A. From &#8220;cheap deals&#8221; to &#8220;wealth&#8209;creation and financial empowerment&#8221;</h3><p>The narrative shift should be:</p><ul><li><p>From: <em>&#8220;You&#8217;ve paid your bills on time, here&#8217;s a deal.&#8221;</em></p></li><li><p>To: <em>&#8220;You&#8217;ve proven financial discipline, now we&#8217;ll help you compound it.&#8221;</em></p></li></ul><p>Concrete ways to do that:</p><ul><li><p>Curated investment products aligned to user maturity and risk profile.</p></li><li><p>Premium credit lines with clearly superior terms.</p></li><li><p>Tools for long&#8209;term wealth planning, tax optimization, and goal&#8209;based investing.</p></li><li><p>Access to alternative assets and structured products typically not marketed to the average retail user.</p></li></ul><h3>B. Embed genuinely sticky financial services</h3><p>The goal is to become the <strong>primary financial cockpit</strong> for this user segment.</p><p>That means:</p><ul><li><p>A consolidated dashboard of cards, loans, investments, and liabilities.</p></li><li><p>Intelligent nudges not just to spend but to save, invest, rebalance, and de&#8209;risk.</p></li><li><p>Monetization via:</p><ul><li><p>Advisory or subscription fees.</p></li><li><p>Asset&#8209;under&#8209;management-based income.</p></li><li><p>Premium credit lines and structured lending products.</p></li></ul></li></ul><p>Here, the revenue comes not from selling &#8220;stuff&#8221;, but from <strong>helping users manage and grow their money</strong>.</p><h3>C. Make the value exchange explicit: and premium</h3><p>A high&#8209;score user with a solid financial profile does not want to feel like just another target in an ad funnel.</p><p>The platform must answer clearly:</p><blockquote><p>&#8220;Because you are financially disciplined, what can we help you do that others cannot access?&#8221;</p></blockquote><p>A smaller set of high&#8209;quality, high&#8209;relevance benefits will outperform an endless scroll of generic offers.</p><h3>D. Drive high margin, not just high volume</h3><p>Premium audiences justify premium economics. That requires:</p><ul><li><p>Tight tracking of unit economics per user.</p></li><li><p>Ensuring each reward, campaign, or partnership has a clear business case and high&#8209;value outcome.</p></li><li><p>Lending products built with rigorous risk controls and clear margin, not just vanity volume.</p></li></ul><h3>E. Scale without diluting the club</h3><p>Exclusivity can be maintained even while scaling, if you:</p><ul><li><p>Expand into adjacent segments that are still financially strong (entrepreneurs, business owners, high&#8209;earning professionals).</p></li><li><p>Create internal tiers (for example, a more &#8220;elite&#8221; layer on top of an already strong base) with radically differentiated benefits.</p></li></ul><p>The key is that growth should not come at the cost of the brand&#8217;s core promise.</p><div><hr></div><h2>Why CRED Still Feels Stuck in the &#8220;Gap Phase&#8221;</h2><p>CRED has done the hard work of:</p><ul><li><p>Building a brand.</p></li><li><p>Acquiring a desirable user base.</p></li><li><p>Owning a mind&#8209;share position as the app for &#8220;credit&#8209;worthy&#8221; people.</p></li></ul><p>But the <strong>monetization architecture</strong> has not yet fully caught up with that ambition.</p><p>Today, the experience still leans heavily on:</p><ul><li><p>Rewards.</p></li><li><p>Offers.</p></li><li><p>Consumer spending.</p></li></ul><p>and far less on:</p><ul><li><p>Long&#8209;term wealth.</p></li><li><p>Serious financial leverage.</p></li><li><p>High&#8209;margin financial relationships.</p></li></ul><p>Until that gap closes, the business will continue to feel like a <strong>premium wrapper around a discount</strong>&#8209;driven core.</p><div><hr></div><h2>The Way Forward for CRED and for Builders Watching It</h2><p>If CRED wants to live up to the mythology it created, the shift ahead is clear:</p><ul><li><p><strong>Re&#8209;position</strong> from a reward app with elite branding to a serious <strong>financial empowerment platform</strong>.</p></li><li><p><strong>Monetize</strong> through high&#8209;margin financial products and services, not just through deals.</p></li><li><p><strong>Use rewards as a hook</strong>, not the foundation of the business.</p></li><li><p><strong>Preserve exclusivity</strong>, even as it scales into adjacent premium segments.</p></li><li><p><strong>Be radically transparent</strong> about data, insights, and how they&#8217;re used to create value for users.</p></li></ul><p>For founders, technologists, and product leaders, there&#8217;s a broader lesson here:</p><blockquote><p>Aggregating a great user base is only half the game.<br>Architecting a monetization model that genuinely respects who those users are. and what they actually need. is the other half.</p></blockquote><div><hr></div><h2>Conclusion</h2><p>CRED began as an ambitious attempt to build an exclusive club for India&#8217;s most financially disciplined consumers. On that front, it has achieved something rare: a brand that people recognize and a user base that most financial institutions would love to own.</p><p>But <strong>brand and user base are inputs, not outcomes</strong>.</p><p>The next phase demands an equally thoughtful <strong>monetization engine</strong>. one that treats high&#8209;credibility users not as a crowd to be sold discounted products, but as partners in long&#8209;term financial growth.</p><p>Whether CRED can make that leap. from rewards&#8209;driven engagement to genuine financial empowerment. will define its real legacy. If it gets this right, it will finally become what it hinted at in the beginning: not just another app on your phone, but the closest thing India has to a true, modern, digital &#8220;black card&#8221; experience for the financially disciplined.</p><div><hr></div><p><em><a href="https://www.linkedin.com/in/navneetsinghlall/">Navneet Singh</a> is the Founder &amp; CEO of Webority Technologies. He writes about engineering-first approaches to building technology companies.</em></p>]]></content:encoded></item></channel></rss>