Story behind the number

A reusable ERP connector foundation

35%

The work, in motionWorkflow illustration

Separate AP and AR connector journeys repeated common work and made the customer experience harder to manage.

Reduced motion · choose a chapter to explore

My contribution

I helped shape the shared journey across registration, connection setup, lifecycle management, sync visibility and error recovery. I translated customer and operational friction into requirements and aligned teams around reusable capabilities.

Results & context

The work contributed to a reported 35% improvement in overall integration-adoption efficiency, spanning delivery effort, support readiness, customer onboarding and the path to stable use.

Financial workflows: 2Accounts payable · Accounts receivable
Effort components: 4Delivery · Support readiness · Onboarding · Stable-use cycle

Indexed illustration · baseline = 100

The end-to-end process covers four effort components. On a normalized total-effort index, the reported 35% improvement is equivalent to moving from 100 to 65.

Baseline index: 100
Equivalent index: 65

(100 − 65) / 100 = 35%

The decision & trade-off

Centralize common connector capabilities while preserving AP- and AR-specific financial behavior. The trade-off balanced immediate product delivery with a more reusable, predictable integration foundation.

Platform reuse · ERP/API product management · Integration lifecycle · Cross-team alignment