Build vs buy · Internal Tools

Custom Internal Tools Development vs Off-the-Shelf (Retool, Airtable, Spreadsheets): Which Should You Choose?

The short answer

Buy off-the-shelf first. For most internal tools a spreadsheet, Airtable, or Retool covers the job for $0 to $30k/year and ships in days. Build custom only when the tool sits on your core workflow, needs deep integration or permissions logic the platform can't model, or when platform seat and usage fees at your scale cross roughly $40k to $80k/yearthe point where a one-time $60k to $150k custom build starts paying back within 18 to 24 months.

What is the honest default: buy, then build only where it hurts?

The mistake we watch teams make is treating this as a single decision for the whole company. It isn't. Each internal tool is its own build-vs-buy call, and the right portfolio is mixed. You run your ops dashboard on Retool, your content calendar in Airtable, your quick ad-hoc analysis in a spreadsheet, and you build exactly one or two custom tools where the workflow is genuinely yours and the volume is real.

Off-the-shelf wins on speed and cost at the start. Custom wins on fit, control, and cost at scale. The framework below tells you which side of that line any given tool sits on before you spend anything.

When is off-the-shelf genuinely the right call?

Reach for a spreadsheet, Airtable, or Retool when the tool is a supporting workflow, not the thing your business runs on. Signs you should buy:

  • Fewer than ~15 people touch it and the process changes month to month. Platforms let a non-engineer reshape the tool the same afternoon the process changes.
  • The data model is flat or lightly relational. Airtable handles records, views, and a few linked tables without a database migration.
  • You need it live this week. Retool wires a CRUD admin panel onto an existing database in a day or two; a custom equivalent is weeks.
  • The logic is standard. Approvals, task tracking, a lightweight CRM (Customer Relationship Management), an internal directory, someone has already solved this, and a custom rebuild buys you nothing but maintenance.

Being honest about this is the point: if a $20/user/month tool does the job, building your own version is a bad trade. You would be paying six figures to own a maintenance burden that a vendor carries for you.

When does custom internal tools development actually pay off?

Custom earns its cost in a narrow, high-value band. Build when:

  • The tool is your core operational workflow. If the tool is how your team makes money, dispatch, underwriting, fulfillment, pricing, the fit gap in an off-the-shelf platform costs you real hours every day, and those hours compound.
  • Integration depth exceeds what the platform models. Two-way sync across four internal systems, event-driven triggers, or logic that has to run server-side and audited is where low-code hits a wall.
  • Permissions and compliance get granular. Row-level access, audit trails, SOC 2 or HIPAA scope, data that legally cannot sit on a third-party platform.
  • Scale turns seat pricing hostile. Retool and Airtable price per user or per usage. Past a few hundred active users, that recurring bill crosses the cost of owning the code outright.
  • The tool is a durable asset, not an experiment. Build things you will still run in three years, not things you are still validating.

Across 2,000+ projects, the pattern is consistent: the tools worth building are the ones a company would refuse to switch off. Everything else stays bought.

How do the options compare side by side?

FactorSpreadsheetsAirtableRetoolCustom build
Upfront cost$0$0 to lowLow setup$60k to $150k typical
Ongoing cost~$0Per seat, scales with usersPer seat + usage, scales fastHosting + maintenance (you own it)
Time to valueHoursDaysDays to weeks6 to 14 weeks
Fit to your workflowLooseGood for recordsGood for CRUD/adminExact
ControlNoneLimitedModerate (bounded by platform)Total
Integration depthManualShallow, via API/connectorsModerate, DB and API friendlyUnlimited
Lock-in riskLowModerate (data + views)High (logic lives in platform)None (code is yours)
Breaks at scale~5 to 10 usersData volume + seat costSeat/usage cost, complex logicOnly if under-resourced

What does total cost of ownership look like at scale?

