How do you build IT that survives a Canadian oil downcycle?

Two oil price collapses, three platform shifts, and an industry that has fundamentally changed shape twice - and yet the same IT mistake keeps producing the same outcome. Operators build for the upcycle. The cycle turns. The IT that looked smart at $107 oil quietly becomes the IT that buries you at $47.

Building IT for the cycle is not a phrase. It is a planning discipline. We're builders and operators - that's where this discipline comes from. Two downcycles, thirty-plus M&A transactions, and the same pattern showing up every time. Here's what it actually means.

The cycle is gravity, not weather

The most common framing of commodity cycles in Canadian oil and gas treats them like weather - temporary conditions you wait out, react to, occasionally complain about. That framing is wrong, and it produces the IT decisions that compound badly.

The cycle is gravity. It is the constant force that determines what survives. Operators don't "wait out" the cycle any more than they wait out gravity. They build for it, on both ends - or they get crushed when the direction of the force changes.

The 80-person operator who built sophisticated production accounting at $107 WTI in 2024 is the same 80-person operator who can keep running it at $47 WTI in 2027 - because the cost structure was built with the downcycle in mind. The operator who bought enterprise-grade software, hired full-time admins to run it, and locked into five-year service contracts at peak is the operator paying for capability they can no longer afford when the cycle turns.

Which three forces compound across cycle turns?

What we've watched, across thirty M&A transactions guided through both 2014-2016 and 2020-2021:

Force 1 - Operational discipline. Operators who built measurement discipline in the upcycle (JIB reconciliation, AFE tracking, production data accuracy) carry that discipline into the downcycle. The reverse never happens. No operator suddenly develops measurement discipline when commodity prices are crashing.

Force 2 - Cyber posture. The cyber program you deploy at $107 oil is the cyber program you'll be defending at $47 oil. Cyber attackers don't pause for commodity cycles. The 2024-25 ransomware surge in oil and gas targeted operators specifically because mid-market revenue was strong. If your posture was thin when you could afford to fix it, it's not getting fixed when you can't.

Force 3 - Integration capacity. The operators who became the 2024-25 Canadian consolidators built their M&A integration capability in 2020, when activity was slow and there was bandwidth to work on it. By 2024 they could absorb 30-person bolt-on acquisitions in 90 days. Their competitors couldn't, because they were still running flat out servicing the upcycle.

What does "build for the cycle" look like in practice?

The asymmetric pattern: IT decisions made at $60-90 WTI have small, bounded downside risk. The same decisions made at $107+ WTI have small, bounded upside. The decisions made at $40-50 WTI usually can't be made at all.

What this means for a 50-200 person operator:

• Cyber baseline in the upcycle, not after the incident. Deploying the twelve controls (named industry-standard products, documented, tested) is cheaper at $107 than at $47 - and dramatically cheaper than the post-incident scramble. By the time the underwriter asks for evidence, the work has to already be done.
• Integration capability before the deal. A 30-person bolt-on acquisition is straightforward to absorb if you've already practiced the integration playbook on a hypothetical target. It's catastrophic if you're learning the playbook during the deal.
• Measurement discipline before you need it. The JIB aging that's at 8% of TTM revenue in the upcycle becomes the JIB aging that costs you a multiple turn in the deal, or that you write off entirely in the downcycle. The reconciliation discipline has to be built when you can afford to staff it.
• Vendor consolidation in the upcycle, not the downcycle. Cutting SaaS sprawl is easier when revenue can absorb the consolidation cost. Trying to cut sprawl mid-downcycle creates operational disruption at the worst possible moment.

What it does NOT mean - three misreads to watch for

Some misunderstandings, since this framing gets garbled in practice:

It does not mean austerity. Building for the cycle is not the same as not spending. It's the discipline of building the right capability at the right time - typically more spending in the upcycle on compounding capability, less spending on discretionary or peak-demand-only capability.

It does not mean ignoring the upcycle. The upcycle is when you build. The downcycle is when you harvest the compounding. Operators who ignore the upcycle because they're "saving for the downcycle" miss the window when capability is most affordable to deploy.

It does not mean predicting the cycle. Cycle timing is unpredictable. Building for the cycle means being ready for either direction at any time - not betting on one outcome.

The full thesis lives in Crude Truth - the foundational eBook on building IT for both ends of the oil cycle. Chapter 5 specifically covers the four growth walls and the six levers that compound across cycle turns.

If you'd rather have someone diagnose your specific situation, the IT-and-the-Cycle Assessment is the structured way to do it - three to five days, written report, no obligation.