Build, buy or build with AI: a decision framework for internal software

The short answer

Buy software when your process is the same as everyone else's and a mature product already does it well. Hire a developer when the tool is core to what you sell, must handle heavy scale or complex integrations, and you can fund ongoing maintenance. Build with AI on a business platform when the workflow is specific to your company, the people who do the work can describe it, and you need it running in days rather than months. Most small and mid-size companies end up using all three, each for the right job.

For decades, the internal software decision had two answers. You bought a product and adapted your process to it, or you paid someone to build exactly what you needed and waited. AI has added a third answer: the people who do the work describe it, and an AI platform builds it. That third option is not a replacement for the first two. It changes which jobs each of them should do.

This guide gives you a framework for deciding, a scoring worksheet you can use on your own workflows, real prices for comparison, and a worked example of the costs side by side.

The three options in one table

	Buy	Hire a developer or firm	Build with AI on a business platform
Best for	Standard jobs every company does the same way	Software you sell, heavy scale, complex integrations	Workflows specific to your company
Time to first use	Days to set up, weeks to adapt	Weeks to months	Often the same day
Fit to your process	You adapt to the product	Exact	Exact, described by the people who do the work
Changing it later	Wait for the vendor	Every change is a request to the developer	Describe the change in plain words
Typical cost shape	Per user per month	Salary or project fees, plus maintenance	Per builder, with build allowances
Who protects your data	The vendor	The developer's skill and habits	The platform's rules for every app
Main risk	Paying for unused features and every user	Cost, key-person dependence, backlog	Choosing a platform that leaves security and billing to chance

Five questions that decide it

Answer these in order for any workflow you are considering. The first clear answer usually decides.

Is this a job every business does the same way? Accounting, payroll, email, video calls. If yes, buy. There is no advantage in having your own version.
Is this software part of what you sell? A customer-facing product, a paid portal, a platform your revenue depends on. If yes, hire engineering talent, because the software is the business.
Does it need heavy scale or deep integration? Millions of records, real-time links to many outside systems, strict uptime promises to customers. If yes, lean toward a developer or a mature product.
Is it specific to how your company works? Your job stages, your approval rules, your inspection checklist, your way of handing work from sales to operations. If yes, build with AI.
Can the person who does the work describe it? If they can name the people, fields, steps, rules and exceptions, an AI platform can build it. If nobody can agree how the process works, fix the process first.

A scoring worksheet

For borderline cases, score each option from 1 to 5 on the factors that matter to you. Weight the factors by importance. The scores below are a starting point for a typical internal workflow, such as a purchase approval or a job tracker, at a 25-person company.

Factor	Weight	Buy	Developer	Build with AI
Fit to our process	3	2	5	5
Speed to first use	2	3	1	5
Cost over three years	3	3	1	4
Ease of changing it	2	2	2	5
Security handled for us	3	4	3	4
Independence from one person	2	4	2	4

Multiply each score by its weight and add the columns. Change the weights for your situation: a regulated workflow might weight security at 5, and a product you sell would add a factor for engineering depth where the developer column wins. The point of the worksheet is not the total. It is to make the trade-offs explicit so the decision is not made on enthusiasm alone.

What each option really costs

Prices below are as listed on vendor pages in October 2026.

Buying

Most business software charges per person per month. Retool's Business plan, for example, is $50 per builder and $15 per internal user per month billed annually. Microsoft Power Apps Premium is $20.00 per user per month paid yearly, and Microsoft says the people who run the apps need a license too. Google AppSheet is $5, $10 or $20 per user per month, and every app user, including guests, needs a license. Per-user pricing is fair for software everyone uses, and expensive when most people only open one app occasionally.

Hiring

The Bureau of Labor Statistics put the median annual wage for software developers at $135,980 in May 2025, before benefits, equipment, recruiting and management time. A developer also creates a dependency: the tools they write are understood by them first, and the backlog grows faster than one person can clear it. Even companies with full IT teams struggle to keep up; in MuleSoft's 2022 Connectivity Benchmark, only 37% of IT leaders said they completed every project asked of them the year before.

Building with AI

AI platforms vary widely. Some charge by credits or tokens for every request, including fixes, and some change their units over time. Bubble introduced Workload Unit pricing in April 2023 and drew heavy pushback on its own forum. Look for a platform that prices per builder, includes builds in the seat, does not charge the people who only use the apps, and caps spending.

Example: three years for one company, side by side

Example: a 25-person company wants internal tools for intake, approvals and inspections. Three people will build or maintain tools, and 22 others will use them.

Option	Monthly cost	Three-year cost	Notes
Retool Business, annual	3 x $50 + 22 x $15 = $480	$17,280	Someone still has to build in Retool
Power Apps Premium, annual	25 x $20 = $500	$18,000	Everyone who runs the apps needs a license
One developer at the BLS median wage	About $11,330 before benefits	About $408,000 before benefits	Builds anything, but every change waits on one person
FORGE, 3 seats	3 x $49 = $147	$5,292	Includes 3 builds per seat per month; app users free

