How can we
help you?

CropGen is an AI-powered crop monitoring and LLM-based advisory platform. It combines 12+ satellite vegetation indices, farm data, and advanced AI models to provide farmers with real-time crop insights and personalized, region-specific advisory.

Farmers, FPOs, agribusinesses, agri-input companies, exporters, cooperatives, and consultants who want smart farming, cost savings, and higher yields can benefit from CropGen.

A satellite and AI platform that monitors farm fields and turns what it sees into specific instructions — when to irrigate, what to apply, where the crop is under stress and what to do about it.

Individual farmers and farm managers, FPOs and cooperatives, agri-businesses and agri-input companies, exporters and processors who need traceability, and institutions running agricultural programmes at scale. The same platform serves all of them — what changes is how many fields sit under one account.

No. CropGen works entirely from satellite observation and the details you enter about the field. There is nothing to buy, install or maintain on the ground. The only thing the platform needs from you is an accurate field boundary and correct crop details.

Three things you cannot do by walking. Satellite indices detect stress before it is visible to the eye. The map shows variation across a field, so you can see that one corner is weaker than the rest rather than forming a general impression. And every reading is dated and stored, so a season becomes a record you can compare against rather than a memory.

No, and it is not designed to be. It is a monitoring and decision-support layer. It tells you where to look and what the data suggests; an agronomist brings judgement about your specific crop, soil and market. The platform makes an agronomist more efficient — they walk to the right part of the right field instead of surveying everything.

The platform supports multiple Indian and international languages, selected during sign-up and changeable later from Settings. Advisories and farm communications are delivered in the language on your profile, not just the interface labels.

Yes. Country selection at sign-up sets the regional models applied to your fields, and CropGen has active deployments across multiple countries. Satellite coverage is global.

CropGen analyzes satellite imagery and 12+ vegetation indices (NDVI, EVI, SAVI, NDWI, Chlorophyll Index, etc.) to detect crop health, stress, water status, and growth stage.

CropGen uses LLM (Large Language Models) combined with AI/ML agronomy systems. It converts raw satellite + farm data into easy-to-understand, crop- and region-wise advisory for farmers.

No sensors are required. CropGen primarily uses satellite + AI. But if you already use sensors (soil moisture, weather), CropGen can integrate them for higher precision.

Either works and both reach the same platform. Phone sign-in sends an OTP over WhatsApp; Google sign-in skips the OTP. Choose whichever credential you will reliably have access to, and then use the same one every time.

They are not gone — you are in a different account. A phone-number account and a Google account are two separate workspaces even if they belong to the same person. Log back in with the original method and your fields will be there.

It is optional, and most users leave it blank.

Enter the code CropGen issued to your organisation. Your account is then linked to that organisation's workspace, so fields and reporting sit under the organisation.

Contact your organisation's CropGen point of contact or the LeanCrop team. The account was created as a standalone workspace, so it needs to be linked on the back end rather than fixed from the app.

Yes — go to Settings > Personal Info > Preferred Language. It applies to advisories and farm communications, not only to on-screen labels.

Country selection sets the regional models used on your fields — soil behaviour, seasonal patterns and local climate baselines. Choose the country where the land is, not where you happen to be sitting when you register.

An individual account is intended for one user. Multi-user access, with team members under a single organisation, is part of the enterprise and custom-pricing arrangement.

Your fields sit in your own workspace. If you registered with an organisation code, they sit within that organisation's workspace and are visible to it. For specific data-handling, retention or contractual terms, check the LeanCrop terms agreed during registration.

Per field. Each field you add is subscribed individually, which means you can run analytics on the fields that matter this season and leave the others unsubscribed. Settings > Farm Settings shows the state of every field, and can be filtered to just subscribed or just unsubscribed.

No. Checkout saves your payment method, and recurring billing starts when the trial ends. The full subscription amount is not taken upfront.

Only the billing cycle and price. Yearly carries a discount. The selection applies immediately at checkout, and the platform features are identical either way.

No. The USD / INR toggle changes the display only. Payment is always processed in INR through Razorpay.

Pricing is area-based — the plan rate is applied per acre across the field you have drawn. A larger boundary means a larger monitored area and therefore a higher amount.

