Executive KPI Dashboard Pack

The pain: the numbers exist, the view does not

The data an executive team needs is already in NetSuite. Cash is in the bank accounts and the Bill and Invoice ledgers. Margin is in Item Fulfillment and Invoice lines against item costs. Pipeline is in Opportunities and Estimates. Inventory turn is in Item records and Inventory Detail. AR ageing is in open Invoices with terms.

What is missing is the view. Getting from that raw data to a monthly board pack usually means someone exporting four or five reports, pasting them into a spreadsheet, adding formulas that only they understand, and circulating a PDF that is out of date the day it lands. Ask a follow-up question and the whole cycle repeats. Meanwhile the standard NetSuite home dashboard shows whatever portlets happened to be there when the account was implemented, and nobody trusts the numbers on it enough to act.

The usual answer is a BI project — a warehouse, a connector, an extract schedule, a licence per viewer and a consultant to model the data. That is a reasonable answer for some organizations and a disproportionate one for most. This pack takes the other path: build the reporting inside NetSuite, on native saved searches, KPI scorecards and dashboard portlets, against your actual account structure. No export, no second system, no separate licence per viewer, and numbers that are live because they are the same records the business is transacting on.

This is a build-to-order NetSuite customization. It is not a pre-built file you download. After a scoping call ECOSIRE quotes a fixed price, builds the dashboards against your chart of accounts, subsidiaries, item types, sales structure and custom segments, and deploys them to your sandbox first.

What ECOSIRE builds

Five dashboard domains

Cash. A cash position portlet reading bank and credit-card account balances by subsidiary and currency, with a forward view built from open Vendor Bills by due date against open Invoices by expected receipt date. Saved searches drive a rolling short-term outflow-versus-inflow picture, and a KPI scorecard trends the closing position period over period.

Margin. Gross margin by item, item group, customer, sales rep and subsidiary, built from Invoice and Item Fulfillment lines against item cost. The build handles your costing method and, where you use them, the standard-cost or average-cost fields on the Item record. Margin trend uses a KPI scorecard with prior-period and prior-year comparison, so the board sees direction rather than a single number.

Pipeline. Weighted and unweighted pipeline by stage, sales rep, territory and expected close date, from Opportunity and Estimate records. Conversion ratios between stages, and won-versus-lost by reason, come from saved searches with summary criteria rather than exported spreadsheets.

Inventory turn. Turn and days-on-hand by item, item class, location and subsidiary, built from Item records, Inventory Detail and fulfilment history. Slow-moving and excess stock surface as their own searches with configurable thresholds, alongside stockout risk based on quantity available against recent consumption.

AR ageing. Ageing buckets by customer, subsidiary and currency, with days-sales-outstanding as a KPI scorecard, disputed and promised-to-pay flags carried through from custom fields if you use them, and a collections worklist ordered by exposure.

How it is built

Everything is native NetSuite objects. Saved searches carry the logic, with summary types, formula fields and available filters set so a user can re-slice without editing the search. KPI scorecards hold the period-over-period comparisons. Dashboard portlets — KPI meters, trend graphs, report snapshots and custom search results — are arranged into published dashboards assigned by role.

Where native searches genuinely cannot express a calculation, a SuiteScript 2.1 custom portlet or a Scheduled script writing to a summary custom record fills the gap. We use that sparingly and tell you exactly where, because a saved search your administrator can read and change is worth more than a clever script they cannot.

OneWorld accounts get subsidiary-aware searches and consolidated-versus-entity views, with currency handled through the exchange-rate fields rather than hard-coded conversions. Custom segments already in your account are carried into the searches as filters and grouping dimensions.

Delivery to the right people

Dashboards are published per role — an executive view, a sales-leadership view, a finance view, an operations view — so each audience sees the subset that applies to them, with NetSuite's own role permissions still governing what data they can read. Scheduled saved-search emails deliver the key numbers to inboxes on your cadence, and where the board wants a formatted pack, an Advanced PDF/HTML template renders it from the same searches.

What we do not do

We do not invent metrics. Every KPI in the pack is defined with you during scoping, written down with its exact source records and filters, and reconciled against a report you already trust before sign-off. If a number cannot be tied back to a NetSuite record, it does not go on the dashboard.

Who this is for

NetSuite customers who want management reporting without standing up a BI stack: owner-managed businesses where the executive team is small and time-poor, multi-entity groups on OneWorld that need consolidated and per-subsidiary views side by side, and finance teams who currently rebuild the same board pack by hand every month.

How delivery works

1. Scoping call. We agree the metric list, the definition of each one, the dimensions you slice by, and which roles get which dashboard. We look at your chart of accounts, subsidiaries, item types, sales structure and custom segments. 2. Fixed quote. Written scope and fixed price before any build. Additional metrics beyond the agreed list are quoted separately. 3. Build. Saved searches, KPI scorecards, dashboards, roles and any supporting SuiteScript are developed as an SDF project under version control. 4. Install in sandbox. Deployed to your sandbox first. You compare each figure against the report or spreadsheet you use today, and we reconcile any difference before it goes further. 5. Production install. The same SDF project or unmanaged bundle is deployed to production, dashboards published to the agreed roles. 6. Support. A support window after go-live covers defects and definition adjustments. You own the searches and the project, so your administrator can change a filter without a support ticket.

Lead time is typically one working week from signed quote to sandbox delivery, driven mostly by how quickly the metric definitions are agreed.