Skip to content
M

Proof

Built, not promised

There's one real client so far, and no published testimonial from them yet — that's the honest stage this is at. What's here instead is real: working prototypes, self-initiated products, and the reasoning behind them. What isn't real yet is marked TBD.

Testimonials

No testimonials published yet.

TBD

Evidence

Four full case studies with embedded interactive prototypes

Verified

Salon OS, ChatStall, NOIR, and Architecture Studio each get a full case study (problem, flow, interface, system) with a working interactive prototype embedded in the page, not just screenshots.

View →

Real system design, not just visuals

Verified

Each case study documents the actual architecture behind it — data model, integrations, responsive approach — scoped the way a real engagement would be, not written as marketing copy.

View →

This portfolio, itself

Verified

The office-to-desktop experience you're in right now — a real state machine, a custom drag/resize window manager, dialogue-driven routing — is its own proof of execution, not a template.

Engineering practices

Scoped to what's actually true today for the live products — ChatStall and Wora.media — not a general capability list.

Authentication & access

Founder-reported

Sign-in and sessions run on Supabase Auth, with access scoped per account — a business only sees its own storefront and orders, a creator only their own campaigns and payouts.

Multi-tenancy & data isolation

Founder-reported

ChatStall is multi-tenant — each merchant's storefront, catalog, and orders are scoped to that merchant's own account, whether they're on a shared subdomain or their own connected custom domain.

Database & backups

Founder-reported

Both products run on Supabase-managed Postgres, which includes automatic backups — not a manual process someone has to remember to run.

Payment & payout handling

Founder-reported

Cashfree payment and UPI payout webhooks are signature-verified on arrival, and failed or duplicate events are logged and handled rather than silently dropped.

Error monitoring

Founder-reported

Production errors are tracked and logged, so a failure surfaces on its own instead of waiting for a user to report it.