Your operations team named the gap. Your existing software won’t close it. Build or buy? That frame misses the only path that closes the gap this quarter.

TL;DR

What the Buyer Is Actually Asking

The ‘build vs buy’ question surfaces after the ops leader has identified a specific gap, that reframe is wrong. Both paths measure in quarters; the gap costs margin every shift. The decision framework you need has three paths with concrete criteria for each.

The gap was named before the build-vs-buy question arrived

The gap is real. An HVAC contractor can’t auto-update work orders from technician texts. A 3PL operator can’t reconcile parts-on-truck status in real time. A fleet owner can’t tie downtime to telematics data. The operator asked IT for software, and IT asked procurement. Procurement asked: build or buy?

Why the binary is the wrong frame

Both paths stretch into quarters. The gap costs margin every week. A decision framework with three paths and clear criteria for each beats a pros-and-cons table of two. The binary skips the only path built for the gap between what the SaaS vendor ships in 24 months and what internal dev cannot fund this year.

What Buying Actually Delivers in 2026

For structured, repeatable workflows, mature SaaS ships faster than any internal team can build. Field service crews on an FSM, vehicle fleets on telematics-grade FMS, plants on ERP+EAM all benefit. For the off-system work that drives FTFR, MTTR, and margin, the vendor answer is always “it’s on the roadmap,” 18-24 months out, not this quarter.

Where SaaS wins outright

What your FSM doesn’t close is the off-system 60% of operational reality. Scheduling, dispatch, mobile work order, asset register, journey planning, invoicing: mature SaaS ships these faster and cheaper than internal teams can build, and the FSM works. The FMS works. The ERP+EAM stack works for what they were built to do.

Where the vendor roadmap runs out

For the off-system signal that moves FTFR, MTTR, OEE, contract margin, the vendor answer lands consistently: it’s on the roadmap, 18-24 months out. Per-seat pricing means paying for a ceiling the ops leader hit long ago. Salesforce’s State of Service research, drawing on more than 5,500 service professionals, found mobile workers lose over seven hours a week to admin tasks the system should have absorbed. How fleet telematics hit their ceiling is the same story across verticals. Switching costs compound the longer the roadmap gap runs.

What Building Actually Costs in 2026

Minimum team: 1 staff PM, 2-3 senior engineers, 1 designer, DevOps support. That’s $1.5M-$5M loaded TCO for v1 of one workflow. Nine to eighteen months to ship. One in six IT projects studied had a cost overrun of 200%, on average, and a schedule overrun of almost 70%. The ops leader waiting on internal dev competes for capacity against revenue-generating features.

The honest headcount and timeline for a single workflow

A non-trivial workflow (dispatch integration, parts reconciliation, predictive maintenance) requires one PM to scope the work, two to three senior engineers, one designer for UX, and DevOps support for the pipeline. That is $1.5M-$5M loaded cost and nine to eighteen months for v1 at a mid-size tech company, in line with McKinsey research showing large IT projects deliver 56% less value than predicted.

The hidden cost most internal sponsors don’t acknowledge

The real cost isn’t the budget. It’s the gap running off-system for eighteen months. Every month the workflow lives in WhatsApp is a month of avoidable downtime, missed FTFR targets, manual labor. The ops leader competes for internal dev capacity against quarterly revenue features. McKinsey research on more than 5,400 IT projects, conducted with the University of Oxford, found large IT projects run 45% over budget and 7% over time on average, while delivering 56% less value than predicted.

When Buy Still Wins

Commodity workflows: anything the FSM/FMS/ERP/EAM already ships at maturity. Scheduling, dispatch, mobile work order, journey planning, invoicing, asset register: buy it. Back-office and HR workflows with no field variation are almost always faster and cheaper as SaaS. If the requirement is “we just need what everyone else has,” the third path is not for this scope.

When Build Still Wins

Greenfield system of record requiring a custom data model from day one demands a proper internal build. Such projects need full dev capacity and multi-year timelines. Regulated or sovereign data that cannot leave your firewall should stay in-house. The same applies to workflows that ARE your competitive moat. Multi-year digital transformation programs where the full tech stack is being rebuilt are right for internal builds. They’re wrong for a single-workflow gap that needs to close this quarter.

The Third Path: Tailor-Made Software, Built for You

A vendor writes working software for the specific gap the existing stack doesn’t close, and it integrates to the FSM/FMS/ERP/EAM/CMMS. It ships in weeks. The customer pays only when the operational lift shows up. This fills the gap between what the SaaS vendor will ship in 24 months and what the internal team cannot fund this quarter.

Opsima is the AI-native software factory for industrial operations. It builds the CMMS, TMS, TOS, EAM, ERP, equipment monitoring, and document-processing software an operation runs on, tailored to how that operation actually works.

Two service modes: (1) tailor on top of your existing stack (SAP, Maximo, MainPac, Navis, Priority, JDE, AS400) with zero rip-and-replace, or (2) build the replacement from scratch when the legacy system has been outgrown. Ships in weeks. You pay only when the operational lift shows up.

