Fractional CFO for Technology Services and SaaS

You have both services revenue and recurring revenue. Your investors want ARR metrics. Your services engagements need project costing. Your enterprise customers have procurement cycles from the 1990s. This is a different kind of finance.

The Hybrid Revenue Model Problem

Pure product SaaS companies have one revenue model: subscription. Pure services companies have one revenue model: time and materials or fixed fee. Most technology services companies have some combination — a managed services contract that's recurring, a professional services engagement that builds or implements something, and possibly a software license or SaaS subscription layered in.

This hybrid creates a reporting problem that both types of CFOs struggle with.

The product SaaS CFO looks at the services part and says: 'Why is services margin so low? This looks like a cost center.' They try to optimize services like they're improving SaaS gross margin — and they break the services business in the process.

The traditional services CFO looks at the recurring revenue and says: 'This is great, but why is the revenue recognition so complicated?' They treat it like regular consulting revenue — and they understate the value of the recurring base and misforecast the revenue recognition timing.

The fractional CFO for a tech services company needs to speak both languages — understanding the SaaS metrics that drive valuation (ARR, NRR, logo retention) while also running the project costing and utilization analytics that drive services profitability.

The result is a financial model that shows both: the health of the recurring revenue base (customer count, ARR, retention, expansion) and the profitability of the services delivery engine (project margin, utilization, realized rates).

Revenue Recognition Under ASC 606 — Where Services Gets Complicated

ASC 606, the revenue recognition standard, is well-understood in the product SaaS world — you recognize SaaS revenue ratably over the subscription period, which is intuitive. For services revenue, ASC 606 is more complicated — and most technology services companies don't have a clean implementation.

For time-and-materials contracts: Revenue is recognized as the work is performed. This is straightforward — if you bill monthly in arrears, you're recognizing revenue as you go.

For fixed-fee services contracts: Revenue is recognized based on the pattern of performance. If a contract is for a 12-month implementation, you're supposed to recognize revenue proportionally to the completion of the deliverables — not all at the end when the project is done. This means if you're billing annually upfront for a 12-month project, you have deferred revenue on your balance sheet that you should be recognizing ratably.

The practical problem: most professional services billing systems don't produce the output needed for ASC 606 compliance automatically. The fractional CFO builds the process that calculates percentage of completion by engagement and produces the journal entries for revenue recognition — so the financial statements are accurate, not just the invoices.

This is one of the areas where due diligence on a tech services company most consistently surfaces issues. A buyer doing a QoE on a tech services company will find revenue recognition timing problems — and the correction will often require restating prior periods.

The Enterprise Deal Cash Flow Problem

Enterprise technology services deals — the ones with a Fortune 500 or large mid-market company as the customer — have procurement and payment cycles that are essentially unchanged since the 1990s. The typical enterprise contract process: RFP, vendor selection, legal review, procurement negotiation, contract execution, implementation, and then... payment. Net 30 from invoice, but only after the implementation milestone is signed off. And procurement often sits on invoices for 45-60 days before processing. For a tech services company with a large enterprise engagement, this means: You perform 6 months of implementation work. The customer signs a statement of work, you invoice. The customer doesn't pay for 60-90 days after the invoice. That's a 6-9 month cash conversion cycle on the largest engagement in your pipeline. A fractional CFO models this cycle per enterprise contract and builds the cash flow forecast that shows when cash is expected to arrive — so the firm isn't caught by a large engagement that consumed cash for nine months before paying out. This analysis also informs pricing: the working capital cost of an enterprise engagement needs to be factored into the pricing model, or the engagement looks more profitable than it actually is.

What Growth Equity Investors Actually Want from Tech Services

If you're raising growth equity (Series B or later) as a tech services company, you'll be talking to investors who typically prefer SaaS metrics — but you'll also be trying to explain why your business is different. The investors will want to see:

ARR (Annual Recurring Revenue) from your managed services or SaaS layer — and they'll want to see the net revenue retention rate on that ARR. NRR above 100% means your existing customers are expanding faster than they're churning, which is the most powerful SaaS metric.

Gross margin by revenue stream — the services margin will be lower than SaaS margin, and that's fine. But the blended gross margin needs to be high enough to support your operating expenses.

Customer concentration — if your top 5 customers represent more than 40% of revenue, investors will flag it as risk. Tech services companies often have this issue because enterprise deals are large.

