<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dhiraj Bhat on Medium]]></title>
        <description><![CDATA[Stories by Dhiraj Bhat on Medium]]></description>
        <link>https://medium.com/@dhirajbhat?source=rss-41451638fd93------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*DDZVJHwa-QlEyYogjRl1gQ.jpeg</url>
            <title>Stories by Dhiraj Bhat on Medium</title>
            <link>https://medium.com/@dhirajbhat?source=rss-41451638fd93------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:38:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dhirajbhat/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I Built Three AI Tools This Month. The Best Proofpoint Was When They Refused to Answer.]]></title>
            <link>https://dhirajbhat.medium.com/i-built-three-ai-tools-this-month-the-best-feature-was-the-one-that-refused-to-answer-30edfdb9ac80?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/30edfdb9ac80</guid>
            <category><![CDATA[claude-skills]]></category>
            <category><![CDATA[sales-engineering]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Fri, 24 Jul 2026 05:28:19 GMT</pubDate>
            <atom:updated>2026-07-24T05:33:48.465Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I built three of them this month. Writing the prompt was the </em><strong><em>easy part</em></strong><em> every time.</em></p><p>Everyone keeps promising me that AI will automate the boring parts of my job. Mostly true. The problem is that the boring parts were never the parts that mattered. Moving into a forward facing SE role in my new job has taught me that, quick.</p><p>In Go To Market, the work that actually moves a deal is judgment work. Scoring a demo. Getting an exec ready for a review. Answering an RFP without promising something the company can’t ship. There is no button for that, because “<strong><em>good</em></strong>” keeps moving, and getting it wrong costs you quietly. The deal stalls weeks later and nobody can reconstruct why.</p><p><strong>So this month I built three of these.</strong> Not clever prompts. Real tools, with opinions baked in. Every one taught me the same thing from a different angle. In a GTM org, a skill is not a macro. It is a small product. It needs a definition of done, a golden dataset, and a way to test itself, or it is a confident guess with better formatting.</p><h4>Here is what each one taught me about B2B sales 😆</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/0*3Uhn6E2CUqkIQ6VE.jpg" /></figure><h3>Film Room</h3><p>Athletes watch film. Sales engineers mostly don’t. We run a demo, get a gut feeling, and move to the next one. The feedback loop was broken in two places: it was subjective, and it was late.</p><p>Film Room watches the tape back with you. It scores the demo against a rubric, pulls the specific moments worth stealing or fixing, and hands you something you can give your manager. The choice that made it more than a scorecard: the rubric shifts by who is in the room. A technical deep-dive and a vision pitch to an executive are not the same demo, so they are not scored the same way. It also grades the product from the same tape, not just the rep, so the tool that coaches the human also tells you where the AI itself fumbled. A coaching tool became a product-feedback pipe by accident. (The good features usually are.)</p><p>Where it is now: in use, and stuck on the honest part. Calibration. Making a score from one person mean the same thing as the same score from another. That is the unglamorous middle of the project, and it is where the real learning lives.</p><h3>The exec-review skill.</h3><p>Executive time is the most expensive resource in the building. When prep is inconsistent, the review turns into the exec doing the assembly live. What is the actual ask. What is blocking it. What do you need from me. You just spent your most expensive hour on reconstruction.</p><p>I built a skill that preps a topic for review the way one leader actually wants it. The right layers, the right order, evidence where he expects evidence, everything else cut. This one forced me to encode taste, which is harder than it sounds. A good review is a standard that lives in one person’s head. Turning that into something repeatable meant sitting with him, watching what he kept and what he cut, and writing it down. The skill is not useful because the model is smart. It is useful because it carries one person’s definition of good and applies it the same way every time.</p><h3><strong>The RFP skill</strong></h3><p>RFPs are where <strong><em>confident hallucination gets you in real trouble</em></strong>. The pressure is to fill every box. The temptation is to write the thing that sounds right. But an RFP answer is a claim you will be held to long after the deal closes.</p><p>The skill’s job was leverage without lying. Answer from what is true and defensible. When there is no clean answer, say so and route it to a human, instead of inventing one. The hardest requirement was not fluency. It was refusal. The most valuable thing this skill does is know the edge of what it can safely claim and stop there. A tool that fills every field beautifully is worse than one that leaves blanks, because it manufactures commitments nobody signed off on.</p><blockquote>The pattern : When people hear “AI skill” they picture automating a repetitive task. Push a button, the rote thing gets done. Fine for grunt work. Judgment work <strong>does not</strong> automate the same way, and if you want a tool to do it, you need three things that look more like building a product than writing a shortcut.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FiFGBG74hkKRCFa1HXu%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fdigi995-yes-iFGBG74hkKRCFa1HXu&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExbzhpZHR6ZHV2M3VmNjAzY3FqaW1sMjR4NjkwdWtyNDV6M3gyZHNwNSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FiFGBG74hkKRCFa1HXu%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/1cc46bc15d8267e145fd8b76415e2ea4/href">https://medium.com/media/1cc46bc15d8267e145fd8b76415e2ea4/href</a></iframe><p><strong>A definition of done. </strong>A written standard for what a good output looks like: the structure, what counts as evidence, what gets cut, what the tool should refuse to do. Most people skip this because it is the hard part. In all three of mine, writing down what “good” meant was harder than building the thing that produced it.</p><p><strong>A golden dataset. </strong>Real examples where you already know the answer, so you are measuring against reality instead of your own taste on a given afternoon.</p><p><strong>Evals.</strong> A test you can run again and again, so you catch the tool drifting before your customer does. This is where most AI-at-work projects quietly die. They ship the demo, skip the test, and never notice when the outputs slowly start making things up.</p><p>There is a fourth thing I did not expect…</p><blockquote>The best behavior is often refusal.</blockquote><blockquote>The RFP skill’s best feature is knowing what not to answer. The exec skill’s is flagging what is missing instead of papering over it. A judgment tool that never says “I don’t know” is not confident. It is dangerous.</blockquote><p>Automating a task is easy. Encoding judgment is a product problem, and it has a spec: a definition of done, a golden dataset, evals, and the nerve to leave a box empty. Do that work and your skill becomes something you would stake a deal on. Skip it and you have built a very articulate way to be wrong.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30edfdb9ac80" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Anthropic Logo Is Not the Moat]]></title>
            <link>https://dhirajbhat.medium.com/the-anthropic-logo-is-not-the-moat-e738fd808af4?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/e738fd808af4</guid>
            <category><![CDATA[anthropic-claude]]></category>
            <category><![CDATA[anti-money-laundering]]></category>
            <category><![CDATA[llm-evaluation]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Thu, 14 May 2026 04:20:17 GMT</pubDate>
            <atom:updated>2026-05-14T05:09:31.726Z</atom:updated>
            <content:encoded><![CDATA[<p>FIS announced an AI agent for AML investigations last week. Anthropic’s name is in the headline. BMO and Amalgamated Bank are the design partners. <strong>The stock jumped 5–6%.</strong></p><p>Everyone is looking at the wrong thing.</p><p>In my opinion, the Anthropic logo is the <strong>least defensible part</strong> of this announcement. Claude is accessible via API. So is GPT-5.5. So will be whatever ships next quarter. The reasoning layer is a commodity with a nice press release attached.</p><h3><strong>What FIS built is not.</strong></h3><p>The actual work is the layer nobody writes press releases about:</p><p>a. The data pipelines that feed the agent</p><p>b. The governance architecture that keeps decisions auditable and regulators happy,</p><p>c. The evals that determine whether “compresses investigations from days to minutes” means the agent is actually right or just confidently fast.</p><p>That layer is hard. It takes domain depth, institutional trust, and years of accumulated signal about what financial crime actually looks like in practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OHShRIiZCKuNc7zM" /><figcaption>Photo by <a href="https://unsplash.com/@solenfeyissa?utm_source=medium&amp;utm_medium=referral">Solen Feyissa</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We’ve spent the better part of the last few years living in that layer. Not the demo layer. The “our exam dataset has a 40% label error rate and now we need to decide what to tell the model” layer. The “the regulator wants to see the decision trail and we have to actually produce it” layer.</p><p>Here’s the analogy I keep coming back to. Professional kitchens got access to the same gas ranges at roughly the same time. The Michelin stars did not distribute evenly. The range is not the variable. The mise en place is the variable. What you’ve prepped, how you’ve organized it, whether you’ve done this dish a thousand times before — that’s what separates the output. The AI agent is the range. The data and the governance and the evals are everything else.</p><p>This matters especially in AML, where the ground truth is murky, the false positive rate is a business problem with regulatory consequences, and the SAR narrative isn’t just a summary — it’s a legal document. Getting that right requires more than a capable model. It requires knowing which signals are actually predictive, which typologies map to which customer segments, and how to structure the output so a compliance officer can stake their name on it. None of that lives in the reasoning layer.</p><p>The FIS announcement signals something real about where financial crime technology is going. Core processors are going to be the distribution layer for banking AI, and the “agent bundled with your core” pitch is genuinely hard to beat on procurement cost and regulatory posture alone. What it doesn’t signal is that the hard work is done. The hard work is barely started. The data quality, the evals rigor, the governance design — that’s the work that will separate the implementations that hold up under examiner scrutiny from the ones that don’t.</p><p>I find that genuinely exciting. Not because I like hard problems (although I do, a little). Because the layer where this gets won or lost is the layer I understand best.</p><blockquote>The logo gets you in the room. The evals keep you there.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e738fd808af4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three Stars Apart.]]></title>
            <link>https://dhirajbhat.medium.com/three-stars-apart-d5cc5dc1834b?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5cc5dc1834b</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[job-search]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Fri, 08 May 2026 00:21:54 GMT</pubDate>
            <atom:updated>2026-05-08T19:12:51.492Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>I’ve spent half a decade building fraud and trust products. I underestimated hiring fraud. Here’s what I found going deep on it.</em></h4><p>I’ve been in fraud and trust products for over half a decade. Mostly fintech. AML. Sanctions. The kind of work where the user of the product (a fraud investigator) and the buyer of the product (their VP of Risk) sit one chair away from each other. <strong>Same building. Same incentives. Same vocabulary.</strong></p><p>Hiring fraud is different.</p><blockquote>(Before I went deep on it, I would have told you it was just KYC for jobs. I would have been wrong.)</blockquote><p>The buyer is a Head of HR or Talent Operations. The user is a candidate. They are not in the same building. They are not on the same call. They are barely on the same internet.</p><p>I went deep on this for two weeks and came out with a number that won’t leave my head: three stars.</p><p>That’s roughly the gap between how employers rate background-check tools on G2 and Capterra (averaging above 4 / 5) and how candidates rate the same tools on Trustpilot and BBB (averaging closer to 1.5 / 5). Pick any major player in the category. The pattern holds.</p><p>Same products. Same week. Different reviewers. Three stars apart.</p><p>You can argue the methodology however you want. Trustpilot self-selects toward the angry. G2 self-selects toward the engaged buyer. Discount by a full star either way. You’re still looking at a gap that would tank a consumer product overnight.</p><p>The B2B world has gotten away with it because the candidate isn’t the customer. The HR team is. The candidate’s review doesn’t show up on the procurement spreadsheet. The candidate’s UX doesn’t have a board metric. The candidate’s churn lives in someone else’s KPI dashboard.</p><p>It worked. For a long time, it worked.</p><p>It’s not going to keep working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pxNHPNcnDl9iIITe" /><figcaption>Photo by <a href="https://unsplash.com/@zulfugarkarimov?utm_source=medium&amp;utm_medium=referral">Zulfugar Karimov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Three things are converging</h3><p><strong>One: The candidate has the megaphone now.</strong></p><p>A frustrated candidate ten years ago wrote a complaint to HR and forgot about it. A frustrated candidate today writes a Trustpilot review, posts on r/recruitinghell, screenshots it on LinkedIn with a hot take. The asymmetry of complaint cost has flipped. It’s harder NOT to post than to post.</p><p><strong>Two: Hiring fraud is exploding.</strong></p><p>I checked in with a Staff PM at a major sourcing platform. He said application volumes are up 25% year over year, driven almost entirely by candidates feeding the JD and a resume into an LLM and generating fabricated experience. That’s the new entry-level fraud playbook. Free. Scalable. Indistinguishable from the real thing without good signal.</p><p>The corollary: Every false positive at the verification stage costs the candidate three to five extra days of waiting. Every false negative costs the employer a bad hire. Both numbers climb. Both reviews get worse.</p><p><strong>Three: The buyer is losing confidence too.</strong></p><p>This is the part that surprised me.</p><h3>In a 3,000-manager survey published earlier this year, 70% of HR leaders said they believe hiring fraud is underestimated. 62% said job seekers can fake identity better than employers can detect it. Only 19% said they were “extremely confident” in their current verification process.</h3><p>That’s the buyer telling you, on the record, that they don’t trust the tool they’re paying for.</p><h3>Where this lands</h3><p>We have a category where the user hates the experience, the fraud is winning, and the buyer is losing confidence. Three-star gap, climbing.</p><p>The lazy answer is “ship better candidate experience.” More transparent flag reasons. Faster appeal pathways. A real human to talk to. All true. All necessary. All not enough.</p><p>The harder answer is structural. Background-check products were architected as gates. A flag fires, the candidate sits, the HR team adjudicates, the answer comes back days later. That worked when fraud was rare and signals were high quality. It doesn’t work when 25% YoY volume growth hits a model that can’t differentiate stolen real identities from data-integrity hiccups, while the candidate has Trustpilot open in another tab.</p><p>The architecture has to shift from gating to triaging. Every flag lands in a tiered output. Most cases auto-resolve in minutes. The genuinely ambiguous get human review. The actively malicious get escalated. The candidate sees a status update, not a void. The HR team sees a queue, not a pile.</p><p>And the platforms in this space have to start treating candidate experience as a category metric, not a department metric.</p><h3>Why I care</h3><p>I’m not in this industry. My career is fintech, fraud, AML. But the more I look at hiring, the more it looks like consumer banking did in 2014. A regulated category. A buyer-led product surface. A user that everyone forgot about. Then fintech showed up and ate the experience layer in five years.</p><p>Hiring is next. The signs are already there. ATS-native players have launched their own fraud signals(I corroborated this, too). New Layer 2 specialists are building synthetic-ID and deepfake-interview detection. The incumbents in this space aren’t asleep, but they’re being measured against a buyer-only scorecard while the user keeps a separate ledger.</p><p>The three-star gap is the leading indicator. Until it closes, every product roadmap in this category should be evaluated against one question:</p><h4><em>Does this make the candidate hate us less?</em></h4><p>That’s the next decade’s playbook. Outrun the competitor on the candidate side, not just the buyer side.</p><p>I started by looking at a calibration problem inside a fraud-detection model. I came out the other end thinking about a category-wide UX bankruptcy.</p><p>Three stars apart.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5cc5dc1834b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I versioned my job search like software. It’s at v4.2.]]></title>
            <link>https://dhirajbhat.medium.com/i-versioned-my-job-search-like-software-its-at-v3-5-7e9055b0c270?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e9055b0c270</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[claude-code]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Mon, 13 Apr 2026 21:05:46 GMT</pubDate>
            <atom:updated>2026-04-15T22:04:16.654Z</atom:updated>
            <content:encoded><![CDATA[<p>My job search has a changelog, a backlog, and a 191-kilobyte state file. I realize this makes me sound like a specific kind of unhinged. Bear with me.</p><p>Here’s the thesis, stated early because life is short: most people treat a job search like a thing that happens to them. PMs should treat it like a thing they ship.</p><p>I don’t mean “be more organized” or “use a spreadsheet.” I mean the actual mental model. The skills you’re trying to prove in interviews, user empathy, data-driven iteration, shipping under uncertainty, are the same skills that make the search itself work. And if you can’t run a good process for yourself, why would anyone believe you can run one for their users?</p><p>Let me show you what I mean.</p><h3>The state file</h3><p>A few months ago I built an <a href="https://dhirajbhat.medium.com/i-built-a-job-search-coach-with-claude-code-no-engineers-were-harmed-f8ac17d41ddc?postPublishedType=repub">interview coaching system on top of Claude Code</a>. Not an app. Not a chatbot. A set of markdown files that read a persistent state file, do their job, and write back. Think of it as a product with <strong><em>one user</em></strong> (me) and <strong><em>zero investors</em></strong> (also me).</p><p>That state file, `coaching_state.md`, is now 191kb. It holds my storybank, interview scores across five dimensions, every company I’m talking to, a contact network with promise tracking, my positioning statement, an outcome log, and a narrative consistency checker that flags when I tell contradictory versions of “Why are you leaving?” to different companies.</p><p>This is not a to-do list. It’s a product database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*i5ZeJq1WKsQEVPUJ" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">charlesdeluvio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>And here’s the PM parallel that took me embarrassingly long to see: your job search has state whether you track it or not. Pipeline stages. Recruiter promises. Which version of your “career narrative” you told which company. The question is whether you’re querying that state or guessing at it. I was guessing for the first two weeks. It went about as well as you’d expect.</p><h3>The backlog</h3><p>The system has 28 commands now. Each one exists because I kept hitting the same wall.</p><p>`map` exists because every session started with the same question: “What should I do next?” So I built a command that reads the full coaching state, runs a priority check (is there an interview in 72 hours? a stale recruiter promise? a transcript I haven’t scored?), and tells me the one or two things that actually matter this week.</p><p>`round` exists because after every real interview I was running three commands in sequence: capture impressions, score the transcript, check for state drift. Three commands doing related work on the same event. So I collapsed them into one.</p><p>`sync` exists because my state got inconsistent. Loop marked “active” but the outcome log said rejected. Scheduled interview date passed with no outcome recorded. The kind of drift that happens when you’re juggling six companies and your brain is doing context-switching at a rate it was not designed for.</p><p>None of these were planned. They were reactions to friction. And that’s the PM instinct I want to name: you don’t build features because they sound good on a roadmap. You build them because your user (you) keeps stubbing their toe on the same rock. The backlog isn’t aspirational. It’s empirical.</p><h3>The versioning</h3><p><strong>v1</strong> shipped with 16 commands and a scoring rubric. It was a hypothesis: can a persistent coaching system that learns from each interview actually improve performance over time?</p><p><strong>v2</strong> didn’t add surface area. It went deeper. Transcript parsing across eight formats (Otter, Zoom, Google Meet, Grain, Teams, and three others). Outcome calibration loops that detect whether my practice scores actually predict real interview results. Story-to-question mapping that treats my storybank like a portfolio allocation problem, not a grab bag.</p><p><strong>v3</strong> went wide. Resume optimization. LinkedIn coaching. Outreach sequencing. JD decoding. Salary scripting. Every surface where I interact with the job market, not just the interview itself.</p><p><strong>v3.3</strong> was a single feature: the `round` command I mentioned. One workflow replacing three. It was the smallest version and the most satisfying.</p><p><strong>v3.5</strong> added archetype detection. Is this a Platform PM role or a Founding PM role? Different archetypes need different stories, different framing, different questions. Detected once, cascaded everywhere.</p><p><strong>v4</strong> was the one I didn’t see coming. The system worked. The coaching was good. But every outreach message, every resume bullet, every pitch draft still came back sounding like AI wrote it. Competent, polished, but absolutely not <strong><em>me</em></strong>. So I built a <strong>writing quality gate</strong> that reads my ‘voice-and-style’ file (which may or may not have had a hand in this blog…..) and enforces my actual writing patterns: sentence rhythm, humor register, thesis placement, the whole thing. The system now sounds like its user, not its engine. Which, if you think about it, is the most product-manager version of the problem possible. The feature works, but the voice is wrong. Ship a fix.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R1oQ_F_KY4IdoxMbR42E7w.png" /><figcaption>Long,painful and fun.. as God intended software to be</figcaption></figure><p>Each version solves a category of problem discovered by actually using the previous version. This is not a novel insight. This is just product management. But most people don’t apply it to themselves.</p><blockquote>Your pitch at the start of a search should not be the same pitch six weeks in. If it is, you’re not iterating. You’re just repeating.</blockquote><h3>The outcome loop</h3><p>Here’s where it gets uncomfortable (in a good way).</p><p>After three or more real interviews, the system runs scoring drift detection. My practice scores said I was a 4.2 on Substance. My actual outcomes said otherwise. The system flagged the gap and recalibrated.</p><p>Stories have deployment analytics. Per-story advance rate: how often a story was deployed AND the candidate advanced, divided by total deployments. I know which stories work, not which stories I enjoy telling. Those are very different lists.</p><p>Most job seekers optimize for comfort. They tell the stories they like, prep the questions they can already answer, and practice formats they’re already good at. PMs optimize for outcomes. The difference is measurement. And measurement requires state. Which brings us back to the 191-kilobyte file.</p><h3>The kicker</h3><p>I’ve been in product for a while. I’ve built roadmaps, run sprint retros, argued about prioritization frameworks, and shipped features to millions of users. But the most clarifying product experience I’ve had recently was running my own job search like a product org.</p><p>Not because the tool is clever <strong><em>(it’s a bunch of markdown files and a large language model, let’s not get carried away)</em></strong>. But because the exercise forced me to practice what I preach. Persistent state. Empirical backlogs. Outcome-driven iteration. Honest measurement, especially when the numbers aren’t flattering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VbNfP1OgnGBoUXXlry7zCA.png" /></figure><blockquote>The job search isn’t preparation for the job. It is the job.</blockquote><p>And if the process you run for yourself doesn’t reflect the process you’d run for a team, maybe the gap isn’t in your interview answers. Maybe it’s in the mirror.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e9055b0c270" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trust Is the Moat. The Model Isn’t.]]></title>
            <link>https://dhirajbhat.medium.com/trust-is-the-moat-the-model-isnt-4518d0e8aa97?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/4518d0e8aa97</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 21:11:27 GMT</pubDate>
            <atom:updated>2026-04-06T21:17:42.349Z</atom:updated>
            <content:encoded><![CDATA[<p>I sat down with Justin Leibow on the Products That Count podcast recently to talk about building AI products in high-trust environments. Thirty minutes later, we’d covered everything from fraud networks to the future of consulting. But the thread that kept pulling was this one:</p><blockquote>The companies that win in AI will be the ones that build the best systems around the models. Not the ones with the best models.</blockquote><p>That probably sounds backwards to anyone following the frontier race. New model drops every few weeks. Benchmarks move. Everyone updates their pitch deck. But if you’ve spent time shipping AI into regulated industries (I’ve spent five years doing this at Unit21), you learn something quickly: the model is the easiest part to swap out. The trust is not.</p><h3>PMs Are Becoming System Designers</h3><p>I started my PM career the traditional way. Talk to customers, write flow diagrams, ship features, iterate. I kind of miss the flow diagrams, honestly. But that version of product management is quietly disappearing.</p><p>Today, the job looks more like being a GM for a system. You’re not just deciding what to build. You’re deciding what architecture the AI operates within, what guardrails it needs, how it integrates into workflows people already trust, and what happens when it’s wrong. That’s systems thinking, not feature thinking.</p><p>Every PM in the next three to five years will face this shift. The ones who lean into it will compound. The ones who keep optimizing buttons will wonder what happened.</p><h3>Meet People Where They Are</h3><p>Here’s a thing I’ve seen work repeatedly: don’t ask your customer to adopt a new trust paradigm just so you can ship faster.</p><p>When we deployed AI at Unit21, we didn’t show up saying “here’s our model, sign this DPA, trust us.” We said “you’re already on AWS. You already trust Bedrock’s security posture. We operate within that boundary.” The conversation shifted from “should we trust this AI?” to “what can this AI do for us?”</p><p>Same principle applied when building our fraud consortium. We didn’t ask members to share raw data across organizations (that conversation would have died in legal). We built privacy-preserving systems that let companies collaborate without exposing what they weren’t comfortable exposing. The trust layer became the product’s moat.</p><p>If you’re building AI products and your go-to-market requires customers to make a new trust decision before they can even evaluate the product, you’ve already lost most of the room.</p><h3>The ‘Middle of the Pyramid’ Collapses</h3><p>Here’s where it gets interesting for <strong>knowledge work</strong>. AI isn’t going to replace the top of the consulting pyramid (strategic judgment, relationship context, creative synthesis). And it’s not going to replace the bottom (implementation, execution, hands-on-keyboard work).</p><p>It’s going to collapse the middle.</p><p>The PowerPoint isn’t the value anymore. What used to take a team of analysts weeks to produce, a model can draft in hours. But here’s the thing: previously, a consulting engagement might give you one big recommendation with sub-actions beneath it. Now you can prototype three strategic scenarios and simulate outcomes for each. The client makes a decision grounded in something closer to reality, not a slide.</p><p>The people who thrive will be the ones who can frame the right questions for AI to answer, then exercise judgment on the output. That’s the new middle.</p><h3>The Trust Cycle</h3><p>I don’t think trust in AI moves in a straight line. I think it moves in waves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0vmvblqGPRv8jG9-EMFQjw.png" /><figcaption>In AI, the moat isn’t the model. It’s the system around it</figcaption></figure><p>Right now we’re on the upswing. People are giving AI more decisions, more autonomy, more access. That will continue. But at some point, something breaks at scale. A data leak. A liability question nobody planned for. A decision that an AI made autonomously that shouldn’t have been autonomous.</p><p>When that happens, the pendulum swings back. Human judgment becomes premium again. Not because AI got worse, but because we’ll rediscover that oversight and architecture matter more than raw capability.</p><p>Every high-trust industry and workflow will run on human-supervised AI systems. The differentiator won’t be the quality of the model. It will be the quality of the oversight. The quality of the system around the model.</p><p>That’s what I’d tell any PM building in this space</p><blockquote>Your job isn’t to ship the smartest AI. Your job is to build the system that makes AI trustworthy. That’s where the lasting value lives.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4518d0e8aa97" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Asked Siri for Directions Three Times. It Sent Me to Three Different Wrong Restaurants.]]></title>
            <link>https://dhirajbhat.medium.com/i-asked-siri-for-directions-three-times-it-sent-me-to-three-different-wrong-restaurants-0ea588a15ef0?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ea588a15ef0</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[siri]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Wed, 01 Apr 2026 20:10:12 GMT</pubDate>
            <atom:updated>2026-04-06T21:14:46.299Z</atom:updated>
            <content:encoded><![CDATA[<p>Not three attempts at the right restaurant with slight variations. Three completely different restaurants. In a row. From the same request.</p><p>“Navigate to [pizza place] using Apple Maps.”</p><p>Attempt one: “Getting directions to Round Table Pizza.”</p><p>No. I said the name. The specific name. Try again.</p><p>“Navigate to [pizza place] using Apple Maps.”</p><p>Attempt two: “Getting directions to Carmo Pizza and Pasta.”</p><p>Different wrong answer this time. At least it’s still pizza, I guess? One more shot.</p><p>“Navigate to [pizza place] using Apple Maps.”</p><p>Attempt three: “Getting directions to Bona Pizza Cardona.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*x3hg6b4_cG6zFkPf" /><figcaption>Induces anger every time</figcaption></figure><p>To get it wrong consistently is one thing. To get it wrong uniquely each time deserves a special place in hell. Siri didn’t even commit to being wrong the same way twice.</p><p>This is the state of voice AI in 2026 from a company with a $3 trillion market cap.</p><h3>The Part That Actually Matters</h3><p>I don’t care that Siri got it wrong. Getting things wrong is normal. Every voice assistant has failure cases, and pizza place names are legitimately hard to parse.</p><blockquote><strong>What I care about is that Siri got it wrong <em>differently every time.</em></strong></blockquote><p>That’s not a recognition problem. That’s a system that has no memory, no consistency, and no ability to learn from a correction that happened five seconds ago. You’d think the third attempt would at least narrow the search space. It didn’t. The third answer was the most wrong of the three.</p><p>Compare this to what’s happening in the rest of the industry. Claude can hold context across a million tokens. ChatGPT remembers your preferences across sessions. Perplexity will search, reason, and cite sources in the time it takes Siri to misidentify a restaurant. Google’s Gemini is processing multimodal inputs that would have been science fiction two years ago.</p><p>And Siri is out here playing restaurant roulette.</p><h3>The Timeline Problem</h3><p>Apple announced “Apple Intelligence” in June 2024. The WWDC demo was impressive. Siri accessing your emails, pulling flight data, planning lunch. It looked like the future.</p><p>Then we learned the demo surprised Apple’s own Siri team, because they had never seen working versions of those capabilities. The most impressive features were effectively mock-ups presented on a stage to millions of people.</p><p>The real features got delayed. First to late 2025. Then to spring 2026. Then the AI chief, John Giannandrea, announced his retirement.</p><p>If you’re keeping score: it’s been almost two years since the announcement, and the most visible AI feature on the most popular phone in the world still can’t navigate to a pizza place on the third try.</p><h3>Why This Is Different From Other Apple Stumbles</h3><p>Apple has had slow product cycles before. Maps was a disaster at launch and eventually became good. The butterfly keyboard was a years-long mistake that they fixed. Even MobileMe existed and they recovered.</p><p>The difference now is that the competitive landscape isn’t waiting. When Maps launched badly in 2012, Google Maps was the only real alternative and it wasn’t innovating at a breakneck pace. Apple had time to catch up.</p><p>AI in 2026 is not that landscape. OpenAI, Google, Anthropic, and a dozen well-funded startups are shipping meaningful capabilities on a weekly cadence. The gap isn’t closing. It’s widening. And unlike Maps, where Apple controlled the default on every iPhone, voice assistants are increasingly replaceable. ChatGPT already has a voice mode that works. Gemini is built into Android. The “just use Siri because it’s there” inertia is eroding.</p><h3>The Real Concern</h3><p>Here’s what actually worries me. Apple’s entire AI strategy is predicated on privacy. The pitch is: we process things on-device, we don’t send your data to the cloud, and that’s why you should trust us.</p><p>That’s a legitimate differentiator. I buy it. Privacy matters.</p><p>But privacy as a feature only works if the product is good enough to use. Nobody cares about the privacy advantages of a system that sends them to three different wrong restaurants. The privacy argument becomes a rationalization for a product that doesn’t work, not a feature of a product that does.</p><p>“At least it didn’t send your pizza preferences to a data broker” is cold comfort when you’re parked in front of Bona Pizza Cardona wondering what happened.</p><h3>What Would Actually Fix This</h3><p>Apple doesn’t need to build GPT-9. They need to fix the basics.</p><p>Session memory. If I ask for the same thing three times, the third attempt should at least know the first two failed. Context persistence across a 30-second window is not a hard technical problem.</p><h4>Disambiguation. When the system isn’t confident, ask. “I found a few options near you. Did you mean…” is infinitely better than confidently routing me to the wrong place.</h4><p>Correction learning. If I repeat the same request, that’s a signal. Use it.</p><p>None of this requires a trillion-parameter model. It requires product thinking. The kind of product thinking Apple used to be famous for. The kind where someone sits in a room and says “what happens when the user asks for the same thing three times and we get it wrong every time?” and then they fix it before it ships.</p><h3>The Kicker</h3><p>I eventually typed the address into Apple Maps manually. It worked fine.</p><p>The irony of a voice assistant that forces you back to typing is probably not lost on anyone. But it should be especially not lost on Apple, a company that once made “it just works” the most powerful three words in technology.</p><p>Three tries. Three different wrong restaurants.</p><p>It just works.</p><p>Sources:</p><ul><li><a href="https://www.cnbc.com/2025/03/07/apple-delays-siri-ai-improvements-to-2026.html">Apple delays Siri AI improvements to 2026 — CNBC</a></li><li><a href="https://www.macrumors.com/2025/04/10/chaos-behind-siri-revealed/">Report Reveals Internal Chaos Behind Apple’s Siri Failure — MacRumors</a></li><li><a href="https://www.cnbc.com/2025/12/17/apple-ai-delay-siri.html">Apple punted on AI this year. Next year will be critical — CNBC</a></li><li><a href="https://www.webpronews.com/apples-siri-ai-revamp-delayed-to-2026-amid-skepticism-and-rival-gains/">Apple’s Siri AI Revamp Delayed to 2026 — WebProNews</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ea588a15ef0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I built a job search coach with Claude Code. No engineers were harmed.]]></title>
            <link>https://dhirajbhat.medium.com/i-built-a-job-search-coach-with-claude-code-no-engineers-were-harmed-f8ac17d41ddc?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8ac17d41ddc</guid>
            <category><![CDATA[claude-skills]]></category>
            <category><![CDATA[ai-product-management]]></category>
            <category><![CDATA[claude-code]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Wed, 11 Mar 2026 17:41:00 GMT</pubDate>
            <atom:updated>2026-03-11T17:43:14.441Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ll be honest with you — I didn’t set out to build a product.</p><p>I set out to stop giving terrible interview advice to people I actually care about. The “just be yourself” kind of advice that sounds reassuring and accomplishes nothing.</p><p>So I built something instead. And the part that still surprises me: the whole thing is markdown files.</p><p><strong>What does “building with Claude Code” even mean?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/793/1*CtHP_cjkKw3vjlgENyeF3A.png" /><figcaption>Look ma, no coding!</figcaption></figure><p>Claude Code (if you haven’t played with it yet — go, I’ll wait) is Anthropic’s AI coding assistant that runs in your terminal or IDE. Most people use it to write code faster. That’s fine! But there’s a less obvious use: you can give Claude a CLAUDE.md file that acts as its persistent instructions — a system prompt that loads every time you open a project folder.</p><blockquote><strong>I used that to build a coaching system.</strong></blockquote><p>Not a chatbot. Not a prompt collection. A coaching <em>system</em> — with 23 commands, persistent state across sessions, a storybank, scoring logic, and interview lifecycle management from “I just saw a job posting” to “I just got an offer.”</p><p>The only code in the entire thing? None. It’s markdown all the way down.</p><p><strong>What does it actually do?</strong></p><p>You open a Claude Code session and type kickoff. It asks for your resume, your target role, and your timeline. Then it builds your profile, assesses where you&#39;re starting from, and gives you a prioritized action plan. Not a generic checklist — a ranked list based on your actual gaps.</p><p>From there, you’ve got commands for everything:</p><ul><li>prep Stripe — runs company research and generates a role-specific brief before your interview</li><li>mock behavioral — runs a full mock interview, scores each answer across five dimensions, and gives you the honest interviewer inner monologue (what they were actually thinking while you spoke)</li><li>analyze — paste a transcript from Otter or Zoom, it auto-detects the format and tells you exactly what broke down and why</li><li>stories — builds a storybank of STAR stories with what I call &quot;earned secrets&quot; — the non-obvious insight that makes a story memorable instead of forgettable</li><li>negotiate — walks you through a real offer negotiation with exact scripts</li></ul><p>And because this is Claude Code, everything saves to a coaching_state.md file. Your scores, your storybank, your active interview loops, your patterns. Next session picks up exactly where you left off. No re-explaining context. No starting over.</p><p><strong>Why markdown and not a “real” app?</strong></p><p>A few reasons, some principled and some lazy (I’ll let you guess which).</p><p>The “principled” one: the barrier to building AI tools just collapsed, and most people haven’t noticed yet. You don’t need a backend. You don’t need a database. You don’t need a React frontend with a loading spinner. You need a clear mental model of what you’re building, a disciplined way of expressing it, and a model smart enough to execute it.</p><p>The lazy one: I have a day job.</p><p>The thing that genuinely surprised me is how much structure matters more than code. Getting the scoring logic right, designing the command routing, thinking about what state needs to persist — that’s the real work. Claude handles the execution. The thinking is still yours.</p><p><strong>Is this actually good?</strong></p><p><strong>I mean — I think so? (Biased, obviously.)</strong></p><p>What I know for sure: generic interview prep is broken. Most of it is “here are 50 common questions, practice them.” That’s not coaching. Coaching is figuring out <em>why</em> your answers keep landing flat — is it that you’re not going deep enough on the substance? That you’re answering the question you wanted instead of the one that was asked? That your stories are technically correct but completely forgettable? Those are different problems with different fixes, and no question bank will tell you which one you have.</p><p>The coach does.</p><p><strong>Try it yourself</strong></p><pre>npx skills add dbhat93/job-search-os</pre><p>Then open any Claude Code session and type /coach → kickoff.</p><p>The full system is on GitHub at <a href="https://github.com/dbhat93/job-search-os">dbhat93/job-search-os</a>. It’s free, open source, and — in a delightful twist of fate — it’s now listed in two of the largest Claude Code skills collections on the internet, one with 23,000 stars.</p><p>Not bad for a folder of markdown files.</p><blockquote>The real lesson isn’t about job searching. It’s that the gap between “I have an idea” and “I built the thing” just got a lot smaller. You don’t need an engineering team. You need a clear head and a well-organized folder.</blockquote><blockquote><em>Until next time!</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8ac17d41ddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who doesn’t love a personal scam story?]]></title>
            <link>https://dhirajbhat.medium.com/who-doesnt-love-a-personal-scam-story-0ff2b8ecaa80?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ff2b8ecaa80</guid>
            <category><![CDATA[scam]]></category>
            <category><![CDATA[claude-code]]></category>
            <category><![CDATA[identity-theft]]></category>
            <category><![CDATA[fraud]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Mon, 16 Feb 2026 19:38:25 GMT</pubDate>
            <atom:updated>2026-02-19T19:49:19.660Z</atom:updated>
            <content:encoded><![CDATA[<h3>Who doesn’t love a personal scam story? ft Claude Code</h3><p>I’ve been quiet on this front for a little while, but sometimes life wakes you up.. when you’ve already been awake since 4am for an India vs Pakistan cricket match on a lazy rainy Sunday.</p><p>Through my time at Unit21, I went through different phases of how I felt about my job, and what it meant for my self-worth. Started off being like “Oh nice, typical Bay Area SaaS, will be great to learn” and as I got deeper into the world, began to go into “If we actually succeed, we <em>can</em> make a meaningful dent in illicit activities” territory.</p><p>With that backdrop, my Sunday afternoon made me feel at first, really afraid and eventually really good about what I’ve spent the last five years of my life on:</p><blockquote>Combating fraud, scams and money laundering at scale for some of the best financial platforms around. At Unit21, I’ve worked with over 100 financial institutions building systems to detect and stop scams before money moves.<br>And yet — for 30 seconds on a Sunday afternoon — I felt a flicker of doubt.</blockquote><h3>A scam attempt, told in 2 parts</h3><blockquote>Unfortunately for unsexy bloggers (me) no one likes reading anymore… so I worked through a way to make it interactive and fun using Claude Code.</blockquote><figure><img alt="https://dbhat93.github.io/scam-story/" src="https://cdn-images-1.medium.com/max/1024/1*MKrqG4CWGvBALNprMbXlhQ.png" /><figcaption><a href="https://dbhat93.github.io/scam-story/">Open the Clickthrough here to try it out!</a></figcaption></figure><p>Here’s what this exercise taught me about B2B product marketing:</p><p><strong>Nothing, </strong><a href="https://dbhat93.github.io/scam-story/"><strong>I just like using tech</strong></a><strong>, so leave me alone OK?</strong></p><h4>The setup</h4><p>It started off with a phone call (on a Sunday, reiterating) claiming that I had a major issue/ escalation linked to me and that I either had to come into the <a href="https://www.cgisf.gov.in/">Consulate General of India</a>, in SF or to deal with this ‘quickly and over the phone’. It was a local 415 number, which dropped and then I got another call from a different 415.</p><p>According to this ‘official’ (they used names of real officials listed on the CGISF website) I had a phone number in India based in New Delhi that was apparently linked to fraud, scams and ‘illegal’ activity in September 2025, when I was in the US. Apparently this was flagged to India’s Ministry of External Affairs. When I stated that I was not in India at the time(by the way, def was skeptical throughout) they led me to believe it was a case of identity theft. Then, he connected me to his ‘superior’ from the CGI (also a real name of an official) who claimed that this was real and that I had to urgently get a<a href="https://en.wikipedia.org/wiki/No_Objection_Certificate"> No Objection Certificate</a> from the New Delhi police to avoid any issues for me. Eventually I got impatient and started asking him for several layers of verification — what is the consulate address? what’s your badge number? He increasingly grew animated but to his credit remained somewhat calm.</p><p>Eventually I dropped the hammer:</p><blockquote>“Thanks for your scam attempt, I know this game and will report you”</blockquote><p>Guess what? He kept going, and telling me that <em>I </em>was being irresponsible ignoring a Government official. Then, I ‘calmed down’ and said OK, I can speak to the Delhi police, I need help. He offered to connect me via a secure line and to ask for NOC immediately. Made me take down notes, told me the shop address of the SIM Card purchase, with a Case number et al. Check it out — if you can read my non-print writing of course.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u3FQkGPPqjIJ8MVPGgSSrw.jpeg" /><figcaption>I’ve redacted the real official’s name, but everything else is as I heard it!</figcaption></figure><h4>The move</h4><p>‘Senior Officer’ pressed some buttons on his phone, and ‘<strong>securely connected me’</strong> to the Delhi police, all while the phone was still connected to a US 415 line?</p><p>Then, I spoke to the “New Delhi Police” who said “You need to get on a video call” and guess what, they video called me immediately via Whatsapp, no warning whatsoever. The WhatsApp profile had a legitimate looking display picture of New Delhi police. The video call could totally be mistaken for being legit, except for the lovely daylight on the person’s face at 2:45AM IST.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F5120823&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fsleepy-tomandjerry-%25D9%2586%25D8%25A7%25D8%25B9%25D8%25B3-onnato-gif-5120823&amp;image=https%3A%2F%2Fmedia.tenor.com%2F4SDGbkjv5YgAAAAN%2Fsleepy-tomandjerry.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/5461bf25169208ef0ac2033ec287fa06/href">https://medium.com/media/5461bf25169208ef0ac2033ec287fa06/href</a></iframe><p>Everything else — backdrop, uniform etc looked legitimate. When I asked if he was comfortable talking to me at 2:45 AM, he said “This isn’t a hospital, police is 24/7”. I also(of course) ran a reverse search in the background against the “Delhi police” phone number, which turned out to be linked to several scams. <strong>Rookie move…</strong></p><p>Oh, and his name was <a href="https://www.reddit.com/r/todayilearned/comments/ccn7yf/til_that_the_name_used_by_the_indian_legal_system/">“Ashok Kumar”, i.e., the “John Smith” of India</a>. This was definitely the endgame, and for me, the beginning of my planned ending to this scam.</p><p>He said he wanted to take a statement from me and for this, I needed to be in solitude, with a clear background, live verification using a Government issued ID with no background noise. At this point, I’d had enough. Blocked all the numbers, made some coffee and then wrote this blog!</p><h4>The lessons</h4><ul><li><strong>Fear is the scammer’s best weapon.</strong> By connecting YOUR identity to criminal activity, they trigger panic. You stop thinking critically and start thinking about self-preservation.</li><li>The classic problem-solution setup: Create urgency, then offer to be the helpful guide. <strong>Real authorities provide reference numbers</strong> and ask YOU to contact them through official channels.</li><li>Scammers research real names, addresses, and titles from public government websites. <strong>Familiarity is NOT proof of legitimacy.</strong> Always verify independently — look up the real number yourself and call back.</li><li>No legitimate police or government agency conducts identity verification via impromptu video calls. This is an attempt to capture your ID documents on camera for identity theft. <strong><em>Ironic eh?</em></strong></li><li><strong>Threats of arrest or warrants are high-pressure manipulation tactics.</strong> Real law enforcement follows proper legal procedures — they don’t threaten you into compliance over a video call.</li><li>THE BIGGEST RED FLAG: <strong>Demanding isolation. Scammers need you alone so no friend, family member, or colleague can break the spell.</strong> Any “official” demanding you can’t tell anyone is almost certainly a scammer.</li></ul><blockquote><em>The irony isn’t that they tried to scam someone who works in fraud.The irony is that this tactic probably works on intelligent, capable people every day.</em></blockquote><blockquote><em>Scams don’t target stupidity.</em></blockquote><blockquote><em>They target emotion.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ff2b8ecaa80" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Big 4 ‘AI’ Consulting firms?]]></title>
            <link>https://dhirajbhat.medium.com/the-big-4-ai-consulting-firms-926c6159000a?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/926c6159000a</guid>
            <category><![CDATA[bain]]></category>
            <category><![CDATA[mckinsey]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[bcg]]></category>
            <category><![CDATA[consulting]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Wed, 03 Sep 2025 04:30:53 GMT</pubDate>
            <atom:updated>2025-09-03T04:30:53.710Z</atom:updated>
            <content:encoded><![CDATA[<p>For generations, MBA students (…. perhaps another piece coming on <strong>that) </strong>and business studies graduates have had their equivalent of the Big Tech (FAANG) destinations — the Big 3 strategy consulting firms — Bain &amp; Co, McKinsey and BCG.</p><blockquote>Not to be confused with the Big 4 (PWC, E&amp;Y, Deloitte and KPMG) that provide a wide range of services like auditing, tax and technology consulting arms.</blockquote><p>I get that its still quite confusing — so I built out an interactive <a href="https://dhiraj-bhat-strategy-canvas.netlify.app/">Strategy Canvas</a> (click through it — its fun!) as to where I see the relative position of each org in the value chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tf0Q8dgmtYQNkXPKVA2u4w.png" /><figcaption><a href="https://dhiraj-bhat-strategy-canvas.netlify.app/">It’s interactive!</a></figcaption></figure><h3>Why it’s changing</h3><p>Well.. there was some pretty transformative tech that has launched in the last 3–4 years that has the potential to flip the entire industry around.</p><p>ChatGPT (have you heard of it?) and all its other evil AI friends are coming for us all, and none more so than the traditional business models of the world’s McKinseys.</p><p>Here’s why</p><p>McKinsey and their ilk prided themselves on providing expertise, guidance, coaching and action plans to the biggest, baddest enterprises in the world. A lot of their expertise has led to great innovation, and some…</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/ChrisJBakke/status/1932311114521747798&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/2aae1cad317811d938fe3cf3c313d5a5/href">https://medium.com/media/2aae1cad317811d938fe3cf3c313d5a5/href</a></iframe><p>On the other hand, here are some <strong><em>actually</em></strong> great examples:</p><ul><li>McKinsey used what they called a GANDALF(Google, Amazon, Netflix, Apple, Linkedin, Facebook) strategy to lead DBS Bank’s digital transformation in the 2010s. This resulted in the current state, wherein digital revenue is 2x that of traditional customers</li><li>Aviva Insurance enlisting McKinsey’s <a href="https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/the-organization-blog/become-flexible-and-speed-up-with-a-helix-model-part-one?utm_source=chatgpt.com">double helix approach</a> to drive a reduction in claims costs by using 90+ specialized ML models, which resulted in claims costs dropping 11% over the following six months.</li><li>Bain partnered with <a href="https://investor.uber.com/news-events/news/press-release-details/2025/Uber-Expands-AI-Data-Platform-to-Power-Next-Gen-Enterprise-and-AI-Lab-Needs/default.aspx">Uber on a transformative AI and Data Platform</a> project. Bain co-developed Uber’s <strong>Michelangelo</strong> ML platform, which manages over 5,000 models producing 10 million predictions per second. This embedded AI across the business, from ride matching to enterprise solutions, enabling Uber to become a global leader in AI innovation.</li></ul><h3><em>These weren’t just slide decks. They were real, industry-shaping transformations. But here’s the uncomfortable truth: if you can distill those lessons into playbooks, datasets, and models… what happens when AI delivers 90% of that analysis in seconds — at a fraction of the cost?</em></h3><p>Think about it. For decades, armies of 24-year-olds with fresh MBAs would descend on client sites, crank through Excel, run regressions, interview executives, and eventually distill it all into a 200-page deck. Today, most of that “heavy lift” can be done in hours (minutes?) with a reasonably well-trained <strong>AI stack.</strong> No flights to client HQ. No midnight pizza in war rooms. Just prompts, datasets, and simulations.</p><p>As a fun sidebar, I added an example AI stack below to augment these tasks — I probably can’t get to<strong><em> 90%</em></strong>, but it’s a good framework :)</p><p><a href="https://festive-hornet-50b.notion.site/AI-Powered-Consulting-Workflows-for-B2B-SaaS-1ba8c094196a80f8b7ebd883704cfdf2">🚀 AI-Powered Consulting Workflows for B2B SaaS | Notion</a></p><p>Boards have never wanted a three-month engagement to tell them what they already suspect — they want an answer <strong><em>yesterday</em></strong>, and AI doesn’t have a billing rate. It doesn’t sleep. It doesn’t second-guess itself after six rounds of internal reviews. That’s the existential threat.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F978532213316794273&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fterminator-terminator-robot-looking-flex-cool-robot-gif-978532213316794273&amp;image=https%3A%2F%2Fmedia.tenor.com%2FDZRx3RAGN6EAAAAN%2Fterminator-terminator-robot.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/673f0848feb3910ffaec161e09c4dd8d/href">https://medium.com/media/673f0848feb3910ffaec161e09c4dd8d/href</a></iframe><p>But here’s the nuance: AI can’t yet replace the political capital, the subtle stakeholder management, the coaching and storytelling that make strategies stick. McKinsey doesn’t just sell “answers.” It sells credibility. When a CEO waves around a McKinsey slide deck, that carries boardroom gravity AI alone can’t match… yet.</p><p>Which brings me to the fun part — if we were to sketch out a new “Big 4 of AI Consulting,” who makes the cut? <strong>OpenAI</strong> (know them?) is the obvious candidate, not as a consultant per se, but as the infrastructure that’s already rewriting how analysis gets done. <strong>Palantir</strong> is embedding AI decisioning directly into the arteries of enterprise ops. <strong>Accenture</strong> has bet the farm on AI training 250,000 people. And then there’s <strong>Bain </strong>themselves<strong>, </strong>who<strong> </strong>cut an early deal with OpenAI — essentially trying to straddle both worlds before LLMs eat their lunch.</p><p>So maybe the right question isn’t “will AI kill McKinsey?” but “who do MBA grads in 2030 want on their resume — McKinsey, or OpenAI?”</p><p>If history is any guide, disruption doesn’t politely knock on the door — it kicks it down. Just as the FAANGs reshaped what “dream jobs” looked like for the prior generation, firms that crack the AI–consulting code will redefine prestige in business careers. The future Big 4 might not wear suits or churn out slide decks at all. They might look more like product companies than partnerships. And that’s the uncomfortable reality for today’s incumbents: the battle isn’t about who has the smartest people in the room : it’s about who has the smartest machines — and who knows how to make them sing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=926c6159000a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agents won’t be your moat]]></title>
            <link>https://dhirajbhat.medium.com/agents-wont-be-your-moat-f81d888b88a7?source=rss-41451638fd93------2</link>
            <guid isPermaLink="false">https://medium.com/p/f81d888b88a7</guid>
            <category><![CDATA[generative-ai-tools]]></category>
            <dc:creator><![CDATA[Dhiraj Bhat]]></dc:creator>
            <pubDate>Wed, 05 Mar 2025 13:07:48 GMT</pubDate>
            <atom:updated>2025-04-15T03:40:46.186Z</atom:updated>
            <content:encoded><![CDATA[<p>AI Agents: They’re everywhere. I’d be remiss if I didn’t write about them. Companies, much like me, are having the FOMO (Fear of Missing Out) hit them hard — and they’re all putting the work in.</p><p>For the uninitiated: What are AI Agents? For the rest of you, this is merely <strong>“AI Agent definition #527951751”</strong>… skip away!</p><blockquote>An AI Agent is an application of Generative AI that is designed to understand its parameters and constraints, process bits of information <em>under</em> those parameters and take actions or generate outputs to achieve specific goals. Depending on the complexity and sophistication, it can operate autonomously or semi-autonomously.</blockquote><p>Put even simpler….</p><blockquote>It’s a virtual assistant that is designed by you, for you and operates within the boundaries that you define.</blockquote><p>Naturally, in the world post the furious innovation in the realm of Large Language Models (LLMs), there have been a few models (and thereby, the companies behind them) that have risen to the top (<strong><em>And might I add, new tech supervillains</em></strong>) : OpenAI’s ChatGPT, Anthropic’s Claude, Meta’s Sonar and Google’s Gemini. More recently, a model based out of China, DeepSeek R1 has <a href="https://www.foxbusiness.com/technology/deepseek-ai-chatbot-burst-scene-fears-about-overblown">exploded on to the scene</a>.</p><p>Within that, the stack of LLM applications have been written about quite well and in-depth, particularly on X.</p><p>Going back to our focus area for this post: AI Agents. The simplest, best way to learn and understand this is to go back to the hottest startup in internet Search - Perplexity AI and what they did for their customers’ holiday shopping needs -&gt; They built out a <a href="https://techcrunch.com/2024/11/18/perplexity-introduces-a-shopping-feature-for-pro-users/">shopping assistant Agent all within their app</a>. I built a very basic, easy-to-follow click-through to explain what the basic components are:</p><p><a href="https://nimble-churros-35f860.netlify.app/">Vite + React + TS</a></p><h3>So.. where <em>is the industry, really</em>?</h3><p>AI has grown at an exponential rate in the past 24 months. Investment in AI <a href="https://www.linkedin.com/news/story/ai-spending-soars-500-to-138b-6242884/">topped $13B in 2024</a>, and shows no sign of slowing down — in fact, quite the opposite. Naturally, as companies have learned more and more about areas of business that can be augmented or supercharged with AI, specifically ‘<a href="https://medium.com/towards-data-science/agentic-mesh-the-future-of-generative-ai-enabled-autonomous-agent-ecosystems-d6a11381c979">Agentic</a>’ AI, they have flocked to invest in developing<strong><em> their own agents.</em></strong></p><p>Some common use cases that may already even be making their way into our day-to-day lives:</p><ul><li>Shopping assistants (as evidenced above)</li><li>Travel planning</li><li>Customer support and IT help desk functions</li></ul><h3>Do AI Agents represent a competitive advantage?</h3><h4>No. The adoption curve for AI has been quite rapid, which means Agents alone won’t be enough to acquire and retain customers.</h4><p>I’ll get into why below. To be clear, in my opinion, while AI Agents can help lock in customers, retaining them becomes orders of magnitude easier if these Agents are woven into a broader ecosystem, inherently making them more integrated. (Think AirPods pairing with your iPhone❤)</p><p>To get a benchmark and a sense of how it looks, I asked ChatGPT to help me build out a plot. Below is what I asked for :</p><blockquote>You are playing the role of a Data Visualization expert in this prompt.</blockquote><blockquote>How long did Cloud storage for software products take to gain adoption? For instance.. How long did it take to go from 5% Cloud based product adoption to 70%?</blockquote><blockquote>Once you have this, I’d like you to trace product adoption for Generative AI across industries since the launch of ChatGPT. As your final output, give me a diagrammatic representation to show the relative speed of adoption between the two. I realize Generative AI may not be at the same level of adoption as where Cloud has gotten to today, but the curve would be good to trace. Use any public information to make this determination. If you are stuck, ask questions Instead of inventing data.</blockquote><h4>It did a good job of not inventing data.. It asked for a couple of clarifications:</h4><p><em>1. </em><strong><em>Cloud Storage for Software Products:</em></strong></p><p><em>• When you say “Cloud storage for software products,” are you referring to the broader SaaS adoption or specifically to cloud storage services ?Do you have a particular set of products or a time period in mind for this adoption curve?</em></p><p><em>2. </em><strong><em>Generative AI Adoption:</em></strong></p><p><em>• For tracing Generative AI adoption across industries since ChatGPT’s launch, are you interested in metrics such as user engagement numbers, enterprise adoption rates, or another form of adoption measurement? Are there specific industries or data points you want to highlight?</em></p><p><em>3. </em><strong><em>Diagrammatic Representation:</em></strong></p><ul><li><em>Would you like a comparative plot (e.g., a line chart) that shows the adoption curves for Cloud-based products and Generative AI on the same timeline, or would you prefer separate visuals?</em></li></ul><p>Here’s what I ended up with :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a9oF8VJz3wYzi2JqE9F0CQ.jpeg" /><figcaption>SaaS adoption seems to have been a slow burner compared to Gen AI…. and by a distance</figcaption></figure><p>Armed with this data, I feel even more strongly about my premise -&gt; Companies, specially those in the Business-to-Business realm, shouldn’t merely rely on their adoption of AI as a moat… at least, not for long.</p><p>While AI Agents are becoming increasingly common, the differentiation can be found in the ways companies integrate these agents into their overall ecosystems. For instance, end-to-end solutions that tie together data, customer usage patterns and go across product lines can create a much more compelling and longer-lasting competitive advantage that goes beyond simply offering AI features.</p><p>With AI going as far as to be assistive in its own implementation<em> (say, using </em><strong><em>Cursor</em></strong><em> to make API calls to OpenAI) </em>the software development cycles are speeding up at a rate we’ve not seen before. As AI features become the new commodity, I’d expect to see companies rushing to reinvent their business models — think of it as the ‘subscription twist’ on the classic one-time sale.</p><blockquote>What isn’t changing? The product <em>innovation cycle</em></blockquote><p>I still believe the best products are born from looking into genuine customer pains. Just because they can be built quicker doesn’t mean they’re going to turn out better. Simply try <a href="https://www.google.com/search?q=air+frying+vs+microwave+cold+pizza&amp;oq=air+frying+vs+microwave+cold+pizza&amp;gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIICAEQABgWGB4yDQgCEAAYhgMYgAQYigUyDQgDEAAYhgMYgAQYigUyDQgEEAAYhgMYgAQYigUyDQgFEAAYhgMYgAQYigUyDQgGEAAYhgMYgAQYigUyCggHEAAYgAQYogQyCggIEAAYgAQYogQyCggJEAAYgAQYogTSAQg2NDcyajBqN6gCALACAA&amp;sourceid=chrome&amp;ie=UTF-8">air frying a cold pizza instead of microwaving it</a>, and you’ll see <em>exactly</em> what I mean.</p><p>Air fryers aside, I bring this up because I also thought about <strong>customer <em>adoption </em>cycles</strong>— are our customers really ready for this rapid pace of change? The learning curve and integration challenges might just slow down the honeymoon period.</p><p>If, like me — you’re building out a product stack, your motto should be “Come for the AI Agents, stay for holistic solution(s)” — could work the other way, too!</p><p>Some examples come to mind</p><ul><li>(From last week) Google embedding Gemini into things like a Google Meet, bringing transcription into GSuite without the need for third-party transcription products. (<strong><em>Say goodbye to Gong</em></strong>)</li><li>Microsoft (unsurprisingly) providing AI into their trusted set of tools (<strong><em>Come for the copilot, stay for Office 365</em></strong>)</li></ul><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f81d888b88a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>