Yes. Subscriptions are managed per field from Settings > Farm Settings. An unsubscribed field stays in your account with its history intact; it simply stops receiving fresh analytics.

The field and its recorded history remain in your account. Re-subscribing resumes monitoring. This is why we recommend marking a finished crop as harvested rather than deleting the field.

When you are onboarding many fields at once, need multiple team members on one workspace, want a dedicated account manager, or are looking at API access or a white-labelled deployment. Contact Sales on the plan screen. See Section 15.

CropGen offers a free trial, then monthly or annual subscription plans, based on acreage and services (monitoring, advisory, yield prediction, sustainability).

If you are charged extra, activate by mistake, or cancel within 30 days, you get a full refund.

Farmers and agribusinesses own their data. CropGen only analyzes it securely and does not sell it.

Add Field in the left menu, choose the land status, find the location on the map, and tap each corner of the plot to close a boundary. Then fill in the crop details and save. The full walkthrough is in Section A.3 of the User Guide.

No. Use Add Fields on the map to import GeoJSON, KML or Shapefile directly. The boundary is drawn for you. For anyone onboarding more than a handful of fields, this is faster and more accurate than marking corners by hand.

Accurate enough to exclude everything that is not crop. This is the single biggest driver of data quality on the platform. If the boundary includes a road, a bund, a farm structure or part of a neighbour's plot, those pixels are analysed as though they were your crop. The health score drops, the area is overstated, and the nutrient recommendation is calculated for land you are not farming.

Choose Crop in field when a crop is already sown and standing. The actual sowing date — today or earlier — is required. Choose Barren land when nothing is standing; fallow or under preparation. The crop you plan to sow and the expected sowing date are then required.

Yes, more than most people expect. Sowing date is the anchor for crop age, BBCH growth staging and accumulated heat units — which in turn drive the nutrient targets and every stage-specific recommendation. Correct it as soon as you notice, from Settings > Farm Settings.

Yes. Use Add another crop on the same boundary. Both crops are tracked, one marked as the main crop and the other as the intercrop, and the analytics view lets you switch between them.

No — use Mark harvested on the crop instead. Deleting removes the season's history along with the field, and that history is what the next season's yield baseline and field comparisons are built from.

There is no practical limit on an ordinary account — each field carries its own subscription. Accounts running large portfolios are usually better served by the enterprise option and enterprise arrangement, which adds team access and a dedicated manager.

Yes. Go to Settings > Farm Settings, select the farm card, and the boundary opens alongside the crop details for editing. Fixing a boundary is always worth doing — every subsequent reading improves.

Whenever a satellite passes over it. The scene timeline under the map lists every available pass with its date and cloud percentage, so you can see exactly what is available for your field rather than assuming a fixed schedule.

Almost always cloud. Optical satellites cannot see through it, so a heavily clouded pass produces an unusable scene. Check the cloud percentage on the timeline, then switch to Satellite 1, which is radar-based and unaffected by cloud.

Use Satellite 2 normally because it provides higher visual detail and the full vegetation, water and nutrient index set on clear-sky days. Switch to Satellite 1 during monsoon and overcast periods, or whenever the optical scenes show high cloud, because it is radar-based and can see through cloud.

Treat low single-digit cloud as clean and anything above roughly a third as suspect — the reading may be describing cloud rather than crop. At 90%+ it is certainly cloud. When in doubt, step back to the nearest clear scene on the timeline, or move to Satellite 1.

Yes. Pick any past date on the scene timeline, or set a custom start and end date to compare a period. The time-series charts under the map show the same information as a trend rather than a single day.

Because it is different — different crop, stage, irrigation, soil and management. That is the point of field-level monitoring. What matters is the trend within your own boundary over time, and the variation between zones inside it, rather than a comparison against the plot next door.

Fine enough to resolve variation within a normal field — the zoning analysis, for example, works on a 10-metre grid. It is not fine enough to identify individual plants; for that, photograph the plant and use Disease Detection.

