Real problems, solved — in the open.
No inflated dashboards here. These two engagements are our primary proof — concrete problems and the rebuilds that fixed them, told straight. Both ran on the Microsoft stack: Dynamics 365, Power Platform, and AI-assisted workflows.
Paper-Free, Audit-Proof Corporate Accounts Payable
A Swiss care provider processed every supplier invoice on paper. We moved the entire workflow — capture, approval, audit — onto SharePoint Online and the Power Platform.
The Challenge
Every supplier invoice arrived on paper. Each one was stamped, physically walked between department heads for sign-off, and filed away in binders afterward. Approvals stalled silently whenever a manager was on leave, nobody could say where a given invoice was without searching the building, and proving a complete approval history at audit time meant pulling folders by hand.
Our Approach
We built a fully digital accounts payable flow on SharePoint Online and Power Automate. AI Builder OCR captures invoice data on arrival, so nothing is retyped. Each invoice then moves through a three-stage approval chain with deputy routing — when an approver is unavailable, the invoice automatically continues to their deputy instead of waiting. Documents are archived to SharePoint with automatic 10-year retention applied at filing, and every action is timestamped.
The Outcome
Supplier invoices are now handled end to end without paper. Every invoice carries a complete, timestamped audit trail from capture through final approval. Retention is enforced by the system rather than by filing discipline, and no approval stalls silently — deputy routing keeps invoices moving even when approvers are away.
- Invoice arrives
Supplier invoices land as documents instead of paper that has to be stamped and carried.
- AI Builder OCR
Invoice data is captured on arrival, so nothing is retyped by a person.
- Approval — stage 1 of 3
The invoice routes to the first approver in the chain rather than to a physical in-tray.
Approver unavailable? It continues to their deputy instead of waiting. - Approval — stages 2 and 3
The same routing repeats through the remaining two stages of sign-off.
- SharePoint archive
Filed with 10-year retention applied automatically, carrying a complete approval history.
Automated Lead Intake & Routing
A manufacturer's inquiries arrived from two disconnected channels. We built an AI-scored pipeline that filters junk, routes genuine leads to the right owner, and keeps D365 in sync.
The Challenge
Sales inquiries arrived through two disconnected channels — a lead intake form on the website and a shared email inbox — with no consistent way to tell a genuine product or pricing inquiry from spam and noise. Every lead had to be read, judged, and manually forwarded to the right key account manager, which meant delays, inconsistent routing, and no clear record of who owned a lead or why.
Our Approach
We built an automated pipeline that pulls leads from both the website form and the email inbox into a single flow. An AI processing step scores and filters each lead, screening out junk and spam before anything reaches a person. Genuine leads are routed to the appropriate KAM based on the inquiry, who can accept or reject them directly. Accepted leads are automatically set with that person as the lead owner in D365; rejected leads route to Sales Ops, who either discard them or reassign them.
The Outcome
Every inbound lead — form or email — now reaches the right person automatically, with junk filtered out before it ever creates work. Ownership in D365 is set the moment a lead is accepted, giving sales a clean, auditable record of who owns what and why, while Sales Ops handles the exceptions instead of the entire inbound stream.
- Website form + shared inbox
Both channels feed one pipeline, instead of two queues nobody reconciles.
- AI scoring and filter
Each lead is scored and screened, so spam and noise never reach a human.
Junk is discarded here — it never becomes somebody's work. - Routed to a KAM
The lead reaches the key account manager the inquiry actually belongs to.
- Accept or reject
The KAM makes the one judgement call the machine should not make.
Rejected leads route to Sales Ops to discard or reassign. - Owner set in D365
Accepted leads are written to D365 with that person as the lead owner.
Hard Dynamics 365 problems, worked through in full.
Longer write-ups of specific technical problems in the Microsoft stack — the constraint, the approaches that fail, and the one that holds up in production. The first three are in progress.
- Plugin performance in DataverseWhy synchronous plugins quietly become the bottleneck at scale, and how to measure the real cost before splitting work out.In progress
- Dataverse integration patternsChoosing between dual-write, virtual tables, Azure Service Bus and plain API calls — and what each one costs you later.In progress
- Power Pages authenticationExternal identity, table permissions and web roles: the model most portals get wrong on the first attempt.In progress
Facing something that looks like this?
Both of these engagements began the same way — by working out what was actually wrong before proposing what to build.