ghost

ghost

Payment flexibility for hundreds of merchants

Payment flexibility for hundreds of merchants

Ghost’s B2B payment functionality was narrow with low adoption. Significant manual involvement was required to support multi-millions in weekly order values.

MY ROLE

  • End-to-end research and design

  • Aligned leadership across 3 organizations

  • Designed flexibility and operational control


IMPACT

  • 24% adoption to 96%

  • 1,000 monthly hours saved (=6 FTE)

  • Zero failures across $47M in transactions

  • Streamlined infrastructure and workflow

  • Shortened deal lifecycle

MY ROLE

  • End-to-end research and design

  • Aligned leadership across 3 organizations

  • Designed flexibility and operational control

IMPACT

  • 24% adoption to 96%

  • 1,000 monthly hours saved (=6 FTE)

  • Zero failures across $47M in transactions

  • Streamlined infrastructure and workflow

  • Shortened deal lifecycle

MY ROLE

  • End-to-end research and design

  • Aligned leadership across 3 organizations

  • Designed flexibility and operational control


IMPACT

  • 24% adoption to 96%

  • 1,000 monthly hours saved (=6 FTE)

  • Zero failures across $47M in transactions

  • Streamlined infrastructure and workflow

  • Shortened deal lifecycle

IMPACT

  • 24% adoption to 96%

  • 1,000 monthly hours saved (=6 FTE)

  • Zero failures across $47M in transactions

  • Streamlined infrastructure and workflow

  • Shortened deal lifecycle

BUSINESS CHALLENGE

BUSINESS CHALLENGE

BUSINESS CHALLENGE

Our rigid system couldn't effectively serve all clients (single-person shops to Fortune 500 companies) threatening retention and competitive advantage.

Finance manually reconciled 76% of payments across three systems, and 40% of orders were delayed awaiting payment.

PROBLEM BREAKDOWN

PROBLEM BREAKDOWN

PROBLEM BREAKDOWN

Auditing 150 deals revealed operational chaos: Numerous use cases, API rate limits, 40+ handoffs per deal. 78% of deals required fully custom terms, and our stakeholders had competing needs.

APPROACH

APPROACH

APPROACH

I embedded with Operations and Finance, mapping out their intensive workflows. My PM, eng leads, and I targeted payment opportunities across dual tracks:

  • Product: Event-based triggers, installment flexibility (10+), multiple payment methods

  • Operations: Deal acceptance payment terms, templatized term options, Finance approval gates

IMPACT

IMPACT

IMPACT

Within 3 weeks of launch we saw:

  • A 57% reduction in operational toil (35hrs → 15hrs/deal)

  • Zero failures across $47M in payments

  • Usage rise to 96%, and event-based triggers influenced milestone tracking

Within 3 weeks of launch we saw:

  • A 57% reduction in operational toil (35hrs → 15hrs/deal)

  • Zero failures across $47M in payments

  • Usage rise to 96%, and event-based triggers influenced milestone tracking

Within 3 weeks of launch we saw:

  • A 57% reduction in operational toil (35hrs → 15hrs/deal)

  • Zero failures across $47M in payments

  • Usage rise to 96%, and event-based triggers influenced milestone tracking

LOOKING BACK

  • Engineering partnership was critical for navigating constraints

  • Influencing operational efficiency can be just as impactful as UI refinement

LOOKING BACK

LOOKING BACK

  • Engineering partnership was critical for navigating constraints

  •  Influencing operational efficiency can be just as impactful as UI refinement

LOOKING BACK

LOOKING BACK

  • Engineering partnership was critical for navigating constraints

  •  Influencing operational efficiency can be just as impactful as UI refinement