Build vs Buy: When Custom Software Is Worth It—and When It Is Not
SaaS first for standard work, custom only where the process is materially different. How to weigh fit, total cost, lock-in, and hybrid options before committing budget.

The Oscillate Journal
Field notes on software, automation, and the operational decisions behind reliable business systems.
Editor's selection
A practical perspective on choosing technology around the way your team actually works.
SaaS first for standard work, custom only where the process is materially different. How to weigh fit, total cost, lock-in, and hybrid options before committing budget.
Explore the archive
Latest thinking
25 articles
Public incident analysisPublic incident analysis: a 2020 public-health reporting failure where oversized transfer files never reached national dashboards—and what that means for any file-based production pipeline.
Public incident analysisPublic incident analysis of a 2012 trading-system release failure: incomplete code deployment, dormant functions, weak stop conditions, and lessons from the SEC enforcement record.
Public incident analysisPublic incident analysis: regulators found a 2018 bank platform cutover where data migration succeeded while customer channels failed—why operational readiness is larger than a completed data load.
Public incident analysisPublic incident analysis: a January 2017 database outage where configured backup jobs were not the same as recoverable data—silent failures, unsuitable replicas, and an untested restore path.
Interface exampleA short list that separates tools that will survive contact with your operation from the ones that demo well and quietly stop being used.
Interface exampleMost stalled AI projects are not model problems. They stall because the business could not answer what a customer or an order actually is.
Interface exampleDocument extraction is the most practical AI use case in distribution and manufacturing. It also fails quietly unless you design the validation first.
Interface exampleAI is good at reading messy input and bad at being exact. Knowing which half of your process is which decides whether it helps or creates work.
Interface exampleUnsupported OS, rising support bills, and “please fax the order”: modernization framed as risk and cash, with a phased case pattern.
Excel for analysis, VBA for the weekly grind, a shared app when the file stops being safe. How to tell which stage you are in—and how to move without a freeze.
Interface exampleGST filings, vendor WhatsApp orders, and Excel registers: automation paths Indian SMEs actually adopt without a full ERP on day one.
Interface exampleWhen a shared Access file is still fine, when architecture is the real problem, and how to migrate data without freezing the office for a weekend.
Interface exampleBackups nobody has tested and ransomware drills that never happened: recovery planning for businesses that cannot afford a week offline.
Interface exampleScreens that spin, reports that timeout: optimization grounded in query plans and measurement, not random caching.
Interface exampleShared admin passwords and public RDP: security as hygiene for real SMBs, not a checklist for enterprises only.
Interface exampleOn-prem server in a closet vs managed hosting: choosing cloud for uptime, backups, and growth without overspending on day one.
Interface exampleDuplicate entry, mismatched addresses, and APIs that look fine in a demo. How to choose ownership, connection method, and where people still approve.
When the “master” workbook lives on one PC and everyone else has copies: moving critical workflows to a desktop app with validation and audit.
Interface exampleDependencies age, logs fill disks, and “we will upgrade later” becomes an outage. Maintenance as risk control, with a realistic release cadence.
Interface exampleWhen “the server is slow again” becomes normal: how ongoing support turns reactive firefighting into stability and a backlog you can plan.
Interface exampleEveryone has a different Excel “source of truth.” How reporting projects start from one decision and a few KPIs, with a realistic consolidation story.
Traffic but no leads, or buyers who still call to ask what you do: fixing the gap between marketing spend and a site that answers real buyer questions.
Interface exampleInspectors in the field, drivers with spotty signal: when a mobile app solves a real access problem instead of duplicating a spreadsheet.
Interface exampleThe contractor who built it left, the OS is old, and the business still runs on it. Practical maintenance and when to phase toward replacement.
Field staff vs plant floor: a practical decision frame for web vs desktop, with anonymized examples from logistics and manufacturing.
Have a system problem?