You signed a 3-year contract for your SaaS platform based on a build timeline that no longer exists. Building a custom replacement used to take twelve months and an entire engineering team. That timeline has collapsed to days or weeks.
The build-complexity moat — historically the strongest economic justification for SaaS lock-in — dissolved in roughly 18 months. Enterprises are already building in numbers that would have been unthinkable two years ago: 1 Source 1 Retool 2026 Build vs. Buy Report. 817 enterprise respondents. https://retool.com/reports/state-of-ai-2026
- A majority now ship production software with AI assistance. 51% did so in 2026.
- A third have already replaced a SaaS tool. 35% swapped at least one out for custom-built software.
- Most plan to build more. 78% intend to expand what they build this year.
That gap, between the contract you signed and the market you’re now in, is what the Full-Stack Cost Index (FSCI) was built to price. Most TCO models stop at the invoice. FSCI maps seven cost dimensions that determine whether a build-or-buy decision is right, wrong, or a negotiating position you haven’t taken yet.
What is the Full-Stack Cost Index (FSCI)?
The Full-Stack Cost Index is Lynton’s TCO framework for build-vs-buy decisions in the AI era. It maps seven hidden cost dimensions, from dependency labor and AI capability ceilings to switching cost asymmetry, that vendor-supplied calculators systematically ignore. The framework reveals the true compounding cost of SaaS lock-in over a 5-year horizon.
What Existing TCO Models Miss
Vendor-supplied TCO calculators always favor the vendor. That’s not cynicism. They’re built to justify the renewal.
Gartner and Forrester frameworks are somewhat better, but they’re structured around licensing costs and onboarding fees. They don’t model what you’re paying in labor to keep a platform running. They don’t price the switching cost asymmetry — the fact that you pay exit costs once, but pay dependency costs every year you stay. None of them price the AI capability ceiling, which in 2026 is the most consequential dimension of all.
FSCI corrects these gaps. Existing frameworks start at the invoice; the real cost is downstream, buried in partner retainers and admin time. They treat switching costs as a permanent liability, when you actually pay them once and save every year after. And they ignore AI entirely: the value of a software architecture in 2026 is set by what it lets your AI agents do, and that ceiling is the vendor’s roadmap, not your business needs.
The Full-Stack Cost Index: Seven Dimensions
The dimensions are ordered deliberately. Each one reveals a cost the previous one hid. Work through all seven before you run the numbers.
Dimension 1: Direct Platform Cost: The Invoice Problem
Start here, but don’t stop here.
A typical mid-market HubSpot deployment costs approximately $162,000 in Year 1 when you add up the Marketing Hub Enterprise base fee, contact overages, seat costs, Content Hub, Operations Hub, and mandatory onboarding (based on a 100-employee company with a 20-person marketing and sales team, 40,000 contacts, and a 50-page website). 2 Source 2 Lynton line-by-line breakdown: see The Real Cost of HubSpot. Methodology: 100-employee company, 20-person marketing/sales team, 40,000 contacts, 50-page website. HubSpot publishes a 5% annual renewal increase. The effective rate, once tier creep, seat additions, and contact overages are factored in, runs 8–12% based on Lynton’s aggregate client data.
Over five years at 8% escalation, that mid-market deployment approaches $950,000–$1,025,000. The same capabilities on an open-source stack: $2,580–$19,740 per year in platform fees, depending on chosen tooling. 3 Source 3 Open-source stack cost range: open web framework & CMS ($0–$3,600/yr hosting), open source CRM ($0–$3,600), analytics ($0-$1000), workflow automation ($0–$5,400), email delivery ($120–$6,000). Low end assumes self-hosted open-source tools. High end includes paid tiers. Engineering labor excluded from both.
The invoice is the entry point. Most companies stop there. FSCI starts there.
Pull your last 12 months of invoices and agency bills before your next renewal. Add Dimensions 2 and 4 before you model the math.
Dimension 2: Dependency Labor Cost: Where the Real Cost Lives
For most mid-market companies, Dimension 2 doubles or triples Dimension 1.
30–50% of a marketing-ops FTE goes to platform maintenance rather than marketing. Configuring workflows, managing integrations, untangling platform quirks, training new team members on undocumented logic that lives only in someone’s head. Then add the partner retainer: $24,000–$60,000 per year for an agency to handle the platform administration your team can’t do alone. Internal admin time runs approximately $30,000 per year.
Add it all up and the real annual number runs roughly three to four times the headline license fee. Most CFOs are modeling off the invoice. 10 Source 10 A company paying a $43,200 Marketing Hub Enterprise license typically spends $80,000–$120,000 once seats and overages are included, and $150,000–$200,000 per year once partner retainers and admin time are added.
Pull your last 12 months of invoices and agency bills. Add 30% for internal admin time. The gap between that number and what you thought you were paying is Dimension 2.
Dimension 3: AI Coding Tool Cost Collapse (The 2026 Update)
This is the dimension that invalidates every TCO model published before 2025.
One practitioner built a full sovereign stack — website, CMS, CRM, and automation — in four days using AI coding tools. 4 Source 4 X post, June 11 2026. Full stack built with Claude Code: Astro + Payload CMS + Twenty CRM + n8n. Four days. Corroborated in Lynton’s When Building Is Free. SaaStr documents similar velocity across multiple cases: a paid portal tool replaced in one day, and 12+ vibe-coded applications collectively used 800,000+ times. 5 Source 5 SaaStr, 2026. Multiple documented vibe-coding cases. 30–60 min/day maintenance per app reported. https://www.saastr.com GitHub Copilot reached 77,000 enterprise organizations as of Microsoft’s Q2 FY2025 earnings. 6 Source 6 Microsoft Q2 FY2025 earnings. GitHub Copilot enterprise organization count: 77,000 organizations. The build-complexity argument assumed a world where replacing a marketing stack took 6–12 months and a team of engineers. That world ended.
Dimension 3 doesn’t mean you should build everything. It means the build-complexity moat is no longer a legitimate reason to stay. Any vendor quoting a 12-month build timeline at your next renewal is pricing in a risk that no longer exists.
The build-complexity moat was the strongest economic justification for SaaS lock-in for a decade. AI coding tools removed it in 18 months.
For technical leadership: your team’s capacity to prototype a replacement is now days, not months. A working prototype changes vendor math without committing to a migration.
Dimension 4: What is Switching Cost Asymmetry?
Switching cost asymmetry is the structural imbalance between the cost to leave a platform and the cost to stay. Exit costs are paid once, while dependency costs compound annually. CFOs often mistakenly model switching costs as permanent liabilities, making the renewal math favor the vendor instead of the business.
A full-suite migration off HubSpot costs $50,000–$75,000 for the website rebuild, plus $10,000–$25,000 for CRM data extraction and automation rebuild. That sounds large. It is large. But you pay it once.
The ongoing dependency cost — Dimensions 1 and 2 compounding annually at 8–12% escalation — you pay every year. The typical 5-year savings from a full-suite escape is approximately $830,000 ($195,000 modern stack vs. $1,025,000 HubSpot). 7 Source 7 $195,000 over five years: modern stack at $39,000/year average in platform fees and hosting. Excludes implementation engineering labor on both sides. See The Real Cost of HubSpot for detailed inputs. Payback period: 12–18 months.
The asymmetry runs deeper than the migration math. The longer you stay, the more entrenched the dependency becomes. Every new workflow built in the current platform, every report, every automation, raises the switching cost incrementally. The vendor’s leverage grows annually. Yours shrinks.
There’s also a play that doesn’t require migrating at all: the credible prototype. A working replacement built in days is enough to change a vendor negotiation. You don’t have to migrate to use Dimension 4 as leverage. Reframe the switching cost as a one-time capex expense against five years of compounding savings. On a 5-year horizon, staying on a platform with a high Dimension 1+2 score is almost always more expensive than leaving.
Dimension 5: What is the AI Capability Ceiling?
The AI capability ceiling is the hard limit on automation potential set by a vendor’s proprietary architecture. When you rely on a closed SaaS platform, your AI capabilities are locked to their roadmap, preventing you from training autonomous agents on your specific, underlying business data.
Proprietary architecture like HubSpot Breeze is bolt-on AI over a closed CMS and CRM with no access to the underlying data model. You can’t train it on your specific workflows. Customer data enriched over seven or more years may not be exportable in a format suitable for custom model training or autonomous agent integration, which means it powers the vendor’s product roadmap rather than your competitive advantage. 8 Source 8 Lynton client observation on data portability limitations. HubSpot does offer data export functionality for standard objects, but the enriched relationship graph and workflow logic that constitute institutional knowledge are not portable in usable ML-training formats.
Open architecture inverts this. AI agents act across your full data model, automate workflows at any layer, and compound institutional knowledge from your actual customer interactions. The gap between bolt-on AI and native AI on an open stack is not a feature gap. It’s a strategic trajectory gap.
72% of tech leaders say AI ROI is unclear or not yet measurable (KPMG 2025). Part of why: they’re trying to extract AI value through a vendor’s bolt-on layer, not from their own data.
Your platform’s AI ceiling is not abstract. It’s the hard limit on what your marketing and sales teams can automate this year and next. Competitors running open architecture are compounding an advantage that widens every quarter you stay, and the compounding effect is harder to close the longer it runs.
Dimension 6: Integration and Maintenance Debt
This is where the build case is frequently oversold, and where FSCI requires intellectual honesty from both sides of the argument.
SaaS vendors bundle integration maintenance into the subscription fee. Building your own stack means owning the integration layer: API rate limits, schema changes, authentication failures, data format mismatches between tools designed independently. SaaStr data puts maintenance at 30–60 minutes per day per production application, which means five replaced tools equals roughly 25 hours per week of overhead.
That’s real. But it’s only half the comparison.
Proprietary platform integrations fail too. They’re just opaque failures. HubSpot workflow bugs, Salesforce sync issues, data discrepancies you can’t root-cause because you don’t have access to the underlying logic. Lack of control over black-box integration logic. The honest comparison isn’t “self-owned integration debt” vs. “no integration debt.” It’s “self-owned integration debt you can see and fix” vs. “platform integration debt you’re filing tickets about.”
The recommended migration sequence for buyers who score high on Dimensions 1, 2, and 5 is website first, CRM second, automation third. Not because the other layers don’t matter, but because the website is the highest-ROI migration with the lowest organizational disruption. You replace the most visible piece while keeping the operational core stable during transition.
For technical leadership: the question isn’t whether you’ll have integration maintenance. You will. The question is whether you own the code that governs it or whether you’re at the vendor’s support queue.
Dimension 7: Opportunity Cost (The Offensive Case)
The first six dimensions are defensive: what are you spending? Dimension 7 is offensive: what are you leaving on the table?
The $830,000 in 5-year savings isn’t just savings. It’s deployable capital into AI infrastructure that compounds, into site performance that moves conversion rates, into development capacity that builds institutional capability instead of maintaining a vendor dependency.
35% of enterprises replaced a SaaS tool with custom software this year (Retool 2026). 52% of C-suite executives say AI hasn’t delivered expected value (PwC 2026). 9 Source 9 PwC 2026 AI Business Survey. https://www.pwc.com/us/en/tech-effect/ai-analytics/ai-predictions.html The correlation isn’t coincidental: companies trying to extract AI value through proprietary bolt-on layers are hitting the ceiling described in Dimension 5. The ones compounding AI advantages are running open stacks.
You’re not buying software. You’re buying — or foreclosing — strategic optionality.
The capital locked into SaaS contracts is capital you can’t deploy into the AI infrastructure gap widening between you and competitors who moved first. Dimension 7 is what makes this a CEO conversation, not a CFO one.
The FSCI Decision Model
Score your stack across the seven dimensions. The result isn’t a binary “leave/stay” — it’s a decision about where to start.
| Dimension | Score 1–5 | What high means |
|---|---|---|
| D1: Direct Platform Cost | Invoice growing faster than value delivered | |
| D2: Dependency Labor Cost | 2x or more of the invoice hidden in labor | |
| D3: Build Cost Collapse | Vendor’s build-complexity argument no longer holds | |
| D4: Switching Cost Asymmetry | One-time exit cost less than 18-month savings | |
| D5: AI Capability Ceiling | Platform AI blocks your business roadmap | |
| D6: Integration Maintenance Debt | Opaque failures; no access to root-cause or fix | |
| D7: Opportunity Cost | Capital locked that should be deployed elsewhere |
High D1 + D2 + D5: Strong economic and strategic case to move. Start with the website — highest ROI, lowest political risk, fastest payback.
High D4 alone: Don’t migrate yet. Build a credible prototype. Use it to renegotiate the renewal. Spend the switching cost knowledge before you spend the switching cost capital.
High D6 alone: Phase the transition deliberately. Migration sequencing matters more than migration speed. Start with the layer generating the most opaque failures.
High D5 + D7 only: This is the CEO conversation about strategic trajectory, not the CFO conversation about this year’s budget. Bring it to a planning cycle, not a renewal cycle.
Does FSCI Apply to Platforms Other Than HubSpot?
The examples in this article are HubSpot-specific because HubSpot is the platform Lynton spent 16 years inside. The data is concrete, the cost model is verified, and the migration paths are production-tested. The framework itself applies across any mid-market SaaS platform where Dimensions 1, 2, and 5 are plausible: Salesforce Marketing Cloud, Adobe Marketo, Pardot, WordPress VIP. The specific numbers change; the structural logic doesn’t.
The question FSCI asks is the same regardless of platform: what is the true annual cost of the dependency, and what does the alternative look like across all seven dimensions? A vendor that scores well on D3, D5, and D6 — genuinely low build-complexity moat, genuine AI capability, genuinely transparent integration layer — earns the renewal. Most don’t pass that test honestly.
The Framework in Practice
Most mid-market companies have never run the full seven dimensions. They’ve modeled the invoice (D1), vaguely acknowledged switching costs in their worst-case form (D4), and stopped there. That’s how vendors win renewals they don’t deserve.
Run the FSCI before your next renewal. Not to justify leaving, but to know whether leaving is the right call, and what position you’re negotiating from if it isn’t. The answer might be “stay for now and build the prototype.” It might be “leave and start with the website.” It might be “this renewal is your best negotiating leverage you’ll ever have.”
What it won’t be is “sign the renewal and don’t look at the math.”
If you want to run the seven dimensions against your current stack before your next renewal decision, our free AI assessment is the fastest starting point.
The FSCI is the framework for Lynton’s HubSpot Reckoning series. For the line-by-line HubSpot cost breakdown that feeds Dimensions 1 and 2, see The Real Cost of HubSpot. For the build cost collapse thesis behind Dimension 3, see When Building Is Free. For the stay-vs-go decision logic that applies Dimension 4, see Should You Leave HubSpot?. For the sovereign stack architecture that high-scoring companies build toward, see the Sovereign Stack Blueprint.
The research is free. So is the diagnosis — 60 seconds →