The Long Version

Brought in to lead the Payments vertical — ~$6–7M ARR across three products at very different life stages. Digital Authorizations was the wedge and the cash generator. Payment Links was a newborn. Digital Contracts had been quietly left to die. On top of the portfolio sat 20+ PSP integrations and partnership relationships — Stripe, Adyen, Shift4, Elavon, Nexi, Global Blue, and a long tail — all needing an owner.

Three things shipped:

• Resurrected Digital Contracts as AI Contracts, built around the first-ever Payment Hub for Hotel Sales & Catering teams. Hotels sign digital contracts, the Hub auto-generates payment links, and non-room cash flows (events, catering, F&B) run through one surface instead of five. A product that had been written off became a live upsell story.
• Drove global PSP expansion into enterprise chains — Ant Financials integration plus a handful of others — unlocking cross-border processing for hotel brands that couldn’t previously be served on-platform.
• Modeled the $100M ARR business plan for Payments as part of the vSaaS model, and surfaced the platform investment it required. Founders chose to deploy that capital into AI innovations for hotels instead. Different bet, different timing — role concluded by mutual agreement.

Grew the business to ~$9M ARR, brought new clients on, and upsold AI Contracts to hotel staff who were happy to see it. Represented Canary at the annual Hilton conference.

Product lesson: running a payments vertical isn’t one job. It’s managing three products at three life stages while the partnership surface underneath keeps shifting — and being the one who tells the founders, in numbers, what scaling it actually costs.

Brought in by the CEO and executive team — hired in three days — to launch Stax Processing. The money-movement platform underneath had been acquired from FIS for roughly $4M and was proving a misfit inside the Stax architecture. It was leaking money: failed and delayed payouts to merchants, and it couldn’t effectively process third-party ACH for Stax’s ISV partners. PE and management needed a credible answer, fast.

The directive was build-or-buy. I pursued both paths in parallel — working with the engineers who had been band-aiding the platform, the PE stakeholders setting the timeline, and every layer of the internal team. Having an IC role with a VP title was what actually moved the needle; it meant I could make calls in the room and do the work in the codebase the same day. Running both paths also bought the time to learn the entire Stax stack soup-to-nuts, which is what eventually made the recommendation defensible.

After two to three months of iterative cycles, the answer was fix, not replace — and we fixed it. Saved $M and months that a new platform build would have cost.

Once stable, the work shifted to scale and sustainability. I moved to the business side of the product — aligning the upstream systems contributing to the money flows, and initiating external NACHA ACH audits so the new Stax Platform and the company could stand up to scrutiny. The platform carrying $500M+ monthly TPV and $20M daily consumer ACH ended up on a foundation it could actually grow from.

Once ACH was stable, Platform Reconciliations was the next honest question — and the same one I’d answered at Payrix four years earlier. Reconciliation across card brands, sponsor banks, and the Stax platforms themselves. “Where is the money, and how accurately can we know?” is the question every PE investor and acquirer asks before writing a check. Started the same rebuild pattern at Stax. Same story, different company.

Stax couldn’t retain me as FTE due to internal budget constraints. I was glad to have helped them on their PE journey toward the next billion-dollar outcome.

Product lesson: “fix or replace” is only a binary if you haven’t done the architecture read. Having run this sequence once (Payrix) made running it the second time (Stax) faster and more confident.

Recruited by the CPO as VP Product to bring back the glory days of Payments at Yodlee. Yodlee was a division of Envestnet (public) and contributed ~$200M ARR to Envestnet’s ~$1B annual revenue, serving 17 of the top US banks. The wedge was Account Verifications — letting a bank authenticate users who held bank accounts elsewhere — a mature $25M business with classic late-stage shape: cash-generative, flat, harder to grow every year.

The charter: grow or reinvent the mature book, and find the next line that could help the division scale beyond $200M against Envestnet’s billion-dollar ambition.

• Reinventing the wedge — Account Tokens. 0→1 launch. The bank-account analog to what card tokens became for cards: keeps underlying bank info safe and compresses the Account Verification lifecycle. Same data core-competency Yodlee was already known for, packaged so it could be sold beside the existing AV product without cannibalizing it.
• Finding the next curve — Subscription & Bill Tracker. 0→1 launch. Fed off Yodlee’s data but served a higher purpose for consumers: help them save money by cancelling or renegotiating forgotten subscriptions. In active discussions for deployment to Bank of America Diamond customers, Navy Federal Credit Union, and several smaller banks at the time.

Together, the two 0→1 initiatives drove a 5–8% gross revenue increase — a meaningful lift on an otherwise mature $200M book, and a rebuilt case for Yodlee continuing to matter inside Envestnet.

That case didn’t get to play out all the way. Envestnet came under increasing investor pressure and had to slow down; large RIFs followed across the org. Yodlee eventually went from a public-company division to a private PE-owned business. The 0→1 work stayed shipped; the strategic context around it shifted.

