SaaS Revenue Metrics & Cohort Analytics

Board packs and investor updates run on a metric vocabulary NetSuite does not natively speak. Finance can produce a flawless income statement and still be unable to answer, without a spreadsheet, how much of this month's recurring revenue movement was new business, how much was expansion on existing accounts, how much was contraction from seat reductions, and how much walked out of the door. NetSuite holds every input — subscriptions, subscription lines, subscription change orders, invoices, revenue arrangements, revenue recognition plans, customer records — but it stores them as transactions inside accounting periods, not as a monthly recurring-revenue ledger with movement attribution.

A saved search can sum invoice amounts in a period. It cannot express that one customer downgraded two seats in March, upgraded in July, and therefore belongs to both the contraction and the expansion bucket of the same trailing-twelve-month window. It cannot produce a cohort triangle showing what the accounts that started in a given quarter are worth eighteen months later. It cannot separate committed recurring revenue from one-time implementation fees and usage overages sitting on the same invoice. So the month closes, someone exports several saved searches into a workbook, reapplies last month's formulas, finds the ARR number no longer ties to the general ledger, patches it by hand, and ships the deck. The metrics are unauditable, they drift between analysts, and nobody can drill from a number on slide four back to the subscription line that produced it.

What ECOSIRE builds

ECOSIRE builds a SuiteScript 2.1 metrics engine that sits on top of your existing subscription and billing data, produces an auditable month-by-month recurring-revenue ledger inside NetSuite, and reports on it without an export step.

A normalized recurring-revenue ledger

The foundation is a custom record type holding one row per customer, per subscription line, per accounting period. A Map/Reduce script walks subscription, subscription line and subscription change order records using SuiteQL through the N/query module, normalizes every billing frequency — monthly, quarterly, annual, multi-year, prepaid — down to a single monthly recurring amount, and stamps each row with subsidiary, currency, item, price plan, sales rep, customer segment and any custom segment values you already use for reporting. One-time fees, professional services and usage-based charges are tagged rather than deleted, so they can be reported separately or folded into a broader revenue view at your discretion.

Where SuiteBilling is not in use, the same ledger is derived from Sales Order and Invoice transaction lines filtered by recurring item types and contract dates. The downstream metrics are identical; only the source lane changes.

Movement classification with an arithmetic guarantee

Every period-over-period delta is classified as new, expansion, contraction, churn, reactivation or non-recurring. The engine then asserts that opening MRR plus every movement equals closing MRR for each subsidiary and segment. If the assertion fails, the run fails and the period is not published — a broken month is visible immediately rather than surfacing as an unexplained variance in a board meeting six weeks later.

Metrics and cohorts

On top of the ledger the engine computes ARR, ARPA, logo churn, gross revenue retention, net revenue retention and the quick ratio per period, per segment and per subsidiary, writing results to a metrics custom record so history is immutable and comparable. The cohort engine keys accounts on their first revenue period and produces both revenue and logo retention triangles by months-since-start, which is what makes expansion visible: a cohort can retain 95% of its logos and 115% of its revenue, and the two facts belong in the same table.

CAC payback and LTV are calculated from a sales-and-marketing spend custom record fed by GL account, department, class and custom segment totals, combined with the new-logo counts already in the ledger. Gross-margin assumptions are configuration, not hard-coded, and every assumption is recorded on the metric row that used it.

Reporting surfaces inside NetSuite

SuiteAnalytics workbook datasets are built over the snapshot records so finance can pivot and chart without touching script. A custom dashboard portlet puts the current-month movement waterfall on the home page. A Suitelet drill-down opens the underlying subscription, invoice or customer record behind any figure, so a question in a board meeting is answered with a record, not a formula. A token-authenticated RESTlet exposes period metrics and cohort rows as JSON for your BI or warehouse tooling.

OneWorld, currency and period discipline

In OneWorld accounts the engine filters and rolls up by subsidiary, translates to a reporting currency using consolidated exchange rates, and aligns strictly to accounting periods rather than calendar months. Closed periods are immutable by default; restating a closed period is an explicit, logged action available only to the role you designate.

Who it is for

This is for SaaS and subscription businesses already running billing in NetSuite that have outgrown saved searches — typically companies reporting to a board or investors monthly, with multiple products or plans, contraction and expansion happening on live contracts, and a finance team currently rebuilding the same workbook every month. It is equally relevant to OneWorld groups where each subsidiary sells the same product and the consolidated retention picture is currently guesswork.

It is not a fit if you have no recurring contracts, or if your recurring revenue lives entirely outside NetSuite in a billing system that does not push line-level detail into the ERP. We will tell you that on the scoping call rather than after the quote.

How delivery works

Everything ECOSIRE sells is built to order. Nothing here is a pre-packaged download and there is no trial to install.

1. Scoping call. We walk your account with you: how subscriptions are modelled, which item types are recurring, how change orders are raised, what your current metric definitions are, and which subsidiaries and segments matter. Metric definitions are agreed in writing — MRR is not a universal constant, and the version we build has to be the version your board already uses.

2. Fixed quote. You receive a fixed-price quote and a written scope covering record types, scripts, reporting surfaces, historical backfill range and the support window. No hourly drift.

3. Build. We develop against your sandbox as an SDF project. Typical build time is two to four weeks from a signed quote, longer where a deep historical backfill across many subsidiaries is in scope.

4. Install in sandbox, then production. The project is deployed to your sandbox first for user acceptance testing with your real data, including a full backfill run and a reconciliation of closing MRR against the general ledger. Only after you sign off does it go to production as an unmanaged bundle or SDF deployment that you own outright.

5. Support. Training sessions for the finance team, written documentation of every metric rule, and a post-go-live support window for defects and configuration adjustments. Because you own the source and the SDF project, you are never locked to us for future changes.