Know where the money and the empty hours are. Describe your services and capacity and Taskade Genesis builds a reporting app that turns your bookings into weekly revenue, utilization, and no-show numbers by service, by person, and by day, with a short written summary you actually read.
The Time Tracker is a live Taskade Genesis app on this page. Sort a column, see how a real hours-and-totals table behaves, then press "Use this app" to clone it in about ten seconds and build the weekly revenue and utilization report described here on top of it.
Booking businesses usually measure one thing, total bookings, and it is the least useful number available. It hides the service that is busy and unprofitable, the person whose diary is full of short appointments, and the two hours every afternoon that never sell. Splitting the same data by service, person, and time slot is what turns a diary into a management report.
What the build gives you: revenue per service and per person, utilization against the hours you actually offer, average booking value, no-show and late-cancellation rates, lead time from request to appointment, new versus returning customer split, and a weekly written summary naming what changed and what to look at.
The same data renders across the layouts you need:
- Table view for the full breakdown by service, person, and week
- Board view to group services by margin or by demand
- Calendar view to see the empty hours where they actually sit
- Plus List, Mind Map, Gantt, and Org Chart across the rest of the 7 project views
Automations produce the report. A scheduled trigger runs weekly, an AI action writes the summary from the numbers, and the report is sent to your inbox and your team channel. The Stripe integration keeps revenue accurate by pulling actual payments rather than quoted prices. Across 100+ bidirectional integrations, Stripe and forms pull in while email and Slack push the report out. Automations run on paid plans; the Free plan includes 10 flow runs in total.
The AI agents in the app carry 34 built-in tools including persistent memory and file analysis. The Reporting agent compares this week to the last several rather than to the same week, so it flags genuine changes instead of ordinary variation, and it explains what a number moved because of.
Utilization deserves care in how you define it. Hours booked against hours in the day flatters everyone. Hours booked against hours you actually offered for booking is the number that shows the gap, and the gap is where the growth is. Defining it once, honestly, is more valuable than any dashboard.
Lead time is the most underrated column here. A service booked three weeks out is priced too low or under-resourced. A service booked the same day has demand you are not capturing. Neither shows up in revenue until much later, which is why lead time is the earliest useful signal a booking business has.
The other habit worth forming is reading the report against a decision rather than as news. Every week should end with one of three answers: change nothing, change a price, or change the hours you offer. A report that never produces a decision is a report nobody needs, and the written summary exists precisely to make the decision obvious rather than leaving it buried in a table.
Clone the app, invite whoever makes the decisions, and the numbers are yours, computed from your own records rather than a vendor's dashboard.
Learn recurring runs in Learn, AI steps in Learn, and the Stripe connection in Learn. Browse live builds in the Community Gallery. Pair this with the multi-location booking desk to compare sites, and the no-show reminder cadence to fix the number this report will make impossible to ignore.
Frequently Asked Questions
Where do the revenue numbers come from?
From actual payments where Stripe is connected, and from booking values where it is not. Using payments rather than quoted prices is what keeps the report honest about discounts, refunds, and unpaid balances.
How should utilization be defined?
Hours booked against hours you genuinely offered for booking, not against the whole working day. The stricter definition is less comfortable and far more useful, because it shows you the sellable gap.
Does the report explain itself?
Yes. An AI step writes a short summary naming what moved and by how much, compared against several previous weeks rather than a single one, so ordinary variation is not reported as a trend.
Can I see performance per staff member?
Yes, by revenue, utilization, and average booking value. Read all three together, since a full diary of short low-value appointments looks excellent on one measure and poor on another.
What is lead time and why does it matter?
The gap between a request arriving and the appointment happening. Long lead times mean unmet demand and often mean underpricing. Short ones mean spare capacity. It moves before revenue does, which makes it the most useful early signal you have.
Can I compare new and returning customers?
Yes. The split by revenue and by count tells you whether growth is coming from finding new people or keeping existing ones, which are very different problems with very different fixes.
How far back does the comparison go?
As far as your booking records. Because the report is computed from the same records the bookings live in, history accumulates without any separate reporting setup.
Who should receive the weekly report?
Whoever can act on it. Sending it to a team channel as well as an inbox tends to produce better decisions than a private dashboard nobody opens.
