Watermelon Group – Software That Doesn't Taste Like Cardboard

Squeezed In-House

We drink our own juice.

Zevvy is our own product, not a client project. It is where we find out whether the things we believe about software hold up when we are the ones getting paged.

"A charger she could not use, on a highway, at night."

Zevvy started when a family member was stranded because the only charger in reach was incompatible with her car. Nobody had told her. The information existed, scattered across networks that had no reason to talk to each other. That gap is the product.

Route planning that respects the battery

Plans routes that keep charge above twenty percent rather than assuming the driver enjoys arithmetic at 3 percent.

Compatibility from the people who plugged in

Model-specific charger compatibility filtered from community reviews, because the spec sheet and the physical port disagree more often than they should.

Emergency search

Low-battery mode surfaces the nearest charger that will actually work, plus what is walkable while you wait.

Society charging, managed

A live dashboard for apartment complexes: compound map with per-charger status, queue, slot reservations, and auto-billing.

We ship it to our own standard.

Zevvy runs as three codebases: web, iOS, and Android. Nothing reaches master without passing the verification suite.

Codebases

<0.05

Cumulative Layout Shift

<3s

Largest Contentful Paint

320px

Smallest Supported Viewport

Contrast, Enforced In CI

Visit Zevvy See the society dashboard

Served To Production

A better way to pour tea.

Tapri Chai Canada needed to handle orders without forcing store managers to decipher emails.

"Every catering quote was a spreadsheet, a phone call, and a leap of faith."

When the primary constraint on your business growth is how fast a human can manually copy an order from an email into a point-of-sale system, you don't have a food problem, you have a data entry problem. We built a digital storefront that natively pipes orders directly into the kitchen's existing workflow.

Ordering, built rather than rented

A React frontend on top of an order management API we wrote, so the cafe is not stuck inside whatever a restaurant site builder allows this year.

Delivery, checked before it is promised

Orders are validated against the delivery radius before checkout, so nobody pays for a delivery that was never going to happen.

Catering without the back and forth

A guided builder that handles course selection, minimum guest counts, and notice periods, and puts a running estimate in front of the customer instead of a quote request form.

Digital Menu

Brand Story

Catering Configurator

Storefront

NEXT.JS REACT NODE.JS FIREBASE CLOVER API GOOGLE ANALYTICS RENDER NETLIFY

$10,000

REGIONAL DIGITALISATION GRANT

150+

MENU ITEMS SYNCED LIVE

95+

LIGHTHOUSE SCORE

40%

FASTER AVERAGE PAGE LOAD

1.41K

ORGANIC CLICKS IN THREE MONTHS

Visit Tapri Chai

Beneath the rind

We cut into messy problems.

The name Watermelon Group came from wanting to slice into complex systems and reveal clean, structured layers beneath. We don't just ship features—we architect solutions that remain legible long after the first deploy.

The seeds are the data. Everything else is arranged around them.

THE RIND

WHAT USERS TOUCH

THE PITH

API SURFACE

THE FLESH

SERVICES AND LOGIC

THE SEEDS

THE DATA

Two Seeds

Every melon starts with two seeds.

No account managers, no handoffs. The people who scope it are the people who build it.

Chirag Kansal

Co-founder & Director

Architecture and capital

Handles the architecture, the product decisions, and the conversations with capital. Spends most days deciding what a system should look like three years from now, then arguing with the version that exists today. Believes a schema is a promise you make to your future self.

Systems Product Investor Relations

Vinamer Aggarwal

Co-founder & Director

Operations and business

Runs the side of the company that isn't a repository. Operations, client conversations, pricing, and the decisions about what we take on and what we turn down. The reason a scope stays a scope and a deadline stays a date.

Operations Business Client Relationships

HOW WE CUT IT

Three ways to start.

Most work starts with a conversation about what is actually broken. After that, it usually looks like one of these.

Build

A defined scope, a fixed timeline, and a system that is yours at the end of it. Best when you know what you need and want it built properly the first time.

Rescue

An existing codebase that has stopped being safe to change. We map it, make it legible, and hand back something a team can work in again.

Retained

Ongoing engineering capacity for teams that need senior hands without hiring for them. Monthly, scoped in advance, cancellable.

Not sure which one this is? Describe the mess and we will tell you.

Leave us something messy.

A failing cron job, a sketch of an app, a system diagram that scares your PM. We'll take a look.

You can reach us at watermelongroupprivatelimited@gmail.com or call us at +91 79732 27505.

Whether it's a greenfield build or untangling legacy spaghetti, we're here for the problems that need both precise engineering and a bit of poetry.

Software shouldn't taste like cardboard.