labs@atheron:~/industries/agriculture$ scout --field 12 --spray-log --crew

Software for farms

Records kept in the field, not at the kitchen table.

Your spray records are in a notebook. Your scouting notes are on a phone, and your crew schedule is in a group chat. That adds up to a lot of evenings at the kitchen table. We build the systems that capture the work in the field: apps that work without a signal, models that know your crops and records your buyers can check.

Start a project See the example projects

// what you are up against

The problems we hear most.

Records made after dark

Spray, seeding and harvest records are written up at night from notebooks and memory, and buyers and auditors want them complete and on time.

Scouting that rests on one person's eye

Disease, pests and weeds are spotted by whoever walks the field, and by the time a pattern is clear the window to act has narrowed.

Proof a buyer can check

Processors and retailers ask for evidence of sustainable practice, and a stack of PDFs from different auditors is hard for anyone to verify.

Seasonal crews and a group chat

Shifts, tasks and safety notices go out in a chat in several languages, and nobody is sure who saw what.

// example projects

Systems we could build for you.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appMobile appMaterials tracking

Farm app with field records

Hypothetical. Not a client, not a result.

// The problem

A vegetable and berry farm keeps its spray, fertiliser and harvest records in notebooks, and getting ready for a food safety audit or a buyer's questionnaire takes days.

// What we would build

A web and mobile app where crews log field work at the field, offline, against a map of fields and blocks, with product rates, pre-harvest intervals and re-entry times checked as they log, and records ready when the auditor arrives.

// What is in it

Seed, fertiliser and chemical lots labelled with QR codes, and machinery located by GPS
Map of fields and blocks with crop, variety and planting dates
Spray and fertiliser logs with product, rate and the weather at the time
Pre-harvest intervals and re-entry times checked before a block is harvested or entered
Harvest records with lot codes for traceability
Works offline in the field and syncs at the yard
Exports in the formats your CanadaGAP auditor and buyers ask for

// Stack

Next.js
React Native
PostgreSQL with PostGIS
Mapbox
Weather API
DigitalOcean

// estimate

Build: ≈ US$158,000 to US$242,000, delivered within 33 weeksCAD 225,200 to 344,400
Hosting: ≈ US$379 a monthCAD 540 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month
Hardware: ≈ US$4,480CAD 6,380

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Discovery and site walk-through: 0.4 weeks
Design approved: 5.4 to 8.9 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
First build on devices: 2.4 to 3.9 weeks
Stock, receiving and transfers: 2.9 to 4.4 weeks
Tracking and devices working: 1.9 to 3.4 weeks
Testing and fixes: 0.4 weeks
Store submission: 0.4 weeks
Pilot site live: 2.9 to 3.4 weeks
Launch: 0.9 to 1.4 weeks
Rollout: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week
Hardware delivery, after it is ordered: 2 to 4 weeks
API access from the equipment vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 45,040 to 68,880
Discovery 4.6%: CAD 10,359.20 to 15,842.40
Discovery and site walk-through 3.8%: CAD 8,557.60 to 13,087.20
Design approved 8.5%: CAD 19,142 to 29,274
Core features 3.8%: CAD 8,557.60 to 13,087.20
Full build 2.5%: CAD 5,630 to 8,610
First build on devices 10.2%: CAD 22,970.40 to 35,128.80
Stock, receiving and transfers 11.5%: CAD 25,898 to 39,606
Tracking and devices working 7.6%: CAD 17,115.20 to 26,174.40
Testing and fixes 1.2%: CAD 2,702.40 to 4,132.80
Store submission 3.4%: CAD 7,656.80 to 11,709.60
Pilot site live 3.8%: CAD 8,557.60 to 13,087.20
Launch 4.6%: CAD 10,359.20 to 15,842.40
Rollout 4.5%: CAD 10,134 to 15,498
Holdback, 30 days after launch (10%): CAD 22,520 to 34,440
Battery GPS tracker x 15: CAD 4,910. Billed up front, at cost, outside the milestones
Desktop label printer x 1: CAD 870. Billed up front, at cost, outside the milestones
Corded barcode scanner, for our build and testing: CAD 290. Billed up front, at cost, outside the milestones
Cellular GPS development kit, for our build and testing: CAD 310. Billed up front, at cost, outside the milestones

