~/raghav

$ ls ~/work --shipped

Work that ships.

Eight things I built for real people with real problems: a café losing orders, a college drowning in registers, a tea stall living on phone calls. Each one starts from how the business actually works, then gets engineered to keep working as it grows.

If you run a businessThe problem it fixes and what changes day to day.
If you build softwareArchitecture, the hard parts, the trade-offs.
If you designWhy each screen looks the way it does.

Cloud software/

Systems a business runs on every day. Live data, many users, roles, and no room for "it works on my machine".

cloud software · restaurant

Restaurant order system

No paper slips. No lost orders. No shouting across the counter.

Busy cafés lose money in the gap between the counter and the kitchen. Here, guests order from their own phone, the kitchen sees it the same second, and the owner reads the day's sales without touching a register.

Product flow

  1. Guest orders from their phonebrowse by category, cart, place order
  2. Kitchen board updates instantlyno refresh, no runner
  3. Placed → Accepted → Preparing → Readythe guest watches it move
  4. Owner checks menu, sales and ratingsedit prices, hide sold-out items

What changes: fewer wrong orders, faster tables, less running between counter and kitchen at peak time.

Under the hood

Next.js 15→Supabase Postgres→Realtime websockets
  • Orders pushed to the kitchen over websockets, not polling.
  • Each order line keeps its own price, so a menu change never rewrites old bills.
  • Staff passwords are checked on the server and never ship to the browser.
  • Load-tested with k6 scripts for the menu and order paths.

Design call

Built for one thumb at a table and a busy kitchen screen: big tap targets, colour-coded statuses, nothing to learn.

cloud software · institutions

Records platform

Registers and Excel files out. One searchable, audited source of truth in.

Institutions keep staff, student and visitor records across spreadsheets and paper registers, and nobody knows who changed what. One system with roles, bulk imports, exports and a full audit trail, in daily production use at an educational institution.

Product flow

  1. Admin sets up a module and its fieldsStudents, Staff, Visitors, anything
  2. Team imports Excel or adds recordsmap columns, validate, preview, confirm
  3. Search, filter and exportacross large tables
  4. Every change is loggedwho, what and when

What changes: one place to look, the right people see the right data, and who changed what is always one click away.

Under the hood

Next.js 16→one data layer→Supabase Auth + Postgres
  • Modules are data, not code: a new record type needs no deploy.
  • Permissions enforced twice, in the UI and by row-level security in Postgres.
  • Virtualised tables stay smooth with large datasets.
  • Soft deletes and an audit log on every write; 25 automated tests.

Design call

A calm, dense admin built for people who live in it all day: tables first, side drawers instead of page jumps, one search bar for everything.

cloud software · delivery

Tea delivery bookings

A tea stall that takes orders like an app company.

A mobile tea service was running on phone calls and memory. Customers now book a cup to their spot and see when it's coming; the shop accepts, sets an ETA and opens or closes from one dashboard.

Product flow

  1. Customer books cups to their spotname, phone, location, notes
  2. Shop accepts and sets an ETAor rejects when it's too busy
  3. Customer sees status and ETAno "where's my tea?" calls
  4. Marked donetoday's numbers update on the dashboard

What changes: no missed calls, a clear queue, and the owner knows the day's demand at a glance.

Under the hood

HTML + JS→Express API→MongoDB Atlas
  • Stateless API that runs serverless on Vercel.
  • Admin token on every staff route; customers only ever see their own bookings.
  • Rate limits, input validation, security headers, salted password hashes.
  • Route tests run against an in-memory database stand-in.

Design call

Made for a cheap phone in bright sunlight: one form, big buttons, status in colour. The open/closed switch sits right at the top, where the owner needs it.

Apps/

Products built around one behaviour people already want, with every screen designed to get them there faster.

mobile app · social

MeetX

From scrolling to sitting across a table, within the hour.

Everyone's online, nobody's meeting. MeetX shows who's nearby and free right now: knock with one line, chat briefly, meet over coffee. Launching in Bengaluru.

