RIntelligence
78/ 100evidence-weighted strategy score
Merchant ROI13/20
Shiprocket revenue capture20/20
Shiprocket right to win19/20
Execution ease8/10
Buyer understanding7/10
Risk-adjusted viability8/10
Whitespace3/10
Scorecard data table
Evidence-weighted opportunity dimensions
DimensionScoreMaximum
Merchant ROI1320
Shiprocket revenue capture2020
Shiprocket right to win1920
Execution ease810
Buyer understanding710
Risk-adjusted viability810
Whitespace310
Total78100

Workflow and buyer

BuyerLong-tail merchant founder plus Shiprocket growth, success and product teamsValue pool not specified
Minimum lovable wedgeA 10-minute diagnostic that picks one high-confidence attach—such as Checkout, Engage, cross-border or Capital—and stays with the merchant through first value.strategic
Monetization hypothesisfree/included growth layer funded by incremental Shiprocket product revenue; optional Rocketizer upgradeNot specified
Competitive prooffirst-party cohort evidence, not product proofThe UDRHP reports 72.81% of H1 FY2026 Power Merchants using more than two products and 52.27% using more than three. No evidence identifies causal combinations or a coach effect.

Action authority

Direct actionsgenerate merchant diagnostic · recommend one next product · start connector/setup checklist · schedule follow-up · measure first transaction/value eventSubject to the stated integration and merchant-policy boundary.
Approval or policy boundcommercial offer · product enrollment · billing changeMerchant chooses products; Shiprocket systems own eligibility, entitlements and billing.

Assumptions, dependencies, and risks

AssumptionsRocketizer access to the referenced Shiprocket events or surfaces is unproven and must be validated. · One-step recommendations outperform broad dashboards. · Merchant progress can be evaluated without fabricating causality.
Dependenciesunified product catalog and entitlement API · merchant cohort model · first-value events · success-team handoff
RisksCould become internal cross-sell spam. · Merchant ROI is diffuse and attribution is weak. · Portfolio overlap and entitlements are currently unclear.
Proof caveatCross-sectional product use is not proof that coaching causes graduation or retention.

Synthesis references

Normalized evidence

  1. COD-to-delivered-revenue control loop supporting source

    Shiprocket's filing describes platform scale, cohort economics and post-order business context; it does not prove Rocketizer access, permitted use or lift.

    regulator · accessed 2026-07-13
  2. Power Merchant graduation and product-attach coach supporting source

    The portfolio contains multiple specialist products but no public unified attach architecture.

    company · accessed 2026-07-13
  3. Delivery-exception and WISMO resolution supporting source

    Saumya is a deployed catalog surface with verified-order-fact and approval-oriented design, but production sends are unproven.

    company · accessed 2026-07-13