SarthakBatra
Case studyEndura inventory management
Get in touch
Get in touch

Case study · Endura Healthcare · 2026

An inventory app for a medical business

I challenged myself to design a management app for my own wholesale medical business — inventory, purchases and sales, invoicing and tax — and ship it as real, running code.

Role
Head of Design
Year
2026
Industry
Healthcare
Platform
Web app
Built with
Claude · Supabase · Netlify
Medicines Tracker dashboard on a laptop

01 · Goal

End-to-end operations for a new wholesale business

A web app for the purchase–sale flow, distributors, inventory, invoicing, tax, and reports and forecasting.

  1. 01Purchases
  2. 02Sales
  3. 03Distributors
  4. 04Inventory
  5. 05Invoicing
  6. 06Reports
  7. 07Tax filing

02 · Methodology

Research, design, code, run it

01

Research

  • Map use cases against what’s already built
  • Study competitors’ user flows
  • Compare features and USPs
02

Design

  • Start with the primary use cases
  • Add complexity as new ones emerge
03

Implement

  • Production-ready code, not a prototype
04

Test in production

  • Run the business on it, and improve

03 · Research

What’s already out there

I used Google Gemini to find apps that might suit a medical business.

Zoho Books dashboard

Zoho Books

  • Pro: a deep ecosystem that scales with the business
  • Con: not designed for medical businesses
Vyapar invoice and tax invoice preview

Vyapar

  • Pro: built for Indian businesses; handles GST very well
  • Con: likely expensive for the full app
myBillBook payment-out screen

myBillBook

  • Pro: OCR auto purchase entry — photograph a bill, stock updates
  • Con: not designed for medical businesses

04 · Define

Use cases and functional requirements

Written requirements gave Claude the app’s context — who it’s for — so it could lay out the first screens and features.

Purchases

  • Add purchases
  • Inventory from purchase history
  • Cost-price history
  • Invoices for GST

Sales

  • Add sales
  • Inventory from sales history
  • Invoices for GST

Distributors

  • Distributor listing
  • Items linked to each
  • Business per distributor

Inventory

  • Product list
  • Sold by distributor
  • Inventory report

Invoicing

  • Purchase invoices
  • Sale invoices

Reports

  • Purchase and sale reports
  • Sales insights

Tax filing

  • P&L for tax filing
  • Expenses from bills

05 · Design

Why Claude over Gemini or Figma Make

Claude

Not just a design prototype

A real codebase on HTML, CSS and JavaScript. I had Claude store data in the browser, so the app ran locally without hosting or databases.

Slide 1 of 3: Not just a design prototype

06 · Visual mocks

From a design system to the first build

Step 1

Attach a design system that fits

I used Apple’s desktop app design system. To skip wireframing, creating or attaching a design system is a must.

Apple desktop design system components
Claude conversation with feature prompts
Step 2

Use cases, flows and feature prompts

  • Capture purchases and sales
  • Report purchases, sales and profit
  • Remember item details for next time
  • Dark and light modes

07 · Design + code

Five iterations, all running code

Iteration 1

Purchases, sales, basic reports

Totals of purchases and sales, and profit reports built from them.

Slide 1 of 5: Purchases, sales, basic reports

08 · Workflow

My AI design workflow

Figma to Claude to GitHub to Supabase to Netlify
  1. 01Figma

    Design with a fitting system

  2. 02Claude

    Upload or connect via MCP, with requirements

  3. 03GitHub

    Code, branches, versions

  4. 04Supabase

    Database, versioned in Git

  5. 05Netlify

    Latest build always live

Next case studyRedesign of SugarBox e-commerce appIn-Flight Entertainment · 2022

Thank you

Endura inventory management · Head of Design · 2026

Back to homepageAbout me