Inside a Callapina deal: how we backed Bynry

Most deal stories told to LPs read backwards. The fund leads a round, the company hits a milestone, and the narrative is reverse-engineered into a clean line — sourced through this network, won the allocation, here is the trajectory. The reality, when the deal is good, is messier and more interesting. The thesis comes first, the founder appears later, and the work that actually compounds the position happens after the wire.

Bynry is the cleanest illustration in our Fund I portfolio of how that sequence is supposed to run. This essay walks through it in the order it actually happened — the thesis I had written down years before, the cold outreach that started the relationship, the operating advice that earned the right to invest, the round that came together, and the customer and partnership work that has compounded since.

1. The thesis was written before Bynry was a name we knew

In September 2023, while I was Principal at Amane Advisors, I published a piece titled "This is where you'll find the whitespace in the digital US water utilities market." The argument was simple, and at the time it was contrarian. The US water sector has roughly fifty thousand utilities. Almost every digital-utility software vendor was chasing the largest several hundred — the "blue whales" — because that is where the headline contract values were. The procurement cycles for that segment were brutal: long sales cycles, customized pilots, enterprise pricing, eighteen-to-twenty-four-month implementation timelines. Most early-stage vendors that targeted the blue whales died of starvation before they closed a meaningful contract.

The whitespace, as I argued in the essay, was in the forty to fifty thousand small and mid-sized utilities — Tier 3 and Tier 4 — that no enterprise vendor wanted to serve. Their problems were the same as the blue whales. Their budgets were one-tenth the size. Their procurement was faster. Their willingness to pay was real. And nobody was building for them, because the conventional wisdom said you could not make the unit economics work below a certain customer ARR.

The piece argued for three rethinks. Rethink the product — strip it to a "lite" core of five-or-fewer features that delivers value from day one rather than the most-valuable-product version aimed at the blue whales. Rethink the price point — design pricing at roughly one-tenth of enterprise solutions to crack a market that is two orders of magnitude larger by company count. Rethink the go-to-market — replace high-touch key-account selling with a self-service SaaS motion built around online channels, marketing automation, and remote deployment.

I did not have a deal in mind when I wrote that. I was writing because I had spent enough time sitting with utility leaders, water-tech founders, and infrastructure investors to know that almost no one was hearing the small-utility opportunity correctly. The piece was, in retrospect, a thesis statement waiting for a founder.

2. Nilesh, and the difference between hypothesis-led and customer-led

I came across Bynry not long after. Nilesh Pandit had founded the company in 2016 — interestingly, not as a SaaS product company but as a services business. The pivot to specialized utility SaaS came only after deep customer engagement showed where product-market fit actually lived. That iterative path is unusual in seed-stage software. Most founders arrive with a hypothesis and spend two years either confirming or contradicting it. Founders who arrive at the product through services have usually internalized the customer's reality at a level that hypothesis-led founders rarely match.

The reason that mattered for Bynry was that the small-utility wedge — the same wedge I had been describing — required a founder who had already learned to listen at customer-time, not at deck-time. Selling into a city of fifteen thousand meters does not look anything like selling into a Tier-1 utility. The buyer is a utility director or a city manager, not a CIO. The compliance posture is local-and-state, not federal. The reference customer is the next utility ten miles away, not the analyst at Gartner. Founders who have spent four years doing services work for customers in this segment know all of that. Founders who have not, mostly do not.

I reached out. The first conversations were not about an investment. They were about the GTM. Where the lite version of SMART360 would land first, what the rebuilt sales motion needed to look like, who the right early advisory hires were, how to think about the deployment-time-to-value as the company's structural moat. Nilesh and his team were already moving in the right direction; the role we played was to sharpen the conviction and add reps to the customer narrative.

Two things happened in that period that mattered for the eventual investment. First, I got to see how Nilesh operated in real time — how he handled customer feedback that contradicted his prior plan, how he made trade-off decisions when the engineering team wanted to add features the GTM team needed to remove, how he hired. Second, the team got to see how we worked. By the time we started talking about a round, we already had a six-month operating relationship. The pricing of conviction had been done.

3. Why we leaned in when we did

When the round did come together, the case for writing the check was not difficult to articulate. Three things stood out.

