Independent AI and technology advisory, Calgary

Decide where AI belongs.Own what gets built.

DecarbDesk helps you identify where AI is worth using, builds the workflow in systems you control, and hands it over with the controls, records, and training your team needs to run it.

Assess a workflow How it works

What you keep building

A compounding operating asset.

Models, software, and providers change. The knowledge your organization retains, the decisions it can explain, and the work it can run inside written limits remain under your control. Together, these form an operating asset designed to become more useful when reviewed examples, recorded exceptions, evidence, and operating history are kept current and reused. Memory, Intelligence, and Operations show how that asset retains knowledge, supports decisions, and runs work under defined controls.

Memory

Keep decisions, exceptions, precedents, and lessons in your systems.

When someone leaves, the knowledge stays. When a question returns, so does the record behind the answer.

Decision memory · Meeting memory · Evidence library · Regulatory memory · Operational history

See what memory is made of →

Intelligence

Reason over your data, documents, and precedents.

Research and analysis draw on your operational history, with the sources and working shown.

Deep research · Due diligence · Financial analysis · Commercial analysis · Regulatory analysis · Engineering analysis

See how the answers are tested →

Operations

The work runs, and you stay in control.

Invoices are coded, reports assembled, filings prepared, and systems updated. Routine actions run inside written limits. Sensitive or uncertain cases wait for a person.

Human approval · Autonomous execution · ERP actions · Document extraction · Scheduled reporting · Notifications

See the safeguards →

What we build

Seven example workflows across operations, finance, compliance, and data.

Each example begins where an ordinary process map stops: what the system may do, where a person decides, and what evidence remains. The patterns make that boundary concrete before an implementation is scoped to your systems, rules, thresholds, review points, and required outputs.

See all eight examples →

Operations workflow

Work Request Coordinator

Route inbound field and maintenance requests to the right owner with complete information.

System actions: Read submissions from the intake form and the operations inbox into a single record
Confirm asset identifier, location, requested work, and requester contact are present
Reply to the submitter for any required field left blank and hold the request until it arrives
Apply the written rules for discipline, area, and urgency
Assign to the responsible scheduler or supervisor for that area
Human decision: Requests above the agreed urgency or cost threshold wait for a supervisor before assignment
Recorded outputs: Write owner, status, and timestamps to the operations tracker your team runs

Current manual work: Manual inbox triage, retyping requests into a tracker, chasing missing details, and hand-assigning work.

Operations workflow

Operations Reporting Analyst

Assemble the recurring operations report from approved sources with the exceptions already flagged.

System actions: Read volumes, downtime records, and field entries from the systems of record
Compare each figure with the previous period and the recent average
Mark any figure outside the tolerance the operations team agreed
Record the source system, extract time, and record identifier behind every figure
Human decision: A production engineer confirms or corrects flagged deviations before the report is released
Recorded outputs: Post the reviewed summary to the operations channel and the reporting folder
Log sources, flags, reviewer, and decisions for the period

Current manual work: Rebuilding the same workbook from several exports, checking figures against last period by hand, and hunting for the source of a number during the meeting.

Finance workflow

Invoice Coding Clerk

Extract, validate, and code vendor invoices and field tickets for approval.

System actions: Identify whether the document is a vendor invoice, a field ticket, or a supporting attachment
Read vendor, document number, date, line items, proposed cost codes, and totals
Confirm the line items sum to the stated total and the tax is calculated as expected
Look for the matching purchase order, authorization for expenditure, or service entry
Compare the vendor and document number against records already processed
Human decision: A cost analyst confirms the extracted fields and the cost coding before anything is posted
Documents above the agreed threshold go to the budget owner for approval
Recorded outputs: Write the confirmed entry to the accounting system and archive the document with its processing log

Current manual work: Retyping invoice fields, checking arithmetic by hand, hunting for the matching purchase order, and finding duplicate payments at year end.

Finance workflow

Cost Reconciliation Clerk

Compare committed cost, accruals, and posted ledger entries and route the differences.

System actions: Read committed cost, accruals, and posted ledger entries for the period
Match by cost code, vendor, period, and reference, with a confidence score on each proposal
Sort unmatched items by value and by age
Attach the likely reason drawn from previously resolved items of the same shape
Human decision: A cost analyst accepts, corrects, or rejects every proposed match
Adjustments above the agreed threshold wait for the controller before posting
Recorded outputs: Produce the period reconciliation with matched, unmatched, and adjusted items separated
Store each resolution with its reason so the next period can reuse it

