Picture your finance team a quarter from now. The weekly receivables review is prepared before anyone sits down, and ten hours a week have come back to three people. Customers with a late invoice get a call while the problem is still small. The backlog you stopped mentioning is gone. The margin report you have asked for since last year arrives every month. Same team, doing work it never had room for. That is how you 10X what a team can do.
The hours alone will not get you there. Somebody has to decide where they go.
Capacity is a leadership decision.
Freed hours that nobody assigns still get used. They go to the inbox, to the next urgent request and to slightly longer versions of the same tasks. The workflow works, and the business looks the same as before.
The ambition is more capability and more capacity for the people you have. The method is the one that produced the workflow: start from the outcome, then land the work on the roles that do it. So treat gained capacity the way you treat budget: name the amount, choose what it buys and say who is accountable. You know which outcome matters most this quarter. The team knows what the work would take. The worksheet puts both on one page.
It starts from a number you trust. What is an AI workflow worth? Measure it from your own baseline shows how to get one from your own work, with review and correction time counted.
The capacity worksheet.
Copy it, fill in the brackets and complete one for each workflow that goes into daily use.
Capacity worksheet: [workflow name]
- Name the capacity. How many hours a week come back, to which roles, measured over [four] weeks against your own baseline. Count the whole job, review and corrections included.
- Keep the workflow good. Set aside the hours its owner needs to read the exception log, retest and improve it. Assign these first.
- Service quality. What will customers, clients or colleagues get sooner, more often or to a higher standard? [The work] · [hours a week] · [role] · [what you will see by the review date].
- Backlog. Which pile gets cleared, and by when? [The work] · [hours] · [role] · [the count today and the count you want].
- Growth. Which work that brings in or keeps revenue gets more attention? [The work] · [hours] · [role] · [what you will see].
- New work. What will the team do that it has never had room for? [The work] · [hours] · [role] · [the first finished piece and its date].
- Another outcome you choose. Training, cover for absences, a shorter month-end, a calmer week. Write it down as a choice, with hours and a role, so it is a decision.
- Check the sum. The lines add up to the hours in step 1. A line left at zero says “not this quarter” in writing.
One team’s completed worksheet.
An invented finance team put the weekly receivables summary and receivables exception review capabilities into daily use, then filled in the worksheet with the CEO.
Illustrative example with invented data. An invented 70-person managed-services company. The team, the hours and every count are invented.
Capacity worksheet: weekly receivables review
- Capacity gained
- 10 hours a week across the controller and two receivables specialists, measured over four weeks against the four weeks before, with daily review and corrections already counted.
- Keep the workflow good
- 2 hours a week. The controller reads the exception log on Fridays, turns repeated misses into new test cases and approves each change.
- Service quality
- 3 hours a week. The two specialists phone every customer whose invoice passes 15 days overdue, where the team used to wait until day 30. By the review date: every such customer has had a call, and each billing dispute has a named owner.
- Backlog
- 2 hours a week. One specialist works through the 140 unmatched credit notes carried since the spring. By the review date: none left. The hours then move to new work.
- Growth
- None this quarter. The CEO and the controller chose service quality first and will look again at the review.
- New work
- 2 hours a week. The controller builds the monthly margin-by-customer report the CEO has asked for since last year. First report: the end of the quarter’s first month.
- Another outcome
- 1 hour a week. The second specialist learns cash application from the first, so either can cover the other’s holiday.
- Sum
- 2 + 3 + 2 + 0 + 2 + 1 = 10 hours.
Decided by the CEO with the controller. Shared at the finance team’s Monday meeting. Review: the last Friday of the quarter.
Every line is work that people do. The workflow prepares the review and the summary; the specialists make the calls, the controller decides what to do about each exception, and the CEO chooses the priorities. What a fully powered finance team knows before month end shows that review in full.
Decide it with the team, then check it.
Fill the worksheet in with the people whose hours they are. They know which backlog hurts, which customers would notice a call and what they have wanted to build. Build your AI plan with the people who do the work gives you the questions to ask and a way to report back on what they suggest. When people see gained hours go to better work they helped choose, they propose the next workflow themselves.
Two checks keep the worksheet true. First, it is a plan for hours and work this quarter. Decisions about roles and hiring are made separately, by you, with everything else you know. Second, at the review date, compare each line with what happened. Capacity that drifted back into old tasks shows up as a missed line, and you reassign it.
Faster is the floor takes up the question that follows: what the work itself should achieve once it is easy to run.
It all runs on the platform your team already uses: ChatGPT, Claude, Copilot or Gemini. You set the pace, your people do the work that matters most, and your organization keeps control of how the work gets done.
Bring one workflow your team runs every week and the outcome you would fund first if ten hours came back.