Identify what the customer is actually buying
Technology services can mean subscription software, outsourced operations, cloud infrastructure, implementation projects or a combination of these. Their economics differ. A software business may invest heavily before selling to many customers; a professional services business often needs additional delivery capacity as work grows.
Quick Prep’s technology services primer helps you separate those models and connect technical choices with commercial outcomes. It is useful for growth, pricing, profitability, acquisition and technology-investment cases.
Salesforce’s annual filing distinguishes subscription and support revenue from professional services and other revenue. That is a practical example of why a technology company’s revenue mix matters: different activities can have different delivery costs, timing and scalability. Salesforce: Fiscal 2026 Form 10-K
Model subscriptions, usage and people separately
Subscription software may charge by user, account, tier or another contractual unit. Revenue depends on customer acquisition, retention, expansion and realised pricing. An annual contract does not mean all revenue is recognised on the day cash is collected.
Usage-based services charge for activity such as transactions, storage or compute. Customer growth and consumption growth are distinct drivers. Higher usage can raise revenue while also increasing infrastructure costs.
Professional services sell implementation, integration, advisory or delivery work. Revenue can be estimated from billable staff, available hours, utilisation and realised rates, with adjustments for the contract model.
Managed services combine recurring contracts with continuing delivery obligations. Service reliability, support effort, automation and contract scope affect profitability.
Build separate revenue and cost lines when a company combines these models. A high overall growth rate can conceal an increasing share of lower-margin implementation work.
Metrics to use carefully
| Metric | Case use | Definition to check |
|---|---|---|
| Annual recurring revenue | Describes a recurring revenue run rate | Which recurring contracts are included |
| Gross revenue retention | Retention before expansion revenue | Starting cohort and period |
| Net revenue retention | Retention including expansion and contraction | Excludes new customers outside the cohort |
| Acquisition cost | Spend to win a customer | Included sales and marketing costs |
| Gross-margin payback | Time to recover acquisition cost from gross profit | Stable margin and revenue assumptions |
| Billable utilisation | Share of available delivery time billed | Available-hour denominator |
| Revenue per employee | Broad productivity indicator | Outsourcing and business mix |
Contracted value, bookings, billings, recurring run rates and recognised revenue answer different questions. State the measure you are using instead of treating them as synonyms.
Worked exercise: acquisition versus retention
Illustrative interview exercise with fictional values.
A software company begins the year with 100 customers, each generating 12,000 of annual recurring revenue. Starting ARR is 1.2 million. During the year, 10 customers leave. The remaining customers expand their combined annual recurring revenue by 180,000; assume there is no other contraction.
Ending ARR from the starting cohort is 1.2 million − 120,000 + 180,000 = 1.26 million. Net revenue retention is 105%. Gross revenue retention is 90%, because expansion is excluded from that measure.
If the company adds 20 new customers at 12,000 ARR each, total ending ARR reaches 1.5 million. That is a run rate, not automatically 1.5 million of revenue recognised during the year: acquisition and cancellation dates matter.
Suppose acquiring each new customer costs 9,000 and the gross margin on its 12,000 annual revenue is 75%. Annual gross profit is 9,000, giving a simplified acquisition payback of 12 months. This ignores ramp-up, churn, collection timing and additional implementation costs.
A recommendation should therefore ask which customers retain and expand, what onboarding requires, and whether acquisition spending is reaching similar customers. Averages across dissimilar customer groups can be misleading.
Evaluate growth without assuming effortless scale
For a pricing case, identify what customers value and how the charging unit aligns with that value. Per-user pricing can discourage broad adoption; usage pricing can introduce budget uncertainty. Compare willingness to pay, predictability and delivery cost.
For a services profitability case, examine staffing mix, utilisation, project overruns, rework and realised rates. Raising utilisation indefinitely is not a complete strategy: training, quality assurance and business development also require time.
For a cloud or AI business case, estimate cost per completed customer task. Include infrastructure, third-party services, monitoring and human review where required. A cheaper technical component may not reduce the total cost if it increases errors or support work.
For enterprise adoption, examine procurement, integration, data access, change management and time to value. A useful product can still struggle if deployment is difficult or the business owner cannot show measurable benefit.
Practise translating technical choices into business language
Choose one software product and map acquisition, activation, continued use, renewal and expansion. Then create a services model using headcount, available hours, utilisation and billing rates. Explain how the same customer-growth target affects each business’s costs.
Finish recommendations with a commercial metric and an operational condition. For example, a segment expansion may depend on acceptable onboarding effort and retention, not just contract wins. Continue with Technical Skills Enhancement and Finance Modeling to practise the calculations and evidence behind those decisions.
