Skip to main content
Energy Sector

Built for the Field, Backed by Calgary

We build software for Canadian energy companies that actually has to work twenty kilometres past the cell tower. Field tickets that sync when the truck rolls back into range. ESG dashboards that pull straight from your historian. Compliance reports the AER does not bounce back.

Field TicketingESG ReportingAER & BCER ComplianceSCADA IntegrationPipeline Monitoring

The Canadian Reality

Canadian Energy Software Has a Specificity Problem - and We Have Spent Years Solving It

The off-the-shelf SaaS your VP of IT keeps getting demos from was built in Houston for Permian operators. Canadian regulators, Canadian winters, and Canadian remote operations need software that actually understands them.

Walk into a Canadian upstream operator and you find a familiar mess. The production accounting team is exporting from one system and re-keying into another. The field supervisors are running a homegrown Access database that one IT contractor built in 2011 and nobody has touched since. The HSE team is chasing PDF incident forms across three regional offices, and the new Methane Regulations require monthly emissions reports nobody can produce without a week of spreadsheet work. The AER auditor is coming in six months and everyone quietly knows the data lineage will not hold up.

Off-the-shelf software does not solve this because off-the-shelf software was not designed for the Canadian regulatory landscape. The AER's Directive 017 reporting expectations, the BC Energy Regulator's permit workflows, Saskatchewan's IRIS submissions, and the federal Greenhouse Gas Reporting Program all want data in specific structures, on specific timelines, with specific audit trails. Your US-based pipeline monitoring vendor does not know what a Petrinex production volume reconciliation looks like, and your American field service platform was never tested at minus thirty-eight in Fox Creek.

We build custom software for Canadian energy companies because that is what the operators we work with actually need. A field ticketing app that captures crew hours, equipment, and consumables offline at the well site and syncs the moment the truck hits LTE coverage. A production allocation engine that reconciles your DCS, your historian, and your hauler tickets into a single source of truth before the data ever touches finance. An emissions dashboard that connects directly to your flare and vent meters so methane reporting stops being a quarterly fire drill. We have built variants of all three for clients across Alberta, northeast BC, and southeast Saskatchewan, and the pattern keeps repeating.

Headquartered in Calgary means we are in the same time zone as your morning operations call, we have walked your competitors' yards, and the engineers writing your code have actually been to a battery and a compressor station. We have seen what happens when a field tablet has to survive a drop from a sour gas plant catwalk and we design accordingly. That is the part that does not show up in a software demo from a Texas vendor flying in for a one-day pitch.

$2.4B
Annual oilfield services spend wasted on manual data entry across North America
Industry estimate
11 days
Average lag between field work and invoice in paper-based ticketing workflows
32%
Of disputed line items traced back to handwritten field tickets
<1 hr
Time to sync a digital ticket from wellsite to accounting once crew is back in coverage

What's Broken Today

The patterns we keep seeing

ISSUE 01

Field data trapped in paper

Hand-written field tickets, daily drilling reports, and HSE forms still drive most Canadian oilfield workflows. The result is a three-day lag between work happening and finance seeing it, plus a labour bill nobody can verify.

ISSUE 02

Compliance reports built in spreadsheets

AER S30 monthly summaries, Petrinex production submissions, and federal methane reports all get assembled by one or two analysts who copy-paste from five systems. When that analyst quits, the institutional knowledge walks out the door.

ISSUE 03

SCADA islands that do not talk to anything

Your DCS, your historian, your tank-level system, and your hauler dispatch are four different vendors with four different APIs. Nobody can produce a clean barrel-in barrel-out reconciliation without a manual stitching exercise every month.

ISSUE 04

Vendor lock-in disguised as integration

The enterprise platform that promised end-to-end visibility actually charges per-module licensing, per-user fees, and a five-figure professional services bill every time you want a new report. The lock-in compounds with each acquisition.

What We Build

Solutions tailored to oil & gas

Not a generic platform with industry skins. Architecture, workflows, and integrations chosen for oil & gas operations specifically.

Mobile-first apps for crews, supervisors, and dispatchers that work offline at the wellsite and sync the moment they hit coverage. Built for cold-weather gloves, sour-gas zones, and shift handovers that cannot lose data.

Digital field tickets with electronic signatures
Daily drilling and completion reports
HSE incident capture with offline photo upload
Crew timekeeping with geofenced clock-in
Equipment and consumables tracking with barcode scanning

Allocation engines that reconcile DCS, historian, and hauler ticket data into a defensible production number before it touches finance. Built to feed Petrinex without manual stitching.

Automated DCS to historian to allocation pipeline
Petrinex-ready monthly volumetric reporting
Custom royalty and partnership splits
Variance dashboards for production engineers
Audit-grade lineage and version history

Live dashboards and regulator-ready reports for methane, flaring, venting, and Scope 1 emissions. Connects directly to your flow meters, flare monitors, and pneumatic device inventories.

Federal methane regulation reporting workflows
AER Directive 060 flare and vent tracking
GHGRP submission packages
Pneumatic device retrofit inventory and tracking
Public-facing ESG disclosure dashboards

