The Setup
Six months ago, our finance team spent 15 hours every month on month-end reporting. Manual data collection from 5 systems, Excel manipulation, formatting, emailing. Tedious, error-prone, soul-crushing.
We built one Make.com workflow to automate it. Cost: £180 setup + £29/month tool subscription. Time to build: 8 hours.
This is what happened over the next 6 months.
Month 1: Optimistic Launch
The workflow ran, but needed human intervention 40% of the time. Edge cases we didn't anticipate. Data formatting issues. But still: 9 hours saved.
Month 2: The Refinement Phase
Fixed 12 edge cases from Month 1. Added error handling. Improved data validation. Manual intervention dropped to 15%.
Month 3: Breaking Point
API provider changed endpoints. Workflow broke silently. Didn't discover until week 3. Had to manually recreate everything. Nightmare. Month 3 almost killed the project—we seriously considered going back to manual. Thank god we didn't.
Month 4: The Comeback
Rebuilt with better monitoring. Added Slack alerts for failures. Set up weekly health checks. Workflow now catches 95% of issues automatically.
Month 5: Unexpected Expansion
Sales team asked: "Can we use this for our reports too?" Added 3 new output formats. Same workflow, multiple use cases. Value multiplied.
Month 6: Steady State
Workflow runs flawlessly. Zero human intervention. Finance team now focuses on analysis, not data collection. Culture shift: from data entry to strategic insights.
The Numbers: 6-Month Totals
Total Time Investment:
Setup: 8 hours
Month 1-2 refinements: 6 hours
Month 3 crisis fix: 4 hours
Month 4 monitoring setup: 3 hours
Total: 21 hours
Total Time Saved:
Month 1: 9 hours
Month 2: 11.5 hours
Month 3: -18 hours (crisis)
Month 4: 13.5 hours
Month 5: 14.5 hours
Month 6: 15 hours
Total: 45.5 hours saved
Net Savings: 45.5 - 21 = 24.5 hours
Financial ROI:
Cost: £354 (£180 setup + 6 months of subscription at £29/month)
Savings at £80/hour: £1,960
ROI: 454%
Break-even point: Month 2, Week 3
What We Learned
- Month 1 will have issues—plan for 50% manual intervention initially
- Track every failure and fix systematically
- Monitoring is NOT optional—Month 3 proved this painfully
- Build for flexibility—one workflow can serve multiple teams
- True value isn't just time saved—it's enabling strategic work
- Break-even typically happens Month 2-3 for most automations
- The workflow that breaks you (Month 3) makes you stronger
- Invest in infrastructure: alerts, health checks, documentation
Would We Do It Again?
Absolutely. Even with Month 3's disaster, ROI is undeniable. But we'd do these things differently:
1. Set up monitoring from Day 1: Don't wait for failure to add alerts.
2. Build rollback capability: When things break, you need fast manual fallback.
3. Document edge cases as you find them: Don't trust memory—write it down.
4. Plan for API changes: Subscribe to provider changelogs. Set calendar reminders to check quarterly.
5. Start with weekly check-ins, not monthly: Catch issues early.
The bottom line: One workflow replaced 15 hours of monthly work. After initial hiccups, it runs flawlessly. Finance team now does strategic work instead of data entry. Company culture shifted from "we don't have time" to "what else can we automate?"
That cultural shift? That's the real ROI.