How Rebuilding a Delivery System Increased Gross Margin 68 Points in Four Months
A SaaS company struggling with delivery costs transformed margin, efficiency, and team capacity by rebuilding its operational foundation.
Key Results
• Gross Margin: –22% → +46% (+68 points)
• Project timelines: 3 weeks → 5 days
• PM capacity: 5 clients → 21 clients per PM
• Delivery transformed from reactive to scalable
The Situation
A growing B2B/B2C SaaS company appeared healthy on the surface. Revenue was increasing and demand was steady.
But the financial picture told a different story.
Gross margin had fallen to –22%, and the largest cost driver in the business was the Project Management team responsible for implementation and ongoing client delivery.
Delivery was slow, inconsistent, and increasingly expensive.
Leadership knew something needed to change, but the root problem wasn’t obvious.
The Diagnosis
After conducting a full audit of the company’s P&L, operations, and team workflows, the problem became clear.
The delivery organization had no operational system behind it.
Every project was being rebuilt from scratch.
There were no SOPs, templates, or documentation. Timelines varied widely, expectations were unclear, and the team had no shared definition of what “good delivery” looked like.
Key findings included:
• Gross margin at –22%
• The PM team was the company’s largest expense
• Average project timeline: 3 weeks
• Delivery processes varied widely between PMs
• No standardized documentation or playbooks
• No visibility into capacity or cost to serve
The team wasn’t underperforming.
They were operating without a system.
What I Discovered
Through deeper analysis, another important insight emerged.
Although projects appeared unique, the majority of delivery work fell into just 20 repeatable project types.
Yet every one of those projects was being recreated from scratch.
PMs were spending hours rebuilding work that could have been standardized.
This hidden rework was destroying margin and preventing the business from scaling delivery efficiently.
The Operational Rebuild
I rebuilt the delivery operating system around repeatability, clarity, and operational visibility.
Key changes included:
Standardized Project Frameworks
The top 20 project types were identified and documented.
Each project received a full operational playbook including SOPs, templates, resource guides, and training materials.
Defined Delivery Standards
Clear definitions were created for:
• quality
• timelines
• expectations
• success metrics
This eliminated ambiguity across the team.
Operational Visibility
New reporting and workflows provided visibility into:
• project timelines
• team capacity
• delivery cost drivers
Team Alignment
Roles, responsibilities, expectations, and compensation structures were redesigned to align with operational outcomes.
The PM team was trained and coached on the new delivery system.
Instead of reacting to every project differently, they now operated within a consistent operational framework.
The Outcome
Within four months, the impact was dramatic.
Gross Margin
–22% → +46%
(+68-point improvement)
Project Timelines
3 weeks → 5 days
PM Capacity
5 clients → 21 clients per PM
Delivery became:
• predictable
• scalable
• profitable
• consistent
The company could now support significantly more customers without increasing headcount.
The Founder Insight
Many companies assume margin problems come from pricing.
But margin problems are often operational problems.
When delivery systems are inconsistent, manual, and undocumented, costs quietly grow faster than revenue.
Fixing the operational foundation can dramatically change the financial trajectory of a company.
If your company is growing but delivery is becoming slower, more expensive, or harder to manage, the real issue may be the operational system behind your team.