Product flow

  1. See who's nearby and free nowprofessional and social discovery
  2. Knock with one lineno endless swiping
  3. A short-lived chat opensjust enough to set a place and time
  4. Meet in persontables and local offers help pick the spot

Under the hood

Expo appReact admin→Express API→MongoDB
  • One API serves the mobile app and the moderation dashboard.
  • Temporary chats by design: less data kept, less to moderate.
  • Admin tools for users, meetups, offers and reports from day one.

Design call

No feed, no likes. Every screen pushes toward meeting offline, which is the whole point of the product.

app prototype · small business

ShubhSandesh

Every customer greeted on Diwali, before the shop even opens.

Indian shop owners want to greet every customer on festivals but run out of time. A ready post with their name and logo, a reminder on the festival morning, and one tap per person on WhatsApp.

Product flow

  1. Reminder on the festival morning
  2. Greeting ready with name and logopick a design
  3. Pick the message and the people
  4. Send on WhatsApp, one tap each

What changes: a job that took an evening takes a few minutes, and every customer feels remembered.

Under the hood

HTML · CSS · JS→GitHub Pages
  • Clickable prototype to validate the idea before building the backend.
  • Shipped with a trailer and a printable pamphlet for go-to-market.

Design call

Designed for someone on their first smartphone: one step per screen, festive but readable, WhatsApp where they already are.

Websites/

Sites that do a job, not just look nice: book calls, collect documents, teach.

website · consulting

Consultancy site

A personal brand that books its own calls.

A career and MBA consultant needed more than a brochure. Visitors book a free consultation into real open slots; the consultant confirms bookings, blocks dates and edits services and testimonials without calling a developer.

Product flow

  1. Visitor reads services and proof
  2. Books a free call in an open slotblocked dates are never offered
  3. Consultant confirms in the admin
  4. Content kept fresh by the ownerservices, testimonials, site settings

Under the hood

React + Vite→Express on Vercel→MongoDB
  • Data models for appointments, blocked slots, services, testimonials and site preferences.
  • Protected admin routes; the public site reads the same API.

Design call

Trust first: a face, track record and one obvious action, "Book free consultation", repeated where people decide.

website · tax practice

Tax documents site

Tax paperwork without the email ping-pong.

A tax practice in Canada was chasing clients over email for forms and files. Clients now send their request and documents in one form and sign the engagement consent on screen; the practice sees everything in one dashboard.

Product flow

  1. Client fills the service requesttax years, situation, contact
  2. Uploads documents with progressno attachments lost in email
  3. Signs the consent on screen
  4. Practice reviews in the adminwith enquiry analytics

What changes: complete files on day one, fewer follow-ups, faster turnaround.

Under the hood

Next.js→Supabase Postgres + Storage→Upstash Redis
  • Files go straight to object storage, linked to each request.
  • Rate limiting on public endpoints with Redis.
  • Admin login and an analytics view for enquiries.

Design call

Calm and form-first, with clear progress on uploads, so handing over personal documents feels routine rather than risky.

website · editorial

Scent Stories

Perfume, explained without the snobbery.

Buying perfume in India is intimidating for beginners. A gentle illustrated guide: how a perfume is built, the four big scent families, and brands worth trying first.

Product flow

  1. Start with how perfume works
  2. Top, heart and base notes
  3. Find your scent family
  4. Brands to try first

Under the hood

HTML · CSS · JS→JSON content→static hosting
  • No framework, no build step: loads fast on any phone.
  • A pause-motion control for people who prefer less animation.

Design call

Editorial, not e-commerce: serif type, hand-drawn botanicals and slow motion that make a beginner want to keep reading.

$ ping raghav

Got a problem like these?

Tell me how your business runs today. I'll tell you what I'd build, what it costs and when it ships.

Start a conversation

Screens are from the real apps running locally with fictional demo data, or from the live sites. Use the Phone / Desktop switch on each project, and tap a screen to open it.