Akhil J Sathyan Product manager, financial systems Open to new roles
Step in

Financial records people can trust. A platform that’s easier to change.

I find where money leaks between checkout and the books, fix the records underneath, and leave a platform other teams can build on. At Grove, that made the financial records IPO-ready.

Where I help

Find the leaks
Over-refunds, orders that don’t match the ERP, exceptions handled by hand.
Fix the source
Keep the facts of each transaction instead of patching symptoms.
Make it reusable
Billing, pricing and fee capabilities the next team can build on.
Grove · $270M in annual GMV
$3Ma year

in refund leakage closed

About $250K lost every month, adding upRefunds matched what was paid within six months

5%→0.2%

of transactions flagged for reconciliation

1 in 20 needed a manual fix; ~$100K a month written off1 in 500, within a year

−99.5%

realized account-takeover fraud

$430K a year lost to account takeovers~$2K a year within a year, from login and order-flow changes

40%→10%

of platform engineering time spent on upkeep

40% of the team’s time went to upkeepHalved in two years, then halved again

…known for his ability to communicate effectively across the organization, and to create and maintain alignment across some of the most precious projects in the company. Vanessa Garber, manager at Grove · LinkedIn recommendation
That’s the outcome. Step in to see how it unfolded. About a minute.

One overloaded record, retired one job at a time.

When I started, the shipment record behind Grove’s $270M in annual GMV did nearly everything: charging, refunds, order history, subscriptions, offers, even the cart. Every change was slow, and teams saw different versions of the same order. Each project I owned had to pay off on its own and retire one of those jobs. After the 2022 layoffs I took on what had been a Director’s and two PMs’ scope, and from 2023 I was the only product manager on Grove’s platform.

Charging customers→ Charge The Order (2020)
Refund amounts in Support tools→ Refunds from OMS invoices (2020)
Support’s order records→ OMS invoices (2020)
Customer order history→ Order History API v3 (2021)
Subscription items→ Subscriptions model (2022–23)
Offers and pricing→ Subscription pricing engine (2022–23)
Payment data→ Modular payments, led by another team
Cart and checkout→ Shopify (2024)
New-visitor sessions→ Shopify (2024)
Analytics workflows→ Rewritten for Shopify (2024)
Still done by the shipment recordWhen I was retiring itHandled by its replacementChapter numberGrey rows: retired by other teams

By the Shopify cutover, the shipment record wasn’t needed at all.

  1. 012020–21 · Transaction factsKeep what the customer actually paid, per unit.5% → 0.2% exceptions, −46% NetSuite records
  2. 022021–22 · Shared order dataGive customers, Support and Finance one order record.Support upkeep 40 → 5 hours a month
  3. 032022 · FeesShip the fee fast, then make fees reusable.Reused for a new opt-in fee after the first was retired
  4. 042022 onward · Pricing and offersSeparate how prices are recorded from how they’re charged.Explicit offer rules and a reusable pricing service
  5. 052022–24 · SubscriptionsFund the next test on a longer-term signal.Subscribe & Save became a core program
  6. 062024–25 · MigrationDecide what survives the move to Shopify.The compatibility contract and cutover order
That’s the arc. Go deeper into the six decisions and what each one left behind. About five minutes.

Six decisions, and what each one left behind.

Each project started with a business need. The product decision was how to meet it while leaving the platform easier to work with.

01

Financial integrity · 2020–2021

Stop reconstructing what the customer paid.

Over-refunds exposed a deeper problem: the records didn’t keep the facts needed to explain or reconcile an order.

Before · two units bought, one at 50% off

$10.00

refunded for the discounted unit. The record kept only a blended total, so Support fell back to full list price.

After · amounts kept per unit

$5.00

refunded: exactly what was paid, read from the stored transaction instead of an expired promotion.

The problem
Records drifted apart between shipment, order, invoice and NetSuite. Finance and Ops needed a principal engineer to reconcile the exceptions every month.
What I decided
Group the real exceptions with Finance and Ops, rank them by money and frequency, and keep the per-unit amount paid at the moment of charge. I sequenced the fixes to meet IPO-readiness deadlines.
~$100K/moin write-offs from order-to-NetSuite mismatches, addressed
−46%NetSuite line-item records, easing scaling concerns
−90%customer-deposit liabilities needing manual review
2 weeks → 1 dayto clear the monthly exception backlog

“A key ingredient to what has allowed Grove to go public.”

Manager, 2021 performance review, on this work
02

Shared data and controls · 2021–2022

Give customers, Support and Finance the same order.

Different teams needed different views of an order, not different versions of what happened.

Order History API
Customer order history
Support tools
Finance reporting
Operations
Analytics
The problem
Customer history, Support tools and financial reports disagreed. Agents logged into customer accounts just to see what the customer saw.
What I decided
Define the facts each consumer needed and make one API the shared source. Keep financial distinctions in the data and tailor only how each screen shows them. SOX access controls for the IPO were sequenced alongside.
40 → 5 hrsmonthly engineering upkeep for the Support plugin
62 → 16open Support tickets, with 100 resolved in 2022

“…his ability to combine a deep understanding of the product’s technical intricacies with exceptional thoughtfulness.”

