Edmonton is our headquarters. The senior consultants on our calls have spent careers inside Northern Alberta’s energy, manufacturing, and professional services companies — and that’s the work we ship from this office.
Most clients within an hour of downtown started the same way: a Microsoft 365 tenant they pay for every month, a handful of SharePoint sites that grew faster than anyone planned, a Power Apps proof-of-concept stuck at 80%, and a real business process still running on email and Excel. That’s the gap we close.
What Northern Alberta clients ask us for
Oil & gas — replacing paper run tickets and brittle field tools
Drilling, completions, and oilfield services teams across Northern Alberta still run daily operations on paper forms and disconnected spreadsheets. Field tickets get re-keyed in the office days later. HSE incidents sit in a clipboard in someone’s truck until end-of-shift. Maintenance schedules live in a binder on a shop wall, and the only person who knows the rotation is on days off.
We’ve built the alternative — a Power Platform field operations system on Dataverse with offline-capable Canvas Apps for crews and Model-Driven Apps for the office. The flagship is Bonanza Drilling, an Alberta drilling contractor where we replaced 25+ paper forms with mobile data capture, cut data retrieval from ~30 minutes to instant, and tied HSE checklists into a single auditable platform.
If you’re scoping similar work, our walkthrough on Power Apps for field operations covers the architecture, the patterns that hold up at scale, and the 90-day delivery plan we use. The broader practice context lives on the Oil & Gas industry page.
Manufacturing & industrial — quality docs, SOPs, asset history
Edmonton’s industrial corridor — Fort Saskatchewan, Sherwood Park, the Refinery Row plants — runs on documented procedures and equipment lifecycle data. SharePoint is usually already in place; what’s missing is the structure that lets a maintenance technician find the right SOP on a tablet at 11pm without paging the day-shift supervisor.
We design the information architecture, migrate from legacy file shares, and tie SharePoint into asset management so equipment history follows the equipment, not someone’s inbox. The deeper-dive on the metadata model that holds up at scale is in our SharePoint DMS metadata post.
Professional services — payroll, client portals, document workflow
Engineering firms, accounting practices, and law offices in and around Edmonton are consolidating from a patchwork of point tools onto the Microsoft 365 tenant they already pay for. The wins are usually payroll and accounting workflows, client document portals on SharePoint, and Power Automate flows that retire the email-attachment-approval-chain pattern.
For the cleanup work that usually comes first, our Microsoft 365 migration guide covers the sequence we use to move teams off legacy file shares and shared mailboxes without breaking anything in flight.
Recent engagements
A snapshot of the kind of work we ship out of Edmonton:
- Bonanza Drilling — Alberta oilfield contractor. Dataverse + Canvas Apps for field tickets, HSE checklists, and payroll export. 25+ paper forms retired; data retrieval cut from ~30 minutes to instant. Full case study →
- Industrial services SharePoint migrations. Moving long-running on-prem farms to SharePoint Online, with information architecture rebuilt against actual roles instead of the legacy AD groups inherited from acquisitions.
- Energy services Power BI rollouts. Dashboards over Dataverse for utilization, downtime, and HSE trend reporting — retiring the weekly Excel report that no one fully trusts.
- Professional services workflow automation. Power Automate flows for client onboarding and document approvals; the typical pattern cuts new-engagement setup from days to hours.
Where we work
Our Edmonton team handles work throughout the metropolitan area and across Northern Alberta:
- Edmonton — downtown, west end, south side, Mill Woods
- St. Albert, Sherwood Park, Fort Saskatchewan
- Leduc, Beaumont, Spruce Grove, Stony Plain
- Drayton Valley, Whitecourt, Grande Prairie — remote + on-site as needed
Most engagements run hybrid: workshops and discovery on-site, build remote, demos and rollouts back on-site. For deeper SharePoint-specific work in this region, the dedicated SharePoint consulting in Edmonton page has more.
How we engage
First contact to written response: one business day. We don’t run a discovery deck — we ask about your pain points and a timeline. The response back is a candid read on what we’d do, what’s already there to leverage, and what would be wasted effort. From signed scope to first usable build is typically four to eight weeks, depending on the surface area.
If you’re earlier than that — still scoping the problem, still mapping who owns what — a 45-minute call with a senior consultant is the right next step. No pitch deck. No junior account manager.
Why pick a local team
You can engage Microsoft consulting from anywhere. The reason to pick someone in Edmonton: the people on the call already know what a field ticket looks like, what HSE reporting Alberta regulators actually require, what your IT team has been promising on the M365 roadmap, and what’s reasonable to ship in a quarter when half your users work out of a truck.