Product lesson: you don’t kill a $25M wedge — you reinvent it with a second product alongside it, and you find the next curve before the current one flattens. The hardest part is convincing a mature org it still has room to innovate. The 5–8% is what you hand back when someone asks whether it was worth trying.

Hired by the PE investors to drive Payrix’s next stage of growth — and set up the exit. Three workstreams, all pointed at the same outcome:

• Multi-processor framework. Payrix was already running on FIS/TD Bank. The growth story needed headroom and failover — a second rail. Built Fiserv/Wells Fargo alongside, creating a true multi-processor platform that unlocked the next leg of revenue growth and removed single-processor concentration risk at the same time.
• Unblocked the M&A cycle. Partway through the acquisition process, platform reconciliation surfaced as a diligence hurdle — the kind that quietly stops deals. Built a resilient reconciliation solution that matched platform dollars against bank settlement and card-brand settlement end-to-end. The work that kept diligence from stalling.
• World-class product team and a full brand redesign. Scaled product 5 → 15, hired ten product managers and engineers under M&A timing pressure. Drove a full brand redesign to reposition Payrix ahead of the process. Both mattered — buyers are buying the team and the story, not just the tech.

Run-rate ARR went $10M → $50M. FIS/Worldpay acquired Payrix; it became Worldpay for Platforms, now part of the Global Payments organization.

Product lesson: valuation problems in payments are usually operational problems wearing a finance costume. Fix the plumbing AND build the team AND sharpen the story — and the multiple follows.

First Product hire at Rapyd in the US, based in Mountain View — introduced to the founders by ex-PayPal colleagues. Rapyd was early at this point: a global-first payments ambition without a real US presence yet, and I ended up with fingerprints all over the stack that came next.

• Seeding the Global Payments Network. Built the first partner integration delivering an end-to-end money-movement experience across APMs — banks and wallets. That integration became the starting point for RPGN (Rapyd Global Payments Network), which grew to 60+ APMs and 1,000+ payment methods — competing with Stripe, Adyen, and a long tail of local APM players.
• Global Issuing, built in Latin America first. Built Rapyd’s first Global Issuing Platform in Mexico — the one Uber and Rappi adopted to get drivers onto cards (and lower their fraud rates in the process). Extended issuer infrastructure into Brazil and South Africa, each with its own banking rails, regulatory shape, and local realities to work around.
• US money-movement rails. Built ACH processing with Evolve Bank & Trust to give US clients clean load and unload ramps — the piece that made Rapyd a credible platform for US fintechs, not just a cross-border network.
• Global product org. Built out the product team across SFO, Tel Aviv, and Singapore — three time zones, one roadmap.

Post-Covid, the company slowed global operations and refocused inside the EU via an Icelandic payments acquisition. Rapyd is now a $5B+ valued company — I had a hand in the early rough starts that got it there.

Product lesson: the 60+ APMs came because the first integration was done right.

Verifi was the deliberate move out of the PayPal bubble. Five years inside PayPal had taught me global scale, but it had also kept me inside one operating model. Verifi — based in LA, the industry leader in Chargeback Management — was a bigger, more nuanced field. Took the Director of Product role hybrid: Bay Area home base, flying to LA every other week. The commute was the cost of seeing how the rest of the payments ecosystem actually worked.

The portfolio. Three distinct product lines, all designed to feed the Chargeback Management flywheel:

• Payment Platform — Verifi’s white-labeled extension of NMI, owned end-to-end. Grew it as the conversion target for merchants who arrived through the chargeback door.
• Intel Suite — Verifi’s proprietary toolset that leveraged multiple specialized vendors to help merchants make smarter processing decisions. Owned roadmap and vendor relationships.
• Decline Salvage — helped merchants recover revenue from failed payments. Cash-generative, with a dependency profile that wouldn’t age well.

The flywheel. Merchants came in with a chargeback problem → adopted Chargeback Management → converted to Payment Platform → which itself helped mitigate the chargeback issue that brought them in. Three products tied tightly to the CB anchor — every conversion strengthened the next one.

The deprecation play. Built an automatic Account Updater solution that quietly took over what Decline Salvage had been doing — reducing failure rates upstream rather than recovering lost revenue downstream. The strategic call: deprecate Decline Salvage rather than keep optimizing it. Cleaner architecture, less vendor sprawl, more defensible platform.

Re-platformed the stack. Reduced waste, built platform efficiency, owned the team and built the foundations that were later part of the Visa acquisition story. Along the way: fraud losses cut ~50%, risk exposure down 20%.

Product lesson: the flywheel was visible only because I’d seen what worked elsewhere.

Joined PayPal because my boss from Blackhawk invited me onto his team. Five years, three distinct chapters — each one a different scale and shape lesson.

