Data Analytics in San Francisco, USA

SaaS / Enterprise Software / Data Analytics / San Francisco

A San Francisco-based Series D SaaS company ($185M ARR, 2,800 enterprise customers, providing a cloud security platform for mid-market and enterprise companies, with 1,100 employees and $420M in total funding, with board-level discussion of an IPO within 18-24 months) needed a revenue intelligence platform that would transform its fragmented analytics into an IPO-ready metrics infrastructure. The company had grown rapidly (85 percent YoY for 3 consecutive years) but was approaching the scale where growth-stage analytics were insufficient and public-company-grade analytics were required. Core challenges: (1) Metrics fragmentation — the company's key metrics were calculated in 5 different systems: ARR in the billing system (Stripe), pipeline in CRM (Salesforce), product usage in the analytics warehouse (Snowflake), customer health in the CS platform (Gainsight), and financial reporting in the ERP (NetSuite). Each system had its own definition of fundamental concepts: "customer" was defined differently in Salesforce (by account) versus Stripe (by subscription) versus Snowflake (by workspace). The company had 3 different ARR numbers floating around the organisation — the billing system showing $185M, the finance team reporting $181M (after adjustments for credits and disputes), and the board deck showing $188M (including committed but not yet billed contracts). This "ARR spread" was unacceptable for an IPO-track company — public market investors and SEC scrutiny requiring one auditable number. Net Revenue Retention: the company's most important metric was calculated manually by a 3-person analytics team — a monthly process taking 2 weeks that involved reconciling expansion, contraction, and churn across billing and CRM data. The manual process was error-prone (the team had corrected NRR calculations retroactively 3 times in the past year) and opaque (board members asking "how is this calculated?" received different answers from different people). (2) Cohort analysis debt — investors and the board wanting cohort analytics showing how each customer vintage performed over time. The company could produce basic cohort charts but couldn't answer follow-up questions: "what's the NRR for the 2023 cohort versus the 2022 cohort, controlling for segment and use case?" or "which product module drives the most expansion within the first 12 months?" The analytics team spending 60 percent of their time on ad hoc data pulls for executive and investor requests — each request taking 2-5 days because the underlying data wasn't structured for flexible analysis. Pre-IPO investor due diligence (the company had received inbound interest from 3 crossover funds) required analytical depth that the current infrastructure couldn't provide — fund analysts wanting to decompose growth into new business, expansion, price increases, and cross-sell, with each component trackable over time. (3) Product usage to revenue disconnect — the company selling a cloud security platform with usage-based pricing (base subscription plus consumption for data scanned, APIs monitored, and cloud accounts protected). Product usage data lived in Snowflake, billing data in Stripe, and account relationship data in Salesforce — but the three were poorly connected. The company couldn't answer: "which customers are using more than their contracted capacity and should be upsold?" or "which customers have declining usage and are at risk of downsizing?" — the two most important commercial intelligence questions for a usage-based SaaS company. Product-qualified expansion: usage patterns that predicted expansion (customers adding new cloud environments, increasing scan frequency, or exploring new product modules) weren't systematically identified or routed to the sales team. The expansion pipeline was driven by account manager intuition rather than data. (4) Customer health scoring — the company had implemented a CS platform (Gainsight) with customer health scores, but the scores weren't trusted. Health scores were based on: support ticket volume, NPS survey responses, and product login frequency — but not on actual product usage depth, billing trajectory, or competitive intelligence. A customer could have a "green" health score while usage was declining and they were evaluating competitors — because the health score didn't incorporate the signals that actually predicted churn. Customer success managers making portfolio decisions based on unreliable health scores — spending time on "green" customers who didn't need attention while missing "green-but-actually-at-risk" customers who were quietly churning. The company's logo churn was 8 percent annually — acceptable for enterprise SaaS — but gross revenue churn was 12 percent because the highest-churning customers tended to be larger accounts. (5) SOX readiness — the company's CFO and auditors (Big Four, engaged in anticipation of IPO) identifying material weaknesses in the analytics infrastructure: revenue recognition (ASC 606) calculations done partially in spreadsheets, no single source of truth for financial metrics, and insufficient controls around metric calculation changes. The auditors recommending 12-18 months of remediation — the CFO wanting to accomplish this in 6 months to maintain the IPO timeline. SOX compliance requiring: documented metric calculation methodologies, change control for analytical processes, access controls for financial data, and audit trails for all financial reporting.

