PSHR INNOVEX PRIVATE LIMITED
A focused merchant pilot with measurable outcomes
VyapaarMate brings direct orders, payment status and customer follow-up into one workspace. Our incubation plan is to test that workflow with local food businesses and use the evidence to improve the product and subscription model.
Proposed incubation work. The targets below are not completed interviews, customers, revenue, funding or confirmation of admission to any programme.
Core product
One connected operating workflow
01
Receive
A customer places a direct order or booking through the business catalog.
02
Operate
The owner and authorised staff track fulfilment and payment status in one workspace.
03
Follow up
Customer records and permitted updates support service and repeat visits.
04
Learn
Explainable rules highlight actions. The pilot measures whether they help the owner.
Catalogs, orders, booking tools, staff roles and decision-support modules are implemented in the product. Payment-provider confirmation and WhatsApp delivery depend on configured services and must be verified for a live pilot. Recommendation accuracy remains a validation task.
Market entry
Two cohorts with separate evidence
Bengaluru
Build on local outreach to food businesses. Measure onboarding, weekly use and willingness to pay within this cohort.
Any Bengaluru launch discount applies only to eligible Bengaluru businesses and is confirmed at checkout.
Andhra Pradesh
Seek introductions through RTIH for a separate cohort of tiffin centres and small restaurants. Start from the founder’s Kadapa and Tirupati connections.
Confirm the local segment, merchant consent and pilot terms before onboarding. Track this cohort separately from Bengaluru.
Proposed first 90 days
Turn a working demo into useful merchant evidence
Days 1–30
Understand the merchant
20 owner interviews
Recruit across the two cohorts, choose one initial food-business segment in each, and rehearse the complete demo.
Evidence to review: Dated interview notes, workflow baseline and agreed pilot scope.
Days 31–60
Observe real operations
5 consenting pilot businesses
Record onboarding effort and observe order handling. Report each cohort separately; the five-business target is across both cohorts.
Evidence to review: Weekly usage, support effort, consent records and merchant feedback.
Days 61–90
Review willingness to pay
Review repeat use
Compare paid conversion, continued use and service costs. Decide whether to improve, extend or pause each cohort.
Evidence to review: Usage trends, paid subscription records and a decision on the next cohort.
Commercial validation
Measure software adoption separately from merchant sales
The owner is the paying customer
The current checkout supports a monthly software subscription. Additional configuration or onboarding work is scoped separately. Annual billing is a proposed option and is not available in the current checkout.
Compare the subscription collected with cloud, messaging and support costs. Validate pricing with each cohort before expanding.
A consistent reporting period
- Merchants completing onboarding and handling their first real order.
- Merchants using the core workflow each week, by cohort.
- Paid subscription customers and recurring subscription value, excluding tax and one-off setup fees.
- Repeat use, merchant retention and support minutes per business.
- Merchant order value, demo data and separate client-service income reported outside subscription revenue.
Incubation request
The support that moves the pilot forward
We seek merchant introductions, mentoring on pilot design and pricing, and technical reviews of reliability and rollout readiness. Funding and investor discussions should follow a milestone budget and evidence from actual usage.
The three-year direction is to establish a repeatable paid offering, strengthen retention and local support, and expand into selected clusters when customer outcomes and operating costs justify it.