Chapter 1 — The PayPal Card and the Home Depot launch. PayPal’s first-ever in-store initiative, with The Home Depot as launch partner. PM for the first-ever PayPal Card product; owned the end-to-end build and rolled it out to the first 25,000 users. Sat on the integration team with Discover (the processing layer behind the card). Worked alongside a depth of engineering, product, and business talent I hadn’t seen at that scale before.

Eleven months in, the project was shelved. The mobile phone had become the new in-store rail, and PayPal correctly went all-in on mobile-first. The card stopped being the vehicle for the in-store experience the company needed. Which was its own product lesson: sometimes you build the right thing for a window that closes faster than the build cycle.

Chapter 2 — Mobile-first consumer experience. Moved into the consumer app rebuild. Owned the layer managing payment instruments — cards, banks, wallets — plus balances and FX inside PayPal. Wallet features shipped inside the new mobile app launched across 208 markets with 10M+ downloads.

Chapter 3 — Core Payments and the Stored Value platform. Joined the Core Payments team for the re-architecture of the Stored Value platform — the foundational infrastructure underneath the PayPal Wallet. Launched a new global holdings system for 200M+ users across 25 currencies. Built transfer services for global money movement and partnerships with external financial institutions.

Earlier highlights worth keeping in view: 5% revenue growth from building the platform capability for digital gift cards on eBay.com and paypal-gifts.com, working with industry aggregators (Aug 2013). And the original Payment Card consumer rollout hit 80%+ activations (Jul 2012).

Principal Systems Engineer at Blackhawk Network (NASDAQ: HAWK) in Pleasanton — building the payment-processing infrastructure for the largest prepaid card network in the US. Holiday season was the largest annual capacity event for the platform, and the engineering teams that held it together are where I cut my teeth.

Four workstreams that mattered, in chronological order:

• Canadian telecom integration (Oct 2008). First real ownership project. Wrote the integration that brought a Canadian telecom partner onto the platform — direct revenue impact via volume growth.
• High-capacity processing engine (Apr 2009). Led implementation teams to build and manage the ~2,700 TPS payment processing engine — the engine that held uptime through every holiday season.
• NOC real-time dashboard (Nov 2011). Designed and launched a real-time financial-transactions dashboard for the global Network Operations Center. Reduced response times 50%. The first time I built something where the user wasn’t another engineer — it was a product, with humans on the other side.
• Technical leadership and mentoring. Guided technical leadership, training, and advice across the organization — the work that quietly shifts the org’s competency floor.

Four years of writing code, reviewing code, and being on-call when it broke. What I noticed wasn’t “can this scale?” — that’s a compute-and-architecture exercise. It was “which product decisions force it to scale this way?” Once that question started keeping me up at night, the next move was clear.

Product lesson: the NOC dashboard was the early signal — my first piece of software where the user wasn’t another engineer. The move from engineering to product wasn’t a pivot. It was following the questions that mattered most.

Sr. Software Engineer at Marketlive (Petaluma, CA — now Kibo). Led the performance portfolio of the Marketlive 5.x commerce product — identified and fixed bottlenecks for a 20% out-of-the-box performance lift. Spent days averting LIVE-site issues through monitoring, brainstorming, and FAQ-style triage. Also acted as Technical Evangelist with clients — the role that taught me to translate between engineering language and stakeholder language. Bridging those two audiences turned out to be most of what a product leader actually does; I just didn’t know that yet.

Project Lead at Syntel (NASDAQ: SYNT) — SF / Mumbai. Led a series of banking-and-financial-services projects: consumer phone-banking, B2B credits, online banking. Technical Lead for application development at Wells Fargo Bank, NA. Built and ran an onsite-offshore delivery model for banking-grade software — distributed teams, strict SLAs, audit-ready process. Recipient of Syntel’s Manager’s Award for the alliances that kept the offshore-delivery model intact. Three and a half years of learning how disciplined delivery actually works inside a regulated bank.

Senior Software Engineer at MphasiS (NSE: MPHASIS), working across international assignments. Delivered key initiatives for Emirates Bank (Dubai), Saudi American Bank (Riyadh), Citibank (LATAM), JP Morgan Chase, and Procter & Gamble (Mumbai). Early exposure to cross-border banking systems and the wildly different regulatory shapes they operate under. If I’ve ever seemed unfazed by the “but what about this jurisdiction?” question, this is where that started.

Software Consultant at PSI Data Systems (now part of Aditya Birla Group) in Mumbai. Built web-based software for Stock Exchange brokers — my first exposure to the rhythm of capital-markets technology and the latency expectations that come with it.

The first job. Software Engineer in Mumbai, building financial accounting software. Launched new systems for Maharashtra State Financial Corporation (MSFC) and State Industrial & Investment Corporation of Maharashtra (SICOM) — state-level lending and investment institutions. Two and a half years of writing code, debugging code, and shipping it to users who needed it to work the next morning. The apprenticeship that everything since has been built on.