Ankuram Nursery
How a simple request for an online store turned into a custom commerce platform with logistics automation, order workflows, payment reliability, and a foundation for future multi-tenant growth.
Building Software Around a Business, Not Just a Website
Every project starts with an idea. Sometimes that idea changes completely once you begin.
When we first spoke with Ankuram Nursery, the request sounded simple. They wanted a website where customers could order plants online. We assumed it would be another e-commerce project with products, a shopping cart, payments, and order tracking.
But after a few meetings, we realized we had misunderstood the problem.
The nursery already had a website where customers could see their products. The real challenge wasn't selling plants online. It was everything that happened after an order was placed.
Understanding the Business Before Writing Code
Before writing any code, we spent time understanding how the business actually worked. We talked to the people handling orders, deliveries, and customer calls. Instead of discussing features, we asked questions about their daily work. How do orders move from one person to another? What causes delays? What problems do they face every day?
That time turned out to be more valuable than any technical planning.
The more we learned, the more we realized this wasn't a typical online store.
A Business with Unique Processes
Plants weren't sold one by one. Most products were sold in trays, crates, or bulk quantities. Customers had to order a minimum quantity. Deliveries within Maharashtra usually went through bus services, while orders outside the state were sent by railway. Employees managed everything through spreadsheets, phone calls, and WhatsApp messages. It worked because the team had years of experience, but many important business rules existed only in people's minds.
There was one moment that repeated throughout the project.
Just when we thought we understood the complete process, someone would smile and say, "There's one more thing..."
Sometimes it was about how a certain product should be packed. Sometimes it was about transport. Sometimes it was a special case they had learned to handle over the years.
Those "one more things" slowly became the real project.
Building Around the Business Instead of Changing It
At one point, we thought we could simply customize an existing e-commerce platform. The more we understood the business, the clearer it became that this approach would force the nursery to change the way they worked. Instead, we decided to build software that adapted to their process instead of asking them to adapt to the software.
That decision shaped everything that followed.
Solving Railway Deliveries
One interesting challenge was railway deliveries. Customers needed to choose a railway station instead of a home address. Our first idea was to build our own database of railway stations. It seemed reasonable until we realized we would also become responsible for maintaining thousands of stations and keeping the information updated.
Instead of creating another problem for ourselves, we found RailRadar, which already maintained this data. We reached out to the maintainer, explained what we were building, and integrated their service into our platform. Looking back, that simple decision probably saved us weeks of future work.
Sometimes the Simple Solution Wins
Not every problem needed a complex solution, though.
For bus deliveries, we searched for APIs that could help us. After discussing the actual workflow with the client, we realized they only used a fixed list of pickup locations. Building a simple managed list solved the problem perfectly. It reminded us that the best solution isn't always the most advanced one. Sometimes understanding the business leads to a much simpler answer.
Improving Internal Operations
As development continued, we also noticed something interesting.
The biggest improvement wasn't for customers.
It was for the people working inside the nursery.
Earlier, employees constantly coordinated through phone calls and messages to know what was happening with an order. As the number of orders increased, keeping everyone updated became harder.
The new platform brought everything into one place. Instead of asking someone for the latest status, employees could simply check the system. They knew what had been completed, what was waiting, and what needed attention next. Small improvements like these saved time every day and reduced unnecessary communication.
From Operations to Growth
After the first version was launched, our conversations with the client also started changing.
Initially, every discussion was about making operations easier. Once that became smoother, they started thinking about growth. They wanted referral rewards, loyalty programs, and easier sign-in options to improve the customer experience.
It was interesting to see how solving one set of problems created space to think about the next ones.
The Biggest Lesson
Looking back, one thing stands out more than anything else.
Building the software wasn't the hardest part.
Understanding the business was.
Many businesses have processes that have evolved over years. From the outside, those processes may look complicated or even unnecessary. But once you spend time with the people doing the work every day, you realize every small step usually exists for a reason.
This project reminded us that good software isn't about adding more features. It's about solving real problems without forcing people to change the way they work.
What started as "Can you build us a website?" became something much bigger. Together with the client, we transformed years of experience, spreadsheets, phone calls, and daily routines into a platform that supports the business as it continues to grow.
The biggest lesson we took away from this project was simple.
Before writing code, spend time understanding the people behind the business. The better you understand their work, the simpler—and more useful—the software becomes.
Tech Stack
Next.js
Tailwind CSS
Spring Boot
PostgreSQL
Git
Docker
Nginx