Start from the decision you are about to make, not from the index name. Use Crop Health for the overall view, Crop Health (dense) for a denser crop, Crop Health (simple) for a quick look, Early Stage Health for recently sown crops, Dry Land Health for dry and sparse fields, Water in Leaves for irrigation checks, Plant Water Level for plant water status, Nitrogen Level for fertilization decisions, Waterlogging Risk after rain, any Satellite 1 index when it is cloudy, and Field View when you just want the plain picture.

A measure of how much healthy, living vegetation is in each pixel. Higher means denser and more vigorous. It is the most widely used vegetation index in agriculture and the one most of the crop health views are built on.

Because one formula does not work equally well across all conditions. The standard index saturates on a very dense canopy, which is where the Dense Version corrects for. The Simpler version is a faster, coarser read. Early Stage and Dry Land versions are correct for exposed soil, which otherwise drags the reading down on a young or sparse crop.

Check three things before you act: cloud on that scene, recent harvest or cutting, and whether an event on that date — such as heavy rain, heavy rain or a heat spell — coincides with the drop. If none of these explain it, open the index map, find which part of the field the drop is coming from, and walk to that patch.

The class breaks for the selected index show how much of your field falls into each class — in hectares and as a percentage. It turns a colour picture into a number you can act on: for example, part of the field is weak, or a certain percentage falls in the lowest class.

Yes. Hover anywhere on the boundary for a patch-level insight with the area, class and recommendation. Below the map, the vegetation and water index charts give minimum, mean and maximum values plotted across the season.

CropGen provides 12+ vegetation indices, including: NDVI, EVI, SAVI, MSAVI, NDWI, OSAVI, GNDVI, ARVI, VARI, Chlorophyll Index, DVI, SIPI.

Yes. CropGen identifies stress zones early and provides preventive and curative LLM-based advisory for pest, disease, and nutrient management.

Yes. CropGen analyzes soil and crop status to recommend NPK requirements, irrigation schedules, and water stress alerts.

It is a vegetation-based score for the whole field, banded into a plain label such as Moderate or Good. Read it as a summary, not a diagnosis — the map underneath tells you whether a score is an evenly average field or a strong field with one bad corner. Those need different responses.

An international scale for describing what stage a crop is at, from germination to maturity. CropGen uses BBCH so advice is matched to the stage the crop is actually in rather than being generic — for instance, the nutrient targets in Advanced Soil Analytics change with the BBCH stage.

Because crops develop on accumulated heat, not on the calendar. Two fields sown in the same week can be at genuinely different stages if one had a warmer month. GDD tracks the heat the crop has actually received, which is why the growth stage in CropGen can differ from a fixed crop-duration table.

Check the sowing date on the field first — that is the anchor for the whole calculation, and a wrong date shifts every stage. Correct it in Settings > Farm Settings.

Treat it as a planning baseline for the crop, variety and area you entered, adjusted by what the satellite is seeing — not as a guarantee. It is most useful as a comparison: how this season is tracking against the standard, and whether a management change moves the number.

No. The soil report is generated from satellite data and the historical performance of the field. It is intended for analysis and interpretation — understanding relative soil condition, comparing fields, and spotting where attention is needed. It is not a substitute for a laboratory soil test and must not be used on its own to fix application rates. Before deciding what to apply and how much, carry out a physical soil test and use the CropGen values as supporting context.

Three things a lab test cannot do cheaply. It covers the whole field rather than the few points you sampled. It is available immediately, with no sampling round. And it can be regenerated over time, so you can watch a parameter move across seasons. Use it to decide where and whether to sample, then let the lab decide the dose.

The lab, for absolute values — it measured your actual soil. CropGen is inferring from satellite observation across the whole field, and it is calibrated to show pattern reliably rather than laboratory-exact figures. Use the lab for the number and CropGen for the distribution: which part of the field is short, and by how much relative to the rest.

It compares current uptake against the target required at the crop's current BBCH stage, states the deficit for nitrogen, phosphorus and potassium, and converts that deficit into a quantity for your area. Because the target moves with the growth stage, the same field gets different advice at different points in the season.

Use it as a starting point, cross-checked against a physical soil test and your agronomist's view of the crop. The recommendation is a well-reasoned estimate from satellite data — good enough to plan around, not something to commit a season's input budget to without confirmation.

