The current public storefront price for UG25 is USD 13,917. Treat that figure as one documented line in a procurement file, not as a delivered-project price, total ownership cost, or promise that training, commissioning, payload integration, delivery, spares, support, lead time, warranty, duties, taxes, or other services are included. A defensible quote review turns every undocumented item into a supplier-confirmation field and records who owns the answer.

Buyers get into trouble when a familiar phrase fills a blank. Ready to fly, complete system, standard support, or delivery included can mean different things across sellers, configurations, countries, and contracts. The quote matrix should preserve the supplier's exact wording, distinguish confirmed scope from buyer assumption, identify excluded or unresolved items, and show what evidence will be required before acceptance.

Build a Scope Matrix Before Comparing Prices

Create a line-by-line matrix for the aircraft, payload, ground equipment, power equipment, transport cases, communications components, software, data storage, manuals, commissioning, training, integration, testing, delivery, customs support, spares, tools, documentation, and post-delivery support. These categories are questions, not claims about what the UG25 includes. Add only the rows relevant to the buyer's intended configuration and operating model.

For every row, record included, excluded, optional, buyer-supplied, supplier-confirmation-required, or not applicable. Cite the quote page, product page, attachment, or written response that supports the state. Add quantity, configuration identifier, revision, price basis, delivery point, tax treatment, and acceptance evidence when available. Do not let an empty cell behave like included.

Separate Product Facts From Commercial Terms

The product record and the commercial offer answer different questions. The product record identifies the public model and approved facts. The quote should identify the exact configuration, quantities, options, services, commercial terms, and validity. A buyer may use a public page to confirm identity, but the final contract should not rely on a changing webpage to define all obligations.

Preserve the date and currency context for the public price. Record whether the supplier's quote uses the same model, configuration, and currency. Ask whether shipping, duties, taxes, payment fees, insurance, export or import support, and destination handling are included. Do not calculate a landed cost until each basis is known or explicitly labeled as an assumption.

Make Configuration Identity Specific

Write the aircraft model, hardware revision when supplied, payload and mount identity, communications arrangement, ground-control components, power setup, accessories, software or firmware references when applicable, and documentation revision. If the quote uses a bundle name, ask for the underlying line items. A bundle is convenient for sales but weak for acceptance if the buyer cannot reconcile what arrived.

Ask which items are factory installed, supplier integrated, delivered loose, or buyer supplied. Ask what configuration evidence will accompany shipment and what changes require a new quote. Do not infer compatibility from a payload mass alone. Physical, electrical, data, software, balance, environmental, operational, and approval interfaces may require separate evidence from qualified parties.

Keep Training and Commissioning Separate

Training should identify audience, prerequisites, location, duration, language, materials, instructor role, attendance evidence, evaluation method, and limits. Commissioning should identify site prerequisites, configuration verification, setup responsibilities, test objectives, acceptance authority, evidence package, and unresolved-item handling. A demonstration, familiarization, training session, and contractual acceptance test are not interchangeable.

If neither service is documented, mark it unknown. Ask whether travel, accommodation, site access, local permissions, equipment, consumables, and rescheduling are included or buyer responsibilities. Record what happens if the site is not ready or a test cannot be completed. This protects the buyer from treating a general support conversation as a committed deliverable.

Ask Support Questions That Can Be Measured

Replace does support come with it with specific questions. Identify support channel, service hours, language, response target if offered, information required to open a case, escalation route, remote access conditions, software or firmware handling, replacement process, and exclusions. Ask whether a response target is a contractual commitment or an operating objective. Ask when the support period starts and which serial or configuration identities it covers.

Record who owns initial diagnosis, log collection, packaging, shipping, site access, and return-to-service decisions. Do not infer that remote advice authorizes technical work. Qualified personnel, supplier documentation, buyer procedures, and local requirements should control maintenance and configuration changes. A support promise is useful only when the buyer can map it to an actual incident workflow.

Treat Lead Time as an Unknown Until Confirmed

The approved UG25 record does not provide a lead time. Ask for the start event, such as cleared payment, signed order, configuration freeze, or another condition. Ask whether the answer covers production, integration, testing, export preparation, shipment, customs, and destination delivery. A single number without start and end events can create false schedule confidence.

