Why No Farm App Was Built for Philippine Sugarcane Smallholders

I spent two years looking for a farm management app that worked for my situation before I gave up and built one.

Not two years of casual browsing. Two years of downloading trials, reading documentation, running into paywalls, and eventually arriving at the same conclusion every time: this was made for someone farming five hundred hectares in Queensland, not for a family cane operation in Negros Oriental.

The apps that existed were not bad. They were wrong. Wrong crop, wrong scale, wrong country, wrong infrastructure assumption. And when I looked at why, the reason wasn't that no one had tried to solve the problem. It's that the market that existed for farm management software was never our market.

Who the Tools Were Built For

The serious farm management platforms, AgriWebb, FarmLogs, Granular, and FieldView, are built for broadacre farming in markets where farms run into the hundreds of hectares, internet connection is reliable enough to be assumed, and the farmer has a computer on a desk somewhere. They price in USD or AUD. They treat offline access as an optional edge-case feature, not a baseline requirement.

For sugarcane specifically, the dedicated tools are even narrower. CanePro Estate, built by SQR Software in Australia, runs on Microsoft SQL Server and is deployed across 28 large operations covering more than 300,000 hectares. The company knows there's a smallholder segment. They built a separate product called CanePro Farmer for it but don't actively sell it in Australia, which tells you something about where they see the commercial logic.

Smartcane BMP, the Queensland grower accreditation platform, is a compliance self-assessment tool. Real growers use it by compiling evidence off separate systems and uploading it, sometimes via USB stick because rural Queensland internet is also slow. It's not a daily farm record. It was never designed to be.

None of these were wrong to build. They solved real problems for the markets they were aimed at. But the Philippine sugarcane smallholder was not the market anyone was thinking about. The typical farm is five to fifteen hectares. The farmer operates under intermittent mobile signal, records crop notes in a notebook that gets wet, pays workers by the day and settles up at the end of the week.

The RSSI Outbreak Changed My Timeline

I had been planning to build the app for a while. The 2026 red-striped soft scale insect outbreak pushed me to finish it.

By July 2026, RSSI had affected more than 92,000 hectares of sugarcane nationwide. Negros Oriental declared a state of calamity. Bais City, where I farm, had already declared its own local calamity weeks before. Fields across the province were compromised, and farmers trying to access government assistance or cooperative support were being asked to document damage they had no systematic way of recording.

The documentation problem was not about fraud. It was about the fact that pest sightings had been logged in people's heads, and memories are hard to submit to an SRA validation team. The gap between 17,000 reported hectares in Negros Oriental and 1,571 SRA-validated hectares at the time wasn't mostly deception. It was mostly paperwork that didn't exist yet.

That's when I understood what the app needed to do first: create a verifiable record at the moment something happened, without requiring the farmer to be connected to the internet.

What Philippine Sugarcane Farming Actually Looks Like

About 75,000 farmers grow sugarcane in the Philippines across roughly 440,000 hectares of planted area. Negros Island accounts for about 65% of national production. The average Negros farm is not large. It sits in a landscape where hacienda-style operations and family smallholdings exist side by side, often separated by the same mill access road.

The mill relationship is central to how a Philippine cane farmer operates. You don't sell sugarcane at the gate; you deliver it through a quedan system, where the mill weighs the cane, determines the Commercial Cane Sugar content, and pays the farmer a proportion of the resulting sugar. That transaction creates quedan receipts, delivery tickets, and mill statements that a serious farmer tracks carefully, because the numbers directly determine income.

Then there's the labor piece. Most cane farms in Negros rely on a mix of permanent and seasonal workers. Daily pay, worker attendance, task assignments by field: this is farm administration that happens in real time and needs to be logged before the week ends or the figures get lost. The paper notebook is not a failure of imagination. It's been the only practical tool available.

Field records work the same way. Planting dates, variety, ratoon counts, fertilizer applications by field. All tracked in memory or on paper. When a field underperforms, the farmer often can't go back and check what happened because the record either doesn't exist or was lost.

Rural connectivity complicates everything. PIDS Discussion Paper 2023-29 found that only 11.4% of rural households have home internet access (Briones, Galang & Latigar, citing Albert et al. 2021). In sugarcane country, where farms are spread across municipalities, many located away from town centres, that figure is a ceiling, not a floor.

What I Built

Sugarcane Farm Manager is a free, offline-first progressive web app available at lmreyna.com. It runs in a phone browser with no installation required and works without internet access.

Eight modules, each focused on something a Negros cane farmer actually needs:

Field management: map your fields, track planting dates by variety, log ratoon counts, record crop growth stages. Everything stored on the device, synced when connection is available.

Pest management: a reference database for nine Philippine sugarcane pests, with RSSI flagged as an active outbreak. A declaration form that creates a GPS-pinned, timestamped, photo-supported sighting record. A community spread map showing validated SRA outbreak data alongside operator-reported sightings, clearly labeled so the difference is visible.

Labour tracking: daily worker rosters, worker-day pay logging, task assignment by field. Designed for the hacienda model where labor costs are the primary variable expense and need to be tracked week by week.

Expense tracking: input costs by field, category, and date. The thing a farmer needs when they want to know whether the second fertilizer application on a specific field was actually worth it.

Export: CSV export of all farm data, compatible with the reporting formats SRA extension offices can accept.

The app does not try to do everything. There is no harvest scheduling module, no CCS prediction tool, no logistics management. Those gaps are deliberate for now. Adding them without the infrastructure to do them properly would make the app worse, not better.

Why It Took This Long

No one built this before because the market economics didn't make sense in the way they need to for a commercial software company.

A farmer in Negros Oriental who manages a ten-hectare operation and keeps records in a notebook is not a high-value SaaS customer. There is no subscription revenue model that works at smallholder scale when the farmer's margin on a good year is measured in tens of thousands of pesos. You can't charge USD pricing to a market earning peso returns. You can't require internet access in areas that don't have reliable internet. You can't design for enterprise workflows when the "enterprise" is one person and their family.

Government programs tried to fill this gap. Project SARAi, funded by DOST with PHP 420 million across two phases, developed crop advisories for sugarcane. SPIDTECH provides AI pest identification. These are real tools with real use. But they're built to deliver information from government agencies to extension workers, not to help an individual farmer record what happened on their own farm last Tuesday.

The gap that remained was specific: a daily-use record-keeping tool, free, offline, designed for the scale and workflow of a Philippine sugarcane smallholder. That's what didn't exist until this year.

I built it because I needed it. The RSSI outbreak confirmed that other people needed it too.