You signed up for a bundled platform on year one's promise: CRM, messaging, invoicing, and accounting in one place at ₹35 lakhs annually. The math felt clean. No Zapier integrations. No separate vendor negotiations. One contract, one login, one bill. Then year two lands. Your team grew. API calls tripled. You needed the advanced contract module. Storage overages appeared. When you run the renewal numbers, the bill sits at ₹52 lakhs—48% higher—and the conversation shifts from "this was a good decision" to "why didn't anyone warn us about this?" This is not a platform failure. It is how bundled software actually works. When you consolidate tools, you also consolidate growth costs. The vendors know this. Your finance team should too. The year-one illusion Bundled platforms compete on a simple promise: lower total cost of ownership. You trade single-tool optionality for all-in-one simplicity. The per-user fee looks 30–40% cheaper than buying CRM, invoicing, and accounting separately. Year one delivers on that premise. A 10-person team on Orin at ₹35L feels like a win next to: HubSpot CRM: ₹10L (10 seats at ₹1L each) Separate invoicing (Zoho or Xero): ₹3–5L Accounting sync or native tool: ₹2–3L SMS/messaging layer: ₹1–2L That bundle is genuinely cheaper. But it assumes your team stays at 10 people, your API calls stay flat, and you never need a feature outside the standard tier. None of those assumptions hold. Scenario 1: The agency that discovered API overages A 12-person digital agency signed up for a bundled platform. Year-one spend: ₹36L. By month eight of year two, they'd hit API quota limits. Each client project was a fresh integration: pulling data from Shopify, syncing leads to their CRM, triggering SMS reminders for booked calls. The bundled platform's base plan included 500 API calls per month per user. They needed 8,000. Cost breakdown for year two: Base (12 seats at ₹2.8L per seat): ₹33.6L Seat creep (+3 people at ₹2.8L): ₹8.4L API overage tier (5,500 calls/month): ₹6.8L Advanced contracts module: ₹2.1L Storage overage (50 GB beyond limit): ₹0.9L Total: ₹51.8L That is a 44% increase. The agency was paying ₹1.43L per extra month of service. They couldn't undo it mid-contract. They either ate the cost or spent 60 days migrating to a modular stack. What would they have paid for best-of-breed alternatives? A CRM like Pipedrive (₹14L), Zapier (uncapped at ₹6L for 8,000 tasks), a separate invoicing tool (₹3.6L), and accounting (₹1.8L) would land at roughly ₹25.4L. But they would now own integration debt: setting up workflows, debugging syncs, managing data flows across four separate vendors. That costs 2–4 weeks of engineering time or $2–4K in outsourced integration work. Scenario 2: The services firm drowning in timecard bloat A 15-person services firm used the bundled platform's built-in HR and timecard module. Year one: ₹42L, neat and tidy. By year two, they were running four concurrent projects with staggered billing periods. The timecard module worked, but barely. Managers were logging into separate dashboards to reconcile hours against project codes. The native accounting module didn't auto-route billable vs. non-billable hours by project. Custom fields for tax codes (critical in their jurisdiction) hit a hard limit of 20. They needed 28. Cost for year two: Base (15 seats): ₹42L Seat creep (+2 new team members): ₹5.6L Advanced HR module (attendance, compliance, workflows): ₹3.2L Advanced accounting module (multi-project GL, custom fields): ₹2.8L Custom API integrations (to route hours correctly): ₹1.8L Professional services (data migration, training, custom fields setup): ₹2.1L Total: ₹57.5L That is 37% growth year-on-year. And they still weren't happy. The bundled platform's HR module lacked local compliance reporting for their jurisdiction. They ended up running a separate compliance tool anyway—negating the integration benefit entirely. What would a modular stack cost? A best-of-breed HR tool (₹4.2L), a dedicated project accounting platform (₹3.6L), their existing CRM (₹14L), and invoicing (₹3.6L) would total ₹25.4L—but they would need a middle layer like Orin's automation engine to sync hours to billing, billable hours to invoices, and invoices to GL accounts. That adds another ₹1.2L, landing at ₹26.6L. The modular path saves money but trades complexity for flexibility. Scenario 3: The SaaS team hit by usage-based module explosions A 20-person SaaS company chose a bundled platform with metered billing, AI features, and storage pooling. Base cost year one: ₹48L. Year two: they launched a new product line, onboarded 200 additional customers, and activated the embedded AI chat widget for all of them. Suddenly: Storage jumped 400 GB (beyond the 200 GB base): overage charges of ₹4.2L AI chat widget scaled to 50,000 monthly interactions (from 2,000): ₹3.6L API calls for customer data syncs: ₹2.8L Seat creep (team grew to 25): ₹2.8L Advanced permissions and audit logging (compliance requirement): ₹1.4L