The patent before the prototype—and the long shape of Indian deep tech.
India ships software the world rents and hardware the world tolerates. Anscer is in the smaller, harder column — an Indian-built autonomous mobile robot that competes inside European warehouses on accuracy, not price. Raghu's argument is that the moat in deep tech is filed, not coded; that owning the IP at the edge of the perception stack matters more than the assembly line; and that a robotics company in Bangalore is a fifteen-year compounding bet, not a five-year SaaS sprint.
In sixty seconds.
India has built two kinds of technology companies: services firms that bill by the hour and consumer-tech firms that bet on distribution. Deep tech is a third species — capital-heavy, cycle-long, defended by patents rather than virality — and the country has never had the muscle memory for it.
Raghu's argument is that an Indian robotics company can earn its right to exist abroad by inverting the usual sequence: file the IP first, build the prototype second, win the foreign reference customer third, and only then come home for scale. Anscer's autonomous mobile robots are not cheap — they are accurate, repairable, and serviceable from Bangalore, and that combination is the actual wedge against the China-and-Europe duopoly.
The harder claim sitting underneath: most Indian deep tech dies not from a missing market but from a missing decade of patient capital. Anscer is the test of what survives if you behave, from year one, as if the next decade is non-negotiable.
Where to land in the conversation.
Each chapter opens the YouTube video at that timestamp in a new tab.
Five ideas to carry into your own work.
Mental models lifted from the conversation that travel beyond robotics. Each one is the kind of thing you can quote in a strategy meeting on Tuesday.
File before you build
The classical founder sequence is prototype, pitch, patent. Raghu inverts it. A provisional in the perception stack costs a few lakh and buys a year to figure out whether the idea is worth a real filing. The prototype that follows is now defending a claim — not generating one — and the conversation with investors and customers begins from inside the moat.
Cheap is the wrong axis
The story India tells itself about hardware is "we will be cheaper." Anscer doesn't compete that way. Their AMRs land in the same price band as European peers and undercut by being serviceable from India — twelve-hour support, in-country spares, retrofit firmware, and an engineer on a plane when the floor is down. The wedge is not unit cost. It is total cost of operating the robot for ten years.
The reference customer abroad
An Indian deep-tech founder's first real customer should be someone the next ten customers respect. A pilot inside a Tier-1 European logistics 3PL outranks ten warehouses in Bhiwandi for one specific purpose: the next German buyer will return the call. Home market scale is a different problem and a later one. The proof-of-life customer lives wherever the category already has gravity.
The Bangalore service moat
A European competitor's robot, when it breaks in Pune, ships a part from Munich on a fourteen-day lead. An Anscer robot ships a part from Whitefield by the next morning. That asymmetry — engineering, manufacturing, and service co-located in one timezone — is structurally hard to copy and structurally easy to underrate. The moat is not the firmware; it is the fact that a field engineer can land in Frankfurt the same week.
"Capital with patience" vs "capital with a clock"
SaaS pattern-matching from Indian VCs collapses on deep tech because the unit economics never look right at year three. The right partner is a fund that has done a fifteen-year hold before — Speciale Invest, a few corporate venture arms, a sovereign wealth office, the rare strategic angel. The wrong partner is anyone whose return model demands a 2028 exit.
Fifteen things to actually walk away with.
Each one carries the timestamps where the moment lives, and a transferable note for work that isn't robotics.
India ships software well; it has barely begun to ship hardware.
Vishal opens with the diagnosis that frames everything else in the conversation. India is the largest exporter of services and one of the largest exporters of software talent. It has not, in any matching sense, learned to ship physical product that the rest of the world buys from it. Raghu doesn't argue with the diagnosis. He sharpens it. The gap is not capability — Indian engineers built the Mars Orbiter and the Chandrayaan landers — it is the absence of an investor and procurement environment that funds a five-year build before a single revenue dollar.
The reframe matters: hardware is not waiting for a clever founder. It is waiting for an institutional patience that no Indian fund has yet supplied at scale. Anscer exists in the small window where that patience is finally beginning to appear, at funds like Speciale Invest and the new deep-tech vehicles inside Lightspeed and 3one4.
An autonomous mobile robot is not a self-driving car.
Raghu spends a careful minute pulling apart the two categories most people in the conversation will conflate. A passenger AV operates in an open world with unbounded edge cases — pedestrians, weather, regulation. An AMR operates in a constrained one: a warehouse floor, a hospital corridor, a factory aisle. The planning problem is different, the safety case is different, the regulatory path is different, and the unit economics are completely different. AMRs are profitable in 2026; passenger AVs are still subsidised research projects.
The deeper point: deep-tech founders in India should look for the constrained twin of every glamorous unsolved problem. The constrained problem has a buyer, a contract template, an insurance market, and a path to gross margin.
Patents are filed before prototypes are wired.
The most counter-intuitive habit Raghu describes. Most Indian hardware founders treat a patent as a victory lap — something to file once the device is working and a customer has bought one. Anscer files the provisional months before the soldering iron is plugged in. The cost is small. The benefit is enormous: by the time the prototype exists, the IP is already cited in a USPTO database, the priority date is locked, and the next conversation with a strategic investor or a foreign acquirer starts inside a defensible position rather than next to one.
There is a quieter consequence. The discipline of writing the claim forces clarity about what the invention actually is. A team that cannot describe its novelty in patentable language usually has not yet found its novelty. The filing is a thinking tool, not just a legal one.
The BOM is the strategy.
Raghu walks through the bill of materials of an AMR with the calm of someone who has rebuilt the spreadsheet a dozen times. The LiDAR is a commodity from a half-dozen vendors in Shenzhen, Korea and Germany. The motor controllers are increasingly Indian. The chassis is local. The wheels are local. The compute is the obvious imported expense and the firmware on top of it is the value capture. The question is not "can we make this in India," it is "which line of the BOM do we want to own and which do we want to buy in volume."
The strategic frame: every Indian hardware founder should be able to point at the BOM and say which two or three lines hold the patent moat, which lines are pure commodity, and which lines are the firmware-on-silicon hybrid where the IP actually lives. If you can't draw that picture, you don't have a hardware company; you have an assembly line.
The first reference customer should outrank the next ten.
The most useful piece of go-to-market advice in the conversation, told sideways. Anscer chose to chase a small pilot in a European 3PL ahead of larger, easier contracts in India. The pilot lost money on a per-deal basis. It made the next year of deals possible. The principle Raghu names: a reference customer whose logo is recognised by your next ten prospects is worth more than three customers whose logos are not.
For Indian deep tech specifically, the asymmetry is severe. A German warehouse signing off on an Indian AMR is, in itself, a market signal that the rest of the Western buying universe can read. The reverse is not true. Ten warehouses in Hyderabad do not buy you a single conversation in Stuttgart.
Service from India is the structural moat.
The line Raghu returns to twice. A European AMR vendor has the firmware and the brand. They do not have a service organisation that can land a field engineer in Mumbai by the next morning. Anscer can. Once a Western 3PL has rolled out a fleet in an Indian or Southeast-Asian facility, the cost of switching is not the firmware — it is rebuilding the service relationship. That is a moat that compounds with every robot shipped.
The further implication: Indian deep-tech founders should treat the service organisation as a first-class product, not an after-sales cost centre. Spares stocking, remote diagnostics, retrofit firmware, training programs — these are the artefacts that turn a one-time hardware sale into a fifteen-year customer.
Defence and dual-use are a quieter revenue stream than they look.
Raghu is candid about the appeal of defence procurement — DRDO, the iDEX program, the Make-in-India defence corridor in Tamil Nadu — and equally candid about the cost. Defence contracts have long evaluation cycles, high evidentiary bars, and brutal payment terms. They pay eventually; the working capital required to wait is the kind of money a software company never needs. The right way to approach defence is as a slow, prestige-laden second business unit, not as a near-term cash engine.
The deeper observation is about dual-use. An AMR designed for warehouses can, with a different chassis and a hardened compute stack, become a logistics robot for a forward base. The IP travels. The Bureau of Indian Standards work travels. The customer doesn't.
Bangalore's hardware stack is finally legible.
A quietly important observation buried halfway through the conversation. A decade ago, an Indian hardware founder could not, in a single trip across Bangalore, find a CNC house that did short runs, a sheet-metal shop, a PCB assembly line, a motor-controller vendor, and a firmware contractor who knew ROS. In 2026 they can. The stack is not yet at Shenzhen's density, but it is no longer the open question it was. The supplier ecosystem that ATL, Tonbo, Cyient, Bharat Forge and a hundred smaller shops created over fifteen years is what Anscer is drafting on top of.
The framing matters because every Indian deep-tech narrative now has to acknowledge what the previous generation built. The current cohort is not pioneering. It is the second wave on top of a supply base laid by the first.
The China-plus-one window is real, narrow, and not what most founders think it is.
Raghu is sober about the geopolitics. Yes, Western buyers are diversifying out of China. No, they are not doing it by ordering twice as many Indian robots. They are doing it by qualifying Indian, Vietnamese and Mexican vendors as second sources — small allocations, long qualification cycles, painful audits. The right reading is that the door is propped open, not flung open. The founders who walk through are the ones who can survive the eighteen months of qualification work before the first real purchase order arrives.
The corollary: any pitch deck that says "China-plus-one" without describing the qualification path is gambling on a tailwind it has not earned the right to use.
The PLI scheme is a useful subsidy, not a strategy.
Raghu's reading of the Production Linked Incentive scheme is unsentimental. It is real money on the table — disbursed against actual manufacturing output — and it changes the BOM math at the margin. It does not, in any meaningful sense, decide which Indian hardware companies survive. A robotics business whose unit economics only work with the PLI rebate is a business whose unit economics don't work. The subsidy is a tailwind, not a thesis.
This is the thing he most wants the next cohort of founders to hear. Government schemes solve a financing problem, not a product problem. A company that gets confused about which is which will be in trouble the day the policy changes.
The fifteen-year founder timeline is a feature, not a warning.
The single sentence in the conversation that should be quoted to every Indian SaaS investor who tries to fund a hardware company. Raghu says, plainly, that Anscer is a fifteen-year company. Not five. Not seven. He is not negotiating. The unit economics, the patent moats, the service organisation, and the certification stack each take three to five years to mature. A founder who privately believes they will be done in six is going to make decisions that destroy the company in year nine.
The frame travels. Founders should not adopt timelines because their investors prefer them. They should adopt the timeline the underlying physics demand and then find investors who can live with it.
ISO 9001 and CE marking are admission tickets, not differentiators.
One of the most useful pragmatic notes in the conversation. An Indian AMR cannot be sold into a German warehouse without CE marking, an ISO 9001 quality system, and a machinery-directive conformity assessment. None of this makes the product better. All of it costs eighteen months and a meaningful chunk of equity. The founders who underestimate this line item end up raising a "manufacturing" round that is in fact a "certification" round in disguise.
The mature reading: budget for certification the way a SaaS company budgets for SOC 2 — as a non-negotiable, planned, scheduled engineering project with a named owner and a real deadline. Treat the audit as a build, not a tax.
The hard part isn't the robot. It's the warehouse around it.
The most quietly humbling line in the episode. Raghu describes integrating an AMR fleet into a customer warehouse as a six-month project where the robot itself is two months and the warehouse — the WMS, the racking layout, the safety procedures, the union conversations, the night-shift training — is four. The product is technical. The deployment is sociological.
The structural implication for any robotics founder is that the team must contain people who have run a warehouse, not just people who have built one. Without that knowledge in the room, the company will design beautiful robots that the floor refuses to use.
"Make in India" is a slogan; "design in India" is the actual ambition.
Raghu separates the two phrases that most policy conversations conflate. Make-in-India is about the assembly line — the final-mile manufacturing step that adds five to ten percent of the value. Design-in-India is about the IP — the perception stack, the planner, the safety case, the proprietary firmware — where forty to sixty percent of the value sits. India can be a Make-in country without being a Design-in country; many of its electronics factories already are. Anscer is built to be both.
The distinction matters because investors and policymakers measure each differently. PLI rewards the first. Patent filings and IP-backed revenue reward the second. A founder who confuses the two will optimise for the wrong incentive.
The right investor has done a hardware exit before.
Closing his thoughts on capital, Raghu describes the test he applies to a prospective lead investor. Have they previously held a hardware company for nine years and made money on it? If not — if their wins are all SaaS — they will, with the best intentions, push for decisions that look like SaaS playbooks: aggressive marketing spend, headcount-led growth, multiple-expansion via narrative. Those moves kill hardware companies. The right fund has a track record of patience that no amount of conviction at the partner meeting can substitute for.
The advice cuts harder than it reads. Most Indian founders cannot afford to be picky about investors. Raghu's point is that, in deep tech, you cannot afford not to be picky.
Lines worth keeping near your desk.
The jargon, unpacked.
Some of these will be obvious; some won't. Skim, mark the unfamiliar, come back later.
Check what you actually retained.
Try to answer before you click. The point is to notice where the conversation is fuzzy in your memory, then return to the transcript.
Five questions worth sitting with.
No correct answers. Type into the boxes — your responses are saved locally in this browser.
Raghu files patents before prototypes. Where in your own work could "write the claim first" be the discipline that surfaces what you're actually building?
Anscer wins on serviceability from India, not on price. What is the meter your buyers haven't yet been measuring on — the axis where you would win uncontested?
A small German pilot beat three Indian contracts as a reference. Which single customer in your market would, if won, make the next ten conversations easier?
The fifteen-year frame is dictated by physics, not preference. What is the honest minimum timeline of the thing you are building — and does your cap table know?
"The robot is two months; the warehouse is four." Where in your product is the sociological work hiding underneath the technical one — and who on your team has actually lived it?
Where to push back.
The strongest version of each disagreement, written to be persuasive — not to win.
"File patents before the prototype."
The counter is that the relevant moat in robotics is rarely a single patent claim — it is the integration of perception, planning, mechanical design, and field-tuned firmware that no patent could fully describe even if it tried. Strong patent portfolios in industrial robotics belong to ABB, Fanuc, and Kuka; they did not stop Universal Robots or Mobile Industrial Robots from eating the cobot and AMR markets. The patent is useful as a negotiating instrument and a defensive shield, but the durable advantage is in tacit engineering knowledge, not in claims filed at the USPTO. Spending months on filings before there is a working prototype is also a way to defer the only test that matters: does the machine work on a real floor.
"Serviceability from India is the moat."
The steelman against this: any large vendor can buy or build an India service base in eighteen months once the category becomes worth the spend. KION already operates field engineers across South Asia for its forklift business. Geek+ and Locus Robotics could replicate the model with a single round of capex. The Bangalore service advantage is real today; it is not durable past the moment a competitor decides the market is worth defending. The truly durable moat is whatever Anscer learns about Asian warehouses in those years that a competitor cannot acquire by hiring — and that is a much narrower claim than "serviceability from India."
"India needs patient capital it doesn't have."
The push: the capital exists; it is just not packaged as venture. Indian family offices have held hardware businesses for thirty years — Bharat Forge, Sona Comstar, Tube Investments. Sovereign vehicles like the National Investment and Infrastructure Fund will deploy patient money against the right thesis. The constraint is not capital quantity but capital format — founders need to learn to raise from sources that are not VCs, not the other way around. Treating "patient venture" as the only honest format is a narrowing of the funding stack that hurts the conversation.
"Defence is a prestige slow lane, not a cash engine."
The counter is that the cash dynamics of defence have shifted under the iDEX programme and the increased pace of MoD procurement post-2020. Companies like ideaForge, Tonbo, and BharatRobotics have grown defence revenue lines faster than any commercial channel. Treating defence as a prestige slow lane is, in 2026, an older lens. For a robotics company with a credible dual-use story, defence may in fact be the fastest path to revenue scale — the slower path is the European commercial certification cycle. The hierarchy depends on which segment is moving faster in the specific year a founder chooses.
Three angles on Monday morning.
If you don't work in robotics, here's what to take.
If you're a founder
- Write the patent claim before you write the code. If you can't describe the novelty in claim language, you haven't found it yet.
- Identify the single foreign reference customer whose logo would unblock your next ten conversations. Price the first sale as marketing.
- Read your BOM the way an investor reads your P&L. Mark which lines are commodity, which lines hold the IP, and which lines are firmware-on-silicon.
- Match investor track record to your business physics. A SaaS fund will, in the hard quarter, try to make your hardware company behave like a SaaS company. That moment breaks companies.
- Treat certification (ISO 9001, CE, UL) as a planned engineering project with a named owner. Audit calendar is product roadmap's twin.
If you're an engineer
- Learn ROS 2, then learn the BOM. Most robotics engineers know one of these well. The job changes the day you know both.
- Spend a week inside a working warehouse before you design anything for one. The four months are not technical; they are sociological.
- Treat service infrastructure as a first-class product. Spares stocking, remote diagnostics, retrofit firmware — these are artefacts, not chores.
- Map your supplier base. The Indian hardware stack only became legible because hundreds of engineers spent fifteen years building it. Know which vendors you couldn't have started without.
If you're an investor
- Ask the founder to draw the BOM on a whiteboard. If they cannot name the patent-holding lines and the commodity lines, they don't have a hardware thesis.
- Insist on a defensible patent filing strategy with priority dates and jurisdictions before the Series A, not after it.
- Test for "patient capital coherence" — does the founder's timeline match the fund's hold horizon? A six-year founder in a fifteen-year company is a mistake waiting to happen.
- Discount any pitch that uses "China-plus-one" without describing the qualification path. The tailwind is real and slow; the deck is fast.
- Audit the service organisation alongside the engineering org. In hardware, the second is a product the first cannot replace.
A decade of Indian deep tech, briefly.
The arc that frames Anscer's window.
The whole conversation, searchable.
Click a timestamp anywhere on this page to open YouTube at that moment. Full transcript will be added in a later pass.