In month six, a partner at a well-known Mumbai VC firm reached out. They'd heard about us through a mutual contact. The pitch was simple:
- take ₹8 crore
- grow faster
- capture the market before someone else does
We said no. We've said no twice since. This is an attempt to explain why — not as a manifesto, but as an honest account of the reasoning, including the parts that have cost us.
What the VC path looks like
I've watched enough funded startups up close to know what the money buys. It buys speed in the short term. Hiring happens faster. Sales cycles compress. Marketing gets loud.
The product roadmap gets prioritised by what drives the metrics investors care about — usually DAU, GMV, ARR — rather than what makes the product genuinely better.
The trade-off is that you now have a boss. Not one boss, but a cap table full of them, each with their own model of what success looks like. The best VC firms are genuine partners.
The median firm is a quarterly board meeting where you explain why growth is slower than a slide deck from eighteen months ago. And the incentive structure — grow fast, exit faster — is structurally misaligned with building something that lasts.
None of this is a moral claim. Venture capital is the correct instrument for a genuine land-grab, where the market rewards whoever gets there first and margins can wait. It's the wrong instrument for a product where the thing being sold is reliability.
Why bootstrapping fits this specific product
AIVA is a product where trust matters more than growth speed. Our customers are putting their customer relationships in our hands.
When a clinic deploys AIVA to answer inbound calls, they're not just trusting a piece of software — they're trusting us with the first impression their patients get. That trust is built slowly, through reliability and consistency, not through a 3x growth quarter.
Bootstrapping forced us to get to revenue quickly, which meant building something customers would actually pay for. We were profitable by month 14 — not from financial conservatism, but because customers renewed, expanded, and referred.
The week-by-week version of how that happened is in profitable since month 14.
The framing I've found most useful here is Paul Graham's default alive or default dead — the question of whether your company survives on current trajectory without raising again. Being default alive early doesn't make you right. It makes the decision about funding yours rather than the calendar's.
We answer to our customers, not to investors. That's not a positioning statement. It changes what we build.
The decisions it actually changed
The abstract claim is easy to make, so here are the concrete ones.
The 2.0 rebuild. We stopped shipping features for four months to rebuild the entire stack. That's a difficult conversation with a board watching quarterly growth and a straightforward one when the only people to convince are your customers.
It's the single highest-return decision we've made, and I'm not confident we'd have been allowed to make it on someone else's timeline.
Staying small. We cap ourselves at eight people. Capital would have made a 30-person team affordable, and a 30-person team would have needed a management layer, and the thing that makes us fast is that there isn't one.
Building in Rajkot. Our runway maths only worked because of where we chose to build. Funded, we'd have had no reason to make that call, and we'd have lost the retention advantage that came with it.
Features we didn't build. Bootstrapping kills things that demo well and don't get used, because we pay for them out of revenue rather than someone else's.
The list of what we've deliberately not built is mostly a list of things that survived exactly as long as they were hypothetical.
Hiring order. We hired customer success before sales, which is the wrong order for a growth chart and the right one for renewals.
What it costs
I want to be honest about the costs, because I've seen bootstrapping romanticised by founders who haven't done it.
It's slower. We could have three times the customers right now with outside capital. We didn't hire a head of sales until month 18. We've turned down enterprise deals that would have required hiring faster than we could maintain quality. There are roadmap items that have sat for six months because we don't have the headcount to ship them safely.
It's also psychologically heavier. There's no cushion. A bad month is a real problem, not a blip in the data. The months before we crossed into profit were genuinely stressful in a way that funded founders don't experience.
And it means being outspent on visibility. Competitors with capital appear in more places than we do. We've made our peace with that by being unusually direct about what the product does and doesn't do — the reasoning is in honesty over hype — but it's a real disadvantage, not a clever strategy.
How we'd know if we were wrong
I'd rather hold this as a decision than a belief, so it's worth writing down what would change our minds. Three things would.
If the market turned out to be winner-take-all. Our whole argument rests on this being a market where a slower, more reliable operator can keep winning customers indefinitely.
If distribution consolidated — if two or three platforms became the default way small businesses buy this, the way payment processing consolidated — then being right about product quality wouldn't matter, because nobody would be evaluating products. We watch for that and haven't seen it.
If a genuine capability required capital we can't earn. So far every capability we've wanted has been buildable from revenue, and the 2.0 rebuild proved the expensive ones are too.
If that stopped being true — if the next necessary thing required infrastructure at a scale revenue can't reach — the honest response would be to raise, not to pretend the capability doesn't matter.
If staying small started costing customers rather than just growth. Slower growth is a cost we've accepted. Slower support, or a reliability gap because eight people can't cover the surface area, would be a different thing entirely — that's the customer paying for our preference, which isn't a trade we'd defend.
None of the three is currently true. If one becomes true, I'd like this paragraph to be the thing someone quotes back at me.
The choice we made
We chose to build a company we'd want to work at, for customers we'd want to keep, at a pace we could sustain without burning the team out. That meant saying no to capital that would have accelerated the clock without necessarily improving the outcome.
It also shapes something customers see directly: our pricing is pay-as-you-go with no minimum commitment, because we've never needed to inflate contract values to hit a number for a board.
Two years in, profitable, with a team that's been together since early days and a customer base that genuinely likes the product — we're happy with that trade. More about who we are is on the about page.
The VC offer is still open. We still say no. If you'd rather judge the product than the funding model, start free with ₹500 of credit.