Your services org is a P&L. Most software companies don't run it like one.

Most services organizations were assembled, not designed.

The financial model was inherited from whoever wrote the first statement of work. Nobody has revisited it since, and the symptoms show up somewhere other than the services line — in renewal timing, in reference quality, in the implementation that quietly ran a quarter long.

The gap between the organizations that run this well and everyone else is not a market condition. It's a set of decisions — about pricing, staffing model, scope discipline, and what gets measured. Which means it's fixable, and fixable without a reorganization.

Software companies from $5M to $200M in ARR — and the firms that deliver for them.

Large enough that services is a real P&L with real people in it. Small enough that there is no internal services strategy function, and no appetite for a consulting engagement priced past the size of the problem.

The same work applies to boutique consultancies and systems integrators, where services isn't a line on the P&L — it is the whole business. Different buyer, shorter decision, same nine questions.

• Services is losing money, or making margin nobody can explain.
• Implementations are running long and the dates keep moving.
• Delivery problems are starting to show up in renewals.
• A new services leader inherited the org and needs a baseline.
• An acquisition left two delivery organizations that never merged.
• Fixed-fee work is priced from estimates nobody has checked against what it actually cost.

A diagnostic, not a retainer.

The organization is scored one to five across nine operational dimensions against a defined maturity ladder — so the result is legible, repeatable, and traceable to evidence rather than to one person's opinion. Fixed fee, fixed scope, fixed end date, every time.

1. The conversation

   Thirty minutes, free, and structured. It ends with observations, not a proposal.

2. The diagnostic

   Interviews, evidence, and a scored assessment across all nine dimensions.

3. The findings

   The three highest-value problems, quantified in your dollars, ranked by impact over effort.

4. Remediation, if you want it

   Packaged modules, separately priced, entirely optional. The diagnosis is the product.

For smaller organizations there is a two-week version of the same method — four dimensions instead of nine, a short findings memo instead of the full report set. Both are described here.

The same operator lens, pointed at a partner delivery motion.

Software vendors build partner programs to move delivery off their own bench. Most of them are designed by people who have done one half of the job — delivery specialists who have never sat on the vendor side, or alliance leaders who have never carried the services number the program was meant to relieve.

The work is the same discipline applied to a different organization: what a partner has to do to reach a tier and what they get for it, the economics that answer "what's in it for me" in the currency partners actually run on, enablement designed backwards from time-to-first-successful-deployment, and the governance that makes an escalation resolvable before it becomes one. What that engagement looks like.

Run by someone who has actually carried the number.

Twenty-five years building and running professional services organizations inside software companies — including an eight-figure services P&L spanning multiple products and regions, with responsibility for margin, utilization, delivery quality, and the renewal conversations that follow from all three.

These are problems solved in production — against real resistance, with real consequences for getting them wrong — rather than patterns observed from outside. That is the whole difference between this and a benchmark report.

• 25Years running services organizations
• 9Dimensions scored in the diagnostic
• 3–4Weeks from kickoff to readout
• 1Active engagement at a time