Service architecture
Three high-value use cases, one controlled operating model.
Spray
Guided from request to verified closure.
Map
Guided from request to verified closure.
Inspect
Guided from request to verified closure.
Sky-led drone operations
Premium aerial work, coordinated above the field.
Sortie gives drone services a sharper operating layer: public trust, guided pilot execution, dispatch control, and completion proof that does not depend on guesswork.
Mission airspace
Live readiness
Coverage92% route context
Evidence4 records required
ControlNo skipped states
Pilot action locked
Next step appears only when the sequence allows it.
Backend-enforced mission states
Direct evidence uploads
Server-side pricing discipline
Pilot-first field actions
Static public website
Completion proof before closure
Services
A public face that feels as precise as the work in the sky.
The website frames the promise clearly while real booking, tracking, pricing, and execution remain inside the role-specific product surfaces.
Field ready
Crop spray
Coordinated spraying missions with acreage context, pilot assignment, and a final executed-area record.
Crop and acreage context
Scheduled pilot dispatch
Executed area record
Clear capture
Mapping
Aerial capture for boundaries, terrain, progress, and land intelligence that needs reliable visual context.
Boundary documentation
Site progress visibility
Aerial evidence archive
Proof led
Inspection
Repeatable inspection workflows for assets where visual proof matters more than unstructured field notes.
Asset-grade evidence
Before and after capture
Operations review path
Workflow
Every mission moves through a deliberate flight path.
The sequence stays readable for customers, practical for pilots, and enforceable for operations.
1
Confirmed
Customer
2
Assigned
Ops
3
En route
Pilot
4
On site
Pilot
5
In progress
System
6
Completed
System
No skipping
Each state follows the previous one.
Role clarity
Customer, pilot, ops, and system actions stay distinct.
Proof gate
Completion waits for every required evidence record.
Customer app
Request services, follow mission state, and receive completion proof.
Pilot app
Move through guided actions, submit proof, and close work from the field.
Admin console
Assign pilots, monitor exceptions, and preserve the operating sequence.
Command layer
Public brand, field execution, and admin governance stay aligned.
Platform
A premium website wrapped around a serious operating system.
The landing page can be beautiful because it does not pretend to be the product backend. It points people to the right app, then lets the system enforce the rules.
Dispatch integrity
Operations assigns pilots and watches exceptions without breaking state order.
Pilot ergonomics
The field app narrows the pilot experience to the next valid action.
Completion discipline
Evidence, final area, and system checks define closure.
Completion proof
A mission closes only when the evidence package is whole.
The public promise is simple, but strict: guidance can happen in the interface; verified completion is decided by the system.
Checklist
Readiness is recorded before active work can open.
Before photo
The initial site condition is captured at the mission location.
After photo
Completion is backed by a visual record from the field.
Final area
The executed area is stored as a numeric completion record.
Checklist recorded
Before recorded
After recorded
Area recorded
Evidence package ready
Completion can now be released by the system.
Pricing model
Clear inputs without a fragile public calculator.
Sortie can explain how pricing is shaped without publishing hardcoded rates. The actual quote belongs to the product system, where mission context is evaluated correctly.
Service type
Area or acreage
Crop or site context
Location
Mission date
Product rule
Final quotes are calculated by the product system, not the marketing site.
Apps
One brand, three work surfaces.
Customers request and track from mobile. Pilots execute assigned work in the field. Operations manages dispatch, exceptions, and governance from the admin console.
Customer app
Request and track
Choose service
Spray, mapping, or inspection
Track progress
Clear state-by-state movement
Receive proof
Photos, checklist, and final area
- Confirmed
- Assigned
- En route
Pilot app
Execute and upload
Next action
Only the valid step is shown
Submit proof
Checklist, photos, and area
Close mission
Completion follows evidence
- Confirmed
- Assigned
- En route
Contact
Start with the mission context. We will route the right next step.
Share the service type, location, and timeline. The website does not store form data; it opens a prepared email so the enquiry stays in your mail client.
hello@sortie.in
Customer enquiries
App links soon
Launch channel
Partner route
Pilot onboarding
FAQ
The important boundaries are clear before launch.
Can customers book on this website?
No. This is the public marketing site. Booking and tracking belong in the consumer mobile app.
Does the site calculate final prices?
No. The website explains pricing inputs while final quotes remain in the product system.
What makes a mission complete?
Checklist, before photo, after photo, and final area must all be recorded before completion is released.
Launch channels
A sharper public presence for serious field operations.
Store links can remain placeholders until launch. Contact routes stay as plain email links, keeping the public site static and free of stored personal data.