Start from this example

Example projectWeb appMobile appAICustom LLM

Crop scouting with custom vision

Hypothetical. Not a client, not a result.

// The problem

An agronomy service scouts many fields every week, and catching disease and weeds early depends on which agronomist walked the field that day.

// What we would build

A scouting app where agronomists and growers photograph leaves and plants, with a custom vision model fine-tuned on your own labelled images of local crops, diseases and weeds suggesting what it sees and how sure it is. A custom model fits because general models do not know your crops or your region; it runs on GPUs you rent, and the photos stay yours.

// What is in it

Phone photos tagged to the field and block they were taken in
A model fine-tuned on your labelled images, measured on a held-out set before use
Suggestions with a confidence level, confirmed or corrected by the agronomist
Corrections fed into the next round of training
Maps of findings by field across the season
Photos queued on the phone until it has a signal

// Stack

PyTorch
React Native
Python
Next.js
PostgreSQL with PostGIS
AWS GPU

// estimate

Build: ≈ US$171,000 to US$261,000, delivered within 33 weeksCAD 243,600 to 372,000
Hosting: ≈ US$6,710 a monthCAD 9,550 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

AI route: Custom LLM
Model running cost: ≈ US$6,530 a monthCAD 9,300 a month

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Data and evaluation plan: 0.4 weeks
Design approved: 3.4 to 5.9 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
First build on devices: 2.4 to 4.4 weeks
Training: 4.9 to 8.4 weeks
Testing and fixes: 0.4 weeks
Store submission: 0.4 weeks
Evaluation and red-teaming: 3.9 to 4.4 weeks
Launch: 0.9 to 1.4 weeks
Production: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week

How it is paid

Deposit 20%: CAD 48,480 to 74,160
Discovery 4%: CAD 9,696 to 14,832
Data and evaluation plan 5.6%: CAD 13,574.40 to 20,764.80
Design approved 4%: CAD 9,696 to 14,832
Core features 3.3%: CAD 7,999.20 to 12,236.40
Full build 2.2%: CAD 5,332.80 to 8,157.60
First build on devices 8.7%: CAD 21,088.80 to 32,259.60
Training 16.9%: CAD 40,965.60 to 62,665.20
Testing and fixes 1.1%: CAD 2,666.40 to 4,078.80
Store submission 2.9%: CAD 7,029.60 to 10,753.20
Evaluation and red-teaming 11.3%: CAD 27,391.20 to 41,900.40
Launch 4%: CAD 9,696 to 14,832
Production 6%: CAD 14,544 to 22,248
Holdback, 30 days after launch (10%): CAD 24,240 to 37,080
GPU time for training and testing, at cost: CAD 1,200. Billed up front, at cost, outside the milestones

Start from this example

Example projectWeb appWeb3

Sustainability credentials

Hypothetical. Not a client, not a result.

// The problem

Growers are asked by several buyers for proof of sustainable practice, and each buyer receives a different PDF it cannot easily check or trust.

// What we would build

Credentials issued by the certifying body to each farm when an audit passes, anchored on a public chain so any buyer can check that a credential is genuine, current and not revoked, without calling anyone. Only a fingerprint of the credential goes on chain, never farm data. If a single buyer is the only one asking, a signed PDF and a database do the job for less, and we will say so.

// What is in it

Credential issued by the certifier after an audit, in the W3C Verifiable Credentials format
A fingerprint anchored on a public chain, with no farm data on chain
Growers share a credential with a link or a QR code
Buyers check it is genuine, current and not revoked in one step
Revocation and expiry handled by the certifier
Smart contract tested and independently reviewed before launch

// Stack

Solidity
Polygon PoS
W3C Verifiable Credentials
Next.js
PostgreSQL

// estimate

