Put revenue beside the hours used to deliver the work. Compare services and reporting periods, then check costs and margin before changing the timetable.
Revenue with its month-on-month change, bookings, customers and revenue per delivery hour. The booked-work snapshot is dated Jul 31, 2026, with scheduled revenue kept separate from cash received.
Compare bookings, revenue, delivery hours and revenue per hour for each service. Revenue per hour measures income before costs; it does not show profit.
See revenue, sessions and hours for each person in the same period. The percentages are illustrative here; total available hours are not shown, so check the underlying availability before comparing utilisation.
Mako uses observed attendance, visit frequency, unused credits, and time since the last visit to organize descriptive attention levels. Historical membership value is shown as context, not as predicted loss.
See scheduled work for the dated August windows alongside recurring revenue. The windows overlap; they show booked work rather than payments collected or predicted bookings.
See revenue, service performance and team utilisation together.
The example groups key metrics, service efficiency, team performance and retention signals. Check the reporting period and included source records before comparing the figures.
Confirm the export fields and supported views for the report you need. Keep its reporting period and metric definitions with the file when reviewing it in a spreadsheet.
Revenue per hour is revenue divided by the hours used to deliver a service. It helps compare income per delivery hour; compare costs and margin separately when assessing profit.
Mako uses observed attendance, visit frequency, unused credits, and time since the last visit to create descriptive, rules-based attention levels. These signals do not predict cancellation.
Compare utilisation against each person's configured availability for the same period, including part-time hours and time off. Total available hours are not shown in this example.
The main metrics cover July 2026. Booked work uses a Jul 31 snapshot and the dated August windows shown in the example.
Yes. The guided product demo requires a valid work email. No credit card or sales call is required.
Yes. Both weekly windows sit inside the 30-day window. Compare them separately rather than adding their totals.
The example attributes revenue to named instructors. Studio-level membership revenue is separate; this is not a full allocation of the monthly total.
It gives context for the customers needing review. It is kept separate from a prediction of cancellation or future lost revenue.
Compare the work recorded across services and periods, then check the costs before changing the timetable.