Thirty percent smaller.
Same operational backbone.
How a 42-person Calgary wireline specialty firm contracted by 30% deliberately, preserved the operational platform intact, captured institutional knowledge before each departure, and was ready to scale back up when the cycle turned.
FOR: Operators · 25–50 people · deliberate downsizing in downcycle
Quick answer
A 42-person Calgary wireline specialty firm chose to contract by 30% during the early 2026 downcycle - deliberately, not reactively. Vencer's engagement preserved the operational platform intact (identity, accounting, cyber baseline, backup integrity), captured institutional knowledge from each departing employee before they left, and kept the firm ready to scale back up when the cycle turned. Six months after the trough, they were back to 38 people on the original platform.
A 42-person specialty firm contracting deliberately.
42 people. A wireline services specialty firm in Calgary, founded in 2009, that had grown through two cycle turns and was now looking at the third. The owner had decided to contract by 30% over the next six months - deliberately, not under duress - to preserve the company’s ability to scale back when the cycle turned.
The owner of the company - we will call him Greg, though he could have been any of the founder-owners we have worked with through this exact moment - called us in November 2025. He had spent the previous month making one of the hardest decisions of his career. The company was profitable. The team was solid. The market was just slowing in a way that was going to compress his margins for the next twelve to eighteen months, and he wanted to get ahead of it rather than be forced into reactive cuts later.
Greg had been through 2014 and 2020 with this company. He knew the pattern. He had watched a competitor in 2015 cut too late and too deep, then spend three years rebuilding capability from scratch while better-disciplined firms took their market share. He did not want to be that competitor. The contraction plan was to reduce headcount from 42 to roughly 30, retire some equipment, consolidate the office footprint, and keep the operational backbone intact for the eventual recovery.
The company’s operational reality was Mixed in the practical sense: Microsoft 365 in the head office, a specialized scheduling and wireline-data platform that ran on a local server, customer billing through WolfePak, field tablets for the crews, and a small server room handling the scheduling platform. None of it was bad. All of it was sized for 42 people doing the volume the company had done at the peak of the 2024 upcycle. The question was how to right-size all of it for the new operational footprint without breaking the parts that needed to remain ready for growth-back.
Greg’s actual question to us was: “How do I take 30% out of this business in six months without losing what I will need to win the contract that comes back in 2027?”
Right-size without breaking. Cut people without losing institutional knowledge. Preserve the platform for growth-back.
The contraction work split into three distinct categories of difficulty:
- Operational systems that could be right-sized cleanly. Network bandwidth sized for 42 people could be reduced for 30. File storage could be re-tiered with less-used historical data moved to lower-cost storage. Office systems - meeting room AV, common area printers, building access controls - could all be right-sized to the smaller footprint. This was the easy work, mostly administrative.
- People decisions with operational consequences. Twelve people were going to leave the company over six months. Each of those twelve had access to systems, knowledge about how things worked, and relationships that the company needed to either transfer or document before they left. The hardest case was the controller, who had built the customer billing setup almost entirely on her own knowledge. She was on the list of departures because the new operational scale did not need a full-time controller. Her institutional knowledge could not be allowed to leave with her.
- Platform investments that needed to be preserved. The cyber baseline. The backup setup. The monitoring coverage. The identity and access discipline. Greg knew from 2020 that cutting these to save money during the contraction would create the kind of vulnerability that gets exposed by a ransomware incident at exactly the worst moment. The platform that would support the eventual recovery had to come through the contraction intact.
The other constraint was emotional. Twelve people were going to lose their jobs. The remaining thirty would be watching how the transitions were handled and would draw conclusions about the company they were continuing to work for. Greg cared about doing the contraction in a way that was professional, dignified, and operationally clean - not just in a way that satisfied the cost target.
The forced-contraction scenario covered in Chapter 10 of The Operating System applies to operators who are responding to circumstances rather than choosing them. The deliberate-contraction scenario is structurally different and in many ways harder. The discipline required is the same as in forced contraction - protect the baseline, cut from the right places, preserve reversibility - but the time pressure is less, which creates the temptation to over-engineer the process.
The operators who handle deliberate contraction well typically emerge with 25% to 35% lower operating cost, the same operational capability, and a meaningfully better employee relationship with the team that stays. The operators who handle it badly end up either cutting too little (defeating the purpose) or cutting in ways that the staying team interprets as warnings of more cuts to come (which creates retention problems precisely when retention matters most).
A Co-Managed engagement, with offboarding discipline as the centerpiece.
Vencer had been the Co-Managed partner for the company for two years before the contraction work began. That history mattered. We knew the systems, we knew the people, and we knew which institutional knowledge lived where. The contraction work was not a new engagement - it was the application of existing capability to a specific moment. The work happened in three phases over six months.
Phase 1 - documentation before departures (months 1 through 2).
The hardest part of any contraction is capturing the institutional knowledge that will leave with the departing employees. We spent the first two months working alongside the twelve people who were going to leave, capturing what they knew before they left. Some of this was formal documentation. Most of it was structured conversations recorded with permission, where they walked through how they did their work, what they knew that nobody else did, and what would break if they were gone tomorrow.
The controller’s work was the highest priority. The customer billing setup had three years of accumulated decisions encoded in formulas, manual reconciliations, and workarounds that only she fully understood. We spent six full days with her over five weeks - not extracting her work product, but capturing the reasoning behind it. By the end, the new billing flow was documented in a 28-page runbook that the part-time bookkeeper who would replace her could follow without needing to call her after she left. The controller told us, on her last day, that this had been the most respectful exit she had ever seen handled by a previous employer. Greg sent us a note that evening.
Phase 2 - the offboarding discipline (months 2 through 5).
Twelve people left the company over fourteen weeks. The offboarding procedure we had documented during our initial engagement two years earlier - the one covered in The Operating System Chapter 4 - was the procedure each departure followed. Every one of the twelve offboardings was completed within 24 hours of the employee’s last day. Every access was removed. Every license was reclaimed. Every device was returned and wiped. Every shared drive permission was reviewed. Every distribution list was updated.
Three months after the last departure, we ran a verification audit. Of the twelve people who had left, zero had any remaining access to any company system. Compare this to the company’s 2014 contraction, before our engagement, when a similar number of departures had taken nine months of cleanup work and had left at least four people with active access for over a year. The difference was not technology. The difference was discipline, written down.
Phase 3 - right-sizing the operational backbone (months 3 through 6).
The systems work happened in parallel with the offboarding work, but at a more deliberate pace. We right-sized the network bandwidth, the file storage capacity, and the office systems to the new headcount. We renegotiated cellular plans down to the actual usage levels of the smaller team. We consolidated some vendor relationships. We tiered the file storage so historical data moved to lower-cost archival storage that could be brought back forward later if needed.
What we did not change: the cyber baseline (preserved), the backup setup (preserved - including the immutable cloud storage that protects against ransomware reaching the backups), the 24/7 monitoring through our Singapore and Calgary operations (preserved), the SentinelOne endpoint protection (preserved), the Proofpoint email security (preserved), the patching cadence (preserved), the documented identity and access discipline (preserved). The platform that would support the eventual scale-back was kept intact.
One specific decision worth naming: the specialized scheduling and wireline-data platform that ran on the local server. The platform was sized for 42 people doing peak-cycle volume. The smaller operational scale did not need that capacity. We had the option to scale the platform down to save money. We chose not to. Scaling it back up later, when the recovery came, would cost 3 to 4 times what the savings would have produced over the contraction window. Greg agreed without hesitation. He had been through this before.
30% smaller. Same operational backbone. Ready to scale back when the cycle turns.
Before and after.
The moment it mattered.
The moment that mattered was not the cost reduction. It was a conversation Greg had with one of the staying team members in month four. The team member was a senior wireline operator who had been with the company since 2012. He had watched the previous two contractions from inside. He asked Greg, directly, whether this one was the start of a slow decline or a deliberate position-taking. Greg was able to walk him through the plan, the preserved platform, and the readiness for scale-back - with specific evidence rather than reassurance. The senior operator stayed. So did the rest of the team that was going to stay.
The recovery began in mid-2027 - somewhat later than Greg had anticipated. The company started hiring back in Q3 of that year. The first five new hires were onboarded onto the existing operational platform in under three weeks, using the same systems that had been preserved through the contraction. The scheduling platform that had been kept at full capacity was running its first peak-cycle volume by Q1 2028. Two of the staying team members went on to become senior leaders during the recovery; one of them is now Greg’s operations director.
The competitor Greg had been determined not to be in 2015 is still in business. They never fully recovered the capability they cut in 2020. Greg’s company has approximately 90 people today. The competitor has approximately 50.
The deliberate contraction scenario covered in Chapter 10 of The Operating System applies to operators who have the foresight to take the cost reduction before it becomes unavoidable. The operational discipline required - protect the baseline, cut from the right places, preserve reversibility, capture knowledge before people leave - is the same as in forced contraction, but the time available to do it well is different. The operators who use that time well typically emerge from the cycle bottom with materially better posture than those who hold position too long and then have to react.
The Co-Managed engagement model is structurally well-suited to contraction work because the institutional history matters. Vencer’s two-year prior engagement with this company meant the contraction work was the continuation of an existing relationship, not the start of a new one. For Canadian operators who want to manage the cycle deliberately rather than reactively, a long-relationship IT partner with cycle-aware perspective is one of the practical assets that distinguishes the operators who emerge stronger from the operators who do not.
Does this story sound familiar?
The pattern in this case study has played out across dozens of Canadian oil and gas companies in the 10 to 100 person range. If you recognize parts of it in your own operation - or you suspect you might - the next step is a structured conversation with a Vencer engineer.
The IT-and-the-Cycle Assessment is a 3 to 5 day structured review of your specific operational situation. We pressure-test where your IT stands today, where it needs to be for what you intend to become, and what one bad day looks like at current state. You leave with a written report, a 90-day plan, and named owners. No hype. No vendor pitch. Just the truth about where you are and what to do next.
For a faster diagnostic, three free tools at vencergroup.com cover the same territory in less time: the Hidden IT Cost Calculator (12 minutes, quantifies your IT cost burden across three price-cycle scenarios), the Cyber Risk Self-Score (5 minutes, scores your cyber baseline against 12 critical controls), and the IT Myth-Buster sheet (the seven objections you’ll hear from inside your own company and how to think about them).
Vencer operates from Calgary headquarters with delivery teams across four continents. For Canadian-headquartered operators with international exposure - whether that means US basin extension, international service contracts, cross-border M&A, or international counterparties with their own cyber and audit requirements - the cross-border operational capability is built in, not bolted on.
Calgary, AB T2P 3J4
insights@vencergroup.com
One operator's outcome. Your situation has different variables. These numbers are real; the applicability to your operation requires conversation. The 30-min review is where that starts.
→ Book the 30-min review