Track Product and Service Money Separately

Part III · Build a Product Customers Will Buy S3-14 · Planned

Task

Separate product revenue and pipeline reporting from services reporting.

Summary

Show product revenue, sales opportunities, costs, and results separately from custom services.

Blended numbers hide the business

A company can report growing revenue while learning almost nothing about whether its product works as a standalone business. A contract may combine software, implementation, consulting, training, support, and pass-through costs. If the full amount is reported as product revenue, the product appears stronger than it is. If the full amount is reported as services revenue, genuine product progress disappears.

The separation must begin where the commercial promise is recorded. Dashboards cannot repair a quote, contract, invoice, or opportunity that never distinguished product from service work.

Classify each commercial line

Use a controlled catalogue for every item the company sells. Each quote, order, opportunity, invoice, and revenue entry should carry the same product or service code. A practical classification is:

  • Product: software, licence, subscription, usage, or another standard product charge.
  • Service: customer-specific implementation, consulting, training, managed work, or custom development.
  • Mixed: a temporary exception that must be split before reporting.
  • Pass-through: third-party costs billed without becoming product revenue.
  • Unclassified: an explicit error state, not a convenient default.

Do not let teams invent new labels in free text. Assign ownership of the catalogue, document when a code may be used, and retain the original classification when corrections are made.

Carry the distinction through every system

The same classification should survive the complete path from pipeline to accounting:

  1. The opportunity identifies product and service value separately.
  2. The proposal and order form preserve those lines.
  3. The contract states what each line promises.
  4. Billing produces matching invoice lines.
  5. Accounting maps those lines to controlled revenue and cost categories.
  6. Product, support, and delivery systems connect effort and outcomes to the same customer and offer.
  7. Management reporting reconciles to the source systems.

If finance, sales, and delivery use different definitions, publish a mapping and reconcile it every reporting period. Never hide unexplained differences in a balancing category.

Report the product and services separately

At minimum, separate these measures:

AreaProduct viewService view
PipelineProduct opportunities and product valueService opportunities and service value
RevenueSubscription, licence, or usage revenueImplementation and custom-service revenue
Direct costHosting, product support, transaction costsDelivery labour, contractors, travel, and rework
Customer effortProduct onboarding and supportProject management and custom delivery
ResultActivation, use, retention, and expansionMilestones, acceptance, utilization, and project margin

Two completeness measures expose whether the reporting can be trusted:

Amount classification completeness=in-scope amount with a valid classificationtotal in-scope amount×100 \text{Amount classification completeness} = \frac{\text{in-scope amount with a valid classification}}{\text{total in-scope amount}} \times 100
Record classification completeness=in-scope records with a valid classificationtotal in-scope records×100 \text{Record classification completeness} = \frac{\text{in-scope records with a valid classification}}{\text{total in-scope records}} \times 100

Completeness is not accuracy. Sample contracts, invoices, and opportunities and compare their classification with the actual promise and work performed. Also test consistency across systems, timeliness of updates, duplicate records, and reconciliation to financial totals.

Treat mixed deals as evidence

Mixed deals are not automatically bad. Early customers may need implementation, migration, or training. The important question is whether the service work is bounded, priced, measured, and becoming more consistent.

Review every mixed deal for:

  • newly scoped work that did not exist in the standard offer;
  • discounts that shift product value into service lines or the reverse;
  • senior or founder effort hidden outside delivery records;
  • custom features required for acceptance;
  • service costs that make the product margin look better than the customer economics;
  • commitments that will recur at renewal.

Repeated exceptions reveal work that must be standardized, automated, priced separately, or removed from the offer.

What must be true before relying on the numbers

The company can rely on the product view when all in-scope commercial lines use controlled classifications, product and service totals reconcile from pipeline through accounting, exceptions are visible, and sampled records match the work customers actually bought. Only then can leadership decide whether customers are paying for the product itself or for a custom service wrapped around it.