Revenue predictability — SaaS investors want ARR. But if your ARR is 60% of revenue and the other 40% is project-based, your revenue is less predictable than a pure SaaS company, and the valuation multiple will reflect that.

The CFO's job is to produce a model that shows all of this clearly — and to be honest in that model about the quality of the revenue. A tech services CFO who can show an investor: 'Here is our ARR, here is our NRR, here is our blended gross margin, and here is our customer concentration analysis' — and walk the investor through the assumptions — has credibility that the founder who hands over a generic pitch deck doesn't.

The Capital Efficiency Question for Tech Services

Tech services businesses are capital efficient in one sense — they don't need large factories or heavy inventory — but capital intensive in another: working capital tied up in enterprise contracts, talent acquisition costs, and the gap between the cost of delivering the service and collecting the cash.

The key metric for tech services capital efficiency is revenue per employee. A benchmark for a healthy tech services business is $150K-$200K in revenue per employee. Below that, the business is likely over-staffed with non-billable people, or billing rates are too low. Above that, the business may be understaffed in ways that create service quality risk.

The CFO model that ties this together:
Revenue per employee by quarter, tracked over time
Gross margin per employee — because revenue per employee can be misleading if the margin is thin
Days in accounts receivable — enterprise contracts with Net 60 terms will show high AR days even if the business is healthy
Backlog conversion rate — how much of the pipeline converts to revenue, on what timeline
A CFO who can show you this model, quarter by quarter, and explain the inflection points, is giving you the analytical foundation for every staffing and investment decision.

Key Takeaways

•Tech services is a hybrid revenue model — the CFO needs to speak both SaaS (ARR, NRR) and services (project margin, utilization) languages fluently
•ASC 606 revenue recognition for fixed-fee services engagements requires percentage-of-completion accounting, not just invoicing
•Enterprise contract cash conversion cycles (6-9 months from work to cash) must be modeled per contract to avoid cash surprises
•Growth equity investors will benchmark tech services businesses against SaaS metrics — the CFO should present the model showing where the business deviates and why
•Revenue per employee is the single most diagnostic metric for tech services capital efficiency — benchmark against $150K-$200K

Frequently Asked Questions

We have both SaaS subscription revenue and services revenue. How should we think about them together?

Keep them in separate models but present them together as a blended view. SaaS subscriptions have high gross margins (75-85%) but require ongoing investment in retention and customer success. Services have lower gross margins (30-45%) but drive customer adoption and expansion. The blended business has a weighted average gross margin that reflects the mix — and that mix changes as you grow the SaaS base relative to services.

How do we handle revenue recognition for our fixed-fee implementation contracts?

Fixed-fee services contracts require percentage-of-completion recognition under ASC 606. The practical implementation: define deliverables and their relative standalone selling prices, estimate total project cost at completion, recognize revenue based on the proportion of cost incurred to total expected cost. This requires: a project costing system that captures actual hours and costs, a mechanism for updating the completion estimate quarterly, and a review process for all open fixed-fee contracts. Most billing systems don't do this — it usually requires a spreadsheet or a专业的 project accounting system.

We're about to raise a Series B. What do we need to have ready?

Three years of financial statements with ARR broken out by cohort (so investors can see net revenue retention), a model showing gross margin by revenue stream, the customer concentration table, a 13-week cash flow, and a use-of-funds model. For a tech services company, investors will also want the backlog schedule — how much contracted revenue is in the pipeline, when it converts to recognized revenue.

Our enterprise customers take 60-90 days to pay. Is this a problem?

It's a working capital problem, not a profitability problem — if the engagements are profitable at the margin level. The issue is that your cash conversion cycle is 60-90 days while your costs (people, infrastructure) are due on a normal payroll cycle. The CFO builds the cash flow model that shows exactly when cash comes in per enterprise customer, and models whether the gap is being financed by debt, equity, or working capital that should be deployed elsewhere.

What's a reasonable blended gross margin for a tech services company?

It depends on the mix. If you're 60% SaaS and 40% services, blended gross margin should be 55-65%. If you're 30% SaaS and 70% services, expect 40-50%. The key is tracking them separately so you can see whether the SaaS margin is holding and whether the services margin is being optimized — or eroded by scope creep and underpricing.

This article is part of our The Complete Guide to Fractional CFO Services guide.