[{"data":1,"prerenderedAt":98},["ShallowReactive",2],{"profile":3,"writing-use-case-embarrassed-by":14},{"name":4,"role":5,"tagline":6,"location":7,"contact":8},"Sankar Vema","AI Builder & Architect of Agentic Systems","I help enterprise leaders turn AI ambition into capability that actually ships.","India · open to global advisory engagements",{"email":9,"linkedin":10,"github":11,"blog":12,"twitter":13},"sankar.vema@gmail.com","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fsankarvema\u002F","http:\u002F\u002Fsankarvema.github.io\u002F","http:\u002F\u002Fsankarvema.blogspot.com\u002F","https:\u002F\u002Ftwitter.com\u002Fsansvema",{"id":15,"title":16,"body":17,"date":83,"description":23,"draft":84,"excerpt":85,"extension":86,"meta":87,"navigation":88,"path":89,"seo":90,"slug":91,"status":85,"stem":92,"tags":93,"__hash__":97},"writing\u002Fwriting\u002Fuse-case-embarrassed-by.md","The Best AI Use Case Is the One You Are Embarrassed By",{"type":18,"value":19,"toc":75},"minimark",[20,24,29,32,35,39,42,46,69,72],[21,22,23],"p",{},"Ask a leadership team for their flagship AI use case and you will hear something\nimpressive: a customer-facing assistant, a strategy copilot, a moonshot. Ask\nwhich AI use case actually paid for itself, and if they are honest, it is\nsomething they are almost embarrassed to mention. Reconciling invoices. Reading\nclaims. Tagging tickets. The boring stuff is where the money is.",[25,26,28],"h2",{"id":27},"why-the-boring-wins","Why the boring wins",[21,30,31],{},"The value of an AI use case is roughly volume times friction times repeatability.\nThe flashy use cases are usually low volume, high stakes, and full of edge cases,\nwhich is exactly where AI is hardest to trust. The unglamorous ones are the\nopposite: enormous volume, painful manual friction, and a task bounded enough\nthat a machine can do it reliably. That is the sweet spot.",[21,33,34],{},"A back-office process run ten thousand times a day, each time costing a person a\nfew minutes of tedium, is a bigger prize than a dazzling assistant used twice a\nweek. It just does not demo well.",[25,36,38],{"id":37},"the-reason-it-gets-skipped","The reason it gets skipped",[21,40,41],{},"It gets skipped for a human reason, not a technical one. Nobody gets promoted for\nautomating the invoice queue. The prestige sits on the shiny front-end. So the\nhighest-ROI work stays unfunded while the demo-friendly work absorbs the budget.\nThat is a governance failure dressed up as a roadmap.",[25,43,45],{"id":44},"what-to-do-now","What to do now",[47,48,49,57,63],"ol",{},[50,51,52,56],"li",{},[53,54,55],"strong",{},"Follow the toil, not the glamour."," List the tasks people do the most and\nenjoy the least. Your best use case is near the top.",[50,58,59,62],{},[53,60,61],{},"Score by volume times friction, not by visibility."," Pick the one that moves\na real number, even if it never makes a slide.",[50,64,65,68],{},[53,66,67],{},"Ship it quietly, then show the result."," A boring workflow in production\nteaches more, and saves more, than ten impressive demos.",[21,70,71],{},"The best AI use case in your company is probably one nobody wants to present.\nFund it anyway.",[21,73,74],{},"So which of your workflows is too boring to demo, and too expensive to ignore?",{"title":76,"searchDepth":77,"depth":77,"links":78},"",3,[79,81,82],{"id":27,"depth":80,"text":28},2,{"id":37,"depth":80,"text":38},{"id":44,"depth":80,"text":45},"2026-08-01",false,null,"md",{},true,"\u002Fwriting\u002Fuse-case-embarrassed-by",{"title":16,"description":23},"use-case-embarrassed-by","writing\u002Fuse-case-embarrassed-by",[94,95,96],"enterprise","adoption","value","LiT7M9uxlxUFom_phRYW2I4y0fTt1OiZiB-7baUccLI",1790601541773]