A Fractional CFO Customer Profitability Review: Find the Cost to Serve

Two customers can generate the same revenue and consume very different amounts of your team's time. One accepts the standard service, supplies complete information, and renews with few changes. The other needs repeated revisions, exceptional reporting, and senior intervention. A revenue report treats them as equals. A customer profitability review makes those differences visible before the next renewal decision.

A fractional CFO can lead this review by connecting account revenue, delivery costs, and the work required to maintain the relationship. The useful output is a small set of commercial decisions with named owners. It should explain which accounts need a different service model, better operating processes, or a revised scope, and how confidently the available data supports each action.

Define the decision before building the model

Choose a specific question and a consistent period. For example: which service contracts renewing next quarter need a scope discussion? That is more manageable than trying to calculate the lifetime value of every customer while rebuilding your accounting system.

For a first review, select accounts that represent different service patterns: a large standard account, a complex account, a recent customer, and a mature customer. Include more than the accounts that managers already describe as difficult. Otherwise the model can become a numerical justification for existing opinions.

Write down what management may change. Options might include the package offered at renewal, the route for support requests, a reporting requirement, or the frequency of account meetings. The CFO should also identify decisions outside the review's authority, such as changing contractual commitments without the account owner's approval.

Separate delivery margin from the cost of maintaining an account

Start with recognized revenue for the selected period, then subtract directly attributable delivery costs. Review credits and refunds consistently with finance's reporting policy. Do not mix annual contract value with one month's delivery costs or cash collections with revenue earned.

Next, consider customer-specific support and administration. ACCA's explanation of activity-based management describes using activities and their cost drivers to understand customer profitability. It also warns that reducing activity does not necessarily eliminate the associated fixed cost. Those distinctions matter when management converts a report into a proposed action.

For this review, use a clearly labeled contribution measure: revenue less direct delivery and the selected account service costs. Keep unallocated company overhead visible below that measure. Avoid calling it final net profit if rent, leadership, product investment, or other costs remain outside the calculation.

The method and examples below are an illustrative management workflow, not a prescribed accounting standard or a claim about any company's results.

Build a small activity map with the operating team

Ask service leaders where work accumulates, then inspect the systems that could substantiate it. Support tickets may show request volumes but miss the hours spent on escalations. Calendar entries may reveal account meetings but include time already charged to delivery. A model needs definitions before it needs automation.

Choose a few activities that could change the decision. Customer support, account administration, and special reporting are often sensible candidates for a service business. For each, document the source, the measurement unit, the cost rate, and the boundary with other activities.

If support time is already included in direct delivery labor, do not charge it again as a separate activity. If an employee divides a day between customers and internal training, do not allocate the entire day to whichever customer had a ticket open. Reconcile the total assigned time to available records and leave unexplained time visible.

Use an explicit confidence label for estimates. Recorded project hours, a manager's retrospective estimate, and an unsupported assumption are different evidence. A first version can contain estimates, provided readers can identify them and see whether plausible changes would reverse the decision.

Work through an illustrative two-customer example

Assume two accounts each generate $20,000 of revenue in one month and each incurs $10,000 of direct delivery cost. Support and account administration are separate activities outside that delivery figure. The internal planning rates are $100 per support hour and $80 per administration hour. All numbers are invented for illustration.

The selected contribution is 43% of revenue for A and 24% for B. That difference identifies an investigation, not an instruction to end B's contract. The service team might discover that B is still onboarding, that your own reporting errors generate the extra work, or that sales promised a service the standard package does not cover.

The hourly planning rates also need interpretation. A fully loaded internal rate can describe the capacity consumed without representing a cash payment that disappears when a task stops. If B needs fewer support hours next month, the immediate benefit may be time available for other customers. Finance should not automatically record that capacity as a cash saving.

Test the explanation before proposing a price change

Meet with the account and delivery owners. Ask them to explain the largest differences using actual events from the review period. Separate recurring requirements from unusual incidents, then examine a longer period where the account history permits it.

For an onboarding customer, show setup effort separately from steady service. For a customer affected by your own quality problem, show the cost of fixing the problem separately from optional requests. This prevents a blanket price increase from concealing an operating issue that will also affect other accounts.

Run a simple sensitivity check on uncertain inputs. In the illustration, reducing B's estimated support time from 40 to 30 hours raises contribution by $1,000 to $5,800. B would still consume more of the selected service costs than A. If a smaller change reverses your conclusion, improve the evidence before negotiating from the model.

Choose an action with an owner and a review date

A useful review can produce several different actions. Standardize a custom report that repeatedly consumes analyst time. Bundle small requests into a scheduled session. Clarify what the current package includes. Offer an appropriately scoped service at renewal. Assign process changes to operations and commercial conversations to the account owner.

Describe the expected mechanism rather than promising a percentage improvement. For example, replacing three manually assembled reports with one agreed template should reduce preparation work. The next review should check whether the template was adopted, whether preparation time changed, and whether the customer still receives what was agreed.

For each action, record the current measure, the proposed change, the accountable person, the customer impact, and the next decision date. Include implementation effort. A reporting automation project that consumes substantial engineering time should not be approved solely because the spreadsheet shows an attractive gross saving.

Keep customer strategy and cash timing visible

A low current contribution can be acceptable for a deliberate reason, such as a bounded introduction period or a specific learning objective. Record who approved the exception, what evidence would justify continuing it, and when it expires. Avoid using vague future potential to make every difficult account exempt from review.

Payment behavior belongs in the discussion, but it is a separate question from the cost of serving an account. A profitable contract can still create a collection problem. Connect material timing concerns to your 13-week cash forecast review without relabeling unpaid invoices as service activity costs.

Review the model when service terms, staffing, or delivery methods change. Keep historical versions so that managers can distinguish a real operating improvement from a change in allocation rules. The goal is consistent decision support, with enough detail to challenge the conclusion and little enough complexity to maintain it.

Scope the fractional CFO engagement around decisions

Ask a prospective fractional CFO to explain how they would reconcile the inputs, work with account leaders, and distinguish available capacity from avoidable cost. Request an anonymized example of the decision record they would deliver, rather than a promise that every customer will become profitable.

A practical initial scope includes a sample of accounts, an agreed contribution definition, documented assumptions, a management review, and responsibility for updating the model. Our guide to choosing a fractional CFO can help you evaluate the broader engagement. Bring your account types, renewal calendar, and current reporting limitations to find an executive so the search starts with the problem you need to solve.