The India Stack Lens Applies Here Too
Jaideep Bansal's Azista SpaceTech waited 18 months for regulatory clarity before building hardware. He didn't rush beta. Most founders do—and waste capital.
The mistake: treating this like a SaaS launch. You cannot iterate fast on orbital mechanics. Regulatory gatekeeping isn't friction. It's the product itself.
Phase 1: Regulatory Sandbox (Months 1-6)
File with IN-SPACe immediately. Not after you have working hardware. Before.
This isn't bureaucracy theater. The portal now has 14 active applications. Competition for attention slot is real. Early filers get assigned ISRO liaisons faster.
Second: identify your specific regulatory constraint. Launching from Indian soil? Get SADA (Security Approval and Clearance) from DCMA. Using foreign ground stations? Need GAGAN integration testing. Carrying classified payload? ISRO's institutional review takes 6+ months.
Don't guess. Call the specific department. Write down names.
Phase 2: Anchor Tenant Pre-Commitment (Months 3-9)
A waitlist of 50 startups means nothing in space tech. One signed LOI from a government ministry means everything.
Target: Indian Railways, Power Ministry, or Disaster Management Authority. They need satellite imagery. They have budget. They move in fiscal year cycles.
Ground truth: Skyroot's success came partly because ISRO agreed to launch their demo flight before full certification. That was public commitment. It shaped everything downstream.
Approach one ministry per quarter. Give them a free trial dataset. Three months. No strings. Then cost of commercial service becomes concrete comparison, not abstract.
Phase 3: Insurance and Financial Close (Months 6-12)
Insurance isn't optional overhead. It's a customer requirement.
An 800 kg satellite costs roughly 50-80 crores to build and launch in India. Insurance premium: 4-10 crores. Most space companies absorb this in pricing.
The actual problem: your insurance broker doesn't understand Indian space sector. They'll quote you rates fit for aviation. Find a broker who worked on PSLV insurance cases. Not optional.
Close insurance 3 months before launch window. Underwriters need payload documentation, launch provider certification, and ground control procedures. Parallel this with regulatory approval—don't sequence it after.
Phase 4: Data Infrastructure and Ground Testing (Months 6-15)
Like Paytm had to build backend infrastructure before consumer beta, you need ground infrastructure finalized before orbital operations.
Requirement one: data downlink stations. India's Bhubaneswar and Sriharikota ground stations must test your satellite pass sequences. This takes 60-90 days. Request slots now.
Requirement two: command and control facility. ISRO won't hand over operational control until your facility passes security audit. Budget 2-3 crores for hardware. Timeline: 4 months minimum.
Requirement three: APIs and customer dashboards. Your first customers are government agencies with legacy systems. You cannot ask them to use your mobile app. Build government-grade APIs. Test with one internal ministry first.
Phase 5: Limited Orbit Beta (Months 12-18)
Now—finally—beta. But not 100 customers. Maybe 3-5.
Definition: one government customer, one commercial customer, one internal validation.
Timeline: 90 days minimum. You need full orbital cycles. Satellite passes over India roughly 14 times per day. You need 1,000+ passes of clean data before scaling.
Metric that matters: downlink success rate. Target 98% minimum. Government won't accept 95%.
Phase 6: Pricing and Commercial Launch (Months 18-24)
Price starts with cost structure, not market research.
Cost of operations: 15-20% of satellite capex annually. Add insurance (8-12%). Add ground station fees (2-3%). Add margin (30-50%).
For an 800 crore satellite, annual operating cost runs 120-160 crores. Divide by customer slots. Pricing emerges.
Compare: Skyroot charges ~100-200 crores for dedicated launch slots. Not because market supports it. Because each slot needs insurance, regulatory approval, and launch window optimization.
Phase 7: Community and Regulatory Narrative
PR happens at regulatory inflection points, not at beta.
When you clear SADA: announce publicly. When you get anchor customer LOI: announce. When launch date confirmed: announce.
Journalists covering space tech understand the sector's physics. They care about regulatory breakthroughs, not feature releases.
Second: build engineering credibility with IIT community. Hire from space labs. Publish satellite performance data in IEEE. Government customers trust educational institution connections.
The Core Implication
Space tech founders who treat this like B2B SaaS fail. Regulatory approval isn't a side project. It's the product roadmap for months 1-18.
Your competitive advantage: starting regulatory conversations six months before your competitor. Most won't. You will.