Platform Insights and reporting¶
Draft. Platform Insights has implemented reporting services and a partially connected staff console. The intended screens are further ahead than the frontend. Hosted availability, reporting accuracy for a particular environment and reader acceptance remain under review.
Platform Insights helps authorized Zerohive platform administrators understand subscriptions, commercial activity, customer growth and licensed capacity across the platform. It brings related measures together so the responsible team can investigate changes rather than judge the business from a single total.
This is a platform staff capability. Being an executive, workspace administrator, manager or billing contact does not automatically grant access. Ordinary members and external participants continue to work within their own permissions. An authorized team can explain relevant findings through an approved reporting process without exposing another organization's information.
For analytics within an organization's work, see HiveOrbit. For an individual invoice, payment or commercial intervention, see billing operations. Platform Insights supplies context; it does not itself change a subscription, purchase capacity, approve a refund or contact a customer.
Questions the views help answer¶
| View | Useful questions | Read the results with |
|---|---|---|
| Revenue | What paid invoice value is recorded? What is the current recurring run rate? How is it distributed across plans? | Currency, reporting dates, invoice timing and current plan attribution |
| Subscriptions | How many accounts have each subscription state? What are the plan and seat distributions? How do selected groups compare over time? | The distinction between current records and a reconstructed historical snapshot |
| Countries | Where are accounts and revenue concentrated? How do markets differ in growth, trials and plan mix? | The different meanings of the map and revenue table |
| Growth & Trials | How many accounts were created or activated? Which trial cohorts later paid? Which trials are approaching expiry? | Cohort membership and whether a measure uses the selected window or today's date |
| Products & Seats | How many seats, memberships and product licences are recorded? Where is capacity being added? | Licensing and membership counts, which are different from actual product use |
| Churn analysis | Which subscriptions have ended, what reasons are recorded, and what payment recoveries are visible? | The recorded cancellation and payment definitions, not assumed customer intent |
Understand the dates before comparing results¶
A reporting window selects activity between two times. An as-of date is a cutoff used by particular views. Granularity groups a trend into days, weeks or months. These controls serve different purposes; changing one does not make every card a historical snapshot.
The current reporting implementation combines activity within the selected window with current account, plan, membership and licence records. For example, recurring revenue uses current recurring amounts, and a past subscription cutoff filters when accounts were created without reconstructing their old subscription states. A plan change made later can therefore affect the interpretation of an earlier period.
Some trial-expiry lists count forward from the current time, even while a past period is selected. Product adoption uses current licence and access records. A comparison should state the dates, the measure, the population and when the result was retrieved. Preserve that context when sharing findings; a screenshot without its filters can be misleading.
Revenue, recurring value and payment outcomes¶
Recorded revenue is derived from paid invoices. The query uses their net amounts even where the interface calls the total “Gross Revenue.” This is not a complete accounting statement, a bank settlement reconciliation or a tax-inclusive sales total. Reconcile important financial decisions with the responsible finance team's records.
Monthly recurring revenue (MRR) is the current recurring amount for accounts classified as active, trialing or past due. Annual recurring revenue (ARR) is that monthly amount multiplied by twelve. ARR expresses a run rate, not a promise that this amount will be collected over the next year. Average revenue per account (ARPA) in the revenue summary divides MRR by the current count of those accounts; other views use different revenue bases.
The payment-success measure compares paid invoices effective in the period with invoices issued in the period. Those can be different sets of invoices. Past-due counts can also include older unpaid invoices. Do not interpret these three counts as mutually exclusive pieces of one fixed cohort or infer a payment-provider success rate from them.
Revenue movement distinguishes new recurring value, expansion and ended subscriptions. In the inspected implementation, contraction is not calculated and its returned value is always zero. A zero contraction value therefore does not demonstrate that no customer reduced their commitment. Expansion uses qualifying paid purchase amounts; it should not be assumed to be a normalized recurring uplift.
The commercial breakdown distinguishes self-service Enterprise, quote-only Enterprise Plus and direct Private Cloud records. Private Cloud attached to Enterprise Plus is included within the Enterprise Plus population; adding the attachment count again would double-count those customers. A reporting category or historical commercial record does not establish that a product or hosting option is currently available to purchase.
Currency and forecasts¶
The currency selector does not convert every card. The revenue trend accepts a reporting currency, while the revenue summary and forecast use USD. Country performance provides USD and a country-local amount; the current country view does not support an arbitrary reporting-currency selection.
Conversion uses recorded exchange rates effective on or before the relevant date. If neither a usable direct rate nor a reverse rate is found, the current calculation retains the original amount. A currency label alone therefore does not prove that every contributing amount was converted. Missing-rate handling and reconciliation must be checked before comparing markets or relying on combined totals.
The forecast projects recurring value using recent trial conversion, churn and expansion assumptions. Its upper and lower ranges are calculated heuristics, not statistically calibrated confidence intervals. The model does not guarantee future sales, payments, renewals or customer retention. Read the assumptions, compare them with the commercial circumstances, and explain uncertainty when using the projection in planning.
Subscriptions, countries and customer retention¶
Subscription views group accounts by their recorded status, plan and hosting model. A cohort is a selected group of accounts, such as those created or activated in a given period. The retention calculation uses recorded creation, activation, payment and period-end dates; it does not replay the complete history of every subscription.
Future cohort offsets are not automatically excluded by the current calculation. A populated cell must not be treated as an observed future outcome. The final design's presentation and the implementation still need reconciliation for this case.
Country concentration shows how much of recorded period revenue belongs to the largest markets. However, the map's revenue measure is a recurring-value snapshot, while the table's revenue is paid invoice value in the reporting window. The two do not measure the same thing and need not reconcile. Country rows are based on represented account records; a country missing from the result is not proof that its market has no potential or that Zerohive is unavailable there.
Churn analysis counts subscriptions currently marked canceled or expired whose recorded period end falls within the window. Its reasons come from available billing activity, with a status fallback. They are not a customer survey. A recovered account means a later paid invoice was found after an earlier non-paid invoice in the selected period; it does not prove that a previously departed customer returned.
Net revenue retention combines the starting recurring base, ended recurring value, recovered value and qualifying expansion amounts. It can exceed 100%, but the current calculation uses record-based approximations and mixed payment and recurring measures. Use it as an investigation signal with those definitions attached.
Growth, trials, capacity and product adoption¶
New accounts are selected by creation date. Activation rate uses accounts created in the window and activated within it. First-payment conversion counts can include older accounts, and trial-cohort conversion can reflect a payment after the selected period. These populations should not be combined into a single funnel without checking the definitions.
Licensed seats represent recorded capacity. Active memberships represent membership records marked active; one person can hold memberships in more than one organization. They are not a count of unique people who logged in or used the product recently. Seat utilization compares those membership records with licensed seats and can exceed 100% in inconsistent or overallocated data.
Product adoption describes recorded access and product licences. It does not measure time spent, completed work, satisfaction or productivity. The current calculation can count an organization as having access because a licence record exists even if that record is no longer active. Review the accompanying active-licence count before concluding that everyone counted can use the product today.
Advanced HiveComms demand distinguishes active add-on seats, seats purchased in the reporting period and seats with cancellation scheduled for term end. Scheduled cancellation is different from completed expiry. Recorded purchase workflow quantities also need outcome reconciliation before being treated as completed, paid capacity changes.
When results are missing or unexpected¶
A reported zero, a missing measure, an empty list and a failed request have different meanings. The current view retains successful reports when another report is unavailable and identifies the missing part. An unavailable view can result from access, invalid selections or a service failure. Neither an empty presentation nor a selected URL proves that no business activity occurred. Read the displayed issue and the available figures in their own scope.
The current views include nested cohort, product, seat and forecast details. That does not certify that every relevant record or measure was supplied. Some fields can be missing, and a displayed summary is not a complete historical reconstruction. A missing row, chart or breakdown is not proof that the underlying account or activity is absent. The authorized team should reconcile the reporting records and definitions before relying on a material discrepancy.
Results may be cached for different lengths of time, and related views can be refreshed separately. A newly recorded event may not immediately appear everywhere. The current response does not provide a universal data-freshness or completeness certificate.
When asking the authorized team to investigate, provide the view, selected dates, relevant currency, retrieval time and the discrepancy you expected them to explain. Use approved support channels and avoid including another organization's details, access tokens or private financial data. The team should reconcile source records and reporting definitions before drawing a conclusion or changing a customer's account.
Preparing a useful business discussion¶
Start with a question, such as whether recorded expansion is concentrated in a few markets. Compare measures that share the same dates, currency and population. Separate observed records, current-state snapshots and projections in the discussion. Follow up material exceptions through billing operations and use service oversight when data collection or availability is in doubt.
Public documentation explains the capability and its limits; it does not publish platform figures or grant access to the staff console. The private staff guide supplies the intended action sequence, and the integration reference records the exact calculation and implementation boundaries.