Build: ≈ US$66,500 to US$102,000, delivered within 20 weeksCAD 94,700 to 144,800
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Specification: 0.4 weeks
Design approved: 2.4 to 4.4 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
Contracts and tests: 1.4 to 2.4 weeks
Testing and fixes: 0.4 weeks
Testnet deployment: 2.9 to 3.4 weeks
Launch: 0.9 to 1.4 weeks
Mainnet: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

An outside audit of the contracts, if you want one: 2 to 4 weeks

How it is paid

Deposit 20%: CAD 18,940 to 28,960
Discovery 4.2%: CAD 3,977.40 to 6,081.60
Specification 5.3%: CAD 5,019.10 to 7,674.40
Design approved 4.2%: CAD 3,977.40 to 6,081.60
Core features 12.6%: CAD 11,932.20 to 18,244.80
Full build 8.4%: CAD 7,954.80 to 12,163.20
Contracts and tests 16%: CAD 15,152 to 23,168
Testing and fixes 4.2%: CAD 3,977.40 to 6,081.60
Testnet deployment 5.3%: CAD 5,019.10 to 7,674.40
Launch 4.2%: CAD 3,977.40 to 6,081.60
Mainnet 5.6%: CAD 5,303.20 to 8,108.80
Holdback, 30 days after launch (10%): CAD 9,470 to 14,480

Start from this example

Example projectBot with a web dashboard

Telegram bot for seasonal crews

Hypothetical. Not a client, not a result.

// The problem

An orchard hires seasonal workers who speak several languages, and shifts, field assignments and safety notices go out in a group chat where messages get buried.

// What we would build

A Telegram bot that sends each worker their own shift and field in their own language, asks them to acknowledge each safety notice, and lets supervisors post changes from a simple admin screen.

// What is in it

Shifts and field assignments sent to each worker in their language
Safety notices and re-entry warnings that must be acknowledged
Supervisor changes posted once and translated
A record of who received and confirmed each notice
Workers reply to report an absence or a problem

// Stack

Telegram Bot API
Node.js
PostgreSQL
Translation API
DigitalOcean

// estimate

Build: ≈ US$28,800 to US$44,100, delivered within 10 weeksCAD 41,000 to 62,800
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Commands agreed: 2.9 to 3.4 weeks
Working in a test server: 2.4 to 3.9 weeks
Hardening and testing: 0.5 to 1 weeks
Launch: 0.9 to 1.4 weeks

How it is paid

Deposit 30%: CAD 12,300 to 18,840
Commands agreed 15%: CAD 6,150 to 9,420
Working in a test server 30%: CAD 12,300 to 18,840
Launch 15%: CAD 6,150 to 9,420
Holdback, 30 days after launch (10%): CAD 4,100 to 6,280

Start from this example

Example projectWeb app

Yield and input cost dashboard

Hypothetical. Not a client, not a result.

// The problem

A grain farm has yield maps in one program, input invoices in its accounting software and field notes in a spreadsheet, and nobody can see what each field actually cost to grow.

// What we would build

One dashboard that pulls yield, input and field data into a single store every night, so you can compare fields, varieties and products by cost per acre and plan next season from your own numbers.

// What is in it

Yield files, input invoices and field records loaded every night
Cost per acre by field, crop and variety
Season against season comparisons
Exports for your lender and your agronomist

// Stack

Next.js
PostgreSQL
dbt
Metabase
DigitalOcean

// estimate

Build: ≈ US$60,900 to US$93,200, delivered within 15 weeksCAD 86,700 to 132,700
Hosting: ≈ US$344 a monthCAD 490 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.4 to 3.4 weeks
Core features: 2.4 to 3.4 weeks
Full build: 1.4 to 2.4 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access from the equipment vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 17,340 to 26,540
Discovery 7.7%: CAD 6,675.90 to 10,217.90
Design approved 7.7%: CAD 6,675.90 to 10,217.90
Core features 23.3%: CAD 20,201.10 to 30,919.10
Full build 15.5%: CAD 13,438.50 to 20,568.50
Testing and fixes 7.7%: CAD 6,675.90 to 10,217.90
Launch 8.1%: CAD 7,022.70 to 10,748.70
Holdback, 30 days after launch (10%): CAD 8,670 to 13,270

