100+
businesses served historically
Across the founders’ earlier service and adjacent business work—not Tripeaz customers or traction.
Investors & Ecosystem
Building the operating system for India’s fragmented taxi businesses.
Tripeaz begins with booking exchange: helping taxi operators find fulfilment partners and reduce empty return travel. The longer-term opportunity is a trusted operating layer for partner history, fleet workflows, compliance and business growth.
Company
Wolfron Technologies LLP · Rajkot, Gujarat, India
- Stage
- Pre-public launch
- Revenue
- Pre-revenue
- Product
- Working MVP
- Market
- India · B2B taxi
The structural problem
Demand is only the start of the operating problem.
A large part of India’s taxi market is made up of independent operators, travel agents, drivers and regional fleets. After a booking arrives, fulfilment still depends on fragmented networks and manual coordination.
- Supply and demand are distributed across local networks.
- Empty return journeys reduce vehicle utilization.
- Partner reputation rarely travels beyond personal relationships.
- Small operators lack one shared operating workflow.
- 01
Demand arrives
A customer enquiry or booking reaches an operator.
- 02
Fulfilment fragments
Vehicles and partners are searched across calls and chat groups.
- 03
Trust stays informal
Identity, history and reliability are difficult to assess consistently.
- 04
Operations remain manual
Assignments, alerts and records sit across disconnected tools.
The wedge
Booking exchange is the wedge. The operating layer is the opportunity.
The initial workflow is narrow enough to be useful now and connected enough to create a broader operating platform over time.
Entry point
Booking Exchange
Step 2
Repeat Transactions
Step 3
Partner History
Step 4
Trust & Reputation
Step 5
Operations
Step 6
Compliance / Transactions
Step 7
Business Growth
Platform thesis
Network → trust → operations → infrastructure
Status labels distinguish what exists in the current build from what is being developed or remains on the roadmap.
- Current Build
STAGE 01
Network
Booking exchange, Give/Need workflows and return-trip discovery form the entry point.
- In Development
STAGE 02
Trust
Partner history, reputation signals and authorized verification workflows can make repeat coordination safer.
- Current Build
STAGE 03
Operations
Core driver, vehicle, assignment, alert and multilingual workflows are in the Current Build; deeper operating workflows remain in development.
- Roadmap
STAGE 04
Infrastructure
Compliance, transaction and growth services extend the platform after the core network is working.
Current progress
What exists today
The core system is already working. Closed beta is next. The product remains pre-public launch, and these signals describe build progress and testing—not a claim of launch, revenue or scaled adoption.
Working MVP
Current Build
A working product exists. Tripeaz is not publicly launched and does not claim an active user base.
Pipeline processing
Thousands of real booking leads
Used to develop structured ingestion—not presented as completed bookings, customers or revenue.
Mobile retrieval
Testing
Retrieval is being tested while relevance and matching quality remain in development.
Operator feedback
4–5 workflow testers
They help test workflows and UX; they are not counted as active users or customers.
Distribution insight
The advantage begins before product launch.
Historical service work created market access, operating context and direct operator relationships. It must not be confused with Tripeaz product traction.
≈ ₹1 crore
cumulative taxi-client ad spend managed historically
Historical client advertising spend—not Tripeaz revenue or funds raised.
Thousands
direct operator conversations across states
Market discovery and relationship depth—not product usage.
July–August 2024
Orions work exposed the post-booking gap.
The founders worked on websites, customer acquisition, Google and Meta advertising, lead funnels and operator coordination for taxi businesses. Generating demand made the next constraint visible: operators still needed a reliable way to fulfil each booking.
Founder-market fit
The team has worked across both sides of booking coordination and understands why each operator type has different incentives.
- Driver
- Single-car owner
- Travel agent
- Fleet owner
- Larger operator
Operator feedback: 4–5 workflow testers are helping refine the MVP. They are not presented as active users or customers.
Team & company journey
Product, market operations and engineering in the founding team.
The current product is being built in-house, with roles grounded in who has actually led each part of the work.
Chaitanya Pandita
Co-Founder & CEO
Leads product, partnerships, government/API relationships and company building. Built the initial working prototype and has worked on automation and conversational product workflows.
Aditya Rajput
Co-Founder & COO
A technical COO and market operator leading operations, sales, operator relationships and go-to-market—not positioned as a third engineer.
Anand Jethava
CTO / Founding Engineer
Leads engineering, architecture, mobile, backend and data systems. Wrote most of the current production MVP.
2021
Chaitanya and Aditya meet as first-year Computer Science engineering classmates.
Apr 2022
Chaitanya and Aditya start Orions Tech Elite.
Jul 2023
Anand joins the technical and project team.
Jul–Aug 2024
The team works directly with taxi and travel businesses.
Late 2024–early 2025
The team investigates the booking-fulfilment problem.
Jul–Aug 2025
Tripeaz becomes the team’s main startup focus.
Sep 2025
Wolfron Technologies LLP is incorporated.
Feb 2026
Anand joins full-time as CTO.
Institutional ecosystem
Progress without overstating the relationship.
Each institution is described by its actual stage. Selection, eligibility and pending support are not presented as funding received.
Atmiya Innovation Foundation (AIF)
The incubation and innovation arm of Atmiya University. Tripeaz is selected / qualified for incubation; onboarding and documentation are in progress. No investment or grant is implied.
PIERC
Offered an eligible SSIP support pathway of up to ₹2.5 lakh. The support has not been received.
i-Hub Gujarat
Prawaas sponsorship occurred. Tripeaz progressed through multiple Srujan rounds; the final decision and support of up to ₹10 lakh remain pending and have not been received.
Staged business model
Monetization follows product maturity.
The sequence begins with a simple partner subscription and expands only as network, trust and transaction capabilities become real.
Stage 1
Partner subscription
Planned entry subscription around ₹300 per month. This is a pricing hypothesis, not current revenue.
Stage 2
Premium marketplace & SaaS
Premium tools, leads, promoted visibility, advertising and compliance workflows.
Stage 3
Transaction infrastructure
Payments, escrow, referrals, fleet tooling and GPS-linked services.
Stage 4
Expanded demand channels
Corporate, event, large-fleet and direct-to-consumer opportunities after the B2B core matures.
Technology
A practical stack for an operating product.
The architecture supports mobile workflows, structured data, real-time coordination and multilingual interaction. The technology is a means to make taxi operations work—not a separate AI thesis.
- Mobile
- React Native + TypeScript
- Backend
- Node.js, NestJS, PostgreSQL + Prisma
- Real-time
- Firebase and notification infrastructure
- Automation
- Structured booking ingestion and workflow automation
- AI & language
- Gemini and Sarvam used; OpenAI GPT family planned for evaluation/testing; Bhashini considered
- Government rails
- DigiLocker and API Setu integration foundation
Company status
- Company
- Wolfron Technologies LLP
- Incorporated
- September 2025
- Country
- India
- Product
- Tripeaz Taxi Partners
- Product stage
- Pre-public launch / closed-beta preparation
- Revenue stage
- Pre-revenue
Pre-revenue companyNo term sheet, valuation, commitment or investment agreed
Investors & ecosystem
Follow the product as the operating layer takes shape.
Review the current product, claim boundaries and staged roadmap, then email the team directly to continue the conversation.