Record quote validity, expected milestones, buyer dependencies, change-control effects, notification requirements, and remedies or next steps if the plan changes. Distinguish estimate, target, and contractual commitment. Build the project schedule with visible uncertainty until the supplier confirms the applicable basis in writing.

Keep Warranty Questions Explicit

The approved UG25 record does not provide a warranty term. Ask for covered products and components, start date, duration, geographic scope, exclusions, required maintenance records, claim process, diagnostic steps, shipping responsibility, repair or replacement decision, turnaround basis, and effect of integration or modification. Do not imply a warranty exists merely because support is available.

Ask which document controls if a product page, quote, invoice, and warranty statement differ. Have qualified commercial or legal reviewers interpret terms relevant to the purchase. The procurement matrix should link to the controlling document and keep open questions visible; it should not paraphrase complex terms into an unsupported promise.

Use UG25 Facts With Their Conditions

The current UG25 product page identifies a fixed-wing VTOL drone for wide-area mapping and inspection. The approved record lists a 2.5 kg maximum payload and up to 240 minutes of no-load flight time. Those are product facts with qualifiers, not evidence of loaded endurance, mapping coverage, sensor compatibility, or acceptance for a proposed project.

Ask the supplier to separate public product facts, proposed configuration, expected performance evidence, required tests, commercial commitments, and unknowns. Keep the public USD 13,917 price connected to its storefront source and date. If the quoted configuration costs more or less, record why rather than editing the public fact.

Run an Evidence-Based Quote Review

• Freeze the requirement and proposed configuration.
• List inclusions, exclusions, and buyer-supplied items.
• Cite evidence for every confirmed line.
• Mark taxes, duties, shipping, and delivery basis.
• Separate training, commissioning, and acceptance.
• Record support and escalation terms.
• Confirm lead-time start and end events.
• Link warranty questions to the controlling document.
• Name owners and due dates for every unknown.
• Approve only the scope supported by the final record.

Use the same-day mapping subcontractor deliverables guide to connect quote scope with file and sign-off obligations. Use the same-day campaign availability plan to keep support, spares, and turnaround assumptions visible after the purchase decision.

Close the Decision Without Hiding Unknowns

The final procurement record should show the requirement, selected configuration, evidence sources, accepted inclusions, exclusions, price basis, commercial terms, acceptance plan, risks, open questions, owners, and approval authority. Unknown does not mean unsuitable. It means the buyer still needs a documented supplier answer, test, or contract decision before relying on the item.

Reopen the review when configuration, quantity, destination, schedule, scope, integration, acceptance criteria, or controlling terms change. Buyers can compare current public product paths in the VTOL and fixed-wing drone collection. Use the UNITED UAV contact page to request a configuration-specific quotation and ask that every response distinguish included scope, optional scope, buyer responsibility, published fact, proposed test, and unresolved term.

Compare Offers on the Same Evidence Basis

If several offers are considered, normalize the requirement and evaluation fields before comparing totals. Record whether each offer includes the same aircraft configuration, payload scope, ground equipment, delivery point, documentation, services, acceptance evidence, and commercial terms. A lower visible number may simply exclude work another offer lists openly. The matrix should show the difference without assuming which package is better.

Keep scored evaluation, technical compliance, commercial review, and approval records traceable to source documents. If a supplier clarifies an item, record the date, author, affected line, and whether the quote was formally revised. Do not copy one supplier's interpretation into another supplier's empty field. Unknown remains unknown until that seller confirms it.

Prepare the Purchase Order for Readback

Before issue, read the final purchase order and attachments as the receiving and acceptance teams will read them. Verify model and configuration identity, quantities, delivery basis, included services, documents, milestone evidence, acceptance authority, invoice trigger, change control, support references, and controlling terms. Resolve conflicts between the matrix and contract package. A strong internal comparison is wasted if the final order drops the conditions that made the decision defensible.

Keep the Decision Current Until Order Acceptance

Check the public product identity, supplier quote revision, currency, configuration, availability statement, and controlling terms again before order acceptance. Record any difference from the approved evaluation. If a material term changes, send it back through the required approval path rather than treating the earlier decision as permanent. This last readback closes the gap between the offer that was evaluated and the obligation the buyer actually creates.