Start from this example

Example projectWeb appAPI

Equipment, weather and books joined up

Hypothetical. Not a client, not a result.

// The problem

A mixed farm types the same field work into its equipment portal, its farm records app and its accounting software, and the three never quite agree.

// What we would build

A small integration service that reads work records from your equipment portal, adds the weather for each job, files them to your farm records and posts input use to your books, with one screen that shows every sync and anything that failed.

// What is in it

Work records read from the equipment portal
Weather at the time of each job attached
Input use posted to your accounting
A status screen with every sync and every error

// Stack

Node.js
PostgreSQL
John Deere Operations Center API
QuickBooks Online API
DigitalOcean

// estimate

Build: ≈ US$90,500 to US$138,000, delivered within 24 weeksCAD 128,900 to 197,100
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.4 to 3.4 weeks
API contract agreed: 1.4 to 1.9 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
Core resources built: 2.4 to 3.9 weeks
Security, gateway and connections: 1.9 to 2.9 weeks
Testing and fixes: 0.4 weeks
Docs, SDKs and load tests: 1.4 to 1.9 weeks
Launch: 0.9 to 1.4 weeks
Launch and first callers: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

API access from the equipment vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 25,780 to 39,420
Discovery 2.5%: CAD 3,222.50 to 4,927.50
Design approved 2.5%: CAD 3,222.50 to 4,927.50
API contract agreed 5.8%: CAD 7,476.20 to 11,431.80
Core features 7.6%: CAD 9,796.40 to 14,979.60
Full build 5.1%: CAD 6,573.90 to 10,052.10
Core resources built 17.6%: CAD 22,686.40 to 34,689.60
Security, gateway and connections 11.7%: CAD 15,081.30 to 23,060.70
Testing and fixes 2.5%: CAD 3,222.50 to 4,927.50
Docs, SDKs and load tests 5.8%: CAD 7,476.20 to 11,431.80
Launch 2.5%: CAD 3,222.50 to 4,927.50
Launch and first callers 6.4%: CAD 8,249.60 to 12,614.40
Holdback, 30 days after launch (10%): CAD 12,890 to 19,710

Start from this example

// by service

Go deeper on one kind of work.

Pages for the services we have the most to say about in this industry.

~/apps

Farm records app

Custom farm operations apps for growers: field work logged offline at the field, spray and harvest records checked as they are entered, and exports for food safety audits and buyers.

~/ai

AI crop scouting

A crop scouting app with a custom vision model fine-tuned on your own images of local crops, diseases and weeds, with agronomists confirming what the model suggests.

~/web3

Grower credentials

Credentials issued by certifiers when a farm passes an audit, anchored on a public chain so any buyer can check they are genuine, current and not revoked, with no farm data on chain.

// questions

What buyers in this industry ask us.

Do you also work with co-ops and agronomy services?

Yes. Many of these systems are run by a co-op or an agronomy service on behalf of many growers, and we design the permissions for that.

Our farm has poor coverage. Will the apps still work?

Yes. Field apps are built offline first and sync when they reach a signal or the yard Wi-Fi.

How do payments work?

A deposit to start, then payments at agreed milestones, with 10% held until 30 days after launch. The deposit is a smaller share on larger projects.

Who owns the code and the models?

You do, once the work is paid for, including any model trained on your photos.

// other industries

Nearby industries.

~/food-beverage

Food and beverage

Food safety and traceability apps, wholesale ordering apps, label review agents and shared cold-chain records on a private ledger.

See the examples

~/supply-chain

Supply chain

Inbound control towers, multi-tier sourcing ledgers with supplier portals, supplier risk agents and sustainability data portals.

See the examples

~/energy

Energy and utilities

Field inspection and work order apps for your crews, operations assistants on private models, renewable certificate ledgers and feeder load forecasting.

See the examples

All industries

// where we work

Find your market.

We work from Kelowna with clients across Canada, the United States and further afield. Each market page covers working hours, hosting, the privacy law that applies, and prices in your currency.

Every market

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call