Current manual work: Pasting exports into a workbook, matching reference numbers by eye, and investigating the same timing difference every period.

Compliance workflow

Filing Coordinator

Assemble a recurring regulatory or emissions submission package with its review trail attached.

System actions: Pull the measurement, volume, and activity data the submission requires from the named sources
Compare collected inputs against the required field list and name what is missing
Run the calculation method your organization approved, recording the method version used
Show each result against the previous period and flag results outside the historical range
Human decision: The preparer confirms inputs, method version, and results
The person accountable for the submission approves the package before anything is submitted
Recorded outputs: Produce the completed package, the supporting workbook, and the source trace
Store inputs, method version, results, reviewers, and decisions together

Current manual work: Emailing each area for its numbers weeks out, maintaining the calculation in a single workbook one person understands, and searching mailboxes to reconstruct a past submission.

Compliance workflow

Vendor Review Coordinator

Assemble the review file for a third-party system, vendor, or model before it is approved for use.

System actions: Create the record with the requesting owner, the intended use, and the data involved
Issue the standard questions on data handling, hosting, access, subprocessors, and support
Record each answer against its question and chase the ones still open
Compare responses with your written requirements and mark every gap
Prepare a summary of findings, gaps, and residual risk with each point cited to an answer
Human decision: The named reviewer records a recommendation and the reasoning behind it
The accountable approver records approve, approve with conditions, or decline
Recorded outputs: Store questions, answers, gaps, recommendation, decision, and any conditions with their dates

Current manual work: Question lists that differ by reviewer, vendor answers left sitting in a mailbox, and renewal reviews that start from nothing.

Data and reporting workflow

Data Quality Owner

Check scheduled data loads against the official source and send failures to the responsible data owner.

System actions: Compare loaded rows against the source count for the same window
Confirm the newest record falls inside the expected window
Compare current columns and data types with the agreed fields and formats
Apply the checks for missing values, allowed ranges, and relationships that the data owner defined
Order failures by the reports and decisions that depend on the table
Human decision: The data owner decides whether a failed table is held back or released with a stated caveat
Recorded outputs: Write each check, its result, and the decision to the check history
Tell the owners of reports that use the data which tables are held and why

Current manual work: Discovering a broken table when someone questions a number in a report, and arguing about which source is unreliable with no record to settle it.

Connects to the systems already in use

Outlook

Teams

SharePoint

Excel

Slack

Salesforce

Gmail

Google Sheets

Google Drive

Snowflake

Databricks

PostgreSQL

Airflow

Grafana

Jira

Confluence

GitHub

+ more

A decision you can follow

Keep a clear path from the original file to the final decision.

How outputs are evaluated

01
Original file
The document or record the work begins with
02
Company rules
What is allowed, required, or sent for review
03
AI task
Read, organize, compare, or draft
04
Automatic checks
Check required fields, limits, and source support
05
Human checkpoint
A named person handles cases requiring risk or judgment
06
Decision saved
Keep the output, approval, and reason together

An independent practice, working in oil and gas, energy, finance, and technology.

Every engagement is scoped and quoted in writing before work starts. DecarbDesk provides the assessment, implementation, documentation, training, and advisory work described in that scope.

See the seven services →

Start hereWorkflow assessmentA focused review of one process: how the work happens today, which tasks are worth automating, what safeguards they need, and a written recommendation you keep either way.FREE TOOLAgent readiness toolStart with one outcome, answer questions about the work behind it, and see what an agent could safely do today, from preparing drafts to acting within written limits.What to expectHow an engagement runsDiscovery through handover, what your team reviews at each stage, and what sets the calendar.

Ownership

Your environment, your credentials, your asset.

Everything we build runs on infrastructure or provider accounts you control. We document the system, train the people responsible for it, and hand over administrative access. Your team operates it. We can remain available for advice.

Where data must stay inside your network, the workflow can be designed to run there.

The process map, rules, operating record, and evidence stay with you and remain yours if you change providers. Kept current and reused, they can provide context for future, related workflows.

See what you keep after handover →See what it is built with →See how we control the risk →

Start with the problem you need solved.

It may be a workflow, a technology decision, a data problem, or an operating question. Send a short description of what is happening, what should happen instead, and what is getting in the way.

Email the desk Choose a call time