We built a revenue intelligence platform over 10 weeks — creating a single source of truth for all SaaS metrics with SOX-ready controls and IPO-grade analytical depth. (1) Unified metrics layer: one number for every metric. Data integration: connecting Stripe (billing), Salesforce (CRM), Snowflake (product usage), Gainsight (CS), and NetSuite (financials) into a unified metrics model — reconciling entity definitions: "customer" = Salesforce Account, linked to Stripe subscriptions and Snowflake workspaces through deterministic matching. Canonical metrics: every metric calculated once, in one place, with one documented methodology. ARR: sum of all active subscriptions' annualised contracted value, excluding one-time services, with standard adjustments for mid-period changes. NRR: calculated as (starting ARR + expansion - contraction - churn) / starting ARR, with expansion, contraction, and churn each having documented definitions and allocation rules. The "ARR spread" eliminated — one number, auditable from subscription level through financial statement. Metrics catalogue: every metric documented with: definition, calculation methodology, data sources, update frequency, owner, and change history. The catalogue serving as the single reference for: board reporting, investor due diligence, SEC filing preparation, and internal decision-making. Real-time versus period-end: metrics available in two modes — real-time operational view (updated hourly, used for day-to-day management) and period-end financial view (calculated with month-end close adjustments, used for reporting and auditing). Both views reconcilable to each other with documented differences. (2) Cohort and decomposition analytics: investor-grade growth analysis. Cohort engine: flexible cohort analysis across multiple dimensions — customer vintage (sign-up date), segment (SMB, mid-market, enterprise), use case (cloud security posture, runtime protection, API security), geography, and acquisition channel. Any combination queryable interactively, not through ad hoc data pulls. Growth decomposition: total ARR growth decomposed into: new business (first contract), expansion (increased usage or upsell within existing customer), price increase (contractual escalation), cross-sell (new product module), contraction (decreased usage or downgrade), and churn (customer cancellation). Each component trackable over time and by cohort — the analysis that crossover fund analysts would perform during due diligence, now available in real-time. Self-service exploration: business users (VP Sales, VP CS, CFO, CEO) able to explore cohort data without submitting requests to the analytics team — interactive dashboards with drill-down from portfolio to segment to individual customer. Analytics team time on ad hoc requests from 60 percent to 15 percent of total time. Unit economics: customer-level unit economics — CAC (including allocated sales, marketing, and onboarding cost), LTV (projected based on cohort behaviour), payback period, and margin contribution — all available at the individual customer and cohort level. (3) Product-revenue intelligence: connecting usage to commercial outcomes. Usage-to-billing bridge: product usage data (data scanned, APIs monitored, cloud accounts protected) linked to billing contracts — real-time visibility into: customers exceeding contracted capacity (upsell opportunities), customers significantly under-utilising capacity (potential downsize or churn risk), and customers approaching capacity limits (proactive expansion conversations). Expansion signals: machine learning models identifying usage patterns that predict expansion — customers adding new cloud environments, increasing scan frequency, exploring new product modules, or inviting new users. These signals routed automatically to account managers as "expansion opportunities" with specific context: "Customer X has added 3 new AWS accounts in the past 30 days, increasing their cloud footprint 40 percent beyond contracted capacity — estimated expansion opportunity: $85K ACV." Consumption forecasting: predicting each customer's future consumption based on usage trajectory — enabling finance to forecast usage-based revenue more accurately and enabling CS to proactively manage customers approaching capacity inflection points. Product adoption analytics: measuring which product capabilities each customer was using, which they weren't, and which unused capabilities were correlated with higher retention — enabling targeted product adoption campaigns. (4) Customer health 2.0: multi-signal health scoring. Rebuilt health model: customer health scores rebuilt from scratch using signals that actually predicted outcomes — not just support tickets and logins, but: product usage depth and trajectory (the strongest predictor), billing trajectory (expanding versus contracting), stakeholder engagement (champion activity, executive sponsor engagement), competitive signals (G2 review activity, RFP participation), and support sentiment (NLP analysis of ticket content, not just volume). Predictive churn: the health model predicting customer churn with 78 percent accuracy at 90 days — compared to 34 percent accuracy from the previous Gainsight-based scoring. Segmented risk: health scoring calibrated by customer segment — enterprise customers and SMB customers having different baseline engagement patterns, so "healthy" looked different for each. Actionable alerts: health score changes triggering specific interventions — score declining from "healthy" to "at risk" automatically notifying the CS manager with: root cause analysis (which signals changed), recommended action (based on what worked for similar customers), and estimated impact (revenue at risk). (5) SOX-ready controls: IPO-grade governance. Change management: all metric calculation changes going through a formal process — proposed change documented, impact analysis (how does this change affect reported metrics historically?), peer review, CFO approval, and version-controlled deployment. Audit trail: every metric calculation logged with: input data, calculation timestamp, methodology version, and output. Any historical metric reproducible — "what was ARR as of March 31, 2025, calculated with the methodology in effect at that time?" Access controls: role-based access to financial data — analysts could explore product and usage data freely, but financial metrics (ARR, NRR, revenue) had restricted access with audit logging. Month-end close: automated month-end close process — reconciling real-time metrics to financial statements, documenting adjustments, and producing a close package that auditors could review. Close timeline: from 18 business days to 8 business days.

