Big stories

“We started with an Excel sheet”: how three students built a service for farmers

Three students who founded an agritech startup talk about first customers, mistakes and why a farmer needs a forecast on the phone.

For you: You will see that a startup can begin with a simple spreadsheet and conversations with customers, not with an app.

“We started with an Excel sheet”: how three students built a service for farmers

Many startups begin with an app: code, design and a logo first, customers later. This team did the opposite. Three students started by phoning farmers and logging their data in an ordinary spreadsheet. The app came later, when customers asked for it themselves.

The founders of the agritech startup talked about their first customers, their mistakes and why a farmer needs a forecast on the phone. Their experience is useful well beyond farming, for any new project.

Where the idea came from

The idea came during a summer internship, where the students saw farmers at work with their own eyes. Farmers logged watering and fertiliser in a notebook and could not tell why yields differed between neighbouring fields.

The data existed, but it was sitting there unused. Notebook entries are hard to compare. When and how much water went on, which fertiliser was used on which field: none of it fits on a single page. So farmers could not learn from their own experience.

The students saw an opportunity: collect the data in one place and make it easy to compare.

Version one: an Excel sheet

The first version was a spreadsheet the students filled in for farmers over the phone. The farmer says what they did, and a student types it into Excel. No software, no servers, no design.

This approach has several advantages:

  • it costs very little money and time;
  • the farmer does not have to install or learn anything;
  • the team hears directly what farmers actually ask about;
  • if the idea does not work, it can be dropped quickly and another path tried.

The phone calls gave the team the most valuable thing of all: an understanding of the customer's language. Farmers do not talk in technical terms. They talk about their fields, the weather and the harvest.

When the app arrived

The team was in no hurry to build an app. Only when ten farms asked them to keep going did the team build one. That is a real sign of demand. When people themselves say “please don't stop”, the service is clearly useful to them.

This approach is often repeated in the startup world: first make sure people use your solution even when it is done by hand, and only then automate it. Manual work is hard, but it shows which features are needed and which are not.

The biggest mistake: too many features

Their biggest mistake, the founders say, was too many features at the start. The team wanted to give farmers as much information as possible: tables, charts, comparisons. But in day-to-day work farmers did not need any of that.

A farmer needs one answer: water today or not. So the team made the main screen simple, with the answer to one question. Everything else went into reports. Anyone who wants the details can find them there, and everyone else gets the one answer they need.

This lesson applies to any product. People do not pay for the number of features; they pay for a solution to their problem.

Why the forecast lives on the phone

A farmer's workplace is the field, not an office. They are outside all day, while the computer stays at home. The phone is always in their pocket, so the information that helps them decide should be there too.

A small screen cannot hold many tables. That limit pushed the team to focus on what matters. A short answer can be checked in the morning, before watering starts, and the detailed reports can wait until the evening.

What this means for you and what to do now

Farming is a big sector in Kazakhstan, and its data still often lives in notebooks. That means there is room for new services. But the lesson is not only about agriculture. Whether you are a student or run a small business, you can apply these steps to your own idea:

  1. See the problem with your own eyes. At an internship, at work or among people you know, notice what people do by hand and with difficulty.
  2. Don't start with an app. Try delivering the service manually, with a spreadsheet, a chat or phone calls.
  3. Wait for real demand. Write software only when several customers ask you to keep going.
  4. Find the one main answer. Work out what the customer needs every day and show only that on the main screen.
  5. Hide the rest. Move extra data into reports or a separate section.

The first step needs neither money nor a programmer. One spreadsheet and a few phone calls are enough.

Ad Your ad hereA banner on the homepage, in stories and sections. Formats and prices on our Advertise page.

Comments 2

  1. EditorialEditorial

    Привет!

    1. EditorialEditorial

      Привет