Product businesses sell things they can count. Service businesses sell time and expertise, limited by capacity that expires at the end of every working day. That single difference changes how you forecast revenue, measure profitability, price work, and plan growth.
Yet many growing service organizations still run on systems and processes built for product-based businesses: inventory-shaped accounting, invoicing that assumes a shipment, and reporting that arrives after the month has closed. The result is familiar to most finance and operations leaders. Margins are only visible in hindsight, resourcing decisions are made in spreadsheets, and forecasts depend on who happens to have the best mental model of the pipeline.
This article covers the four differences that matter most between product and service operating models, the specific problems each one creates, and how an integrated Enterprise Resource Planning (ERP) platform such as NetSuite closes the gap.
People are the inventory
In a retail or manufacturing business, capacity sits in a warehouse. It can be counted, stored, and sold next month if nobody buys it today. Service capacity works the other way: an hour that goes unsold cannot be put back on the shelf. And much of that capacity is not even yours to hold. Delivery typically depends on a mix of salaried staff, independent contractors, subcontracted partners, and third-party licenses or tooling resold as part of the engagement.
None of it behaves like stock. Every resource carries a different skill set, seniority, charge rate, cost rate, utilization target, availability window, and notice period, and contractors add their own constraints around rate, term, and how quickly they can be stood up. Two people with the same job title can have materially different effects on project margin depending on which work they are assigned to.
The consequence for planning is direct: if you cannot see available capacity by skill and by week, you cannot forecast revenue with any confidence. You are estimating what you can deliver rather than calculating it. Common symptoms include:
- Sales committing to delivery dates before checking whether the right people are free
- Senior staff absorbed into work that a mid-level resource could deliver, eroding margin quietly
- Bench time that nobody notices until the month-end profit and loss statement
- Recruitment decisions made reactively, after a project is already late
Capacity is the constraint on revenue in a service business. Treating it as an afterthought means treating revenue as an afterthought.
Revenue depends on time, not products
A manufacturer invoices when goods leave the building. The trigger is physical and hard to miss. A service business invoices when work happens, and the trigger is a timesheet entry someone has to remember to make.
The billing models multiply that complexity:
- Time and materials (T&M): revenue follows recorded hours and expenses, so unrecorded times are unrecoverable revenue.
- Fixed price: the fee is agreed upfront, which pushes all delivery risk onto the estimate. Profit depends entirely on hours consumed against the plan.
- Milestone billing: invoicing is tied to deliverables or dates, so cash timing depends on delivery discipline rather than effort.
- Retainers and subscriptions: revenue is contracted in advance and must be recognised over time, whether or not the client draws down the hours.
Most growing firms run several of these at once, often within the same client account. Layer on the operational realities and the picture gets harder: scope creep that never makes it into a change order, work logged against the wrong project or task, and the persistent question of what counts as billable.
One missed timesheet does two things. It delays an invoice, which pushes out cash collection, and it understates project cost, which affects the margin on a job that is actually in trouble. Neither error corrects itself.
Project margin is decided during delivery, not at month end
Most businesses find out whether a project made money once the work is finished and finance has reconciled the numbers. By then the outcome is fixed. The firms that consistently protect margin know where they stand while the project is still running, because that is the only window in which anything can be changed.
The practical test is whether your leadership team can answer these questions today, without asking anyone to build a spreadsheet:
- Which projects are over budget on hours right now, and by how much?
- What percentage of recorded hours last month were billable, and how does that compare to target?
- Who is over-utilized and at risk of burning out, and who is under-utilized this week?
- How much work has been delivered but not yet invoiced?
- Which client relationships are profitable after delivery cost, not just at headline revenue?
- What is the value of approved change orders versus scope delivered outside a change order?
If those answers take days to assemble, the reporting cycle is slower than the decision cycle. Delivery leaders end up managing on instinct, and finance spends its time reconstructing history instead of informing the next decision.
Recurring revenue adds a second forecasting problem
Many service businesses now run a mix of project work and recurring revenue: managed services, support agreements, hosting, license resale, or ongoing advisory retainers. It improves predictability at the top line and makes forecasting harder underneath it.
Recurring contracts carry their own accounting and operational demands. Billing schedules, renewal dates, usage tiers, mid-term upgrades, and prorated changes all have to be tracked contract by contract. Revenue has to be recognized across the service period rather than on invoice. And the cost of servicing a retainer sits with the same delivery team fulfilling billable project work, so profitability depends on how much support effort each contract actually consumes.
How NetSuite supports a service operating model
The core idea is that resources, projects, time, billing, and the general ledger sit in one system, so the same record drives operational decisions and financial reporting. In practice, that means:
Resource management connected to project demand. Skills, roles, cost rates, and charge rates live on the employee record. Resource allocations sit against project tasks, which gives a forward view of committed capacity, available capacity, and forecast utilization by person, role, or practice rather than a snapshot of the current week.
Time and expense capture at the source. Staff record time against project tasks from web or mobile, through approval workflows you define. Because that entry feeds costing, billing, and revenue in one step, the timesheet becomes the operational control point rather than an administrative chore.
Billing rules that match how the work was sold. Charge-based billing supports time and materials, fixed fee, milestone, and hybrid arrangements on the same project, generating invoices from approved time and expense rather than manual re-entry. Billing runs process across projects instead of client by client.
Revenue recognized on its own schedule. Advanced Revenue Management handles recognition separately from invoicing, including percent-complete recognition for project work and rateable recognition for retainers and subscriptions. For contracted recurring revenue, SuiteBilling manages schedules, renewals, and mid-term changes.
Project accounting that shows margin in progress. Actual and committed cost accumulate against budget as work is delivered, so project profitability, work in progress (WIP), and unbilled revenue are visible during delivery. Estimate to complete can be revised as the picture changes.
Role-based dashboards over one dataset. A delivery lead sees utilization, allocations, and budget consumption. A controller sees WIP, unbilled revenue, days sales outstanding, and recognition schedules. A chief executive sees pipeline against capacity and margin by service line. Nobody reconciles a version.
Configurations that made the difference for our clients
Standard functionality covers most of a service operating model. The remaining gaps are usually where the money is, and they tend to sit in the same four places. These are configurations and customizations we have built for service organizations running on NetSuite.
Automated annual rate increases on contracts. Contracted rate escalations are one of the most common sources of revenue leakage in service businesses, because applying them depends on someone remembering. We added an increase percentage and effective date to the contract record, then used workflows to apply the uplift automatically when the date is reached. Saved searches give finance a forward view of which customers are due for an increase and when, so the annual review becomes a scheduled process rather than a scramble. Every increase that was negotiated actually reaches the invoice.
Earned and forecast revenue reporting for service contracts. Off-the-shelf reporting tells you what was invoiced. Service leaders need to know what has been earned, which is a different number, and what will be earned over the coming months. We built saved searches and reports that separate revenue earned from revenue billed, and extend the same logic forward across contracted work. Finance can see the current earned position at any point in the month, and the leadership team can forecast from contracted commitments rather than from a spreadsheet rebuilt each quarter.
Automated direct debit collections. For clients billing large volumes of recurring service customers, collections was the bottleneck. We used scripts and workflows to generate payment files in the format the client's bank requires, drawing on the invoices raised for each customer and the collection terms held on the customer record. The bank withdraws the funds directly, so cash arrives on a predictable schedule, the accounts receivable team stops chasing routine payments, and days sales outstanding falls without anyone making a phone call.
Integrations with front-office and payroll systems. Service businesses rarely run everything in one place. Sales and recruitment teams work in Salesforce or TargetRecruit; pay is processed in a dedicated payroll system. We have built integrations in both directions: syncing resources, placements, and project costs between the front-office platform and NetSuite and bringing actual payroll cost back into the project record. That last point matters more than it sounds. Job costing based on standard or estimated rates gives you an approximation of margin. Job costing based on actual payroll cost gives you the real number, and it is often the first time a services leadership team sees true project profitability.
Coordinating people is the growth constraint
Service businesses don't scale by selling more. They scale by coordinating people more effectively, because capacity, not demand, is usually the limit on what can be delivered profitably.
An operating model built for products will keep producing the same three problems: margin that is only visible in hindsight, forecasts built on judgement rather than capacity, and finance teams spending their time assembling data instead of interpreting it. Connecting resources, projects, time, and finance in one system is what turns those four into a single, current view.