← Elevate Aura  ·  Real platforms shipped for real businesses Chennai, India · WhatsApp
Case study · Chennai

Carna Medicare: a 12-module operations platform for a medical equipment distributor.

A medical-equipment distribution business in Chennai was running on WhatsApp and Excel. Elevate Aura built a 12-module operations platform with a field-staff app, a manager dashboard, GST billing, payment tracking and service tracking, and shipped it in 30 days.

Medical equipment · ChennaiReact Native, Supabase, WordPressShipped end to end in 30 days
In one sentence

What was built, and for whom

Carna Medicare is a medical-equipment distribution business in Chennai. Elevate Aura built and shipped a 12-module operations platform for it: a field-staff mobile app, a manager dashboard, GST billing, payment tracking and service tracking, on React Native, Supabase and WordPress, delivered end to end in 30 days.

It is the project Aura Business grew out of, which is why the product covers the sale, the stock, the service contract and the invoice rather than only the pipeline.

Before

The situation

The business was run entirely on WhatsApp and Excel. That is not unusual for a founder-led distribution business, and it works for a while: the owner holds the picture, the field team reports by message, and the spreadsheets are close enough to true on the day they are updated.

The limits show up in the places where two people need the same answer at once. Which quotation went out, at what price. Whether that invoice was paid. Which unit went to which customer, and when its service is due. What the field team did yesterday, and what proof exists. Every one of those answers existed somewhere, in a chat thread or a tab, and each one had to be asked for.

The build

What was built

One platform covering twelve modules, split across two interfaces: a web dashboard for the office and a mobile app for people in the field.

  • Field-staff app. Built in React Native so the team in the field works from a phone rather than reporting back by message.
  • Manager dashboard. A single web view of what is happening across sales, payments and service.
  • GST billing. Tax invoicing native to the platform, so the invoice is raised where the order is.
  • Payment tracking. What has been invoiced, what has been received and what is outstanding, in one place rather than in a receivables sheet.
  • Service tracking. Service work recorded against the customer and the equipment, so history is kept rather than remembered.
  • Website. Built on WordPress alongside the platform.

The data layer is Supabase, which is what keeps the office dashboard and the field app working from the same records rather than from two copies.

The method

How the work ran

Every Elevate Aura build follows the same 30-working-day framework, and this one was no exception.

Discovery

Scope is fixed before anything is built: which modules are in, what each screen has to do, and which parts of the existing way of working are kept rather than redesigned. Fixed scope is what makes a 30-day timeline meaningful rather than optimistic.

Configure

The workspace is set up with the customer's branding across the dashboard, the app and the invoices, and the modules are switched on and shaped to how the business actually works.

Migrate

Existing Excel data is brought in, so the customer list, products and open records become the starting point instead of something to retype.

Train

Office staff learn the dashboard and field staff learn the app, and support afterwards comes directly from the person who built it, on WhatsApp and in person in Chennai.

Before and after

What each part of the platform replaced

Module or componentWhat it replaced
Field-staff mobile app (React Native)Field updates sent as WhatsApp messages and photographs
Manager dashboardAsking each person, then assembling the answer in a spreadsheet
GST billingInvoices prepared separately from the quotation that produced them
Payment trackingA receivables sheet updated whenever somebody had time
Service trackingService history held in an engineer's memory and a chat thread
Shared database (Supabase)Several copies of the same workbook, each slightly different
WordPress websiteEnquiries arriving only through phone and WhatsApp
After

What it changed

The change is a change in where the record lives. Work that used to be reported now writes itself: a field visit is logged in the app rather than described in a message, an invoice is raised from the order it belongs to rather than rebuilt, and service done on a machine is attached to that machine rather than to whoever remembers it.

For the office that means the answer to an operational question is looked up instead of asked for. For the field team it means the day ends without a round of reporting messages. For the owner it means one dashboard rather than a set of separate files that have to be reconciled before they can be trusted.

The platform is the origin of Aura Business, now a productised version of the same work with 12 suites and 87 modules, running in distribution businesses in Chennai today.

Questions

About this project

What exactly was delivered?

A 12-module operations platform with a field-staff mobile app, a manager dashboard, GST billing, payment tracking and service tracking, plus a WordPress website. The stack was React Native, Supabase and WordPress, and it was shipped end to end in 30 days.

Is 30 days realistic for a platform this size?

It is the standard Elevate Aura framework: live in 30 working days where scope allows. It works because the scope is fixed in discovery and because one person builds the whole thing, so there is no handover between teams.

Can we get the same platform?

The productised version is Aura Business, with 12 suites and 87 modules priced by module tier and unlimited users. Custom work is scoped on a call when a business needs something outside those modules.

What happened to the existing spreadsheets?

They were migrated in during setup. Customer lists, products and open records become the starting data in the platform, and exports remain available whenever a spreadsheet is the right tool for a specific analysis.

Who supports the platform afterwards?

The founder, Ragul Sekar, who built it. Support is direct on WhatsApp and in person in Chennai, rather than through a ticket queue or an account-management layer.

The product pages

What this platform became

Have a similar problem to solve?

Tell us how your business runs today and we will scope what a platform like this would look like for you, with a fixed timeline.

Founder-led · Chennai, India · Built and supported by the person who wrote it