3.1.5WEB_APP_DEV

Not a marketing site. A product surface.

Customer portals, internal dashboards, B2B SaaS MVPs, partner portals — anything that needs auth, RBAC, billing, realtime, and an audit log. Success metric is DAU, not bounce rate.

AUTH_TO_LAUNCH

< 2 WEEKS

UPTIME_SLA

99.9%

OWASP_TOP10

REVIEWED

the_logic

A portal is not a website with a login page bolted on.

Customer portals, vendor dashboards, SaaS MVPs, and member platforms have different success metrics, different failure modes, and different architectural requirements than marketing sites. Bounce rate does not matter. Session length and task completion do. OWASP top 10 is not optional. Multi-tenancy has to be right from day one — retrofitting it is expensive.

We start with auth, RBAC, and data model — not with the UI. Clerk or Auth0 for identity, Neon/Supabase for Postgres, Razorpay subscriptions for billing, Inngest or BullMQ for async jobs. The foundation is not exciting, but every shortcut taken here becomes a production incident six months later.

India-specific additions: Razorpay subscriptions with GST 18% on every invoice, INR and USD in the same billing module, UPI for one-time payments, and Sentry + Posthog for observability from day one. Not after the first incident.

capabilities

01
Auth + RBAC + multi-tenancy
Clerk or Auth0, role definitions from day one, tenant isolation at the data layer — not checked in week 8.
02
Billing (Razorpay + GST)
Subscription plans, one-time payments, UPI, INR + USD, GST 18% on invoices, proration. Handled cleanly.
03
Realtime
Supabase Realtime, Pusher, or WebSockets — presence, notifications, and live data depending on what the feature needs.
04
Async jobs + queues
BullMQ on Redis or Inngest for background tasks that should not block the request cycle.
05
Audit logs + observability
Sentry for errors, Posthog for product analytics, a full audit log table for every state mutation that matters.
06
Security review at launch
OWASP top 10 walkthrough, dependency audit, environment variable hygiene check — before a user touches it.

runtime.exec

How it actually runs.

STEP_01 · SCOPE

MVP scope definition

Draw the line between must-have and gold-plate. Define success metrics before a schema is designed.

$ scope --mvp=defined --success-metrics=dau,task-completion

STEP_02 · SCHEMA

Data model + schema design

Postgres schema, relations, indexes, and multi-tenancy strategy agreed before a component is built.

$ schema --tenant-strategy=row-level --rls=true

STEP_03 · FOUNDATION

Auth + RBAC + billing

Clerk/Auth0, role tables, Razorpay subscription plans, and GST invoicing — live before any feature work.

$ foundation --auth=clerk --billing=razorpay --gst=18pct

STEP_04 · BUILD

Feature build with CI + previews

Every PR gets a preview URL against a test DB. No direct pushes to main.

$ build --previews=per-pr --db=test-branch

STEP_05 · STABILISE

Launch + 30-day stabilisation

Sentry + Posthog live at launch. 30-day SLA for production bugs. Retainer priced at kick-off, not post-incident.

$ launch --observability=sentry,posthog --sla=30d

use_cases

Where this gets deployed.

Customer dashboards + self-serve portals

Clients log in, see their data, download invoices, and raise requests — without emailing your ops team.

B2B SaaS MVPs (0→1)

Auth, RBAC, billing, and core feature loop — production-quality in 8–12 weeks, not a prototype.

Internal admin consoles

Ops-facing tools that your team actually uses — kanban boards, approval queues, bulk action tables.

Vendor and partner portals

Tiered access, per-vendor data isolation, settlement dashboards, and document uploads.

Member + community sites with paid tiers

Gated content, subscription tiers, Razorpay billing, member directories.

Two-sided marketplaces

Buyer + seller portals, split settlements, escrow logic, dispute queues.

Recruiter + applicant portals

Job posting, application tracking, interview scheduling, and offer-letter generation — in one authenticated surface.

Training and LMS platforms

Course access by subscription tier, progress tracking, certificate generation, cohort management.

case_study

EDUCATION

Pune test-prep company replaced a 4-FTE manual process with a parent + student portal. Support tickets down 68%.

A ₹50cr revenue test-prep brand was managing fee payments, batch schedules, and progress reports across WhatsApp groups, Excel sheets, and a front-desk team of 4. We built a parent + student portal — Razorpay subscriptions for fees, batch and schedule management, and a progress dashboard per student. The ops team of 4 was redeployed. Parents stopped calling to ask if fees had cleared.

SUPPORT_TICKETS

−68%

FEES_ON_TIME

61 → 89%

FTE_REDEPLOYED

PARENT_NPS

+31

next_step