G2

Greg M.

Chief Operating Officer

Mid-Market (51-1000 emp.)

8/30/2026

"Built by people who've actually run a services business"

5/5

What do you like best about Operating?

It's obvious from day one that Operating was built by people who have lived in professional services. The resource model, positions, allocations, and phases, matches how consulting work is actually planned and delivered, so we spent almost no time bending the tool to fit our reality. Staffing and allocations and the utilization and margin reporting are where we get the most value: we can see planned versus actual capacity and delivery economics in one place instead of assembling them from exports. The integration ecosystem is also a real differentiator. Native HiBob and HubSpot connections, a well-built API, and an MCP server mean the data doesn't stay trapped in the product. Review collected by and hosted on G2.com.

What do you dislike about Operating?

Reporting flexibility. The standard planned and actual reports answer the main questions, but for non-standard cuts we end up going through the API and analyzing outside the tool. More configurable dimensions and saved custom views would remove that step. Worth noting that the API makes the workaround easy, which is why this hasn't been a real problem for us. Review collected by and hosted on G2.com.

What problems is Operating solving and how is that benefiting you?

Operating replaced a set of disconnected spreadsheets and exports with one live view of staffing and delivery economics. Capacity questions get answered during the conversation instead of in a follow-up analysis, and because planned allocations and actuals live in the same system, our utilization and margin reporting is grounded in the same data our staffing decisions were made from. The HiBob and HubSpot integrations and the API mean it fits into how we already work rather than becoming another silo. Review collected by and hosted on G2.com.