# How to Measure Profitability Across Different Service Lines

Measure service-line profitability by matching recognised revenue with the labour, subcontracting, travel and other resources used to deliver it. Show contribution before shared overhead and a reconciled result after relevant allocation. A high hourly billing rate can still produce weak profit if work takes longer than planned, staff time is underused or repeat visits are frequent.

Define service lines around how the business sells and delivers work, such as implementation, maintenance and training. Keep projects and customer groups available as additional dimensions so that a good average does not conceal a few costly engagements.

## Separate revenue, billing and collections

A service can be performed, invoiced and collected in different periods. Use recognised revenue appropriate to the applicable accounting policy, and show invoices, unbilled amounts, advances and collections separately where relevant.

Under the AS framework, AS 9 includes service-revenue principles; other frameworks can have different requirements. Review contract milestones, completion evidence, acceptance terms and uncertainty before assuming that every invoice represents earned revenue.

For a management profitability report, identify work still in progress and avoid comparing completed-project revenue with only part of its cost. Equally, do not bring future revenue into the result merely because staff have started work or a proposal has been accepted.

## Capture delivery resources reliably

Use staff time records with practical activity codes. Distinguish customer delivery, rework, travel, training, sales support and general administration. Keep the process simple enough that employees can record time accurately without excessive administration.

Labour cost should include relevant employment costs under the stated method, not merely take-home pay. Decide how leave, non-billable time and shared technical supervision are handled. A standard hourly cost can help, provided it is periodically reconciled to actual payroll and capacity.

Add subcontractors, customer-specific software, travel and other directly attributable costs. Do not allocate a supplier invoice equally across service lines if project records show where the work was performed.

## Compare two service lines

An illustrative Pune IT-support firm earns ₹12 lakh implementation revenue and ₹8 lakh maintenance revenue in a quarter. It records the following delivery costs:

| Quarterly result | Implementation | Maintenance |
|---|---:|---:|
| Recognised revenue | ₹12 lakh | ₹8 lakh |
| Delivery labour | ₹5 lakh | ₹3 lakh |
| Subcontractors | ₹2 lakh | ₹0.5 lakh |
| Travel and direct tools | ₹1 lakh | ₹0.5 lakh |
| Contribution before shared costs | ₹4 lakh | ₹4 lakh |
| Contribution margin | 33.3% | 50% |

Both lines contribute ₹4 lakh, but maintenance does so on lower revenue. This suggests different economics, not an automatic decision to abandon implementation. Implementation may create future maintenance customers or require different capacity and selling effort.

If shared operating costs are ₹3 lakh and reliable resource records allocate ₹1.8 lakh to implementation and ₹1.2 lakh to maintenance, results after allocation are ₹2.2 lakh and ₹2.8 lakh. Show the allocation basis beside these figures.

## Examine hours and realised rates

Suppose implementation uses 2,000 delivery hours. Revenue per delivery hour is ₹12 lakh ÷ 2,000 = ₹600. If maintenance uses 1,000 hours, its revenue per delivery hour is ₹800. These realised rates can differ greatly from quoted hourly prices because of fixed-fee projects, discounts and overruns.

Compare estimated with actual hours by completed project. A fixed-fee job budgeted for 100 hours but requiring 160 loses margin even when its invoice value is unchanged. Identify scope changes, training needs and repeated customer revisions.

For retained support contracts, inspect tickets, response commitments and peak demand. A contract can look profitable in a quiet month but require standby capacity throughout the year. Measure the resource commitment as well as recorded activity.

## Understand utilisation without rewarding overwork

Utilisation commonly compares billable or delivery hours with a defined available-hours base. State which hours are included and how leave, holidays and training are treated. Different definitions can create misleading comparisons.

Low utilisation can reflect weak demand, excessive capacity or valuable non-billable work such as product development and training. High utilisation can coexist with burnout, late invoicing and deteriorating quality. Pair the ratio with delivery performance and staff sustainability.

If payroll remains fixed while billable hours fall, cost per productive hour rises. A standard rate based on unrealistic full utilisation can understate service costs and make every quoted job appear more profitable than the business actually is.

## Keep shared costs and cross-selling visible

Allocate shared scheduling, management, premises and systems using a reasonable driver. Record costs that remain unallocated for a particular decision rather than forcing an arbitrary assignment. Reconcile the service-line total to company operating profit.

Where implementation supports maintenance sales, show conversion and retention evidence. Do not assume every loss-making project creates future value. Track the subsequent contracts and contribution needed to support that claim.

ICAI AS 17 provides segment-reporting principles where applicable, while an internal service-line report can use more detailed management categories. Keep formal reporting requirements distinct from the internal operational view.

Separate contractual scope changes from avoidable rework. Extra hours requested and accepted by the customer may justify an additional fee, while correcting an internal mistake may not. The profitability report should identify the difference before recommending a uniform price increase.

## Turn the comparison into action

Choose actions from the driver: revise scope control, improve estimates, adjust fixed fees, reduce repeat visits or change staffing capacity. Quantify the expected effect and check whether quality or customer retention could suffer.

For the IT-support firm, review implementation overruns and maintenance capacity before shifting sales effort. A useful report shows revenue earned, delivery resources consumed, cash still outstanding and the operational change most likely to improve the next period’s result.

## Sources and references

- [ICAI AS 9: Revenue Recognition](https://indasaccess.icai.org/Volume-III/AS/asb.html?a=110)
- [ICAI AS 17: Segment Reporting](https://indasaccess.icai.org/Volume-III/AS/asb.html?a=118)
- [ICAI AS 1: Disclosure of Accounting Policies](https://indasaccess.icai.org/Volume-III/AS/asb.html?a=104)