The wedge matched a thesis we had publicly committed to. AI compresses both the implementation timeline and the operating cost structure of vertical SaaS. Generative AI handles legacy data migration via OCR and template-based ingestion. AI-driven self-service portals reduce call-center volume by 60-80%. AI-assisted field-technician workflows raise productivity by 75%. Each of those operational improvements directly reduces the cost of serving a small utility, and together they make a previously impossible business model possible. This is the canonical shape of "vertical AI for an under-served market," which is the largest single conviction inside our four-pillar thesis. Bynry was not adjacent to the conviction; it was a textbook expression of it.

The moat was regulatory-and-domain-driven, not just technical. Selling software into North American municipal utilities requires trust, compliance, and political relationships. Bynry's US advisory board — which by then included a former Iowa Utility Commissioner, Swati Dandekar — gave the company the kind of regulatory credibility most foreign-built vendors struggle to earn. Domain depth and regulatory standing are the two moats that compound for vertical SaaS as it scales. The technical moat is replicable; the customer-trust-and-compliance moat is not.

The unit economics targeted a healthy SaaS shape. Bynry was targeting gross margins above 70%, contract durations of three to five years, and net retention above 100% via a tiered pay-per-meter expansion path. The land-and-expand motion was built into the product's pricing tiers rather than being grafted on as a sales tactic. The pricing was disciplined enough to support the cost structure but accessible enough to crack the segment.

We led the pre-seed.

4. What we did after the wire

The investment is the start of the relationship, not the end. Three workstreams have run continuously since the round closed.

The US repositioning. Bynry's transition from being an Indian-engineered company to being a credible US enterprise vendor required intentional repositioning. The headquarters narrative needed to shift to a US-domiciled company with an Indian engineering footprint, not the other way around. The advisory board needed to be more visible. The field-sales motion needed to be built around named US utility leaders, not generalist enterprise reps. We worked with the team on each of these threads. The company today reads as a North American utility software company that happens to have outstanding cost structure, which is the correct positioning for the buyer base it serves.

Customer introductions and ecosystem connects. Through the Callapina diaspora circle and ten-plus years of operator relationships in US infrastructure, we have made introductions both into the utility customer base and into adjacent infrastructure-software companies. The customer introductions matter for the revenue line. The adjacent-company introductions matter for hiring leads, partnership signals, and the texture of the competitive map. Customer intros are tracked per quarter and reviewed at every founder check-in.

The fundraising arc. A pre-seed lead's value to a founder shows up most clearly between rounds. We have helped frame the AI narrative for the next financing — Bynry's AI capabilities are not the marketing veneer you find in most vertical SaaS companies, they are core to the unit economics, and the framing for sophisticated investors has to make that distinction explicit. We have made introductions to follow-on capital, sat on the right strategy calls, and brought sharpness to the round structure when it mattered.

The fourth workstream — partnerships into the broader US utility ecosystem to unlock the market — is the one that will compound the most over the next twenty-four months. The North American utility space is heavily relationship-driven. Most procurement happens through a small number of consulting and integration channels, regional cooperatives, and state-level associations. We have begun introducing Bynry into those channels, starting with the operators in our network who already serve the same buyer profile. The objective is not a single anchor partnership; it is a distribution layer that gives Bynry a structural advantage when the next ten or twenty utilities are evaluating modernization.

5. The pattern this deal expresses

Bynry is, in a specific way, the cleanest expression of how Callapina is supposed to operate.

The thesis came first. We had a public, written view on where the whitespace was in this market three years before we wrote a check. Founders who match a thesis of that specificity surface in a different way than founders who match a generic search.

The relationship was built before the round. The investment was pre-priced, in operating terms, by six months of work that had nothing to do with diligence and everything to do with whether the founder and the firm could actually work together.

The post-investment work has been operational, not observational. Every quarter we can point to specific receipts — a US repositioning that closed, an introduction that produced a customer, a fundraising conversation that improved the next round. The diaspora corridor is the surface; the receipts are what make the corridor compound.

And the whole arc traces back to a piece of writing that was first published with no investment intent at all. That is, in the end, the case for thinking-out-loud as a sourcing strategy. Founders who are building toward a precise wedge in a precise market eventually find the people who have publicly written about that wedge. The investment opportunities you actually win, the ones where the relationship pre-prices conviction, tend to start three years upstream of the first cap-table conversation.

— Vinod Jose, Founding GP

The original water-utilities whitespace essay was published in September 2023 on LinkedIn. The Bynry investment closed in 2024. For more on the company itself, see the Bynry case study.