The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Ankuram Nursery is a domain-specific SaaS-enabled nursery management platform designed to digitize and centralize end-to-end operations of a plant nursery business. The system supports multi-role workflows across customers, administrators, managers, and field/service teams, enabling efficient handling of plant inventory, customer requests, bookings, orders, and service execution.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Finally sharing my new portfolio website.
I wanted to build something that feels like me — clean, interactive, and focused on the work rather than just listing skills.
Built from scratch with a focus on:
→ Clean UI
→ Smooth interactions
→ Responsive design
→ Clear project presentation
There’s still a lot I want to improve, but after a lot of designing, tweaking, and rebuilding, I’m genuinely happy to finally put it out there.
Take a look: https://portfolio-olive-chi-6a94ctldsf.vercel.app/
Really like the clean approach here. The focus on showcasing the actual work makes the portfolio feel much more engaging.
Building a 4-role real-time SaaS taught me one uncomfortable lesson: the hard part was never the code.
I've been building RestaurantOS — one platform connecting Owner, Kitchen, Waiter, and Cashier in a single live workflow (Table → Order → Kitchen → Serve → Billing → Reports).
The tech stack was the easy part. The real challenge: keeping 4 different roles in sync in real time without any of them stepping on each other's data — a waiter updating a table while the kitchen marks an item ready while the cashier is mid-billing.
That forced decisions most tutorials never cover:
⚡ How much state should live client-side vs. source-of-truth server-side
⚡ What "real-time" actually needs to mean per role (a kitchen screen needs sub-second updates, a report dashboard doesn't)
⚡ Designing failure states — what happens when the waiter's app loses connection mid-order
Currently redesigning the UI/UX layer too (motion, better visual hierarchy) while keeping this real-time core intact.
If you've built multi-role or real-time systems — curious what broke first for you. And if you're a founder who needs something like this built, my DMs are open.
the role based flow is easy to follow. what part was hardest to keep real time?
Now Live at https://img2m3.vercel.app/
When your landing Page is so goated that you no longer need a launch video.
Loving the actual Product more than the landing page.
Very usefull