Procurify - 2023
Eliminating errors with reliable data sync
Making managing data consistency sustainable across Procurify and ERP systems.
Project duration​
3 months
Team​
Product designer (me), Product manager, Engineering manager, Software developers (4)
Context
As Procurify expanded into mid-market customers, ERP integration became a critical requirement for retention and growth. Larger finance teams expected Procurify to “just work” with their accounting systems, but our integrations were still fragmented and limited in scope.
We needed to identify the first essential slice of ERP workflow to support — one that would reduce errors, save customers time, and build a sustainable foundation for scaling ERP integrations further.
My role
Product designer
-
Partnered with PM, Engineering, and Customer Success to identify workflow gaps, validate with customers, and define the ERP-as-source-of-truth model.
-
Designed the integration UI, error handling, and activity log
-
Facilitated decision-making with stakeholders through discovery workshops and design artifacts.
Problem
-
Manual, error-prone process: Customers had to manually add hundreds of essential records (like vendors and account codes) into Procurify.
-
Mismatch with ERP: Different data in each system caused failed bill syncs, duplicate records, and confusion.
-
Support burden: The majority of integration-related tickets stemmed from data mismatches between Procurify and ERP.
-
Scaling risk: Without solving this, mid-market customers couldn’t trust Procurify to scale with their ERP workflows.
Solution
We introduced automated syncs for key financial records - Vendor and Account codes as the first step in scaling Procurify’s ERP integration strategy. This diagram showcase the collaborated effort between me, the Product manager and Engineering manager on how we slice up the work and mapping user stories in the workflow.
ERP as the source of truth
Procurify automatically imports essential records on an hourly schedule.
Impact
-
Reduced support tickets by addressing the #1 cause of bill sync errors: mismatched vendors/accounts.
-
Saved customers hours of manual work maintaining data across two systems.
-
Increased trust by making the ERP the clear source of truth while keeping Procurify automatically up-to-date
Reflection
What I learned - principle
-
Tackling systemic problems like data consistency creates more sustainable impact than patching surface-level sync errors.
-
Clear guardrails and constraints (like blocking conflicting integrations) are just as important as adding new features to ensure a reliable user experience.
What I'd do differently
-
Push for earlier validation of automation vs. manual controls with customer — Removing the “sync now” button simplifies the UX, but requires extra explanation for teams used to manual control.
-
Involve Customer Support earlier in the design phase to co-create error handling. This would have been reduced back and forth during rollout.
-
Establish a clearer migration path from legacy bundles sooner, rather than treating it as a post-launch improvement, to make it easier for customers to adopt without friction.