GT Product Consulting
Book a call

Sabhi · Product Management, Strategy, Design & UX

How Sabhi got messaging, payments and shipping into one launch plan

I led product documentation and delivery for Sabhi's closed launch: one buyer journey, one source of truth, and acceptance criteria that say when a feature is actually done.

8
Feature PRDs
13
Step launch journey
300+
UAT scenarios
Sabhi Team Chat with channels, direct messages and a contact details panel
Team Chat, part of the single dashboard that replaced separate messaging, payment and shipping tools.
Client
Sabhi
Services
Product Management, Strategy, Design & UX
Year
2026
Tools
Jira, Product Fruits, Claude
Engagement
Product lead for the closed launch

The company

Sabhi is a B2B platform for recycling and auto-parts businesses that sell over text. It brings SMS conversations, payment links, parcel and freight shipping, and review requests into one dashboard.

The challenge

A single sale moved through SMS, a payment link, a carrier and a review request, each in a different tool. The build was moving fast, but scope kept growing, some screens still ran on demo data, and decisions made in calls were not written down anywhere engineers could build against.

What I did

  1. Mapped the launch journey

    I documented the 13 steps from a buyer's first message to a Google review request, including returns, refunds and chargebacks. Every ticket since points at one of those steps and says whether it's launch-critical or fast-follow.

  2. Wrote PRDs as the source of truth

    I wrote eight feature PRDs, from Inbox to Super Admin, each with key results, guardrails, MoSCoW scope and acceptance criteria. Along the way I made the calls that shaped the build: one internal payment ID across SlimCD and Stripe, one shipment model for parcel and freight, and every record scoped to one business.

  3. Turned the build into testable criteria

    I reconciled the back-end and front-end code reviews against the PRDs, then wrote a UI-only test suite anyone can run from staging: 13 suites covering every launch area plus a role-based access check. I ran it with Claude, read-only, so every failure came back with its root cause.

  4. Rebuilt onboarding for the new app

    The 14 old tours were written for a previous layout. I scored every section of the new app, prioritized 11 flows for Business Admins, scripted 89 cards in Product Fruits and wrote the developer tickets.

  5. Kept scope honest

    WhatsApp, automated A2P onboarding and full carrier automation moved to fast-follow so they couldn't block launch. A shared Definition of Ready and Done kept demo behavior out of production flows.

Sabhi Team page showing roles and permission add-ons for reports, refunds and exports
Roles plus permission add-ons, covered by the role-based access suite. Tester details are blurred.

Results

  • 8

    Feature PRDs

    From Inbox to Super Admin, each with key results, guardrails and acceptance criteria

  • 13

    Step launch journey

    From first message to review request, approved as the closed-launch scope

  • 300+

    UAT scenarios

    Across 13 suites that anyone can run from staging

Want results like these? Let's talk.

A 30-minute call about where your product is and what to do next.

Book a 30-min call