Real-time monitoring of pipeline pressure, flow, and integrity events with alerting that respects on-call rotations and escalation policies. Built to feed regulator-required incident reports.

Pressure and flow anomaly detection
Leak detection signal integration
Cathodic protection survey workflows
Right-of-way inspection mobile apps
CER and provincial incident reporting templates

Field to Office

Watch a Field Ticket Turn Into Revenue

A live mock of the digital field ticket we build for oilfield crews. Build it the way a field operator would - pick the service, add crew and equipment, log consumables - and watch the billable total climb and the ticket hit the back office the instant you submit. On paper, that invoice is eleven days away.

Auto-playing: switch lease, then build a field ticket and watch the billable total climb. Switch to try it yourself.

Tamarack Energy
Kaybob battery · Today
Submit a ticket on the left — it lands in accounting in under an hour and starts the billing clock. On paper, the invoice is 11 days away.

Tamarack Energy

AFE-24-1187 · OpenInvoice · Back office

Synced just now

Tickets today

2synced

Billable today

$11,180

Avg days-to-invoice

18day DSO

Disputed line items

0flagged

Live activity

  • Ticket #4011 synced — $7,360 billable · Wireline

    just now · billing clock started

  • Ticket #4009 synced — $3,820 billable · Hot oiling

    earlier today

Live demo of the kind of field-to-office billing workflow we build for oilfield services. The leases, wells, crews, and dollar figures are illustrative - the real thing works offline at the wellsite, syncs to your accounting and AFE systems the moment the truck hits coverage, and starts the billing clock the instant a ticket is approved.

The Regulatory Map

The rules we design around

Compliance is architectural for us, not a checkbox added at the end.

Directive 017

AER Directive 017

Alberta Energy Regulator measurement, accounting, and reporting requirements for upstream petroleum operations. Governs how production volumes get measured, reconciled, and submitted.

Applies to: Upstream operators in Alberta

Directive 060

AER Directive 060

Upstream petroleum industry flaring, incinerating, and venting requirements. Sets reporting thresholds and approval workflows for emissions sources.

Applies to: Alberta operators with flaring or venting sources

BCER

BC Energy Regulator (BCER)

Permits, drilling and completion data submissions, and emissions reporting for British Columbia operations. Distinct workflows from Alberta - a shared system has to handle both.

Applies to: Operators with assets in northeast BC

Petrinex

Petrinex

Joint petroleum industry reporting platform for AB, BC, and SK. Monthly volumetric, royalty, and allocation submissions flow through Petrinex - your internal systems have to produce compliant files.

Applies to: Operators in Alberta, BC, and Saskatchewan

Methane Regs

Federal Methane Regulations

ECCC's regulations on methane emissions from the upstream oil and gas sector. Tightened in 2025 with a 75% reduction target by 2030 - reporting cadence and verification requirements increased accordingly.

Applies to: All Canadian upstream operators

CER

CER / Provincial Pipeline Reporting

Canada Energy Regulator and provincial bodies require timely incident reporting, integrity management plans, and emergency response data. Mobile-friendly capture has become table stakes.

Applies to: Federally and provincially regulated pipeline operators

Proof Points

Patterns we have shipped

The scenario

Mid-size SAGD operator running paper field tickets across 18 crews

Custom digital ticketing app replaced paper - cut DSO from 47 to 18 days and surfaced $340K of previously-unbilled consumables in the first year.

62% faster billing cycle

The scenario

Oilfield services company managing pumping operations across Alberta and BC

Built a dispatch and crew management system tied to electronic field tickets - eliminated double-entry between dispatch and accounting and gave supervisors a single screen for crew status.

Single source of truth across 4 districts

The scenario

Public upstream company struggling with quarterly ESG disclosure

Built an emissions data pipeline connecting flow meter telemetry to a public-facing ESG dashboard - reduced quarterly reporting effort from 9 person-weeks to 2 person-days.

92% reduction in reporting effort

Tools Chosen for the Job

Why we use what we use

React Native + Expo

Cross-platform field apps that ship to ruggedized Android tablets and iPhones from one codebase. Over-the-air updates push critical fixes without waiting for the App Store.

PostgreSQL + TimescaleDB

Time-series extension for high-volume telemetry from meters, gauges, and SCADA. Survives years of historian data without query slowdown.

AWS Canada Central

Data residency stays Canadian. Lambda, S3, and RDS in Calgary or Montreal regions means PIPA-aligned hosting with no US data exposure.

OPC UA + MQTT bridges

Industrial protocol adapters that pull data from DCS, historians, and edge gateways into your application layer. Battle-tested at production volumes.

Petrinex API integrations

Submission file generation and validation for monthly volumetrics, royalty, and allocation reporting. No more manual CSV uploads.

Next.js + TypeScript

Server-rendered dashboards for supervisors and executives that load fast even on slow camp internet. Type-safe end to end.

FAQ

Questions buyers ask first

Common questions about oil & gas software development in Canada

Ready to talk oil & gas software?

Book a 30-minute scoping call. We will walk through your operation, talk through what's worked for similar Canadian oil & gas operations, and tell you honestly whether we are the right team.