[{"data":1,"prerenderedAt":278},["ShallowReactive",2],{"blog-\u002Fblog\u002Fbuild-vs-buy-ai-feature":3,"blog-surround-\u002Fblog\u002Fbuild-vs-buy-ai-feature":257,"blog-related-\u002Fblog\u002Fbuild-vs-buy-ai-feature":266},{"id":4,"title":5,"audience":6,"body":10,"cluster":221,"contentRole":222,"conversionGoal":223,"cornerstone":224,"date":225,"description":226,"draft":224,"extension":227,"factCheckedAt":222,"faq":228,"featured":224,"language":222,"meta":238,"navigation":239,"order":240,"originalAsset":222,"path":241,"pillar":242,"primaryKeyword":243,"publicationOrder":244,"relatedProject":222,"releaseScope":222,"reviewCycle":245,"reviewMethod":246,"reviewStatus":247,"reviewedAt":225,"reviewedBy":248,"searchIntent":249,"seo":250,"sources":222,"stem":251,"tags":252,"type":255,"updated":222,"__hash__":256},"blog\u002Fblog\u002Fbuild-vs-buy-ai-feature.md","Build vs Buy an AI Feature: Model, API or Off-the-Shelf?",[7,8,9],"indie-founder","solo-developer","product-builder",{"type":11,"value":12,"toc":212},"minimark",[13,21,26,48,110,114,128,136,140,143,163,166,170,182,186,194,197],[14,15,16,20],"p",{},[17,18,19],"strong",{},"The AI build-vs-buy call has three options, not two — build your own model, call a hosted model API, or buy an off-the-shelf tool — and for almost every solo builder the right default is: buy the intelligence, build the product around it."," The mistake I see most is treating \"build vs buy\" as \"train my own model vs use someone else's,\" when the real decision is where you spend your scarce effort. Here's how I actually make the call.",[22,23,25],"h2",{"id":24},"the-three-options","The three options",[27,28,29,36,42],"ul",{},[30,31,32,35],"li",{},[17,33,34],{},"Build your own"," — train, fine-tune or self-host a model, or write a heavy custom pipeline. Maximum control, maximum ongoing cost.",[30,37,38,41],{},[17,39,40],{},"Buy the intelligence, build the product"," — call a hosted model API (the Claude\u002FGPT tier) and put your work into the product wrapped around it. This is the default.",[30,43,44,47],{},[17,45,46],{},"Buy off-the-shelf"," — use a mature tool or SaaS that already does the job. Least effort, least differentiation.",[49,50,51,67],"table",{},[52,53,54],"thead",{},[55,56,57,61,64],"tr",{},[58,59,60],"th",{},"Option",[58,62,63],{},"You spend on",[58,65,66],{},"Right when…",[68,69,70,84,97],"tbody",{},[55,71,72,78,81],{},[73,74,75],"td",{},[17,76,77],{},"Build your own model",[73,79,80],{},"Training, infra, ongoing ops",[73,82,83],{},"You have a real data moat, cost-at-scale, or a hard latency\u002Fprivacy\u002Foffline need",[55,85,86,91,94],{},[73,87,88],{},[17,89,90],{},"API + your product",[73,92,93],{},"The product: problem, workflow, decisions",[73,95,96],{},"Almost always — the intelligence is a component, not the point",[55,98,99,104,107],{},[73,100,101],{},[17,102,103],{},"Off-the-shelf tool",[73,105,106],{},"Integration only",[73,108,109],{},"The job is a commodity and not your differentiator",[22,111,113],{"id":112},"why-api-your-product-is-the-default","Why \"API + your product\" is the default",[14,115,116,117,122,123,127],{},"A hosted model gives you frontier capability for the price of a call. Spending months to train your own to match it is, for nearly everyone, ",[118,119,121],"a",{"href":120},"\u002Fblog\u002Fwhy-most-ai-built-apps-feel-like-demos","building a demo of the wrong thing"," — effort poured into a component instead of the product. The product isn't the model; it's the problem you chose, the outcome you defined, and the ",[118,124,126],{"href":125},"\u002Fblog\u002Fhow-i-use-ai-without-letting-ai-decide","human decisions the AI never makes for you",". That's the part no API ships, and the part your users actually pay for.",[14,129,130,131,135],{},"The failure mode on this side is the thin wrapper: you buy the intelligence and add nothing around it, so you've got a feature anyone can clone. Buying the model is the default ",[132,133,134],"em",{},"because"," it frees you to build the part that's hard to copy — not as a substitute for building it.",[22,137,139],{"id":138},"when-to-actually-build-your-own","When to actually build your own",[14,141,142],{},"Building your own model is right when you can name the specific reason an API can't serve you:",[27,144,145,151,157],{},[30,146,147,150],{},[17,148,149],{},"A genuine data advantage"," — you have proprietary data that makes a tuned model materially better, and that edge is your product.",[30,152,153,156],{},[17,154,155],{},"Cost at real scale"," — you're at a volume where per-call pricing genuinely dominates and owning the model pays for its own operation.",[30,158,159,162],{},[17,160,161],{},"A hard constraint"," — latency, privacy, on-prem or offline requirements an external API can't meet.",[14,164,165],{},"If you can't state which of these applies, you don't have a reason yet — you have a preference, and it's an expensive one.",[22,167,169],{"id":168},"when-to-just-buy-off-the-shelf","When to just buy off-the-shelf",[14,171,172,173,176,177,181],{},"If the job is a commodity that isn't your differentiator — transcription, generic summarisation, a standard extraction — and a mature tool already does it well, buy it and move on. You build where the intelligence ",[132,174,175],{},"is"," the product and buy where it's plumbing. Treating everything as build is how a solo project runs out of time before it ships; the discipline is the same ",[118,178,180],{"href":179},"\u002Fblog\u002Fhow-i-scope-an-mvp","ruthless scope-cutting"," the rest of the build needs.",[22,183,185],{"id":184},"the-honest-answer","The honest answer",[14,187,188,189,193],{},"Build vs buy for AI isn't \"my model vs theirs\" — it's where your effort earns the most. Default to buying the intelligence and building the product; build your own model only when you can name the moat, cost or constraint that demands it; buy off-the-shelf when the job is plumbing. Get that split right and the AI is a component in a product with a point — which is the whole ",[118,190,192],{"href":191},"\u002Fblog\u002Fmy-product-operating-system","operating system"," this sits inside.",[195,196],"hr",{},[14,198,199],{},[132,200,201,202,206,207,211],{},"Part of ",[118,203,205],{"href":204},"\u002Ftopics\u002Fbuilding-ai-products","Building AI Products",". Pressure-test the idea itself with the ",[118,208,210],{"href":209},"\u002Ftools\u002Fai-product-idea-scorecard","AI product idea scorecard",".",{"title":213,"searchDepth":214,"depth":214,"links":215},"",2,[216,217,218,219,220],{"id":24,"depth":214,"text":25},{"id":112,"depth":214,"text":113},{"id":138,"depth":214,"text":139},{"id":168,"depth":214,"text":169},{"id":184,"depth":214,"text":185},"comparison",null,"ai-idea-scorecard",false,"2026-07-29","Build your own model, call a hosted API, or buy an off-the-shelf tool? A solo builder's framework for the AI build-vs-buy call — and when each is the right one.","md",[229,232,235],{"question":230,"answer":231},"Should I build my own AI model or use an API?","For almost every solo builder and early product, use a hosted model API and put your effort into the product around it. Training or self-hosting a model is a big, ongoing cost that only pays off with a specific reason — a genuine data advantage, cost at real scale, or hard latency, privacy or offline constraints an API can't meet. Until you can name that reason, building your own model is buying a problem, not a moat.",{"question":233,"answer":234},"When does it make sense to buy an off-the-shelf AI tool instead?","When the job is a commodity that isn't your differentiator — transcription, generic summarisation, a standard classification — and a mature tool already does it well. Buying there frees your time for the part only you can build. You build when the intelligence IS the product; you buy when it's plumbing.",{"question":236,"answer":237},"What's the default AI build-vs-buy choice?","Buy the intelligence (a hosted model API), build the product (the judgement, the workflow, the decisions around it). The model is a component; the product is what you wrap around it — the problem you chose, the outcome, and the human decisions the AI never makes for you. Get that split wrong and you either reinvent a model you didn't need or ship a thin wrapper with no point.",{},true,5.7,"\u002Fblog\u002Fbuild-vs-buy-ai-feature","building-ai-products","build vs buy AI feature",185,"annual","editorial","reviewed","Tan Gravam","informational-commercial",{"title":5,"description":226},"blog\u002Fbuild-vs-buy-ai-feature",[242,253,254,221],"ai","build-vs-buy","text","pErt2nLkLBiC7qnYVZSKprdx3maIFk8JTXUdVc2179w",[258,262],{"title":259,"path":260,"stem":261,"type":255,"language":222,"draft":224,"children":-1},"The Best Treasury Management System: How to Choose by Category and Fit","\u002Fblog\u002Fbest-treasury-management-system","blog\u002Fbest-treasury-management-system",{"title":263,"path":264,"stem":265,"type":255,"language":222,"draft":224,"children":-1},"Build vs Buy a Treasury Management System","\u002Fblog\u002Fbuild-vs-buy-treasury-management-system","blog\u002Fbuild-vs-buy-treasury-management-system",[267,270,274],{"path":191,"title":268,"description":269},"My Product Operating System for Building Multiple AI Apps","The product operating system I use to build several focused AI products solo: choosing which problem to build, shipping fast, and killing what isn't working.",{"path":271,"title":272,"description":273},"\u002Fblog\u002Fhow-i-decide-whether-an-ai-product-idea-is-worth-building","How I Decide Whether an AI Product Idea Is Worth Building","How to decide what product to build: the short filter I run every idea through — real recurring problem, one-sentence outcome, small enough to ship solo.",{"path":275,"title":276,"description":277},"\u002Fblog\u002Fwhy-i-write-the-expected-output-before-the-screen","Why I Write the Expected Output Before the Screen","Define the outcome before design: I write the exact result the user should get before building any screen, because the screen is only the path to an outcome.",1785306775976]