Dhruvil Sanghvi once wondered what the catch was. He had found experienced software founders willing to spend two days helping younger companies, and the arrangement seemed suspiciously generous. They had businesses to run. He had questions about growing his. Surely, at some point, somebody would ask for equity.
They did not. Sanghvi kept asking anyway. Years later, after he had begun mentoring founders himself, he understood the transaction. There was no invoice. The explanation had required participation.
It is an appealing detail about a founder whose working life concerns the efficient movement of things. Sanghvi built LogiNext around making delivery operations more predictable. His own education in entrepreneurship included a service whose value he could not initially calculate: somebody else's time, freely given.
A family business, with a different syllabus
Business was familiar territory long before software became his profession. His father, grandfather and great-grandfather had each been involved in business. As a teenager, he accompanied his father and watched how the work got done. The expected academic direction was commerce. In class eleven, Sanghvi chose science instead, drawn to mathematics, physics and computers.
That decision gave the family tradition a technical vocabulary. He went on to study computer science and engineering at Nirma University, in the 2006-2010 cohort, then information systems management at Carnegie Mellon. The combination placed him between two useful ways of seeing a company: as a commercial undertaking and as a collection of systems that might be improved.
At Carnegie Mellon he met Manisha Raisinghani, his eventual LogiNext co-founder. He also gained exposure to startup competition. Consulting work at Deloitte and Ernst & Young subsequently brought him into contact with the less photogenic side of enterprise technology: existing workflows, inherited tools, decisions that had to be made again tomorrow.
His later account of the idea starts with several changes arriving together. Smartphones were becoming commonplace. Customers increasingly expected services to come to them. Waiting patiently for a delivery was losing its appeal. The people running those deliveries needed a way to keep up.

