Can Google Sheets handle a full three-statement model?

Yes, reliably. A linked P&L, Balance Sheet, and Cash Flow statement — including a working capital schedule and debt waterfall — fits comfortably within Sheets' limits. Models in the $10M–$100M revenue range with monthly granularity typically run 200,000–400,000 cells, well under the 10 million cell cap. Performance degrades noticeably above 500,000 cells or when volatile functions like INDIRECT, NOW(), or OFFSET appear more than 20–30 times in a single file.

What's the maximum number of tabs a Google Sheets model can have?

Google doesn't publish a hard tab limit, but recalculation performance becomes the practical constraint. Models with 15–20 tabs and heavy cross-tab SUMIFS start showing 3–5 second lag on every edit. Beyond 25–30 tabs, most finance teams split into separate workbooks linked via IMPORTRANGE. The Google Sheets API documentation notes the 10 million cell cap applies per file — splitting workbooks resets the clock on that limit.

How do I prevent IMPORTRANGE from breaking in a board pack?

Share the source file directly with every recipient before sending the destination file. IMPORTRANGE connections require the viewer to have at least read access to the source — Sheets won't auto-prompt during a board presentation, it just shows `#REF!`. The safer approach for distributed packages: copy the IMPORTRANGE output ranges, Paste Special → Values only, and break the live link intentionally before you send. Recipients get clean numbers; you lose the live link, which is fine for a static deliverable.

Is Google Sheets or Excel better for LBO models?

For a bank syndicate deal or PE firm that requires Excel deliverables, use Excel. The recipient will need to run their own sensitivity tables, and Sheets-to-Excel exports mangle complex formatting. For internal FP&A work, scenario modeling, or anything where real-time collaboration matters, Sheets is faster to build in and easier to share. The formula engines are functionally equivalent for 95% of what FP&A teams model — the decision is about the downstream audience, not the formulas.

How do I fix slow recalculation in a large Sheets model?

Replace volatile functions first: INDIRECT, OFFSET, NOW(), and TODAY() recalculate on every single edit regardless of whether their inputs changed. Swap INDIRECT for direct tab references where you can. Replace OFFSET-based dynamic ranges with ARRAYFORMULA or FILTER. For models above 300,000 cells, set recalculation to manual via Tools → Calculation → On change and every minute, then recalculate intentionally with Ctrl+Shift+F9. This alone typically cuts edit lag from 4–8 seconds down to under 1 second.

Google Sheets for Finance: What Works and What Breaks

What Google Sheets Does Well for Finance Teams

The collaboration argument is real. According to Google Workspace documentation, up to 100 users can edit a single file simultaneously — which matters when you're pushing a board pack at 11pm and your VP needs to drop commentary into cells you're still formula-checking.

Cross-tab references work cleanly. A DCF that pulls WACC from an Assumptions tab, revenue from a P&L tab, and depreciation from a CapEx schedule is exactly what Sheets was built for:

=NPV(Assumptions!$C$4, 'Cash Flow'!E8:E12) + 'Terminal Value'!$D$3

Named ranges survive tab renames without breaking. ARRAYFORMULA handles column-level calculations without the drag-to-fill brittleness that bites people in Excel. IMPORTRANGE connects workbooks when you need to pull actuals from a source-of-truth file into a reporting model. For the full mechanics of cross-tab formula patterns, see Sheet Formula Patterns for Multi-Tab Financial Models.

Sheets Finance Formula Patterns That Hold Up Under Pressure

SUMIFS across tabs for contribution margin by SKU:

=SUMIFS('P&L'!C:C, 'P&L'!B:B, ">="&Assumptions!$B$3, 'P&L'!D:D, Returns!$A$7)

IFERROR with INDEX/MATCH for pulling cost assumptions without cascading #N/A errors through the model:

=IFERROR(INDEX(Assumptions!$D$2:$D$50, MATCH(B4, Assumptions!$A$2:$A$50, 0)), 0)

INDIRECT for scenario switching — useful when you need to toggle between base/upside/downside without restructuring the whole sheet:

=INDIRECT("'"&$B$2&"'!D"&ROW())

That last one has a cost. A model with 30+ INDIRECT calls can hit 4–8 seconds per edit cycle. INDIRECT is volatile — it recalculates on every change regardless of whether its inputs moved. If your model is pushing past 200,000–400,000 cells, swap INDIRECT for explicit tab references controlled by a toggle cell and a set of IF statements. The formula gets uglier; the model gets usable again.

When to Stop Using Sheets for Finance

Google Sheets caps at 10 million cells per spreadsheet, per the Google Sheets API documentation (as of May 2026). That sounds like plenty until you're running a 5-year monthly model with 400 line items across 3 scenarios — you'll clear 600,000 cells before you've added charts or helper columns. The cap isn't the real problem. These are:

No version control with intent. Google's revision history shows who changed which cell, but not why. When there's a $215K discrepancy in a $4.2M EBITDA figure six weeks after close, you're clicking through 90+ minutes of revision history hoping someone left a comment. They didn't.

IMPORTRANGE authentication is fragile. Per Google Sheets help documentation, IMPORTRANGE requires the viewer to have at least view access to the source file. Send a board pack to an investor who doesn't have source file access and your revenue tab populates with #REF! errors. Not a great look in a bank syndicate DCF review.

Live data requires manual intervention. If your model ingests actuals from Stripe, HubSpot, or your ERP, you're either pulling CSVs manually or maintaining a web of IMPORTRANGE connections that break whenever someone renames a tab upstream.

The Real Bottleneck

The formula patterns aren't the problem. Most finance teams hit a wall on data freshness — specifically, the gap between when data is available in source systems and when it's reflected in the model. The standard workaround (monthly CSV export, paste into the actuals tab, reconcile manually) works until it doesn't. One missed export and your variance analysis is comparing against stale numbers.

ModelMonkey connects Google Sheets directly to HubSpot, Stripe, and other systems, so your actuals tab refreshes without the CSV loop. It lives in the sidebar and doesn't touch your formula structure — you keep the SUMIFS and ARRAYFORMULAs, you just stop managing the data pull by hand.

In summary: Sheets is the right tool for building, reviewing, and presenting financial models. It becomes the wrong tool when your model needs to stay current automatically, or when your organization needs a change log that holds up to audit scrutiny.

Try ModelMonkey free for 14 days — it works in both Google Sheets and Excel.