Rocketizer

Rocketizer positions the product as AI employees for growing businesses, with Maya as a generalist spanning orders, delivery, growth, and support.

The marketing site presents Maya as a generalist first hire across orders, shipping, support, advertising, and cashflow.

The site markets persistent context across orders, tickets, files, decisions, and voice notes, plus access through WhatsApp, Telegram, and phone and ingestion of PDF, spreadsheet, and voice-note inputs.

The marketing site names Shopify, Gmail, Meta, Zendesk, Freshdesk, Google Ads, Google Analytics, Amazon, and Flipkart as connected tools; it does not document connector-by-connector read and write permissions.

Rocketizer markets natural-language analysis across store, advertising, and marketplace data, including briefings, change detection, root-cause explanations, and suggested next moves.

The site says employees plan steps, use tools, work autonomously, request approval for consequential decisions, and report results. This is a current vendor claim, not an independently exercised action catalogue.

A marketing illustration depicts COD buyer calls and NDR, RTO, and remittance resolution, with failed deliveries falling from 14 to 2 and INR 2.4 lakh saved over 90 days. No customer is named, so the figures are demo copy rather than adoption or case-study evidence.

The marketing site marks Kabir (creative) and Saumya (support) Live, and Gaurav (performance), Aarav (RTO Saver), and Nisha (social listening) Soon.

The public price card is usage-credit based: Starter supplies INR 2,000 of credits per month, Scale INR 5,000, and Enterprise is custom. Task burn rates, overages, expiry, taxes, and contract minimums are not disclosed.

The published onboarding sequence is email signup, Gmail connection, and an optional but recommended Shiprocket connection; the site says setup takes minutes without calls or forms.

Rocketizer says its employees start with Shiprocket commerce-graph intelligence covering Indian orders, couriers, pincodes, COD behavior, delivery outcomes, returns, buyer patterns, and margins.

The site displays 250+ ecosystem partners and 4 lakh+ businesses served. The surrounding copy attributes this scale to the Shiprocket ecosystem, so it is not Rocketizer customer adoption.

A deployed public Rocketizer application loads under the title Rocketizer · AI Employees and exposes employee, approval, artifact, memory, integration, channel, and team surfaces.

Public signup and sign-in routes are deployed with email and Google authentication entry points. The unauthenticated surface does not establish whether new accounts are immediately activated or placed into an approval state.

The current public application assets present Maya, Kiran, Nisha, and Saumya as available employees. This conflicts with the marketing-site roster, which names Kabir instead of Kiran and marks Nisha Soon.

The in-app catalogue describes Kiran as a Creative & Growth employee that turns product notes into ad routes, static posters, captions, and approval-ready packs; its listed poster skill has no required connector.

The in-app catalogue describes Nisha as a Research & Insights employee that compiles audience angles, trend hooks, competitor gaps, reference ads, and a research packet; its listed skill has no required connector.

The in-app catalogue describes Saumya as a WISMO support employee that uses verified order facts to draft email replies and routes risky cases for human review; Gmail is listed as required.

The deployed app surface contains task planning and delegation, approval queues, artifacts, memory proposals, workspace roles, and team invites. Their production enforcement was not exercised without an authenticated workspace.

The deployed app assets present Shiprocket credential connection, Gmail and Google Workspace OAuth, Google Calendar/Drive/Docs/Sheets/Analytics, and Shopify custom-app setup. Unauthenticated inspection cannot verify which connectors are enabled server-side for a new workspace or their effective permissions.

The public demo identifies its workspace data as fixtures, states that Shopify is not live-connected, and uses manual export while Meta Ads is disconnected. It demonstrates workflow UX, not production data access or completed external writes.

The deployed app pricing copy names Kiran and Saumya as live specialists, reinforcing the roster conflict with the marketing site's Kabir and Saumya wording.

The public API health endpoint returned an OK service status during revalidation. This proves a deployed backend endpoint, not the correctness or production availability of individual agent actions.