Cube vs Mosaic for HR Consulting Firms: Retainers and Project Margin

Blending a stable, monthly-recurring retainer fee with lumpy, phase-based project revenue into a single "consulting revenue" number hides which part of the business is actually driving growth. A quarter with two large compensation studies closing can make the firm look like it's scaling, when the retainer base, the more durable part of the business, hasn't moved at all.

Mosaic's recurring-revenue waterfall is a strong fit for the retainer line specifically: new, expansion, and churn logic applies almost directly, since a retainer client renewing or leaving is a clean, discrete event. Track project fees in a separate schedule tied to actual project phases and deliverable dates, which Cube and Jirav both model well as milestone-based revenue. Reviewing the two lines side by side each month, rather than as a single combined total, is usually enough on its own to surface whether the firm is actually growing its durable client base or just riding a strong project quarter.

A compensation benchmarking or job-architecture project moves through distinct phases (data collection, market analysis, client workshops, final report) that each require a different mix of senior and junior staff time. Planning headcount against a flat average hours-per-project number understaffs the analysis-heavy middle phase and overstaffs the lighter kickoff and delivery phases.

Cube and Jirav both let you build a phase-by-phase staffing plan tied to your actual project timeline, so a consultant's calendar reflects when they're actually needed rather than an average smoothed across the whole engagement. That matters most when two or three projects are staggered at different phases simultaneously, since the analysis-heavy phase of one project can easily collide with the workshop phase of another if the calendar isn't built to catch it in advance.

A compensation study that starts as a single-division benchmarking project often expands mid-engagement once the client sees the first round of results and wants the analysis extended to two more business units. If that expanded scope isn't repriced, realization on the project quietly erodes even though the client relationship looks healthy.

Track realized rate against original scope separately from realized rate against final delivered scope, so a project that expanded without a corresponding fee increase shows up clearly in the numbers rather than getting absorbed into an average that looks fine.

A one- or two-partner HR consulting firm typically brings on a third senior consultant once the retainer book alone can't absorb another project without turning down work. Wage growth across the broader labor market has been running close to 3.4% a year¹, a reasonable baseline for a senior HR consulting hire's annual comp increase before adding a premium for compensation-design or HR-technology specialization.

Model the hire against your project pipeline, not your retainer base alone, since a senior consultant's cost is fixed but a compensation study's timing can slip a full quarter waiting on client-side data. Cube and Jirav both let you build that pipeline-timing risk into the hiring trigger directly.

• If retainer revenue is most of the business, Mosaic's automated recurring-revenue tracking is worth using for that line, with project fees modeled separately.
• If project revenue dominates and scope creep is a recurring problem, Cube's flexibility to track realized rate against original versus final scope will serve you better than Mosaic's subscription-oriented defaults.
• If you want a working split model fast without a long build, Jirav's driver-based templates handle both revenue types with less setup time.

Whichever tool you pick, keep the retainer and project lines separate in every report the partners actually look at. A blended number flatters a good project quarter and hides a shrinking retainer base equally well.