Alexandra Marchesano Gilbreath, product teammate at Grove · LinkedIn recommendation
03

A reusable fee capability · 2022

Build a fee that could outlive its policy.

Grove needed a Supply Chain Fee right away. The lasting decision was how to ship it without hard-coding it.

Fee policy
retired Supply Chain Fee Opt-in sustainability fee
Fee mechanics
Hard-coded Reusable fee capability
The policy ended. The capability kept running.

“A great example of a scrappy(ish) test → full rollout to get impact early → build sustainable implementation.”

Manager, 2022 performance review
04

Pricing and offer boundaries · 2022 onward

Make pricing possible to change again.

Four teams had each learned to avoid pricing changes, for four different reasons. I treated that as one business problem, and aligned seven teams on a single pricing source of truth.

Marketingsaw most price changes as too hard to try
Designcouldn’t tell what each displayed price meant
Engineeringfaced a large, expensive rewrite
Merchandisingwanted offers the system couldn’t express
What I decided
Separate how prices are recorded from how orders are charged, so new offers could sit on a stable charging base. Offer rules became explicit: subscription offers take precedence instead of stacking.
What carried forward
A Pricing Adjustment Service scoped for Subscribe & Save’s launch and the tests we expected next, plus a pricing primer so teams stopped rediscovering the rules.

“I am continually impressed as I learn more of the calls you made on what to include vs. not.”

Manager, 2022 performance review, on the Pricing Adjustment Service
05

Subscribe & Save · 2022–2024

Use longer-term learning to decide what to fund next.

The first read didn’t justify a rollout. Later evidence led to a new investment decision, not a reinterpretation of the old one.

Early read. The first test didn’t justify continuing.
Longer-term signal. With Analytics: established customers ordered less often, but subscribers stayed longer and bought bigger baskets than the control group.
New tests. We moved from a blanket discount to selected brands, with tools for Merchandising and Marketing.
Core program. Grove-funded discounts built the repurchase evidence that brought in vendor-funded discounts.
55% → 85%of products in cart eligible for Subscribe & Save
06

Shopify migration · 2024–2025

Define what should survive the move.

The move to Shopify cut what it cost to run the business. I set the compatibility contract and cutover order across five systems; the earlier platform work made that behavior easier to separate and carry over.

PreserveOrder, billing and Support behavior worth keeping
DropObsolete behavior not worth carrying over
SequenceThe cutover order, and middleware contracts for what remained
That’s the work. At the center: what I’d bring to your team, and where every number comes from.

What I’d bring to your team.

The same five habits ran through every project, whether the reason to invest was financial integrity, operator time or a new commercial program. Here’s what they’d look like on your team.

  1. One fix for a problem several teams are working aroundI connect what Finance, Support, Marketing and Engineering each feel before deciding whether it needs separate fixes or one shared capability.
  2. Value now, flexibility only where it’s earnedShip the immediate business outcome, and build in only the flexibility a concrete next step calls for.
  3. A sequence that pays off at every stageI work with Engineering on dependencies so each stage delivers value on its own, not one big bet at the end.
  4. A domain your teams can build on without mePRDs, pricing definitions and lifecycle audits, so teams stop rediscovering the rules.
  5. Priorities people can seeThe decision, the reasoning and the timing, shared where stakeholders meet the work, not only in planning meetings.

Where the numbers come from

  • 5% → 0.2% exceptions, −90% deposit liabilities needing review, ~$100K/month in write-offsManager, 2020 performance review, with peer feedback from the engineering team
  • $3M a year in refund leakage2020 refund analysis: excess refunds were ~30% of yearly refunds, closed across three projects. The over-refund fix alone was estimated at ~$1.8M a year in my manager’s 2020 review.
  • “A key ingredient to what has allowed Grove to go public”Manager, 2021 performance review
  • Upkeep 40% → 20% → 10% of platform engineering time; 40 → 5 hours of Support plugin upkeepPlatform team’s scheduled work as backlog owner: 20% in 2022 (self-reflection), 10% by 2024
  • Quotes from Vanessa Garber and Alexandra Marchesano GilbreathPublic LinkedIn recommendations
  • 62 → 16 open Support ticketsManager, 2022 performance review
  • −99.5% realized account-takeover fraud ($430K → ~$2K a year)$430K for 2022 from my manager’s 2023 performance review; later figure from fraud loss reporting. Attempted fraud fell too.
  • 2 weeks → 1 day to clear the monthly exception backlogOperations estimate; it varied month to month
  • −46% NetSuite line-item records2021 self-reflection

Also at Grove

Outside this platform story, in the same years:

  • +1,190 bpslogin success after a research-led redesign; the same magic-link login also blocked account takeovers
  • 8h → 48hwindow to catch and cancel suspicious orders, after moving payment capture to ship time
  • −66%page load time on customer-acquisition pages

Looking for product roles on billing, payments operations or financial platform teams.

Before platform work, I launched Grove’s first Android app (10% of annual order volume, 500K+ downloads, 4.8 rating), ran growth analysis at thredUP, and built revenue-cycle data systems for healthcare clinics at Sunbelt Medical.

Akhil J Sathyan