IT Consulting and MSPs: Cube vs Mosaic for Blended Revenue

A managed services agreement that bills a flat per-seat fee behaves close enough to SaaS ARR that Mosaic's waterfall logic, new, expansion, contraction, churn, applies with minor adjustment. The problem is when a single client invoice mixes the managed fee, a one-time project charge, and a hardware markup, and your accounting system doesn't split them at the line-item level.

Cube lets you build a classification layer in your spreadsheet that tags each invoice line by revenue type before it ever reaches the ARR calculation, so hardware markup (which should carry a much lower margin assumption than the managed fee) never gets counted as if it were recurring. Mosaic can do the same if your billing system already tags line items cleanly, but if it doesn't, you'll spend your setup time fixing the source data rather than configuring the tool.

Bringing in a subcontractor for a specialized project (a network migration, say) usually means passing their cost through to the client with a markup. If that pass-through revenue and cost both get counted in your top-line and cost-of-service numbers without being flagged, your margin percentage swings around based on how much subcontracted work happened to close that month, not on how your core delivery team is actually performing.

Build a separate line for subcontracted delivery, in either tool, so a quarter heavy on subcontracted network projects doesn't make your margin trend look worse than the story your own technicians are telling.

A help desk or NOC team needs to scale with the number of endpoints and seats under contract, not with total revenue, since a hardware resale deal adds revenue without adding a single monitored device. Track ratio of technicians to managed seats as its own metric, separate from a general revenue-per-headcount number that a services benchmark would use.

Technician pay has been climbing with the broader labor market. Employment Cost Index data shows civilian wage and salary growth of 3.4% over the trailing year¹, a reasonable starting point for your annual merit-increase line before layering on any local market premium for certifications like specific vendor accreditations. Cube lets you build the seats-per-technician ratio directly into your headcount trigger formula. Mosaic's headcount planner works off department budgets more than a per-unit ratio, so you'd be adapting it rather than using it as designed.

Rule of 40, growth rate plus profit margin, is a SaaS shorthand, and the median private SaaS company posts a score around 25, with the top quartile above 40². A managed services provider can compute the same math, but a firm with a large hardware resale component will show a much lower margin than a pure managed-services book even when the underlying delivery business is healthy, because hardware carries thin margin by nature.

If you use Rule of 40 internally, calculate it twice: once for the whole business, and once for the managed-services-only revenue, stripped of hardware and project pass-through. The second number is the one that actually reflects how well you're running the recurring side of the business.

• If your billing system already separates managed fees, project revenue, and hardware resale at the line-item level, Mosaic's automated classification will likely work with light configuration.
• If those three revenue types are currently mixed on client invoices, budget time to fix that at the source regardless of which tool you pick, since neither tool can classify what it can't see separately.
• If subcontractor pass-through is a meaningful share of revenue, Cube's spreadsheet flexibility makes it easier to exclude that revenue from margin calculations without a workaround.

Whichever you choose, get the invoice-level tagging right first. That fix pays off even if you end up staying on a spreadsheet a while longer.