A good Aerotas quote starts with a clear project boundary and a straightforward explanation of what you need delivered. The more precisely the area of interest and scope are defined up front, the easier it is to price the work correctly and avoid scope drift later.
The most important input: the boundary file
A KML or KMZ with a polygon around the exact project area gives Aerotas the best chance of quoting correctly. That boundary is used both for scope and for downstream planning, so vague descriptions are much less useful than a clean map boundary.
What else to include
- Project name
- Requested deliverable type or product
- Any special features or drafting needs
- Relevant timing or turnaround constraints
- Accuracy or workflow notes when they materially affect scope
Best practice: if the final deliverable has unusual standards, say that before the quote is issued. It is much easier to price the right scope than to retrofit it later.
Ready to request one?
Use the Aerotas app if you already have the boundary ready, or contact the team directly if you need help figuring out the right scope first.