The default advice is always 'use off-the-shelf software.' It's cheaper, faster to deploy, and someone else maintains it. That advice is right most of the time. But there's a class of business where every off-the-shelf tool creates so many workarounds that the workarounds become their own problem. When that happens, the question flips.
What off-the-shelf tools are actually good at
Generic ERP and operations tools shine when your workflows match their assumptions. Standard order management, basic project tracking, common financial processes, typical HR flows. If you're a retailer that sells standard products, ships to customers, and manages straightforward inventory - Shopify, QuickBooks, and a spreadsheet handle it fine. The tools were built for you.
When they break down
The signal that you've outgrown generic tools isn't usually a single failure. It's a pattern. Your team maintains 5+ tools that don't talk to each other. Someone spends hours each week manually moving data between systems. Workarounds are documented in a Google Doc that no one fully understands anymore. New employees take months to learn 'how we actually do it' vs. how the tool is supposed to work. You've built a parallel system in spreadsheets because the tool can't handle your specific logic.
Clear signals you've outgrown generic tools:
- You have 3+ spreadsheets that act as the source of truth for core operations
- Your team regularly exports from one tool and imports into another manually
- You've customized a tool so heavily that updates break your configuration
- New hires take 3+ months to understand your actual workflow
- You're paying for 6+ SaaS tools and they still don't cover everything
What custom ERP means in practice
Custom ERP doesn't mean a multi-year Oracle implementation. For a business with $500k-10M in revenue, it means a web application built specifically for your operations - your workflows, your terminology, your edge cases. It talks to the tools you already use via API. It runs in a browser so anyone can access it. It looks like a simple internal tool, not enterprise software.
Real examples of what gets built
For a construction company (BSM), we built a project tracker that combines procurement requests, subcontractor timesheets, milestone tracking, and invoice management in one place. Before this, they were running 4 separate tools and a dozen spreadsheets. For a logistics company (PLF), we built an invoice portal that tracks shipments, generates invoices based on contracted rates, and pushes data to their accounting system. For a bakery (Cupcake Studio), we built a B2B ordering system combined with production planning - wholesale clients order online, the production team sees what needs to be made each morning.
What it costs
A focused custom operations tool - one core workflow, built properly - costs $8,000-25,000 to build. A more complex system covering 3-4 core workflows costs $20,000-60,000. Compare this to: 6 SaaS tools at $100-400/month each = $600-2,400/month = $7,200-28,800/year in recurring costs, plus the ongoing cost of manual data transfer between them. For many businesses, the custom build pays for itself in 12-18 months purely in tool cost savings, before counting time savings.
Timeline
A focused custom tool takes 8-16 weeks from spec to production. Week 1-2: detailed process documentation and system design. Week 3-10: core build with regular check-ins. Week 11-14: testing, feedback, iteration. Week 15-16: deployment and team training. The team using it on day 1 is usually the team that helped spec it, so adoption is fast.
Who this is for
Custom operations software makes sense for: companies with $500k+ in revenue where software cost and efficiency are real levers, operations that have genuinely unique requirements that generic tools don't cover, teams that have already tried 2-3 off-the-shelf tools and hit the same walls each time. It doesn't make sense for: early-stage companies still figuring out their process, businesses with standard workflows that a $50/month tool handles fine.
How to evaluate whether to build
The clearest way to evaluate: document your actual workflow step by step, then map each step to a tool you use today. Count the gaps - steps where the tool doesn't fit and you're doing it manually. Count the handoffs - steps where data moves between tools. If you have more than 5 gaps or 4 inter-tool handoffs for a single core process, the math on building custom usually works out.
If you're hitting the limits of your current tools and wondering if a custom build makes sense, a free audit call walks through your workflows and gives you an honest answer on whether it's worth it.
Free 30-min audit. We tell you what to automate first and what it would cost.