Sticker price misleads because it ignores time. A spreadsheet is free until three people are editing it at once and someone overwrites the master. Retool is cheap at 10 users and painful at 400. The real comparison is three-year total cost of ownership at your actual headcount.

ScenarioOff-the-shelf 3-yr TCOCustom 3-yr TCOVerdict
15 users, standard workflow~$10k to $25k~$90k to $180kBuy, custom never pays back
75 users, moderate integration~$45k to $90k~$110k to $200kBuy, but watch the trend line
300+ users, core workflow, deep integration~$130k to $300k+~$130k to $230kBuild, costs converge, control wins

Custom TCO folds in hosting and maintenance, which is real and runs roughly 15 to 25 percent of the build cost per year. It is not free to own software. But an off-the-shelf bill that grows with every hire is the quieter, larger cost most teams underweight. The crossover typically lands where platform fees reach $40k to $80k/yearbeyond that, owning the code is cheaper and you stop renting your own workflow.

What is the committed recommendation by company stage?

  1. Pre-seed and seed: Buy everything. Spreadsheets and Airtable. Your workflows are still changing weekly, so you cannot afford to freeze one in custom code. Zero engineering time on internal tooling.
  2. Series A / early growth: Mostly buy, with Retool as the workhorse for admin panels and ops dashboards on your database. Build custom only if one tool is already the bottleneck on revenue and the process has stopped changing.
  3. Series B and scaling: Run a mixed portfolio. Keep buying for supporting workflows. Build the one or two tools that are your operational core, where seat pricing is climbing and the fit gap costs real hours daily.
  4. Enterprise: Build the core, buy the edges. At your scale, per-seat platform economics and compliance scope justify owning the critical tools outright, while off-the-shelf still wins for everything peripheral.

The default answer is buy. The exception, build, is real, valuable, and narrow. Get the exception right and you own the two tools that actually differentiate you while paying a vendor to carry everything else.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
  2. Only 16% of respondents said their organizations' digital transformations had successfully improved performance and equipped them to sustain gains over the long term; even in digitally savvy industries such as high tech, media, and telecom, self-reported success rates did not exceed 26%. Source: McKinsey & Company (2018) →
  3. The 2015 CHAOS data (based on the modern definition of success) reports that only about 29% of software projects succeed, 52% are challenged, and 19% fail, with the three most important success skills being executive sponsorship, emotional maturity, and user involvement. Source: The Standish Group (reported via InfoQ Q&A with Jennifer Lynch) (2015) →
  4. Deloitte's research found that digitally advanced small businesses experienced revenue growth nearly 4x as high as the prior year, were about 3x as likely to have exported, were nearly 3x as likely to have created new jobs, and were more than 3x as likely to have seen more sales inquiries in the last year. Source: Deloitte (research summarized by Google) (2017) →
Rohan Malhotra · Enterprise Software Consultant

Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.

Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.

FAQ

Frequently asked questions

Is Retool considered build or buy?

Retool is buy, a low-code platform you configure rather than code from scratch. It sits between a spreadsheet and a custom build: faster and cheaper than custom, but your logic lives inside the platform, so per-seat pricing and lock-in grow with usage. It is the right middle ground for admin panels and internal dashboards, and the wrong choice once seat costs cross the price of owning the code.

How much does custom internal tools development cost?

A focused custom internal tool typically runs $60k to $150k to build, depending on integration depth and permissions complexity, plus ongoing hosting and maintenance of roughly 15 to 25 percent of the build cost per year. Simple single-purpose tools land at the low end; multi-system, audited, role-based tools land higher. The number only makes sense when it is offset by off-the-shelf fees you would otherwise pay at scale.

When do spreadsheets stop being good enough?

Spreadsheets break around five to ten concurrent editors, or when the data becomes relational, when you need real permissions, or when one bad paste can corrupt the source of truth. At that point move to Airtable or a Retool app on a proper database. Spreadsheets stay excellent for one-off analysis and truly small teams; they fail as shared operational systems.

