Finding the Real Cost of SaaS Implementation

A B2B SaaS company was doing many of the right things. Sales was growing fast, and leadership had already responded by hiring additional delivery staff, revising the implementation process, standardizing service packages, and bringing in an experienced implementation partner for extra capacity.

Those investments helped. But the CEO knew Professional Services needed experienced leadership for its next stage of growth and approached me to lead the function.

What I found

The implementation partner was excellent, and the extra capacity was real. But once I looked at the numbers, the company was paying the partner more than it charged the customer for that work. Every partner-delivered implementation was a loss in hard dollars.

The internal picture took longer to see. There was no invoice making the loss obvious. The cost was staff time, and on paper the team looked productive. The problem came into focus as projected completion dates kept slipping and the implementation managers examined how much time they were actually spending on the work.

Service packages had been priced on the assumption that a typical implementation took about 42 hours. In reality, implementations were taking more than 100 hours.

Nobody had caught the gap, including the delivery team doing the work. They did not have a clear picture of how long their own implementations actually took. It took several months of examining how work was really being delivered and watching where timelines kept slipping to surface the true number.

These findings changed how I approached the work. I had not been brought in just to add capacity. I needed to understand what was actually happening inside delivery and make changes that would allow the team to handle the growth in front of it.

What I changed

Three decisions drove the work.

Flexibility over specialization. The two-person delivery team was split by role. One person handled configuration, while the other served as project lead. That structure was efficient when volume was predictable, but it created a bottleneck when demand shifted. I restructured the team so both could lead full implementations, allowing resources to be assigned based on actual demand rather than a fixed division of labor.

Visibility and forecasting over assumption. The 42-hour estimate had gone unquestioned because there was no system generating a better number, and forecasting was built on that same assumption. I replaced the project management tool with one designed to support scheduling, documentation, forecasting, and time tracking, giving the organization better visibility into delivery effort and capacity.

Repeatability and alignment over heroics. I built an implementation playbook to standardize how projects were run, updated kickoff materials and tools, and supported an LMS rollout that gave customers a self-service training option. I also changed implementation revenue recognition to align with project milestones, so Finance and Professional Services had a more consistent view of delivery progress.

What happened during the year

Services delivery revenue grew 77% in one year.

During that year, the delivery organization also gained greater flexibility across the team, more repeatable processes, better operational infrastructure, and a clearer understanding of the effort and economics behind implementation.

The bigger lesson

When sales growth accelerates, the obvious answer is often to add Professional Services capacity. But capacity is not the whole problem.

In this case, the existing team genuinely did not have enough capacity for the volume the business expected. At the same time, implementations were taking more than twice the hours assumed in the service packages, and the company was losing money on work delivered by its implementation partner.

Adding people without understanding those economics would have solved one problem while potentially making another worse. Before deciding to add more capacity, understand what is consuming the capacity you already have, what the work really costs to deliver, and what needs to change in the operating model.

That is the point where implementation stops being a post-sale staffing issue and becomes a growth and operating-model issue.

Want a clearer picture of the implementation work your organization is trying to scale?

Reach out to learn how ClearWay Projects helps SaaS leaders assess delivery capacity, implementation effort, and the operating model behind growth.

• Back to Insights