Time and materials vs managed services: how IT services buyers value each revenue type

IT services buyers usually value contracted managed services revenue above time-and-materials project revenue, because it renews under term agreements, is easier to forecast and shows its margins more clearly. T&M revenue is judged on repeat clients, backlog and utilization. A one-time data license fits neither bucket and should be reported separately as non-recurring.

The verdict: contracted recurring revenue earns the premium

Buyers of IT services firms generally pay more for revenue that renews under a signed agreement than for revenue that has to be resold project by project. Managed services revenue, billed monthly under a master services agreement with a defined service catalog, service levels and a term, gives a buyer cash flow it can forecast. Time-and-materials (T&M) revenue depends on winning the next statement of work and keeping consultants billable.

That does not make T&M revenue low quality. A firm with long-standing enterprise clients, scarce skills and steady repeat work can still earn a strong valuation; it simply has to prove repeatability with evidence that a managed services contract provides automatically. For current multiples by segment and size, use your banker's latest sector update rather than a rule of thumb, because the spread moves with the market.

A one-time data license, if the company signs one, is a third kind of revenue entirely. It belongs in neither bucket and should be shown as non-recurring.

Side-by-side: T&M, managed services and a one-time license

FactorTime and materials (project)Managed services (contracted)One-time data license
Contract formStatement of work and rate card, plus change ordersMaster services agreement with a service schedule, term and renewal termsLicense agreement for an agreed set of the company's records, signed once
Revenue patternLumpy, tied to project starts and finishesMonthly or quarterly, predictable within the termA single payment, usually received about 60 days after invoicing, once data has been selected
What diligence testsUtilization, realized bill rates, backlog, repeat-client rate, client concentrationRemaining contract term, renewal history, churn, revenue per user or device, SLA performanceRights to the records, exclusivity terms, what was licensed, and confirmation that it does not recur
Margin driversBench time, rate pressure, subcontractor mixTooling and automation, technician productivity, scope creepInternal time spent on inventory and review
Main risksGaps between projects, key-person dependence, write-offsSLA penalties, underpriced contracts, churn at renewalClient-owned content mixed into the firm's own records
Typical valuation logicLower multiple unless repeatability is provenHigher multiple when terms are long and churn is lowExcluded from run-rate earnings and valued as cash
Treatment in quality of earningsAdjusted EBITDA, supported by pipeline and backlogRun-rate revenue, often with contracted backlogNormalized out as a non-recurring item
Records it leaves behindSOWs, project plans, estimates versus actuals, status reportsTickets, runbooks, change records, monitoring alertsNot applicable

When managed services revenue wins

Managed services revenue earns its premium when the contract terms do the proving for you:

  • Contracts run for a defined term with auto-renewal, and the renewal history is documented.
  • Pricing is per user, device or service tier, so revenue grows with the client without a new sale.
  • Service levels are written down and met, with ticket data that shows it.
  • No single client dominates revenue.
  • Gross margin has held or improved as tooling and automation scaled.

Converting project clients to defined managed services is a multi-year program, not a pre-sale tactic. A value creation office is the natural place to track it, with conversions, renewals and margin by cohort.

When T&M revenue holds its value

T&M revenue holds up when you can show the behavior a contract would otherwise guarantee:

  • The same enterprise clients buy new projects year after year, and the repeat rate is measured.
  • The firm owns a specialty that is hard to hire for, so realized rates hold.
  • Long programs, such as multi-phase implementations or application support, behave like recurring revenue in practice even though they are billed hourly.
  • Utilization and realized rates are tracked consistently and reconcile to the financial statements.

Revenue that looks recurring but buyers reclassify

Buyers test the substance of the contract, not how often the invoice goes out. These lines are often moved from managed to project revenue in diligence.

Revenue lineWhy it gets reclassifiedWhat strengthens the claim
Prepaid blocks of hoursThe client buys time, not a defined serviceConvert to a service catalog with a monthly fee
Staff augmentation on rolling purchase ordersNo term, no SLA, cancellable at willFixed-term agreements with notice periods
Retainers without a defined scopeBehave like deferred T&MWritten scope, deliverables and service levels
Projects billed in monthly installmentsMonthly billing of a project is still a projectSeparate the build phase from an ongoing run contract

Where a one-time data license fits

