Pain today
Field visits still depend on paper checklists, scattered photos, manual report preparation, and messaging-driven follow-up.
Snapshot
A focused entry point with immediate operational pain and recurring software value.
Aegis SaaS starts where visits, evidence, approvals, and retrievable records all need to stay connected. That makes the first product practical now and expandable later.
Who feels it
Technicians, operations teams, customer reviewers, and finance workflows all suffer when service evidence is fragmented.
Why software fits
Every service cycle creates new work assignments, new evidence, new approvals, and new records that benefit from a shared system.
Why it can expand
Once the operator trusts the system of record, analytics, compliance, reporting, and adjacent maintenance workflows become easier to layer on.
Product
Solar Sanchalak turns field execution into retrievable, approval-ready records.
The product is designed to reduce paperwork friction, improve evidence quality, speed approvals, and create a stronger record across multi-site solar maintenance operations.
Without a system of record
Field work gets completed, but the proof does not travel cleanly.
- Evidence stays fragmented across devices and chats
- Report preparation becomes a separate manual task
- Approval cycles slow down because proof is weak or incomplete
- Historical retrieval and portfolio analysis remain difficult
With Solar Sanchalak
Mobile capture, workflow state, and sign-off stay connected.
- Technicians capture readings, photos, notes, and signatures in one flow
- Operations teams review structured records instead of scattered proof
- Customers receive clearer, approval-ready service evidence
- Organizations build a retrievable operational record over time
Technician mobile app
Designed for field capture, low-friction evidence collection, and visit execution where connectivity may be inconsistent.
Workflow and approval engine
Assignment, validation, review, and state transitions stay structured instead of being spread across manual follow-up.
Reporting and record layer
Signed reports, historical retrieval, and audit-friendly service records become part of the same platform logic.
Workflow
The product closes the loop from field visit to approved record.
The value is not one isolated screen. It comes from keeping field execution, evidence, validation, reporting, and retrieval connected as one operational flow.
- Dispatch and assignment Create or assign work with the checklist, role context, and workflow state already attached.
- Capture on mobile Technicians record readings, photos, notes, and signatures while the job is actually being performed on site.
- Validate and structure Evidence syncs into a tenant-scoped record where it can be validated, linked, and prepared for reporting.
- Review and sign off Operations teams and customer-side reviewers see clearer proof and a more disciplined approval path.
- Retrieve and analyze Historical visits, signed reports, and structured evidence stay available for future retrieval, analytics, and follow-through.
Proof
This is already more than a concept narrative.
The public site should convey serious product posture without turning into internal engineering documentation. These are the strongest current proof points.
Built already
- Multi-tenant backend and role foundations
- Technician submission and reporting flows
- Digital signature ingestion and signed record generation
- Notification, validation, and deployment discipline
Public proof surface
- Dedicated architecture page with system context
- FAQ, privacy, and terms pages already live
- Documentation surface at docs.aegis-saas.com
- Homepage messaging aligned to the actual product direction
Active build focus
- AI-assisted OCR and evidence extraction
- Geo-validation and field-quality controls
- Offline-capable mobile refinement
- Stronger analytics and management visibility layers
Founder
Operator context plus enterprise systems depth.
The product direction is grounded both in observed solar AMC workflow friction and in a longer background in platform and systems design.
Operating context
Built from observed workflow friction inside solar EPC and AMC operations.
Solar Sanchalak did not begin as a generic field-service idea. It grew from direct exposure to the gap between completed field work and credible, approval-ready proof.
- Field pain points observed directly
- Approval bottlenecks understood firsthand
- Reporting needs shaped by operational reality
- Workflow logic tied to real service execution
Founder
Manish Soni
Founder, Aegis SaaS
20+ years across telecom systems, enterprise architecture, and large-scale platform design, now focused on building Aegis SaaS and Solar Sanchalak.
Next Layer
Follow the product as the public proof surface expands.
The public site is intentionally high level. Architecture, FAQ, and documentation already provide a stronger preview of the product direction while the broader platform continues to ship.
View Docs
Read FAQ
For introductions or investor context, Manish Soni can
currently be reached through LinkedIn.
Internal APIs and production application interfaces are still under active development and are not publicly exposed through this site.