Chota Kisan Robotics Pvt. Ltd.

A clear-eyed look at where they stood.

Chota Kisan Robotics Pvt. Ltd. is building affordable automation for small and marginal farmers, an agritech robotics play where the core cost isn’t marketing or headcount, it’s hardware. Every design iteration means new components, new field trials, and new failure modes to fix before the machine can go anywhere near a working farm. That kind of product development is capital-hungry well before there’s revenue to point to, and the founders needed money to keep building without giving up equity at a stage where the product itself was still the main risk to price in.

The Startup India Seed Fund Scheme exists for exactly this gap: grants up to ₹20 lakh, or convertible debentures up to ₹50 lakh, disbursed through a DPIIT-approved incubator on one route or the other, never both. But a SISFS application is not just a funding ask. It has to show a grant-permitted use of funds, tie spending to a phased milestone plan, and back the whole thing with financial projections a committee can sanity-check. Get the categorisation wrong, or leave the milestones vague, and the file stalls in review regardless of how good the underlying technology is.

For a hardware startup, that’s a real trap. Prototyping and field testing span a wide mix of spend, materials, fabrication, testing time, and it’s easy to draft a budget that reads as scattered rather than staged. Chota Kisan needed the proposal built so the incubator committee could see a clear line from rupees to milestones to a working product, not just a number.

CapEasy prepared the SISFS grant proposal from the ground up. That meant building a grant-permitted budget that covered product development and prototyping, structuring it against a phased milestone plan rather than a lump sum, and putting financial projections behind the ask so the numbers held together end to end.

The bigger part of the work was alignment: making sure the application matched the scheme’s eligibility criteria and its permitted-activity rules before it ever reached a reviewer. SISFS committees read for exactly this, whether the stated use of funds sits inside what the scheme is designed to fund, and whether the milestone structure is specific enough to actually monitor disbursement against later. An application that’s technically eligible but loosely worded on activities and milestones is still a weak application.

For a robotics venture, that meant being precise about what counted as prototyping spend versus what didn’t, and phasing the milestones around real engineering checkpoints rather than generic calendar quarters. The goal was a document a committee could review quickly and approve with confidence, not one that needed a round of clarifying questions.

Milestone-based structuring also matters because it’s how the money actually arrives. SISFS funds release against milestones, not as a single upfront transfer, so a proposal that treats the plan as a formality rather than the disbursement mechanism sets the startup up for friction later, even after approval.

The outcome

Chota Kisan Robotics was approved for a ₹15 lakh SISFS grant through the NSUT incubator, with funds milestone-released against the plan built into the application.

A Seed Fund approval is the incubator committee’s sanction, not a cheque in hand. Actual disbursement follows the scheme’s own due-diligence and compliance milestones, and it isn’t guaranteed simply because the application was approved. That’s the nature of milestone-released funding, and it’s worth understanding going in rather than assuming approval and disbursement are the same event.

What made it work

The proposal held together because the budget, the milestones, and the projections were built as one connected story rather than three separate sections. A committee reviewing a hardware grant application is looking for that coherence in particular, since prototyping costs are easy to misclassify and milestones are easy to leave vague.

Getting the eligibility and permitted-activity fit right before submission meant the application could be evaluated on the strength of the venture, not delayed by avoidable formatting or categorisation questions.