Selected work

The system behind the outcome.

How I diagnose friction, create structure, weigh tradeoffs, and help teams adopt a more reliable way of working.

Implementation & customer operations

From manual intake to near-instant onboarding

A growing service operation depended on slow, manual handoffs across intake, scheduling, and customer communication.

Result

A connected website workflow reduced onboarding from roughly two days to 2–5 minutes while supporting a larger recurring-customer base.

Workflow designAutomationCustomer experience

See my thinking

Why this mattered

Growth was creating more administrative work at exactly the point when the operation needed speed and consistency.

How I approached it

I mapped every handoff, removed duplicate decisions, standardized intake, and connected customer communication to the operating workflow.

Tradeoff I considered

Standardization required more upfront design work, but it reduced downstream delay and preventable questions.

What I’d improve next

Add funnel analytics and exception reporting so the team can see where customers pause or require manual support.

Program management & analytics

Turning fragmented data into an execution rhythm

Performance information existed, but it did not consistently translate into prioritized interventions, team ownership, or stakeholder clarity.

Result

A repeatable tracking, planning, and coaching cadence helped move readiness-assessment outcomes from 13% to 92%.

AnalyticsOperating cadenceTeam enablement

See my thinking

Why this mattered

Data without an operating rhythm documents a problem; it does not change the result.

How I approached it

I connected measures to intervention planning, established review points, clarified ownership, and used coaching to support consistent follow-through.

Tradeoff I considered

The system needed enough structure to create accountability without becoming a reporting burden for the team.

What I’d improve next

Automate trend visualization and leading indicators so risks surface earlier and coaching can become more proactive.

Strategy & operations

Building a repeatable service operation

Revenue growth was not enough; the business needed repeatable delivery, stronger vendor economics, and clear controls for quality and customer communication.

Result

Annual revenue grew from $35K to $105K, while operating margin moved from deficit to approximately 60% profit.

OperationsSOPsResource optimization

See my thinking

Why this mattered

A service business can grow itself into instability when revenue, capacity, and delivery standards are not managed together.

How I approached it

I standardized scheduling and delivery, renegotiated vendors, shifted procurement strategy, reduced waste, and made customer expectations explicit.

Tradeoff I considered

Efficiency could not come at the expense of customer trust, so changes were evaluated against both margin and service consistency.

What I’d improve next

Build a capacity model and customer-health dashboard to forecast staffing, retention, and profitability by service segment.

Portfolio roadmap

What I'm building next.

These artifacts will turn current learning into visible evidence of AI-enabled operating judgment.

In development

AI Onboarding

An AI-supported onboarding system focused on clarity, adoption, and measurable time-to-value.

In development

Program Command Center

One source of truth for priorities, ownership, risks, decisions, and operating cadence.

Planned

Knowledge Management System

A practical system for turning scattered information into reusable organizational knowledge.