Build vs. Buy: When Custom Software Saves Money and When It Wastes It

Published: 2026-05-20
Author: 30 Percent Crew
Read time: 6 minutes
Keywords: build vs buy software, custom software ROI, when to build internal tools, SaaS vs custom development, internal tooling cost

The default answer for every business problem is "buy SaaS." It is fast, it is predictable, and someone else maintains it. But for some workflows, buying SaaS is the expensive option — especially when the SaaS does 80% of what you need and charges enterprise pricing for the 20% you do not use.

Custom internal tooling is not for everyone. But when the math works, it works dramatically.

The build-vs-buy framework

Ask four questions:

1. How unique is the workflow? If 10,000 other companies do the same thing, buy. If your workflow is specific to your business model, consider building.
2. How many people use it? If 3 people use a tool 2 hours per week, buy. If 30 people use it 20 hours per week, build may make sense.
3. What is the SaaS cost trajectory? Per-seat pricing that scales with headcount is expensive. Flat-rate pricing is more predictable.
4. How critical is data ownership? If the tool holds sensitive client data, custom ownership may be a compliance requirement, not a preference.

When building saves money

Case: Lead intake and routing

A law firm was paying $1,200/month for a CRM with lead capture, plus $400/month for a form builder, plus $300/month for a notification service. The firm needed: a form, a notification, and an assignment rule. Nothing else.

We built a custom intake tool in two weeks. Stack: a simple web form, a database, and email notifications. Total cost: $4,800 one-time build + $50/month hosting. First-year cost: $5,400 vs. $22,800 for the SaaS stack. The firm owns the tool, the data, and the roadmap.

Case: Commission tracking for a real estate team

A team of 15 agents used a $200/month commission tracking add-on inside their CRM. The add-on was slow, inflexible, and missing features the team needed. We built a custom commission calculator in one week. It integrated with their CRM via API, produced PDF statements, and handled their specific split structure. Build cost: $3,200. SaaS cost eliminated: $2,400/year. The tool paid for itself in 16 months — and the team got exactly what they needed.

When buying is still better

Payroll: Never build payroll software. The compliance risk alone justifies the SaaS cost.

Email: Do not build your own email delivery infrastructure. Deliverability is a full-time specialty.

Accounting: QuickBooks, Xero, and Sage exist for a reason. The tax code changes every year. Let someone else keep up.

Security: Authentication, encryption, and access control are not DIY projects unless you have a dedicated security team.

The hidden cost of building

Custom software has ongoing costs:

• Maintenance: Every dependency update, every security patch, every API change
• Documentation: Someone has to write it, and someone has to keep it current
• Training: New employees need to learn a tool that exists nowhere else
• Bus factor: If the builder leaves, the tool becomes a black box

Our rule: if the first-year build cost is less than 18 months of SaaS fees, and the maintenance cost is less than 20% of the SaaS fee, building is usually the right call.

How 30 Percent Crew builds internal tools

When the math favors building over buying, we ship focused internal apps: modern stack, clean UI, fully documented, and fully owned by you. We then train your team and hand off the codebase. The tool is yours — no subscription, no vendor lock-in, no seat limits.

We take thirty percent of verified first-year savings, including both subscription elimination and labor reclamation. No retainer. Request a savings audit →