Akshay Jayan
← All projects
Case study

Poovundo

Engineered the initial 0-to-1 platform, frontend architecture, and full UI/UX design to transform a localized, offline flower delivery concept into a high-conversion digital ordering experience for Onam festival committees.

Role
Product Design & Solo MVP Frontend Architecture
Period
2026
Status
Shipped
01 — Overview

Overview

A seasonal flower-ordering platform engineered to transition a complex, offline marketplace into a lightweight digital flow for Onam pookalam committees. Designed the full UI/UX system and architected the initial end-to-end frontend, focusing on a minimal operational footprint and a highly responsive checkout experience.

02 — Problem

The problem

Designed a custom commerce workflow capable of handling dynamic pricing shifts based on live daily wholesale market rates, shifting the traditional chaotic morning market run into a seamless, time-slotted online delivery system. Streamlined the entire purchasing funnel by weight, ensuring maximum clarity and responsive performance across mobile and desktop viewports under heavy seasonal traffic peaks.

03 — Design process

Design process

Worked with the founder to shape the customer journey, simplify the ordering flow, and translate the product requirements into a focused web experience.

04 — Architecture

Architecture

The website acts as a structured digital order-intake layer while the operational workflow remains connected to WhatsApp and human confirmation.

05 — Engineering decisions

Engineering decisions

06 — Trade-offs

Trade-offs

No significant trade-offs called out for this project.

07 — Challenges

Challenges

08 — Outcome

Outcome

Delivered a production-ready MVP from design tokens to full deployment within a tight seasonal timeline, providing a frictionless checkout loop that eliminated operational friction for regional buyers.

09 — Technology

Technology

Next.jsReactTypeScript
10 — Images

Images

Poovundo flower ordering experience
11 — Motion

Motion

Motion wasn't a deliberate focus for this project.

12 — Lessons learned

Lessons learned

  • Good product experiences do not always require complex systems.
  • The interface should reflect the actual business workflow.
  • Clear decisions and focused flows can remove friction from traditionally offline processes.