What it is, and what it is not

Not off-the-shelf SaaS, and not a custom internal app. A vendor builds working software for the specific gap the existing stack doesn’t close. Capturing off-system data from WhatsApp and radio is the unlock. This is exactly the layer that accounts for the off-system half of operational reality in field-driven industries. Example: a multi-state HVAC contractor whose FSM handles scheduling and dispatch but cannot capture after-hours technician texts and auto-update the work order. The tailor-made software layer builds that workflow on top of the existing FSM, integrating via agentic data capture, reaching the layer the FSM doesn’t.

The unit of work: one workflow, weeks not quarters

The scope is one workflow gap. The timeline is weeks, not quarters. AI-triggered operational workflows on top of the existing FSM, not replacing it. Integrates with SAP, Maximo, and Navis without rip-and-replace via REST and webhooks. The unit of work is scoped, the timeline is compressed, the risk is on the vendor.

How Procurement Frames the Third Path

Scoped statement of work, working-software milestone, value-confirmation gate. Maps cleanly to procurement language without the 9-18 month capex commitment of a build or the per-seat opex lock-in of a buy. IP, data residency, integration architecture are answered upfront: the software runs on top of existing systems and integrates via REST/webhooks to the ERP/CMMS/FSM, and zero rip-and-replace.

The pricing model: not per-seat, not capex

Not per-seat opex, and not multi-year capex. Scoped SOW, working-software milestone (weeks), value-confirmation gate (the operational lift is measured before payment). The commercial model matches the governance model: everything in staging first, IT review and approval, then production rollout. The customer pays only when the operational lift shows up.

What IT needs answered before sign-off

Staging environment: the software is built in a governed staging environment. Nothing touches production until IT approves. Automated risk assessment: every workflow is analyzed for data access issues, security vulnerabilities, governance compliance before IT review. Audit trail: full version control, rollback capability, change logs. Live operational visibility surfaces the data integrated into the unified dashboard, and IT stays in control.

How It Works in Field Operations: One Walkthrough

A regional 3PL operator’s TMS handles route planning and load assignment but cannot reconcile parts-on-truck status, and drivers report via WhatsApp. Discrepancies are caught a day late, reconciled manually against warehouse WMS records. The workflow gap can cost tens of thousands of dollars a month in reconciliation labor and late-delivery exceptions.

Week 0: kickoff working session

The 3PL brings: TMS system docs, WMS integration, examples of driver WhatsApp messages that cause discrepancies, the definition of “parts reconciled.” The vendor brings: a discovery agent that interviews the team via Teams, generates requirements, produces mockups, builds a business case. Week 0 is a working session, not a demo.

Weeks 2-4: working software in staging

Capturing status updates from WhatsApp and radio automatically and syncing reconciled status back into the TMS and a live operations dashboard, and parts-on-truck status becomes structured data. The dashboard surfaces discrepancies in real time. The 3PL sees the operational lift building.

Weeks 4-6: value confirmation and production rollout

Discrepancy detection time drops from days to minutes. The 3PL operator confirms the operational lift. IT reviews the staging environment, approves integration, signs off on risk assessment, and the software rolls to production. The customer pays only after the lift is confirmed. Automated MTBF and MTTR dashboards measure the KPI lift and trigger the payment gate.

For a real deployment shape: PNCT (Port Newark Container Terminal) scaled from ~1,000 to ~14,000 structured status changes per month, added +5% fleet availability, and cut breakdowns roughly 15% with EquipmentOS.

Six Questions to Decide Which Path Fits

Question 1: Is the gap on the vendor’s published roadmap within six months?, and buy and wait. Question 2: Is the workflow your competitive moat or require sovereign data that cannot leave your perimeter? Build in-house. Question 3: Does it live entirely behind the firewall with no external calls? Build. Question 4: Is the gap mostly off-system signal (WhatsApp, radio, photo, voice, paper) that the FSM/FMS/ERP/EAM cannot ingest?, and third path. Question 5: Is internal dev capacity six or more months out for this workflow?, and third path. Question 6: Are you about to sign a six-figure SaaS contract for a feature you need this quarter?, and third path. Take this checklist to your next IT meeting.

Conclusion: Bring the Gap to a Working Session

The build vs buy binary was the right question for a different era. In 2026, it skips the only path built for the gap between what the SaaS vendor ships in two years and what internal dev cannot fund this year. The operational data backbone powers tailor-made operational software that runs on top of existing systems. If your operation spans ports, mining, logistics, and manufacturing and your dispatch gap lives off-system, bring the specific workflow your FSM/FMS/ERP/EAM vendor told you was on the roadmap. See what shipping in weeks looks like. MTTR and fleet availability benchmarks show how much is at stake. Bring your workflow gap to a working session and find out what the third path looks like.

Stop letting operational events vanish into spreadsheets.

Roughly 60% of your ops data lives off-system. Opsima captures it in personalized software, in weeks.

See how it works →

Frequently Asked Questions