Bill Grabe - Former VP, IBM Services

Software Services Strategy: How to Balance Product and Services at Scale

Bill Grabe, Former VP IBM Services and Former Managing Director at General Atlantic

Bill Grabe served as an IBM Vice President and Corporate Officer, where he helped shape the early strategy behind IBM Global Services. After retiring, he joined General Atlantic, where he helped scale global technology investments across Europe, India, and China.

What Founders Should Know About Software Services Strategy
  • Software companies succeed with scalable products. Service-heavy business models risk margin erosion and operational complexity.
  • Keep services lean. Grabe recommends limiting service dependency to focus on replicable product revenue.
  • People-driven services scale differently. Managing utilization, profitability, and hiring becomes essential when service delivery expands.
  • Utilization drives services profitability. As a rule of thumb, 80% of services staff should be billable at all times.
  • Avoid building cost structures too early. Preemptive hiring for service demand can backfire if revenue lags.
What to Know Before Scaling a Software Services Business

Should software companies keep services in house or outsource?

Software businesses thrive on repeatability. Services require labor, and labor doesn’t scale like product. While services can be necessary to implement complex products, they should not become the growth engine. Keeping them lean allows companies to preserve margins and avoid becoming a services business by accident.

What is the right way to grow a services function?

Hire ahead only if demand is confirmed. Grabe cautions against loading up on service headcount without guaranteed utilization. Services teams must run like businesses within the business — with margin targets, accountability, and tight operational control.

How do you manage services utilization effectively?

Utilization is the key performance metric. The benchmark: 80% of your services team should be actively working with customers at all times. Any lower, and margins suffer. Overhead roles should be kept minimal.

What’s the risk of over-relying on services?

Margin compression. Founders risk building a business that becomes harder to scale or less attractive to growth equity firms. Larger service players can undercut pricing. If your services business cannot compete or scale profitably, it becomes a liability in the eyes of buyers or investors.

“Software companies win by building scalable products. Services should support the product, not drive the business.”

Bill Grabe, Former VP of IBM Services

Considering Growth Equity Capital?

Thinking about how to scale services without hurting margins or growth potential?

We work with founder-led companies to scale intelligently and prepare for long-term growth.

Contact our team

About Bill Grabe

Bill Grabe served as VP of IBM Services and was a founding board member of IBM Global Services. He later became a Managing Director at General Atlantic, where he supported global expansion and technology investments across multiple continents.

Software Services Strategy FAQs for Founders

What is a software services strategy?

It’s the plan for how much service your product needs to succeed — and how much is too much. It affects margins, customer success, and scalability.

How do I know if I’m over-invested in services?

If your service headcount grows faster than revenue or utilization falls below 80%, you may be over-indexing.

Do services impact valuation in growth equity deals?

Yes. High service dependency can reduce multiples. Product-led growth is more attractive to investors.

What’s the best way to keep services aligned with product?

Use services to support onboarding and adoption. Measure customer impact, not just delivery hours.

Can services be a long-term growth driver?

Only if they are profitable, well-managed, and don’t cannibalize product strategy. Grabe emphasizes treating services like a standalone business unit.

Join our mailing list for the latest articles, data, and events