Built for the Field, Backed by Calgary
Custom field ticketing, dispatch tools, client portals and reporting workflows for energy businesses. Start with the handoff that costs your team the most time, then build around the people and systems already doing the work.
The Canadian Reality
Connect Your Field Team, Back Office and Customers
Software should fit the way your operation works, from the first field ticket to the approved invoice.
Paper tickets, separate spreadsheets and repeated data entry can make it difficult to see which work is ready to invoice. A custom workflow can bring crew hours, equipment, consumables and approvals into one place.
We build custom software, portals and mobile apps. For an energy project, discovery starts with your users, existing systems, connectivity constraints and approval process. Together we identify a focused first release and the integrations it needs.
The interactive field-ticket demo below is an illustration of that approach. Its companies, people and figures are fictional. It shows a possible workflow so your team can discuss what would need to change for your operation.
Custom software projects start at CA$15,000. Field deployments, complex integrations and multi-team platforms require a larger scoped budget. We establish requirements and an estimate before committing to delivery.
What's Broken Today
The patterns we keep seeing
Field data trapped in paper
When tickets and approvals live on paper or in separate spreadsheets, the back office can struggle to reconcile what happened on site with what is ready to invoice.
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.
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.
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. Device, connectivity and site requirements are assessed during discovery; hardware suitability and site safety requirements remain part of the deployment plan.
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.
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.
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.
Interactive Concept Demo
Explore a Field-to-Office Workflow
Try an illustrative ticketing flow: select a service, add crew and equipment, then review the ticket. This is a concept demonstration, not a live client system or a claim about achieved savings.
Auto-playing: switch lease, then build a field ticket and watch the billable total climb. Switch to try it yourself.
Tamarack Energy
AFE-24-1187 · OpenInvoice · Back office
Tickets today
Billable today
Avg days-to-invoice
Disputed line items
Live activity
Ticket #4011 synced — $7,360 billable · Wireline
just now · billing clock started
Ticket #4009 synced — $3,820 billable · Hot oiling
earlier today
Interactive concept demo of a field-to-office billing workflow. The leases, wells, crews and dollar figures are fictional. Offline behaviour, accounting and AFE integrations, approvals and sync timing would be designed and validated for your project.
The Regulatory Map
The rules we design around
Compliance is architectural for us, not a checkbox added at the end.
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
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
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
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
Federal Methane Regulations
Methane reporting and recordkeeping requirements should be confirmed with your compliance team against the current rules before implementation.
Applies to: All Canadian upstream operators
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
Illustrative Use Cases
What we could build for your team
These examples describe possible solutions, not completed client projects or measured results. Scope, integrations and expected benefits are established during discovery.
The scenario
A field services business collecting paper tickets
An illustrative mobile workflow could capture labour, equipment and consumables, route tickets for approval and prepare accepted records for accounting.
The scenario
A dispatcher coordinating crews across multiple sites
A shared dispatch board could bring assignments, availability and job status together, with a portal for customers to review the work that concerns them.
The scenario
An operations team assembling reports from disconnected systems
An integration layer could collect approved source data into a reporting workspace with validation, access controls and an audit trail. Required formats and interfaces would be confirmed during discovery.
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 Canadian Regions
Canadian cloud hosting can be scoped to your data and operational requirements. The region, backups and third-party services are reviewed as part of the architecture.
OPC UA + MQTT bridges
Potential adapters between industrial data sources and the application layer, subject to interface access, vendor documentation and validation.
Reporting File Workflows
Generation and validation of reporting files against agreed specifications. Submission methods and vendor interfaces must be confirmed during discovery.
Next.js + TypeScript
Server-rendered dashboards for supervisors and executives that load fast even on slow camp internet. Type-safe end to end.
The Underlying Services
Services we draw on for this work
Mobile App Development
Cross-platform iOS and Android apps built with React Native — one codebase, native performance, faster launch
Explore serviceDatabase & API Solutions
Scalable databases and secure APIs that connect your systems — built for reliability and growth
Explore serviceCloud Integration & DevOps
AWS and Azure cloud infrastructure with CI/CD automation — reliable scaling without surprise bills
Explore serviceFAQ
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.