About

I build the operating middle that strategy slides skip

Based in Michigan. Organizations bring me in when platforms, reporting, and adoption have to move together—and the blast radius has to stay contained. The work is systems architecture with change enablement baked in, not bolted on. I also speak with professional audiences on AI ethics, controls, and agentic risk.

  • I stay through cutover, not just the architecture deck
  • I put the new system in the tools people already open
  • I measure the week after go-live, not the launch party
How I work

Judgment under operating pressure

The habits that keep migrations, automation, and decision systems alive after launch. Open Selected work for the cases behind them.

Selected work
  1. Contain the blast radius

    Cutover plans, identity, and rollback so the business keeps running while the stack changes.

    • Governed cutovers with a named rollback
    • Identity and endpoints treated as part of the migration
    • Playbooks ship with the platform, not after it
  2. Adoption is the deliverable

    A live system nobody runs is a failed project. I design for the week after go-live.

    • Scorecards that replace slide decks as the source of truth
    • Workflows inside the tools people already open
    • Support load measured after the first 60 days
  3. Decisions, not dashboards

    Models and coaching loops built for the questions executives actually ask.

    • Forecasts and exceptions on one cadence
    • Audit-ready numbers with a named owner
    • AI that sits in the workflow, not a side chat
Track record

Where the judgment was forged

A condensed path through the environments that shaped how I run migrations, automation, and analytics programs.

  • 2019

    Finance systems integration

    • Sage Intacct and ADP across departmental handoffs
    • Custom APIs replacing spreadsheet reconciliation
    • Month-end close as an operating rhythm, not a fire drill
  • 2020

    Cloud platforms and endpoints

    • Identity, mail, and device management as one cutover
    • Legacy finance and HR stacks retired behind the new platforms
    • Disaster recovery written into the operating model
  • 2023

    Analytics inside the operating cadence

    • Forecasting and exception reporting for leadership decisions
    • Revenue-cycle playbooks the team could run without me
    • SQL reporting that made unbilled work visible in time to act
  • 2024

    AI in the daily workflow

    • Clinical-note review before submission, not after the audit
    • Coaching loops that improved documentation quality in place
    • Appeals and process work inside the tools already open
Background

Finance training, systems craft

Formal grounding in finance, paired with the toolkit I use to ship durable operational change.

Education

Bachelor of Arts in Finance

Calvin College

Finance with complementary study in Mandarin Chinese and development economics—modeling, international business, and structured decision-making under constraint.

Working toolkit

Practical capabilities oriented around reliable execution and measurable operational change.

  • Systems Architecture
  • Process Automation
  • Cloud: Azure / M365
  • Data Analytics (Power BI)
  • APIs & Integrations
  • AI-Assisted Workflows
  • Financial Operations
  • Security & Compliance
Next step

If the bottleneck looks familiar, let's map it

Migration, automation, reporting, or AI-enabled workflow—start with the constraint costing you the most.