Investment thesis
A portfolio designed to compound, not a collection of apps.
Owning several companies is not a strategy. What makes this a holding company rather than a habit is that each venture has a job in the same system, and each one lowers the cost of the next.
1
Create demand
Free utility, search, directories and AI guidance attract people who already have the problem. Nobody pays to be useful to them.
2
Monetise the workflow
Once a provider can see real demand arriving, the operating system that runs their business becomes worth paying for. ERP, AI voice, scheduling, invoicing.
3
Compound the network
Transactions, advertising, referrals and retention grow as density increases — and every venture inherits the engine the last one paid to build.
The argument
The expensive part of a vertical marketplace is not the software.
It is the supply. Assembling every pro, shop, restaurant and pharmacy in a category — and making each record genuinely useful — is where the years go. Once that work is done, the software on top of it is the cheap part, and it is the same software every time.
What the first venture paid for
ZeroFi paid to learn how to ingest a licence board, how to rank a directory without letting a general contractor win every trade query, how to bill an ad click without billing a bot, and how to make a claim flow that a small business will actually finish.
What the others inherited
GymGuide’s advertising engine is ZeroFi’s, ported. AutoDoctors’ repair guides are ZeroFi’s DIY engine, ported. Every claim flow in the portfolio descends from the same design. The marginal cost of the next vertical is a fraction of the first, and falling.
Why the portfolio can compound
The same relationship can create several legitimate revenue paths.
Not forced bundling. Adjacent value, offered when the same customer genuinely has the next problem — and declined when they do not.
Step 1
Demand
Search and free AI guidance
Step 2
Marketplace
A qualified connection
Step 3
Operating system
ERP and workflow
Step 4
AI agent
Voice and automation
Step 5
Commerce
Ads, referrals, transactions
| Customer | Path |
|---|---|
| A restaurant or café | RestaurantPro listing → Basil answers the phone → Moksha supplies the beans |
| An auto shop or dealer | AutoDoctors connection → shop ERP → DIY and parts referrals |
| A field-service pro | ZeroFi lead → ERP and Zoe → Nirah supplies the consumables |
| A compounding pharmacy | PharmacyFlow directory → facility OS → Nirvana builds the integration |
Operating discipline
Capital follows evidence.
The portfolio stays founder-efficient by reusing core architecture and scaling a channel only once its leading indicator has moved. These are the six we watch.
- Demand
- Organic activation and return rate
- Supply
- Claims and verified providers
- Revenue
- Paid conversion and ARPU
- Retention
- Seat, merchant and user cohorts
- Economics
- Contribution margin and AI cost
- Trust
- Quality, privacy and permission incidents
Fund proof, not vanity.
Shared code lowers build cost. Brand-specific data boundaries preserve trust.
What is not on this page
No revenue projections, no forecast, no management case. Those exist, they are maintained carefully, and they are shared under NDA with people who have a reason to see them — not published to anyone who loads the page. If you are one of those people, ask.