The lakes are thawing. The Flames are either in the playoffs or out, and either way Calgary has moved on accordingly. April here is the month where you remember what wind feels like when it is not pretending to be a Chinook. This is also when first-quarter reports land at the energy operators downtown, and the pattern that emerges every year is reliable: three operators in the same industry, at the same scale, with three completely different IT problems and three completely different right answers.
Why two operators in the same business with similar revenue often need very different things from their technology - and what the size of the gap says about how to set expectations.
(I have watched three Calgary E&P operators with adjacent assets, similar headcounts, and the same investor base end up at three different conclusions about cloud, security spend, and managed services - and all three were correct for their specific situation.)
Two operators in the same industry, at similar revenue, often have radically different IT challenges. Not because one is sophisticated and the other isn't. Because the actual technology problem each one has is determined less by industry and revenue than by three other factors that operators rarely benchmark against.
The three factors that actually matter
1. How the business grew. An operator that grew through acquisition has fundamentally different IT shape than one that grew organically. Different systems welded together, different vendor relationships inherited, different data models that don't quite align. An organic grower with the same revenue might have a clean stack but lack the integration discipline an acquirer has been forced to develop. Same industry, same size, different problems.
2. How distributed the workforce is. Two operators with 200 employees and similar revenue but one of them has everyone in an office and the other has 60 percent in the field. The first one's IT investment looks like productivity tooling and security. The second one's looks like connectivity, mobile devices, and edge applications. The center-of-gravity of the technology spend is different, and so is what "good" looks like.
3. How regulated the data is. Two operators in the same industry can have very different regulatory exposure depending on the specific markets they sell into, the customer types they serve, and the geographies they operate in. Healthcare data, financial data, regulated industry data, multi-jurisdictional data - any of these dimensions changes what the IT program has to do. Industry classification is a poor proxy for this.
Why this matters
Two consequences. First, when you benchmark IT spend or staffing against industry peers, the benchmark is usually misleading enough to be actively harmful. The operator with a different growth path, workforce shape, and regulatory exposure looks "outside the range" in ways that are actually correct for their situation.
Second, when you evaluate IT vendors and providers, the relevant question isn't whether they serve your industry. It's whether they have served operators with your growth pattern, workforce shape, and regulatory complexity. An IT firm that has seen ten operators in your industry but only one that grew the way you did is going to be useful for the patterns the ten share and unhelpful for the patterns specific to your shape.
A better question
Instead of "what are companies like us doing," ask "what are operators with our growth path, workforce shape, and regulatory exposure doing differently than industry peers." The answers are more specific, the actionable patterns are more visible, and the things that don't generalize from industry benchmarks stop being a source of confusion.
This also opens a useful framing for the cross-industry learning. The mid-market construction firm with a 70 percent field workforce has more in common operationally with a healthcare services firm with the same field exposure than either has with a desk-bound peer in their own industry. The patterns transfer. The vendor expertise transfers. The questions worth asking transfer.
Industry is one variable. It is rarely the most important one.
This issue of the Operator's Brief is operator pattern recognition from Vencer Group's work with mid-market businesses across industries and geographies. Not industry-specific advice. Read accordingly.
Notes & Methodology
About these figures: This Operator's Brief is a monthly Calgary-rooted, internationally delivered mid-market business observation from Vencer Group. Patterns and trends described reflect Vencer Group's operating experience across mid-market Canadian energy clients - service operators, E&P companies, midstream, and energy services in the 25-300 person range. Industry references (regulatory changes, market events, threat landscape shifts) are drawn from publicly reported sources cited inline where applicable. Specific cost ranges, percentages, and timeframes are Vencer Group estimates based on observations across recent client engagements, framed as estimates where used.
Pattern recognition from 19 years of running operator IT - not prescription for your specific situation. Anyone offering prescription from a blog post is selling something. (Possibly to you.) The 30-min Strategy Review is where the pattern becomes specific to your operation. Free, no proposal, no slide deck.
→ Book the 30-min review