Go to…

↑ ↓ to move · Enter to open · Esc to close

← All projects

Product platforms · Professional work

Owning Spacez PMS, from architecture to daily operations.

End-to-end development across 55+ PMS modules: bookings, calendar, pricing, operations, finance, media, communications, and owner/franchise portals, with a shared design system and Android delivery.

SDE 1 · Spacez Pvt LtdShipped · Web & Android
  • Next.js
  • TypeScript
  • Firestore
  • Firebase Admin
  • Zustand
  • Capacitor
  • Claude API

~/spacez/pms · internal platform

55+operations modules
Web+ Android delivery
  1. 01
    Product workflows

    Bookings, calendar, pricing & daily operations

  2. 02
    Teams & portals

    Access controls, owner/franchise portals & communications

  3. 03
    Platform delivery

    Architecture, backend, shared design system & Android

Capability overview · not an internal product screenshot

01 / context

The product and my role

My contribution spans Spacez and Spacez PMS (Product Management Systems). I own the PMS end-to-end across architecture, backend, frontend, the shared design system, and its caretaker Android app. Its 55+ modules cover bookings, calendar, pricing, invoices, expenses, issues, media, and communications. CashBook is one finance module within this broader platform.

02 / contribution

What I worked on

  • Led architecture, backend, and frontend development across the 55+ module PMS.
  • Developed workflows across bookings, calendar, pricing, daily operations, issues, media, and communications.
  • Built per-section role-based access, external owner/franchise portals, and shared statements, conversations, and request queues.
  • Authored the shared design system and custom design-lint rules enforced before builds and commits; shipped the Capacitor Android app with FCM push and an audit trail.
  • Built the CashBook module for wallet webhook ingestion and derived balances, reconciling seven spend sources while normalizing paise/rupee units and separating cash movements from actual spend.
  • Built B2B proforma and tax invoicing with canonical numbering, add-on line items, server-side PDFs, and in-app previews.
  • Shipped OCR and Claude API document verification with per-document caching, plus an edit-distance classifier for untagged spends.

03 / engineering

Design considerations

Scope access to each team's work

Per-section access controls support internal teams, while owner and franchise portals expose the relevant statements, conversations, and request queues. The shared platform serves different workflows with scoped views.

Make interface consistency part of delivery

The PMS design system is backed by custom lint rules in prebuild and pre-commit. Violations fail the build, making design conventions enforceable across the platform.

Keep finance rules explicit within CashBook

The wallet provider exposes a webhook feed but no balance API, so balances are derived from a seed baseline and an immutable cash-movement log. Reconciling seven spend sources requires consistent paise/rupee units and a separation between cash movements and actual spend to prevent double counting.

Cache verification at the document level

Expense bills and receipts are OCR’d and checked against claimed amounts via the Claude API. Results are cached per document so verification results can be reused.

04 / outcome

Where the work stands

Delivered the 55+ module PMS across web workflows, backend services, the shared design system, owner/franchise portals, and the caretaker Android app. This overview covers my work across the platform; the internal product and employer source code are not public.