Economics & industry

Design services that reach small farms

Fit shared access, contracting, booking and travel to the season.

Sir Airffic Go

Do not make ordering the service harder than using it.

Updated 2026-10-30 · 5 min read

One clear point of entry

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Keep intake to field, objective, timing and contact. Let providers translate the problem into a suitable technical approach instead of asking farmers to choose sensors or models. Bring phone and local-office requests into the same register.

Aggregate without hiding constraints

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Aggregation needs compatible crops, materials, timing, access and boundaries. Adding hectares does not automatically remove travel and cleaning costs. State weather-delay priority, cancellation terms and revisit charges in advance.

Deliver for continued use

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Explain next steps in the farmer’s language. If the service only supplies analysis, agree who performs ground checks. Track return bookings and support time as indicators of whether the service remains usable.

Distinguish easy booking from service capacity

SOURCE-BASED EXPLANATION

A Suphan Buri farmer survey identifies referrals and telephone contact in service use. An IDE-JETRO study records batteries, generators, queues and repair delays. These are contextual studies, not national adoption rates or current price lists. They inform this guide's proposal to distinguish requests received, executable jobs and jobs completed within their agronomic windows, with phone requests entering the same register as online bookings.

Schedule agronomic windows and ground work together

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Keep a requested date separate from a confirmed agronomic window, site prerequisites and the deadline for a decision. Schedule travel, setup, replenishment, cleaning, packing and reporting. Spare aircraft capacity is insufficient if staff, water or charging capacity are unavailable. After weather delays, review urgency and treatment windows, and explain changes rather than silently replacing an agreed queue. Nearby fields may still need separate visits when different crops or materials increase switching work. State who pays for reserved contingency capacity instead of maximizing utilization only on normal-weather days.

Identify services that cannot sustain a low hectare price

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

First examine revenue per visit after travel, field staffing, material handling, energy and variable maintenance costs. Then test whether the remaining contribution can support annual fixed costs and inactive periods, separately considering peak and quiet seasons. The same booked area can produce different margins when it is concentrated at one location or scattered across repeated distant visits. Shared ownership also requires paid coordination, inspection, backup arrangements and accountable staff. Contracting may be preferable when those responsibilities are unclear. Conversely, farms facing frequent urgent demand and long external queues may value spare internal capacity. Compare the cost of timely completion without making equipment purchase the predetermined answer.

Test understanding and learn from refusal

AIRFFIC DESIGN PROPOSAL / FRAMEWORK

Do not end an adoption trial by counting people who operated the interface. Ask first-time farmers to identify their field, explain what the price includes, find a postponement message and describe the next action after delivery. Treat difficulty as evidence for improving local field names, language, connectivity and phone support rather than automatically blaming ability. Alongside repeat bookings, record timely completion, repeated support contacts, complaints, rework and their causes. Include people who declined or stopped using the service. Demand generated through subsidies or free demonstrations should not be treated as willingness to purchase at normal prices; make payment conditions explicit.

Observed taskPractical acceptance criterionWhere to improve
Identify the fieldFarmer and provider indicate the same plotField naming, maps and phone intake
Check service termsFarmer can explain included work and extra chargesQuotation and explanation
Receive a delay or resultFarmer can name the next owner and actionNotifications, handover and support

Check your next steps

Saved in this browser. This checklist does not authorize an operation.
Article data JSON ↓