It is the organic matter fraction of the soil, and the best single indicator of long-term soil health — it drives water retention, structure and nutrient availability. Unlike NPK, it moves slowly, which makes it a useful measure of whether your practices are improving the land over years rather than weeks.

Because the surface can dry out while the root zone is still fine, and vice versa. Reading the subsoil and the deeper layer together — alongside soil temperature and the rain forecast — is what separates a real irrigation need from a dry-looking surface.

A rolling 16-day outlook, with daily temperature, conditions and rainfall. As with any forecast, the first few days are the most reliable and the far end is directional.

Your phone usually reports the nearest city or district station. CropGen resolves to the coordinates of the boundary you drew. Rainfall in particular varies sharply over short distances, so a district forecast can report rain that never reached your plot.

Yes — that is the Weather History lookup. Set a start and end date and pull the record for that field. This is what to use when you are explaining a yield gap, a disease outbreak or a stress event after the fact rather than planning for one.

Rain chances and wind on the forecast, and the insight list — CropGen issues an explicit "no spray needed" or "skip spray today" advisory when wind is high or rain is expected. Spraying ahead of rain wastes the input and the labour.

It is how much water your field is losing per day through soil evaporation and plant transpiration, in millimetres. It matters because it is the demand side of the irrigation equation — read it with soil moisture (supply) and the rain forecast (incoming) and the schedule works itself out.

Because at the end of the season you will want to know what was actually done, when, by whom and at what cost — and memory is not good enough. The calendar also holds the advisories CropGen issued on the same dates, so you can see what was recommended against what was done.

Cultivator, spray, irrigation, fertigation, field monitoring, carbon tracking and other operation types. The form adapts to the type you pick, and captures supervisor, male and female labour counts, estimated cost and free-text comments.

Only the operation type and the progress status are required. Everything else is optional — but the optional fields are exactly what makes the record useful six months later, so fill in what you can.

That is much of its value. For FPOs, exporters and certification bodies the Operations log is an audit trail: what was applied, when, by whom, at what cost, and what the platform advised at the time. It is what turns satellite monitoring into documented practice.

CropGen helps reduce fertilizer, pesticide, and water usage while improving yields. It also measures CO₂ emission reduction and water savings, useful for sustainability and carbon credit projects.

Upload a clear photograph of an affected leaf. The platform classifies the crop, detects the disease and returns suggested control measures.

Fill the frame with the leaf so the symptom is the subject, not a detail in a wide shot. Shoot in daylight, out of glare, because harsh shadows and blown highlights can hide the discolouration the model reads. Photograph early symptoms because a fully collapsed leaf can look the same for many causes, while early lesions are distinguishable. Take several samples because one leaf can mislead, but a consistent pattern across the patch will not.

Pick the crop when you know it — narrowing the model to one crop generally gives a tighter result. Leave it on auto-detect when the sample came from a mixed or intercropped field, or when you are not certain what you are looking at.

They answer different halves of the same question. Analytics shows where in the field the problem is and how much area it covers; Disease Detection identifies what it is. Use the index map to find the weak patch, walk to it, and photograph a leaf from there.

Photograph-based identification is a first read. For an unfamiliar or fast-spreading symptom, confirm with an agronomist before committing to a chemical response across the whole field. Then log whatever you apply in Operations.

A field is not uniform. Applying one rate everywhere over-feeds the strong parts and starves the weak ones. VRA means varying the rate by zone — which saves input on the good ground and puts it where it will actually produce a response.

Rate-controlled equipment lets you apply the maps directly, but the zoning output is useful without it. Even with a conventional spreader, knowing that one third of the field is consistently weak changes how you allocate input and where you sample.

Zoning is built on a published proxy relationship and every map carries its own retrieval confidence indicator. The zone pattern — which part of the field is strong and which is weak — is the reliable output and is what should drive variable rate application. For absolute values, calibrate against samples taken at the suggested sampling points marked on the map.

Not often. Soil carbon and texture change slowly, so once a season — or before a major input decision — is usually enough. The analysis runs on a stack of historical scenes up to the end date you set, so a longer history generally gives a more stable result.