Results over 12 months. Metrics accuracy: the "ARR spread" eliminated — one auditable ARR number used across all contexts (board, investors, internal). NRR calculation from 2-week manual process to automated daily update — zero retroactive corrections in 12 months (versus 3 in the prior year). Auditor assessment: Big Four auditors upgrading the analytics infrastructure from "material weakness" to "effective controls" — removing the primary blocker to IPO timeline. Investor readiness: crossover fund due diligence completed in 3 weeks (versus the 8-12 weeks the company had anticipated) — fund analysts noting "the best metrics infrastructure we've seen in a pre-IPO company." The fund investing $120M at a 35 percent valuation premium to the company's internal estimate — the analytics infrastructure directly contributing to the higher valuation. Analytics efficiency: analytics team ad hoc request time from 60 percent to 15 percent — enabling the team to focus on strategic analysis rather than data pulls. Self-service dashboard adoption: 85 percent of previously ad hoc requests now answered through self-service tools. Revenue intelligence: expansion opportunities identified through product-usage signals generating $28M in incremental ARR in Year 1 — account managers receiving data-driven expansion alerts rather than relying on relationship intuition. Usage-to-billing bridge identifying $14M in contracted capacity overages that hadn't been billed — immediate revenue recovery. Customer health: rebuilt health scoring predicting churn with 78 percent accuracy (versus 34 percent previously). At-risk interventions preventing $22M in churn — CS managers receiving actionable alerts 90 days before predicted churn, with specific root cause and recommended action. Gross revenue churn from 12 percent to 8.4 percent in Year 1 — preserving $6.7M in ARR. Operational: month-end close from 18 to 8 business days — enabling faster financial reporting and decision-making. Board deck preparation from 5 days to 1 day — automated dashboard replacing manual compilation. Investor reporting automated — quarterly investor updates generated from the same metrics platform used for internal management. Financial impact: expansion revenue $28M; billing recovery $14M; churn prevention $22M; valuation premium (attributed to analytics infrastructure) estimated at $120M implied in funding round; operational efficiency $2.8M (analytics team, finance team time savings). Annual quantifiable impact: $66.8M (excluding one-time valuation impact). Development: $620K. Annual platform: $180K. ROI: 107x first year.