03 / SYSTEMS ARCHITECTURE / POWER PLATFORM / GOVERNANCE

In production · handed off

The system that runs without its builder.

The keystone build: identified at the company's annual strategic planning meeting, proposed voluntarily, built solo in four months, governed properly, and handed off to IT and operations, where it kept running after Sarah left.

May–Aug2025, a solo build with Senior VP approvals as the work progressed
~20submissions by departure, against an annual sales volume of 30–40 boats
3governed environments: build, test, and managed production
0dependence on her personal account after hand-off

THE BUSINESS PROBLEM

What needed
to change.

Nimbus USA had to track two milestones in the life of every boat: dealer acceptance, and the retail delivery that starts the consumer warranty. The process ran on email, paper forms, and shared folders. There was no reliable way to tie documentation to a hull, prevent duplicate submissions, notify the right teams, or see dealer inventory and retail velocity. Leadership could not evaluate the warranty service the end customer was receiving.

At the annual strategic planning meeting in Orlando, an invitation earned through the reporting and receivables work, Sarah identified the warranty documentation gap and volunteered to own the fix. She designed and built the system solo from May to August 2025, with approvals from the Senior VP as the work progressed.

HOW THE WORK HAPPENED

Judgment made visible.

01 / THE BUILD

One connected architecture, not a form.

A Power Pages portal embedded in the dealer website, backed by a Dataverse data model and Power Automate workflows: searchable dealer, model, and hull selection; document upload; AI-assisted document processing with Azure Document Intelligence; automatic routing to warranty and marketing; SharePoint retention with searchable metadata; and Power BI reporting on dealer inventory and retail-sales velocity.

02 / GOVERNANCE

Built to survive its builder's departure.

Separate build, test, and production environments; changes packaged, versioned, and promoted as a managed solution; service accounts so nothing depended on her login; documentation; user testing with sales and warranty; dealer training delivered by the warranty team; and a formal hand-off to IT and operations before she left the company.

03 / DEPLOYMENT

Real coverage, honestly counted.

Deployed across the Nimbus USA dealer network of about a dozen dealers. Roughly 20 submissions were processed by her departure, meaningful coverage against an annual sales volume of 30–40 boats. Every one of them previously lived in email and shared folders.

04 / THE UPSTREAM FIX

The bug that was actually a process.

An early submission failure traced back to hull numbers not being entered into the system before dealer delivery. Sarah corrected the upstream process rather than patching the portal, recognizing the difference between a technical symptom and an operational cause.

CAPABILITIES IN EVIDENCE

What this work demonstrates.

Power PagesDataversePower AutomateSharePointPower BIAzure Document IntelligenceALM + governanceService designDocumentation + trainingFormal hand-off

Evidence note. Deployed production work for Nimbus USA, built May–August 2025 and handed off before Sarah's departure in March 2026. Submission counts are stated against annual sales volume so the scale reads honestly. Screenshots were not retained; a clearly-labeled reconstruction is planned.

NEXT PROJECTDealer Network Intelligence