The Dilemma Every Business Owner Faces
Every month, your business pays tens of millions of rupiah for various software subscriptions: CRM, project management, inventory systems, accounting software. The total cost keeps rising—last year it was Rp 15 million/month, now it's Rp 22 million/month. And every time you need an additional feature, the price increases again.
Then you hear about "custom software"—build once, use forever. Sounds attractive. But the initial cost is substantial: Rp 200-500 million. Is it worth it?
The real question: What's the break-even point? In which year does custom software become cheaper than SaaS?
This article will answer that question with a complete ROI analysis, TCO calculator, and decision framework based on various business scenarios in Indonesia.
What is SaaS?
SaaS (Software as a Service) is a software model where you "rent" by paying monthly or annual subscriptions. No installation or maintenance required—just open your browser, log in, and start using.
Popular SaaS Examples:
- CRM: Salesforce, HubSpot, Zoho CRM
- Project Management: Asana, Monday.com, ClickUp
- Accounting: Xero, QuickBooks Online
- HR & Payroll: BambooHR, Gusto
Typical Pricing Models:
- Per user: $10-50/user/month
- Per feature tier: Basic ($50/month), Pro ($200/month), Enterprise ($500+/month)
- Per usage: Per transaction, per GB storage, etc.
When SaaS Makes Sense:
• Limited budget (< Rp 100 million for software)
• Need quick setup (< 1 month)
• Standard workflow (no major customization needed)
• Small team (< 50 users)
• Want to focus on business, not IT maintenance
What is Custom Software?
Custom software is software built specifically for your business needs. Created from scratch by a software house, 100% tailored to your workflows and business processes.
Example Use Cases:
- Custom ERP: System integrating inventory, purchasing, sales, accounting in one platform
- Field Service Management: For businesses managing field technicians (HVAC, telco, logistics)
- Booking & Scheduling System: Hotels, clinics, salons with unique workflows
- Internal Dashboard: Reporting & analytics customized for management needs
Cost Structure:
- Development: Rp 100-500 million (one-time)
- Maintenance: Rp 5-15 million/month (bug fixes, minor updates)
- Major updates: Rp 20-50 million/year (new features)
When Custom Software Makes Sense:
• Budget available (> Rp 200 million)
• Very specific workflow (SaaS doesn't fit)
• Many users (> 100 users)
• Highly sensitive data (need full control)
• Long-term investment (5+ year planning)
Total Cost of Ownership (TCO): 5-Year Comparison
Let's calculate the real cost of both options over a 5-year period.
Scenario: Company with 100 Employees
Option 1: SaaS Stack
Required software:
- CRM (100 users): $25/user/month = $2,500/month
- Project Management (100 users): $12/user/month = $1,200/month
- Internal Communication (100 users): $8/user/month = $800/month
- File Storage (1TB): $200/month
- Total: $4,700/month = Rp 71 million/month (assuming $1 = Rp 15,000)
5-year TCO:
Note: This doesn't include:
- Training costs for each employee turnover
- Integration costs between tools (Zapier, etc.)
- Lost productivity due to imperfect tool integration
Option 2: Custom All-in-One Software
Development of custom platform integrating:
- CRM module
- Project management module
- Internal communication (chat + notifications)
- File management
- Dashboard & reporting
Cost breakdown:
Break-Even Analysis
SaaS cumulative cost:
- Year 1: Rp 852 million
- Year 2: Rp 1,789 million (Rp 852 million + Rp 937 million)
- Year 3: Rp 2,820 million
- Year 4: Rp 3,954 million
- Year 5: Rp 5,201 million
Custom Software cumulative cost:
- Year 1: Rp 430 million
- Year 2: Rp 580 million (Rp 430 million + Rp 150 million)
- Year 3: Rp 730 million
- Year 4: Rp 880 million
- Year 5: Rp 1,030 million
Break-even point (financial): Custom software is cheaper from Year 1!
Total savings Year 5: Rp 5,201 million - Rp 1,030 million = Rp 4,171 million (80% savings)
! Wait: Financial Break-Even ≠ Actual Break-Even
The calculation above only looks at cost, but there are other critical factors:
1. Time to Value:
- SaaS: Can start today (setup < 1 week)
- Custom: 3-6 months development before you can use it
2. Opportunity Cost:
- 6 months without software = 6 months running business manually
- Or 6 months using SaaS first (Rp 71 million × 6 = Rp 426 million)
3. Project Risk:
- Statistics: 20-30% of custom software projects experience delays or cost overruns
- Budget of Rp 400 million could become Rp 500-600 million
- 6-month timeline could become 9-12 months
4. Adoption Curve:
- Team needs 2-3 months to fully adopt custom software
- 20-30% productivity dip during training period
Adjusted Break-Even with Risk:
Bottom line: Custom software is still worth it for long-term (5+ years), but it's not a magic bullet. There are trade-offs to consider.
Decision Matrix: When to Choose SaaS vs Custom?
Special Considerations for the Indonesian Market
1. Budget Reality
In the Indonesian context, software development budgets typically range:
- Small business: Rp 50-200 million
- Medium enterprise: Rp 200-500 million
- Large enterprise: Rp 500 million - 2 billion
This is significantly lower than Western markets (US: $50K-500K for similar scope). So the calculations above need adjustment based on your business scale.
2. SaaS Pricing in USD
Most SaaS tools price in USD. With:
- Exchange rate Rp 15,000/$1
- Annual price increase 5-10% (USD)
- Exchange rate can increase 3-5% per year
Impact: Cost increases 8-15% annually (compounded). Over 5 years, costs can double.
Custom software: One-time cost in Rupiah, unaffected by exchange rates.
3. Data Regulations
Since PP No. 71 of 2019, certain industries (banking, telco, etc.) must store data in Indonesia.
SaaS challenge:
- Not all SaaS providers have data centers in Indonesia
- Compliance risk if data leaves Indonesia
Custom software:
- Full control over data storage
- Can host in local data centers
- Compliance guarantee
4. Talent & Maintenance
Developer availability in Indonesia:
- Strong: PHP, JavaScript, React, Node.js, Python
- Growing: Go, Flutter, React Native
- Limited: Niche tech (Elixir, Scala, etc.)
Impact for custom software:
- Choose tech stack common in Indonesia
- Ensure long-term maintenance is feasible
- Avoid vendor lock-in on rare technology
Real Scenarios: 4 Business Types
Scenario 1: E-Commerce Startup (30 employees, 3 years operating)
Needs:
- CRM to track customers
- Inventory management
- Order processing
- Basic analytics
Analysis:
- Users: 30 (still small)
- Workflow: Fairly standard (similar to typical e-commerce)
- Budget: Rp 100 million (not much funding yet)
- Timeline: Need ASAP (focus on growth, not IT)
Recommendation: SaaS
Tool choices:
- Shopify/WooCommerce (storefront)
- Zoho CRM ($12/user/month)
- WhatsApp Business API (customer communication)
Total cost: ~Rp 15 million/month = Rp 180 million/year
Why SaaS:
- Budget insufficient for custom (Rp 100 million not enough)
- Workflow can use standard tools
- Focus on market validation, not building tech
- If pivot needed, won't lose much
Scenario 2: Manufacturing Company (200 employees, 15 years operating)
Needs:
- Production planning
- Inventory (raw materials + finished goods)
- Purchase orders
- Sales orders
- Accounting integration
- Machine monitoring (IoT)
Analysis:
- Users: 200 (large)
- Workflow: Very specific (unique production process)
- Budget: Rp 800 million available
- Timeline: Can wait 6 months (thorough planning)
Recommendation: Custom Software (ERP)
Estimated cost:
- Development: Rp 600 million (comprehensive ERP)
- Training: Rp 50 million
- Year 1 total: Rp 650 million
- Maintenance: Rp 15 million/month (Rp 180 million/year)
Why Custom:
- 200 users × $30/user/month (SaaS) = Rp 1.3 billion/year → unsustainable
- Production workflow very specific, SaaS doesn't fit
- Production data confidential (competitive advantage)
- ROI achieved in 2 years
- Savings of Rp 650 million/year after Year 2
Scenario 3: F&B Chain (20 outlets, 150 employees)
Needs:
- POS system (20 outlets)
- Inventory per outlet
- Central kitchen management
- Delivery integration (GoFood, GrabFood)
- Sales reporting & analytics
Analysis:
- Users: 150 (medium)
- Workflow: Mix of standard (POS) + custom (central kitchen)
- Budget: Rp 300 million
- Timeline: Need within 3 months
Recommendation: Hybrid
Combination:
- SaaS: POS system (Moka, Pawoon) for each outlet - Rp 500k/outlet/month = Rp 10 million/month
- Custom: Central kitchen management + analytics dashboard - Rp 150 million one-time
Total Year 1: Rp 120 million (SaaS) + Rp 150 million (custom) = Rp 270 million
Why Hybrid:
- POS already mature (use proven SaaS)
- Central kitchen workflow unique (build custom)
- Best of both worlds
- Cost-effective
Scenario 4: Consulting Firm (50 consultants)
Needs:
- Project management
- Time tracking
- Client portal
- Document management
- Billing & invoicing
Analysis:
- Users: 50 (medium-small)
- Workflow: Fairly standard (typical consulting flow)
- Budget: Rp 150 million
- Timeline: Need 1 month (onboarding new clients)
Recommendation: SaaS
Tool choices:
- ClickUp (project management): $12/user/month
- Harvest (time tracking): $12/user/month
- Google Workspace (docs): $6/user/month
Total: $30/user/month × 50 = $1,500/month = Rp 22.5 million/month = Rp 270 million/year
Why SaaS:
- Standard workflow (no custom needed)
- User count still reasonable (50 users)
- Integration between tools already mature
- Focus on consulting, not building software
ROI Calculator: Calculate for Your Business
Step 1: Calculate Current SaaS Cost
Step 2: Estimate Custom Software Cost
Step 3: Calculate Break-Even
Step 4: Consider Hidden Costs
SaaS hidden costs:
- Integration tools (Zapier, etc.): Rp 2-5 million/month
- Training for each new employee: Rp 500k/person
- Lost productivity from non-integrated tools: ~10 hours/month/user
- Data export fees (if switching vendors): Can be very expensive
Custom software hidden costs:
- Opportunity cost (6 months development = 6 months delayed ROI)
- Project failure risk: 20-30% of custom projects fail or are delayed
- Team learning curve: 2-3 months for full adoption
10 Mistakes to Avoid
1. Only look at monthly SaaS price, ignore 5-year TCO
Rp 20 million/month sounds small. But over 5 years = Rp 1.2 billion (excluding price increases).
Fix: Always calculate 3-5 year TCO, not just monthly.
2. Underestimate custom software development time
"Vendor said 3 months, definitely doable." → Reality: 6 months.
Fix: Add 50-100% buffer to timeline estimates.
3. Don't account for custom software maintenance costs
"Build for Rp 300 million, done." → Reality: Rp 10-15 million/month ongoing maintenance.
Fix: Budget 15-20% of development cost per year for maintenance.
4. Choose cheap SaaS without checking scalability
"$5/user/month!" → Later jumps to $50/user/month when scaling.
Fix: Check high-tier pricing, not just the cheapest tier.
5. Forget switching costs
"We'll just switch vendors later." → Export data fee: $5,000. Re-training team: 2 months lost.
Fix: Consider vendor lock-in risk from the start.
6. Don't involve users in decision
Boss decides on Tool X. Team hates Tool X. Adoption rate: 30%.
Fix: Trial with actual users before committing.
7. Use too many SaaS tools
10 different tools. Integration nightmare. 20% of team time spent on manual data syncing.
Fix: Consolidate tools. Prefer all-in-one platforms or build custom.
8. Don't plan for data privacy compliance
Use US-based SaaS. Customer data leaves Indonesia. Violates regulations.
Fix: Check compliance requirements before choosing vendor.
9. Don't negotiate SaaS pricing
Accept list price. Could have negotiated 20-30% discount for annual contracts.
Fix: Always negotiate, especially for > 50 users.
10. Build custom software for non-core business
Build custom HR payroll. Core business: F&B. Waste of resources.
Fix: Custom for core business workflows only. Use SaaS for generic functions.
Conclusion
There's no universal answer for SaaS vs Custom Software. The decision depends on:
• Available budget (one-time vs recurring)
• Timeline (need fast vs can wait)
• Customization level (standard vs very specific)
• User scale (few vs many)
• Long-term vision (frequent pivots vs stable roadmap)
Decision Framework Summary:
Choose SaaS if:
- Budget < Rp 200 million
- Users < 50
- Workflow fairly standard
- Need fast (< 1 month)
- Still early stage / frequent pivots
Choose Custom if:
- Budget > Rp 300 million
- Users > 100
- Very specific workflow
- Highly confidential data
- Clear long-term roadmap (5+ years)
- ROI calculation shows 2-3 year break-even
Choose Hybrid if:
- Mix of standard + custom needs
- Moderate budget (Rp 200-300 million)
- Want best of both worlds
Next Steps:
- Calculate your 5-year TCO (both current SaaS spend vs custom estimate)
- Identify core vs non-core workflows (custom for core, SaaS for non-core)
- Get 3 quotes from software houses for custom option
- Run pilot/trial for SaaS options
- Make data-driven decision based on ROI, not gut feeling
Want to discuss ROI for your specific case? Our team at Zeppelin Works is available for a free consultation—we can help analyze your current software spend and explore your options. No sales pressure, just honest assessment. to chat.
Found this article helpful? Share it with business colleagues struggling with rising monthly software subscription costs 📈