From how work runs today to how it should run tomorrow

Process mapping, organizational change, and Epicor delivery—so technology follows the business, not the other way around.

I am more than a technical configurator. My strongest work starts before anyone opens Kinetic: understanding how people actually process invoices, claims, orders, and exceptions today—where handoffs break, who owns decisions, and what “good” looks like for finance and operations.

I map current-state processes with the people who live them, then design a future state that is realistic to adopt. That includes role clarity, control points, and change readiness—not only screens, BAQs, and Functions. Only then do we implement in Epicor Kinetic, ECM/DocStar, integrations, and intelligent automation so the system supports the new way of working.

That combination is intentional: deep Epicor and ECM implementation skill and the ability to lead organizations through process redesign. Technology without process design creates expensive friction. Process design without solid delivery never sticks. I do both.

Core strength

Organizational change & adoption

New processes fail when people are left out. I plan training, communication, and cutover so teams can actually run the new model.

  • Stakeholder alignment across departments
  • Practical enablement for end users and power users
  • Go-live support that respects day-to-day load

Delivery

Epicor & ECM implementation

Kinetic Financials, ECM/DocStar, AP automation, DataLinks, Functions, and integrations—built to match the process we designed together.

  • Financial and document workflows that fit operations
  • Automation that reduces re-entry without losing control
  • Patterns ready for intelligent and agentic layers when appropriate

Map → design → deliver → adopt

Whether the project is AP automation, ECM-driven Kinetic work, or a broader finance process redesign, the sequence stays grounded in the business.

1. Understand today

Map current processes, systems, pain points, and informal workarounds. Hear from the people who run the process every day.

2. Design tomorrow

Define the future-state process, controls, and ownership. Align on what changes for roles, timing, and exception handling.

3. Build in Epicor

Configure and develop Kinetic, ECM, Functions, and integrations so the system encodes the agreed process—not a generic template.

4. Lead the change

Train, support cutover, and stabilize. Success is measured by adoption and process outcomes, not only by go-live day.

Where process design meets delivery

These examples show the technical outcomes. Behind each is process discovery, future-state design, and change with the client team. Full write-ups are in Case Studies.

Featured

Also in the portfolio

Across these engagements the technical tools differ—ECM, IDC, Functions, DMT, labeling—but the approach does not: map the real process, design the future state with the business, implement with control, and help the organization adopt the change.

If you need someone who can sit with finance and operations and deliver in Epicor—not only write technical solutions—I would be glad to talk.

Contact me All case studies Services