Yes — Create / Edit Zones. You can adjust them because you know things about the field the satellite does not: an old boundary, a buried structure, or the corner that always floods.

The Soil Report gives one set of values for the field as a shareable PDF. Zoning gives values mapped across the field, resolved into management zones. Use the Soil Report for understanding overall soil condition and sharing with an agronomist or buyer; use Zoning for deciding where to vary input and where to take samples.

Everything CropGen holds on one field, compiled into a single downloadable PDF — crop health and crop details, weekly crop advisory, soil analytics and the analytics data. It is the artefact that leaves the platform, for a landowner, a lender, a buyer or a certification body.

At the same point in each cycle — monthly, or at each major growth stage. A sequence of dated reports is far more persuasive to a third party than a single snapshot, because it shows management over time rather than at a moment.

Anything about your farm — what to check this week, how crop health is doing, when to irrigate given recent weather, how to read the vegetation indices — and general agricultural questions beyond your own data. Suggested prompts cover the common cases.

Yes, within the focus you set. Choose All farms or a single field before asking — the answer is scoped to whatever is selected, so select the field first if the question is field-specific.

Yes. Double-check important farm decisions with your agronomist before committing input, labour or cost to them. Use the assistant to understand and explore, not as the final authority on a spend.

Boundary files. If the fields exist as GeoJSON, KML or Shapefile, they import directly rather than being marked by hand — dramatically faster and more accurate at scale. Talk to the LeanCrop team about bulk onboarding and an organisation workspace before you start.

Fields and reporting sit under one organisation workspace rather than as scattered personal accounts, and the custom arrangement adds admin team members, a dedicated account manager and priority support. Members join by entering the organisation code at sign-up.

Yes — white-labelled deployments on CropGen infrastructure are an established arrangement, and several partners already run their own branded platforms this way. Contact the LeanCrop team for scope and commercials.

API access is available as a commercial arrangement for partners who want the analytics inside their own application or dashboard rather than through the CropGen interface. Contact sales.

Carbon emissions, capture and net balance are tracked per field as a standing activity, with practice guidance aimed at improving capture. For clients with sustainability reporting obligations, that is the figure that feeds it, and Operations provides the practice record behind it.

Contact Sales on the plan screen, or the LeanCrop Agritech team directly. Enterprise and institutional clients already on custom plans should reach their dedicated account manager.

Yes. CropGen provides field-level + aggregated insights so FPOs can manage thousands of acres at once.

Yes. Input companies use CropGen to give precision advisory, validate product performance, and engage with farmers more effectively.

Yes. CropGen helps exporters track crop quality, traceability, and yield forecasts across large areas.

Yes. CropGen predicts yields using AI and satellite data, supporting procurement, insurance, and trade planning.

Yes. CropGen supports API integration with agri-business or government platforms (e.g., CROPIC).

Yes. CropGen delivers daily LLM-powered advisory for fertilizer, irrigation, and pest/disease management, customized by crop and growth stage.

My fields have disappeared: You are probably in the other account. Log out and sign back in with your original method — phone or Google, whichever you used first. No imagery for recent dates: Check the cloud percentage on the scene timeline, then switch to Satellite 1, which is unaffected by cloud. Health score looks too low: Check the boundary does not include roads, bunds, structures or a neighbouring plot. Correct it in Settings › Farm Settings. Growth stage looks wrong: Verify the sowing date. Staging is calculated from it, so an incorrect date shifts every stage-based recommendation. A field shows no analytics: Confirm the field is subscribed. Subscription state is shown on each card in Settings › Farm Settings. Advisories in the wrong language: Update Preferred Language in Settings › Personal Info. Not receiving WhatsApp messages: Check the number on your profile is the WhatsApp number, the field is subscribed, and CropGen is not blocked. Nutrient advice looks off: Check the crop, variety and sowing date on the field are correct — the targets are crop- and stage-specific. Area shown is larger than my plot: The boundary is over-drawn. Edit it in Settings › Farm Settings; this also affects the subscription amount, which is area-based.

The CropGen team at LeanCrop Agritech Pvt. Ltd. Include your registered phone or email, the field name, and the date you saw the problem — that is enough to reproduce almost anything. Enterprise clients should contact their dedicated account manager.