# Buy AI Tools or Build Your Own?

When an off the shelf AI tool is enough, and when the workflow demands building into your own systems. A decision rule with the honest cost math for both.

<link rel="stylesheet" href="?v=">

<section class="gs-hero">
  <div class="container">
    <div class="gs-breadcrumb">
      <a href="/">Density Labs</a> <span>/</span> Resources <span>/</span> Buy vs Build
    </div>
    <h1>Buy AI tools, or <em>build your own</em>?</h1>
  </div>
</section>
<style>.cmp-table{width:100%;border-collapse:collapse;font-size:14px;margin:8px 0 28px}.cmp-table th,.cmp-table td{border:1px solid var(--line);padding:12px 14px;text-align:left;vertical-align:top;line-height:1.5}.cmp-table th{font-family:var(--font-mono);font-size:11px;letter-spacing:.14em;text-transform:uppercase;background:var(--paper-soft)}.cmp-table td:first-child{font-weight:600;color:var(--ink)}@media(max-width:768px){.cmp-table{font-size:13px}.cmp-table th,.cmp-table td{padding:9px 10px}}</style>
<section class="gs-recap">
  <div class="container">
    <div style="max-width: 760px;">
      <p style="color: var(--ink-soft); font-size: 15px; line-height: 1.7; margin-bottom: 24px;">The decision rule is shorter than the tool listicles suggest: buy for generic capabilities, build when the workflow crosses your systems. Buying AI licenses is not a strategy, it is a receipt. What makes AI pay is the fit between the model and one specific workflow, and fit is exactly what off the shelf tools cannot promise.</p>
      <table class="cmp-table">
        <tr><th></th><th>Buy a tool</th><th>Build into your stack</th></tr>
        <tr><td>Right when</td><td>The capability is generic: transcription, drafting, meeting notes, generic chat</td><td>The workflow crosses your database, your email, your vertical systems</td></tr>
        <tr><td>Time to value</td><td>Days</td><td>Weeks: sandbox by day 60, production by day 90</td></tr>
        <tr><td>True cost</td><td>Licenses per seat, forever, plus the workflows it almost fits</td><td>Build cost plus model usage plus maintenance, owned once</td></tr>
        <tr><td>Accuracy</td><td>Whatever the demo showed</td><td>Measured against your real cases before anything ships</td></tr>
        <tr><td>When it breaks</td><td>A support ticket to the vendor</td><td>Your team reads ordinary code and fixes it</td></tr>
        <tr><td>Failure mode</td><td>Shelfware: another portal your team ignores</td><td>Overbuilding what a $30 per seat tool already does well</td></tr>
      </table>
      <h2 style="font-size: 22px; margin-bottom: 12px;">The four questions that decide it</h2>
      <p style="color: var(--ink-soft); font-size: 15px; line-height: 1.7; margin-bottom: 24px;">Does the workflow touch systems only you run? Does the output need your data to be right, not just plausible? Will the volume justify owning it? Is there a person who owns the output and can define good enough? Four yeses: build. Fewer: buy, or wait. Most companies should do both, in that order of scrutiny, and the ranked answer for your specific operation is what the <a href="/ai-readiness-assessment/">AI Readiness Assessment</a> produces in two weeks.</p>
      <p style="color: var(--ink-soft); font-size: 15px; line-height: 1.7;">Not sure where you stand? <a href="/blog/the-ai-readiness-checklist/">The 20 question checklist</a> takes one meeting, or download the free <a href="/assets/docs/ai-readiness-playbook.pdf">AI Readiness Playbook</a>.</p>
    </div>
  </div>
</section>

<section class="final-cta">
  <div class="container">
    <h2>Know which, <span class="accent">before you spend</span>.</h2>
    <p>Every workflow ranked by ROI and TCO, buy or build called per workflow. $2,500, two weeks.</p>
    <a href="/ai-readiness-assessment/" class="btn-primary">Get your AI Readiness Assessment</a>
  </div>
</section>