Rescuing an AI-built farm rental platform: 200+ customers and 1,000+ deliveries
The first version of this farm rental platform was built with an AI tool. It wasn't ready for real customers: login, payments, and security all had problems, it was buggy, and parts of it were unfinished. I took it over and built it into the full product: public site, customer dashboard with live cameras, plot-sizing calculator, farmer and admin tools, and Stripe payments for one-off harvests and subscriptions. It now runs 30+ live plots across 70+ acres, with 200+ customers and 1,000+ deliveries.
Farm rental and organic produce startup (name kept private)
The problem
An AI-built first version with problems in login, payments, and security, plus bugs and unfinished parts, for a business that takes money from customers in India and abroad.
What I built
A Next.js platform with a public site, a customer dashboard with live camera access, a plot-sizing calculator, farmer and admin tools, and Stripe payments for one-off harvests and subscriptions.
The result
30+ live plots on 70+ acres, 200+ customers, and 1,000+ deliveries across India and international markets.
Timeline
14 weeks
Budget
$40,000
What was wrong with the AI-built first version
The first version was built with an AI tool. Customer login, payments, and security had problems, it was buggy, and parts of the product were unfinished. For a platform where customers pay in advance and watch private camera feeds of their plots, none of that could go live as it was.
The problem: organic food nobody can verify
Urban families and NRIs want organic food they can trust, but store-bought organic comes with no proof of how it was grown. This startup's answer was to let people rent the farm itself: choose the crop, see it growing, and receive the harvest.
The idea is simple to explain and hard to run. Every request has to become a real plot, with the right farmer, a camera on the field, a payment, and a delivery at the end of the season. The product had to make all of that work without the customer ever visiting the farm.
One-time harvests and subscriptions with Stripe
Some customers want one rice harvest; others want vegetables every month. Stripe handles both on the same plot and delivery schedule, with invoicing for India and international customers in the same system.
How the farm rental platform works, from need to delivery
Every customer follows the same path, and each step is handled in the product, not in spreadsheets and phone calls.
01
Share the need
Crop, quantity, and delivery location, by form or WhatsApp.
02
Consultation and quote
A call confirms the crop. The platform sizes the plot and prices it.
03
Book and pay
One harvest or a subscription, paid through Stripe.
04
Sow and watch
A local farmer sows the crop and a private camera goes up.
05
Harvest and deliver
Produce is packed and delivered, with the invoice in the dashboard.
A plot-sizing calculator that works in kilograms, not acres
Customers think in what they want to eat, like 20 kg of rice for the year, not in plot sizes. I built a sizing engine that turns a target harvest into plot area, a plan preview, and a price, so the quote is clear before anyone pays.
It also keeps quotes consistent. Every customer asking for the same harvest gets the same plan, without someone working it out by hand.
Live farm cameras: proof instead of an organic label
Every rented plot gets its own private 24/7 camera link, shown in the customer's dashboard next to crop progress and deliveries. Watching the crop is part of the product, not a promise on the homepage.
I used third-party cameras rather than building a streaming system. That kept setup per plot fast and let the product launch sooner.
Matching each customer to the right local farmer
Each crop needs a farmer who knows it, and short shelf-life produce needs a farm close to the customer. Requests go through admin to a farmer with the right experience and location. The farmer recommends seeds and inputs, the customer confirms, and the platform tracks the crop through to harvest.
01
Customer
Books a plot and says what they want grown.
02
Admin
Reviews the request and picks a farmer by crop and region.
03
Local farmer
Recommends seeds and inputs, grows the crop, sets up the camera.
04
Live camera
The customer watches the plot from their dashboard.
Results
30+
live plots
70+
acres under management
200+
customers in India and abroad
1,000+
harvest deliveries
Key decisions
01
Plot sizing in the product, not a spreadsheet
Every sale starts with a quantity. Automating the plot plan keeps quotes fast and consistent.
Trade-off: The calculator needs crop-specific data to stay accurate.
02
Third-party cameras with a private link per plot
Building a camera system from scratch would have delayed launch. A private link per plot keeps it personal without owning the hardware.
Trade-off: Camera quality and uptime depend on the provider.
03
A consultation before every booking
Renting a farm is a big-trust purchase. A short call confirms crop, seeds, and delivery before a farmer is assigned, which means fewer mismatched plots.
Trade-off: Not a fully self-serve checkout.
04
One Next.js codebase for the site, dashboard, and admin
SEO pages, lead capture, login, the customer dashboard, and admin tools share one system and one deploy.
Trade-off: A larger application, but only one to maintain.
What the client said
“Milan turned our idea into something that actually runs the business, from the first enquiry to the harvest delivery. Customers love watching their plots live.”
Should a new product be self-serve, or start with a consultation?
For high-trust or high-price purchases, start with a consultation. It catches bad fits early and teaches you what customers actually ask. Once the questions repeat, you know what to automate. This platform books every plot after a short call.
Should I build features like video streaming myself?
Usually not in the first version. Use a proven third-party service and spend your budget on what makes your product different. This platform uses third-party cameras with a private link per plot, which let it launch sooner.
Can one codebase run a public website, customer dashboard, and admin?
Yes, and for a small team it's often the best choice. One codebase means one deploy, one login system, and shared data, so the marketing site, the dashboard, and the admin tools never drift out of sync.
Can software run a business that's mostly physical work?
Yes. The software doesn't grow the crop, but it runs everything around it: quotes, bookings, farmer assignments, payments, camera access, and delivery records. That's what lets the business grow past what a founder can track in spreadsheets.