A data license is neither project nor managed services revenue. It is a single payment for licensing an agreed set of the company's own records, typically exclusive for AI training for an agreed term, while the company keeps ownership. Report it as a non-recurring line, outside monthly recurring revenue, run-rate EBITDA and backlog.

Software companies face the same question in their headline metrics; see how to show one-time revenue in the Rule of 40. And before anyone links a license to bonuses or vesting, read how incentive plans treat one-time revenue.

IT services firms come up in this context because of the records each revenue model produces. Managed services leaves years of tickets, resolutions, change records and runbooks; project work leaves estimates, plans, status reports and post-project reviews. AI developers building agents that carry out real work need records of multi-step tasks with outcomes, and that material rarely exists on the public web. Many tech-enabled services companies hold the same kind of history.

The client-rights screen for IT services firms

The obstacle is usually ownership, not volume, because much of what an IT services firm touches belongs to its clients. Five checks decide whether an introduction is worth making.

  • Own versus client content: are tickets, runbooks and project documents held in the firm's own systems, or inside client tenants?
  • Contract terms: do the standard MSA and SOWs leave the firm owning its internal methods, templates and service records, and what do the confidentiality clauses say about client information?
  • Headcount: does the firm have 50+ full-time employees at peak (contractors excluded)? Firms that deliver through subcontractors or offshore partners should count carefully.
  • History: are several years of PSA, ticketing and project records still exportable, including from systems retired after acquisitions?
  • Sponsor: is there an owner, CEO, CFO or authorized representative who would consider a license?

Anything that identifies a client is removed or masked under rules the firm settles with SourceX before work starts. The complete baseline is on who qualifies.

How an introduction works for an IT services owner or adviser

  1. A sponsor, banker, fractional CFO or other adviser registers as a partner and introduces the owner, or shares a referral link so the owner can apply directly with the adviser's credit preserved.
  2. SourceX reviews the firm's size, years of operation, breadth of records and rights position.
  3. The firm lists its systems and years of history in a data inventory; the adviser never touches any records.
  4. Price and terms are agreed with the firm before buyers review anything, and the firm signs only if the terms work.
  5. After signing, the firm prepares and hands over the records under the redaction rules it agreed, and receives its payment.

Partners earn 25% of the eligible platform fees SourceX collects from the referred company's licensing deals, up to $100,000 per referred company, payable only after the buyer pays and SourceX receives its fee. The reward comes out of SourceX's fee, not the company's proceeds, and rewards are not guaranteed.

Next step

If you advise or own IT services firms, list the candidates with the network opportunity finder, run the client-rights screen on each, and register as a partner before making the first introduction. Owners of IT services firms with 50+ full-time employees at peak can also apply directly at sourcex.si/apply.

Common questions

How do buyers value a firm with both T&M and managed services revenue?

Buyers usually look at the revenue mix and judge each stream on its own logic, then reconcile to a view of the whole business. Expect requests for revenue split by type, by client and by year, with contracts behind anything labeled managed. A rising managed share with stable margins tends to support the valuation more than a single blended growth figure.

Is it worth converting T&M clients to managed services before a sale?

It can be, if the conversion is real: a defined service catalog, a term, service levels and a monthly fee the client has actually signed. Buyers look for a track record, so conversions completed shortly before a sale process carry less weight than ones with a renewal behind them. Start early in the hold and track the program as its own initiative.

Would a second data license make that income recurring?

No. Each license is a separate agreement for a defined set of records, and there is no assumption that another will follow. Even if a company later licenses newer records, each payment should be reported as non-recurring in the period it occurs. Treating licenses as a recurring stream would invite the same reclassification that weak managed services claims face in diligence.

Can an IT services firm license tickets that mention its clients?

Only within limits agreed before any work begins. Client names, credentials, configurations and other client-identifiable content are excluded or redacted, and anything the client owns under the contract stays out unless the client consents. What remains, such as how issues were triaged, escalated and resolved, can still be useful once it has been properly de-identified.

Do subcontractors count toward the headcount baseline?

No. The baseline is 50+ full-time employees at peak, with contractors excluded. IT services firms that deliver through subcontractors, offshore partners or staff augmentation vendors should count only their own full-time employees at the firm's peak. Content produced by subcontractors can also raise ownership questions that need checking against their agreements before it goes into any inventory.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment