Tools they already owned. Results they didn't expect.
Every engagement below ran on Microsoft 365 licenses the client was already paying for. No platform migrations, no six-figure software bills — just SharePoint, Power Apps, Power Automate, Power BI and Teams pointed at the paperwork, the silos and the Friday-afternoon reports. Here's what happened.
Every engagement, by service
Filter by the service you're weighing up — or read straight through and notice how often the fix was structure, not software.
Consulting engagements that paid for themselves
Four storage silos became one intranet.
Problem: Files scattered across a file server, personal OneDrives, email and an abandoned SharePoint 2013 site. New joiners spent their first week just learning where things were.
We did: Two-week audit, new hub architecture organized by team and client, metadata-driven search, and a one-page governance pack.
Compliance audit passed without the fire drill.
Problem: Patient-adjacent documents shared through anonymous links; an upcoming compliance review had leadership expecting the worst.
We did: Permission and sharing audit, killed 200+ open links, rebuilt access on Microsoft 365 groups, applied retention labels and wrote the governance policies the auditors asked to see.
Project documents found in seconds, not email threads.
Problem: Every project ran its own folder convention. Finding the current drawing set meant asking in three group chats and hoping.
We did: Standard project-site template with content types for drawings, RFIs and submittals, search refiners by project and discipline, and auto-provisioning of new project sites.
Intranets launched, files moved, nothing lost
1.2 million files off a dying file server in four weeks.
Problem: A 12-year-old on-prem file server was out of space and out of warranty, with 1.2M files, 15 years of duplicates and permissions nobody could explain.
We did: Full inventory and mapping, archived 40% as dead content, migrated the rest with ShareGate into a new library architecture, remapped permissions to groups and cut over on a weekend with a final delta sync.
A branded intranet that passed the records audit.
Problem: The firm's "intranet" was a bare SharePoint 2013 team site nobody opened, while client files lived in folders with no versioning — a problem their records compliance review flagged.
We did: Designed a branded communication-site intranet with matter-based navigation, rebuilt document libraries with content types and versioning, and applied retention labels that satisfied the records requirements.
Google Workspace to Microsoft 365 without losing a grant file.
Problem: The organization got Microsoft 365 through nonprofit licensing but everything — grants, board docs, program files — lived in Google Drive with tangled sharing and no structure.
We did: Mapped every shared drive to a SharePoint destination, migrated with ownership and sharing remapped to Microsoft 365 groups, built a simple branded intranet home, and trained staff in two live sessions.
Apps that killed the paperwork
Leave requests: from lost paper forms to a 4-hour turnaround.
Problem: Paper leave forms passed desk to desk — regularly lost, approvals took 3–5 days, and HR retyped everything into a spreadsheet nobody trusted.
We did: Canvas app on SharePoint lists with manager approval flows, live balance display and Teams notifications. Built and launched in three weeks, zero extra licensing.
Site inspections done on a tablet — even with no signal.
Problem: Safety inspections on clipboards, photos on personal phones, reports typed up two days later back at the office — sometimes never.
We did: Offline-capable canvas app with photo capture, GPS-stamped checklists and digital signatures; records sync when the tablet finds a connection, and failed items open follow-up tasks automatically.
One shared Excel file became a barcode-scanning inventory app.
Problem: Stock tracked in a shared Excel workbook that locked when two people opened it; counts were retyped from paper and the numbers were days stale.
We did: Canvas app with barcode scanning against a SharePoint-backed item list, live stock levels on every handheld, and low-stock alerts to the purchasing team via Teams.
Flows that gave whole days back
Three flows killed eight hours of weekly paperwork.
Problem: Supervisors spent every Friday compiling production numbers into a report, chasing safety-checklist signatures and re-typing purchase requests into email threads.
We did: A scheduled flow that compiles the production report from SharePoint lists and emails it Friday 7 a.m., a checklist flow with automatic sign-off reminders, and a purchase-request approval routed through Teams.
Supplier invoices approve themselves — humans just review.
Problem: 400+ supplier invoices a month arrived as PDF attachments, were printed, hand-keyed, and walked to a partner's desk for sign-off. Two errors a week reached the ledger.
We did: AI Builder extraction pulls vendor, amount and line items from each PDF, a flow matches them to purchase orders, and approvals route by amount — one tap in Teams for the partner, automatic filing to SharePoint.
The 6 a.m. dispatch report writes itself now.
Problem: A coordinator started at 5:30 a.m. to pull shipment data from the ERP, reconcile it against SharePoint trackers, and email the daily dispatch report before drivers rolled out.
We did: A scheduled flow syncs ERP shipment data to SharePoint overnight, flags mismatches for review, and sends the formatted dispatch report to depot managers at 6 a.m. — with an SLA escalation flow for late loads.
Integrations that gave the hours back
Teams and SharePoint stopped fighting over the same files.
Problem: Every client engagement had a Team and a SharePoint site — with different copies of the same deliverables in each. Nobody knew which version went to the client, and two proposals went out with outdated pricing.
We did: Rebuilt the site behind each Team as the single store, mapped channel folders to engagement phases, surfaced SharePoint libraries as Teams tabs, and archived 90 dead Teams.
Email attachments became SharePoint links — automatically.
Problem: Reps emailed quotes and spec sheets as attachments. Every send created another copy, customers received stale pricing, and the "current" version lived in whoever's inbox was newest.
We did: Auto-filing flow that lands inbound attachments in the right customer library, one source folder per account, and Outlook habits retrained to share links instead of files — with version history doing the rest.
Approvals moved out of email chains and into Teams.
Problem: Purchase and document approvals ran on forwarded email threads. Requests sat for days, approvals got lost on vacation handovers, and nobody could say where anything stood.
We did: Approvals rebuilt as Teams-native flows: request from a form, document stored in SharePoint, approve or reject from the Teams activity feed, full audit trail logged automatically.
Dashboards that retired the spreadsheet
Twelve weekly Excel reports became one sales dashboard.
Problem: A sales coordinator spent every Monday assembling twelve regional Excel reports from ERP exports. By the time they landed, the week's decisions were already made on gut feel.
We did: Star-schema model over nightly ERP exports and SharePoint price lists, one sales dashboard with drill-down by region, rep and SKU, and scheduled Monday-morning subscriptions to every manager.
Production and quality on one screen, from machine data and SharePoint.
Problem: Machine output logs lived in SQL, quality checks in SharePoint lists, downtime notes in a notebook. Monthly production reviews argued about whose numbers were right instead of what to fix.
We did: Combined SQL machine data and SharePoint quality lists into one certified model, built a production dashboard with OEE, scrap-rate and downtime drill-through, and added threshold alerts for quality drift.
Project profitability, visible per partner — and only per partner.
Problem: Partners couldn't see which projects made money until the quarterly close, and the finance team refused to circulate the full margin workbook because every partner would see everyone else's numbers.
We did: Profitability model joining timesheets, billing and project budgets, a dashboard with margin by project, client and partner, and row-level security so each partner sees only their own portfolio while managing partners see it all.
Teams work that paid for itself
From 280 orphaned teams to a tenant that cleans itself.
Problem: Three years of unrestricted creation left 280+ teams — duplicates, no owners, guests with standing access and five naming conventions. Nobody could tell which team was the real one for a client.
We did: Full sprawl audit, archived the dead weight, introduced client and project templates with naming standards, assigned owners, and set expiration policies so inactive teams archive themselves.
Job dispatch by adaptive card, not phone tag.
Problem: Dispatchers assigned jobs by calling technicians, who confirmed by text and reported completion by photo-in-a-WhatsApp-group. Jobs fell through the cracks daily.
We did: Adaptive cards in Teams that dispatch each job with one-tap Accept, site details and a completion form — wired to their job system through the Graph API, with escalation if a card sits unaccepted.
An HR bot that answers before HR opens email.
Problem: The four-person HR team drowned in the same questions — leave balances, payslip dates, policy lookups — averaging 60 repetitive emails a day with two-day response times.
We did: An HR helpdesk bot in Teams answering policy and leave questions instantly from the HR knowledge base, with clean escalation of the genuinely human cases to the HR channel.
Retainers that became the safety net
Their only SharePoint-savvy employee quit. Nothing broke.
Problem: One office manager had built every site, flow and permission over four years — then resigned with two weeks' notice. Nobody else knew how any of it worked.
We did: Onboarded on a Starter retainer during her notice period, documented all 60+ sites and flows, took over user and permission management, and became the number the partners call.
30 broken flows nobody owned — now documented and monitored.
Problem: Years of ad-hoc Power Automate flows built by departed staff and old vendors. Approvals failed silently; nobody knew which flows still mattered, or whose license they ran on.
We did: Full flow inventory on a Growth retainer, retired 40% as dead, moved the rest to service accounts, fixed the 30 that were failing, and put every survivor on weekly run-history review.
Adoption died after launch. A champion program revived it.
Problem: A beautiful intranet launched to fanfare, then usage collapsed within a quarter. Staff drifted back to email attachments and desktop folders; leadership was ready to write off the investment.
We did: Role-based retraining built on their real content, a champion in each of six departments, cheat sheets on the intranet home page, and quarterly adoption reports from actual usage data.
Your team could be the next case study.
Book a free 30-minute call. We'll look at your SharePoint and Microsoft 365 setup and tell you exactly where the hours are leaking — no obligation.