What is the biggest hidden cost of off-the-shelf tools?

Per-seat and per-usage pricing that scales with every new hire. A platform that costs $2k/year at 10 users can cost $60k+/year at 400, and that bill never stops. The second hidden cost is lock-in: when your logic lives inside the platform, migrating off later is its own project. Model the three-year cost at your projected headcount, not today's.

Should a growing startup build or buy internal tools?

Buy first, at nearly every stage. Pre-seed through Series A should run on spreadsheets, Airtable, and Retool so no engineering time goes to internal tooling. Build custom only when a specific tool is your operational core, the process has stabilized, and platform seat costs are climbing past roughly $40k to $80k/year. Build the one or two tools that differentiate you; buy the rest.

What does an internal tool cost for a small business with 20 to 50 employees?
Plan on $5,000 to $15,000 for a focused tool that replaces one painful spreadsheet workflow, such as job scheduling, quoting, or PTO tracking. In Digital Heroes projects at this size, the sweet spot is one core workflow, two or three user roles, and a single integration, usually QuickBooks or Google Workspace. Quotes far below $5,000 usually mean a template with your logo on it rather than software built around your process.
Should we build our internal tool in Retool instead of hiring developers?
Retool is the right choice if someone on your team is comfortable with SQL and JavaScript and the audience is a handful of technical users, because a basic CRUD dashboard comes together in days. Hire developers when non-technical staff will use the tool daily, when the logic goes beyond forms sitting on a database, or when per-seat pricing stings, since Retool's Business tier lists at $50 per standard user per month. A pattern Digital Heroes sees often: companies arrive after a year on Retool with a tool nobody can maintain because the one person who built it has left.
How many developers does it take to build an internal tool?
Two to four people covers nearly every internal tool: one or two developers, a part-time designer, and a project manager who doubles as your single point of contact. Internal tools rarely need consumer-product polish, so a full-time dedicated designer is usually wasted budget. On Digital Heroes projects, a two-person core team handles the typical 4 to 8 week build, with a specialist pulled in briefly for a tricky integration or a security review.
Will a custom internal tool scale as our company grows?
Yes, provided it sits on a standard stack with a real database: PostgreSQL comfortably handles millions of records, and adding users costs hosting pennies rather than per-seat fees. The real scaling risks are organizational, not technical: new departments want features, processes change, and the tool needs a budget line to evolve. Set aside a small quarterly improvement budget instead of treating launch as the finish line, and the tool stays useful for a decade rather than getting rebuilt every two years.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
How do we migrate years of spreadsheet or Airtable data into a new internal tool?
Migration is a standard part of the build, not a separate project: the agency writes import scripts that clean, deduplicate, and map your existing rows into the new database. On typical spreadsheet and Airtable histories, Digital Heroes budgets 3 to 10 extra days, most of it spent resolving inconsistencies like the same customer spelled four different ways. The safe sequence is a trial migration first, a review of flagged conflicts with your team, then final cutover over a weekend so nobody loses a working day.
How do I vet a development agency for an internal tools project?
Ask to see two or three internal tools they have shipped and whether those clients still use them daily, because internal tools fail on adoption, not code quality. Good signs: they ask to see your current spreadsheet or process before quoting, they propose a phased build instead of one big launch, and they spell out who handles training and post-launch changes. Walk away from anyone who gives a fixed price before seeing your actual workflow, since internal tools live or die on process details.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Keep reading
let's build

Build something worth launching.

A plan, a team, a timeline, within 24 hours. No decks, no discovery calls. Tell us what you're building and we'll come back with a real scope and a real number.

message us directly · we reply within one business day

mission briefing

Monthly dispatch

Playbooks, real build costs, and what we're shipping. One email a month. No fluff.

visit us

New York HQ

1140 Broadway, Suite 704 · New York, NY 10001

Get directions
Online now

Hey there 👋 How can we help you today?