Acc. XIII · Autolavandula turbinata — carwash queue system, cultivated 2026
Kintab — carwash queue and operations system
Technical founder · Product engineer · 2026 · Independent studio
An operating system for Philippine carwash shops covering live queue, bookings, payroll-lite, and real-time car-ready notifications across owner, staff, and customer roles.
Autolavandula turbinata — carwash queue system, cultivated 2026
Field notes
The context
Carwash shops run their queue on a whiteboard or a group chat, with no shared view of wait time, no automated way to tell a customer their car is ready, and payroll worked out by hand at the end of the week. Kintab replaces that with a role-based system spanning bookings, live queue, and commission payroll.
Cultivation
What I built
- Built the role-based PWA (owner/staff/customer) with a live queue driven by Supabase Realtime, combining bookings and walk-ins into one status feed.
- Built Web Push car-ready alerts and multi-tenant payment gating with manual verification across GCash, Maya, GoTyme, and bank transfer.
- Built Mission Control, the super-admin surface for tenant lifecycle and payment operations.
- Built the offline-first data layer — Workbox and IndexedDB with sync-on-reconnect conflict resolution — so staff can keep working the queue without signal.
- Built attendance tracking and commission payroll with CSV export, customer feedback with LLM-generated weekly digests, and EN/Tagalog/Taglish switching throughout.
- Wrote eight Playwright specs covering core flows, offline emulation, and ban enforcement, and produced the shop's complete marketing suite — brand kit, business cards, flyers, brochure, social assets, and promo video.
Root system
How it works
A three-app monorepo: a Next.js App Router landing site for SEO, a Vite + React role-based product PWA, and a separate Vite + React Mission Control admin app, sharing a Tailwind v4 design system and i18n locales. Zod schemas are the single source of truth on both the client and the Supabase Edge Functions that validate writes. Supabase Postgres carries multi-tenant RLS, email/OTP auth, per-queue and per-booking Realtime channels, Edge Functions for webhooks/LLM/push, and Storage for receipts and photos. GitHub Actions runs lint, typecheck, Vitest, and Playwright on every PR ahead of three independent Vercel deploys.
Harvest
Outcomes
- All three surfaces — landing, product PWA, Mission Control — are deployed.
- Web Push is feature-gated because VAPID keys are unset; Sentry and PostHog SDKs no-op because their keys are unset.
- Mission Control has no password/SSO gate yet on the free Vercel tier — a known pre-launch gap, not a hidden one.
- Pre-launch: no users or revenue.
Herbarium
The work itself




Multi-tenant payment gating with manual verification is a real product requirement in this market, not a stopgap — building it as a first-class state machine (rather than a boolean) made Mission Control's tenant lifecycle screen straightforward. Feature-gating unset integrations (push, error tracking) at build time is cheaper than fielding runtime failures from missing keys later.