The package had a head start
The problem Sanghvi chose has an awkward relationship with presentations. A proposed route can look immaculate on a screen. Then a vehicle fills up, an address proves troublesome, or the next order arrives before the previous one has been assigned. The customer sees a late delivery. The operator sees a series of decisions that have stopped fitting together.
In a 2017 explanation of LogiNext's work, Sanghvi described matching loads, vehicle types, people and arrival times across a distribution network. Different shipments and places required different approaches. Clothing in Singapore and groceries in Jakarta could hardly be expected to obey one convenient set of assumptions.
His ambition was to make the software useful before an operation went wrong. Knowing where a truck is helps. Deciding what it should carry and where it should go next asks more of the system. That distinction gave LogiNext a practical sales argument: better decisions throughout the journey.
There was still the matter of being believed. In a 2016 account, Sanghvi recalled prospective customers questioning whether a young company could deliver what it promised. His team's response was to arrive with analysis of inefficiencies in delivery networks. The pitch became more concrete when the discussion concerned the customer's own bottlenecks.
Plan capacity02
Assign a driver03
Choose a route04
Track & confirm
One customer promise. Several connected decisions.
Conceptual workflow, not measured performance.For an enterprise buyer, confidence has to survive beyond the demonstration. Software enters a business with established routines and people who understand exactly how inconvenient a new tool can be. A useful product has to make sense in that working day, as well as in the meeting where it is purchased.
It also helps explain why his consulting background mattered. He had worked close enough to enterprise operations to see a potential customer before there was a product to sell. The opportunity lay in a recognisable job, performed repeatedly. The difficult next step was turning that knowledge into something another organisation would trust with its deliveries.
The driver gets a vote
Sanghvi's 2020 recollection puts the human difficulty plainly. Delivery associates had habits. Asking them to switch to LogiNext involved more than winning permission from senior management. He described faster reimbursements, incentives and additional delivery opportunities as reasons the change could become worthwhile for drivers.
That is a revealing emphasis for someone selling automation. The person at the wheel still has to use the application. A dispatcher's better dashboard cannot, by itself, settle the driver's objections. Adoption has to travel through the organisation, reaching people who never attended the sales meeting.
The platform's connected web and mobile applications address different participants: dispatchers, shippers, drivers and customers. Sanghvi has described problems ranging from incorrect address mapping to manual records and limited operational visibility. These are modest phrases for the everyday work of getting something to the correct door.
His interest lies in the connections between those jobs. A delivery can be planned, assigned, followed and confirmed. Each stage produces information that matters elsewhere. The attraction of a shared software product is that a recurring operational problem can be addressed across customers, rather than rediscovered separately in every business.
A cheque, then a harder assignment
LogiNext's early work took shape in 2014, followed by its 2015 launch. Seed backing came through Indian Angel Network, with Sanjay Mehta among its early supporters. Paytm backed a $10 million round in 2015. In January 2020, Tiger Global and Steadview Capital supplied a further $39 million, bringing reported funding to about $50 million.
By that 2020 round, customers included McDonald's, Decathlon and Singapore Post. Sanghvi's commercial focus was on traditional businesses seeking capabilities that technology companies could build internally. Selling them a subscription meant offering a way to improve delivery without first assembling a software organisation of their own.
Historical rounds, shown on the same scale. Funding measures capital raised; it does not measure personal wealth.
Recognition arrived along the way: Forbes India included Sanghvi in its 2017 30 Under 30 selection; Entrepreneur India's 35 Under 35 followed in 2019. Those dates mark a public career becoming visible. Inside a growing company, the next assignment was less ceremonial: learning to let other people make decisions.
By March 2023, he was describing management as something he had learned through trial. Working alongside a handful of early employees was different from directing an organisation. Delegating could feel like surrendering control. His response was to give people responsibility while retaining a habit of checking the relevant measures.
“That’s when I learnt the art of trust but verify.”
Dhruvil Sanghvi, 2023
He also discussed teaching employees about gross margin and recurring revenue, so they could understand the commercial consequences of their work. The underlying proposition is sensible: people make more useful decisions when somebody explains what the business needs those decisions to accomplish.
There is an interesting relationship between that management lesson and the product he sells. A logistics platform makes work visible across an operation. A growing company needs some of the same visibility, without requiring its founder to intervene in every task. In both cases, a system earns its place by helping someone make the next decision.
The free advice he eventually understood
The mentoring episode belongs here, because it concerns another kind of control: the belief that every exchange needs an immediately legible return. When LogiNext was around $1 million in annual recurring revenue, Sanghvi travelled from Mumbai to Bengaluru seeking people who understood the next stage of a software business.
He encountered founders whose companies had already crossed $10 million in recurring revenue. At first, he doubted the explanation that they simply wanted to help. Eventually, he began helping others and came to recognise the satisfaction himself. SaaSBOOMi later documented his participation as a mentor in its SGx initiative.
The doubter became part of the arrangement he had doubted. There is a small comedy in that conversion, and a useful account of how entrepreneurial knowledge moves: through questions, examples and repeated conversations, often outside the formal machinery of investment.
His public interests also extend beyond software sales. Asked in 2016 about favourite destinations, he named Alaska, Hawaii and the Himalayas. On LinkedIn, his writing has recruited both Star Wars and Narcos into explanations of logistics. Apparently, a supply-chain problem can be found almost anywhere if one is sufficiently determined.
The road after the funding headline
A founder's story also includes the passages that resist a tidy upward line. In August 2024, an account of LogiNext's corporate affairs described an asset sale to Stellation Inc. for $250,000 as part of a liquidation process. Sanghvi disputed the reported numbers and statements, said clients and employees remained operational, and denied layoffs. The disagreement is part of the public record.
The current LogiNext website identifies its operator as Stellation Inc. dba LogiNext and continues to market delivery software. That confirms the name under which the site operates; it does not settle every disputed detail of the earlier account. The funding milestones and this later corporate chapter belong on the same page.
Earlier interviews had included an ambition to take the company public. Such a goal describes what a founder hoped to build at a particular moment. Reading it beside the later corporate chapter gives the career its proper chronology, with aspirations kept distinct from completed events.
Sanghvi has continued speaking and writing. A March 2025 podcast explored his upbringing, the founding decision and building a software business from India. In a May 2025 essay, he argued that falling costs and easier tools could bring logistics AI within reach of smaller businesses. A July 2025 interview addressed the vulnerabilities created by increasingly connected supply chains.
These concerns return to the question that made his career: who gets access to useful technology, and what happens when it enters an existing operation? There are customers, drivers, managers and founders to persuade. Sanghvi has spent years trying to make their decisions fit together. Even free advice, he discovered, sometimes needs a little time to reach its destination.
Follow the conversation
Interviews, writing and public profiles.