The table compares list prices only. Your own team's time to describe and test tools is similar across the options, because someone always has to explain the work. The difference is in who turns that explanation into a working tool, how fast, and what you pay per person.

The risks each option brings

Buying: paying for every user, for features you never touch, and bending your process to the product.
Hiring: cost, a single point of failure when the developer leaves, and a backlog that never ends.
Building with AI on the wrong platform: security left to the builder and bills that grow with every attempt. When researcher Matt Palmer found 170 of 1,645 scanned Lovable apps exposed in 2025 (CVE-2025-48757), Lovable disputed the CVE, saying each customer is responsible for protecting their app's data, according to the National Vulnerability Database. In July 2025, Fortune reported that a Replit agent wiped SaaStr's live database, holding records on more than 1,200 executives and over 1,190 companies, during a code freeze. And AI output still needs checking: in Stack Overflow's 2025 survey, 45% of developers said debugging AI-generated code is more time-consuming.

Each of these risks is manageable once you name it. For the AI option specifically, the platform decides most of the risk, so choose one that enforces access for every app, checks every piece for security before it is saved, keeps building away from your live data and caps spending.

How most companies combine the three

Buy the systems every business runs the same way: accounting, payroll, email.
Build with AI the workflows that are yours: intake, approvals, inspections, scheduling, handoffs, dashboards.
Connect them with exports and simple handoffs first, then deeper links once the tools are in daily use.
Hire or contract developers only for software you sell or that needs real engineering depth.
Review the mix once a year. Bought tools you have outgrown are often the next candidates to build.

When to switch from one option to another

The right answer changes as a company grows. These are the common moments to revisit a decision.

A bought tool needs constant workarounds. If your team keeps a side spreadsheet to cover what the product does not do, the workflow has become specific to you. That is a build candidate.
The per-user bill passes the value. When most licensed users only open the tool to check one thing, a tool built around that one thing, with free app users, often costs far less.
The developer backlog keeps growing. Move the everyday internal workflows to an AI platform so the developer's time goes to work that really needs engineering.
An AI-built tool becomes part of what you sell. If customers start paying for something that began as an internal tool, bring in engineering depth for it.
A key person leaves. Any tool that only one person understood, bought, built or hired, is a risk. Use the moment to move it somewhere the company owns.

A decision checklist

Write down the workflow in plain words: people, fields, steps, rules, exceptions.
Answer the five questions above in order.
Score borderline cases with the worksheet.
Get list prices for every option, including what users who only open the app cost.
Ask each vendor who protects the data and how.
Ask what a change costs and how long it takes.
Ask what happens to the tool when the person who built it leaves.
Decide, then set a review date three months out.

How FORGE handles it

FORGE is the build-with-AI option made for business teams. Your people describe the work in plain words; a panel of top AI models plans each tool, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. Most teams have their first real tool the same day, as a web, mobile or desktop app.

Every app lives inside your company, people join by invite only, roles for owners, admins, builders and app users decide who can do what, and a complete record shows who did what. Tools belong to the company, not to whoever built them.

A seat is $49 a month with 3 builds, app users are free, changes are a small fraction of a build and only count when something changes, and a build FORGE fails is free. Packs of 10 builds are $150, caps and alerts arrive at 80 and 100 percent, and nothing bills by itself. Our team onboards every company with a workflow workshop that sorts your list into buy, build and hire. Talk to us or compare options.

Questions people ask

When should a small business buy software instead of building?

When the job is standard across companies, such as accounting, payroll or email, and a well-supported product already handles it. Building your own version of something that every business does the same way rarely pays off.

When is hiring a developer the right call?

When the software is part of what you sell to customers, has to handle large scale or complex integrations, or needs ongoing engineering judgment. In those cases a developer's salary is an investment in your product. The Bureau of Labor Statistics put the median annual wage for software developers at $135,980 in May 2025.

What does build with AI actually mean?

It means the people who do the work describe the tool in plain words and an AI platform builds it. On a platform made for business teams, the platform also handles access, security checks and a record of changes, so the builder does not need technical skills.

Is an AI-built tool as good as one a developer writes?

For internal workflows such as intake, approvals, inspections and tracking, a well-built AI tool fits the work closely because the person who knows the process described it. For software you sell to customers or that needs deep engineering, a developer is still the stronger choice.

What are the hidden costs of each option?

For bought software, per-user charges and paying for features you do not use. For a developer, recruiting, benefits, management time and waiting for changes. For AI builders, credit-based billing that charges for every fix, and security left to the builder. Ask about each before you decide.

Can we combine the options?

Yes, and most companies should. Buy your accounting and payroll systems, build internal workflows with AI around them, and hire developers only for software that is core to your product.

See what FORGE builds for your team

We onboard every team ourselves, starting with the work that costs you the most time.

Talk to us