Devansh KhetwaniDK
All projects
Internal use

Next Web Agency

Client tracking and project delivery tooling used for my own freelance engagements.

  • React
  • Vite
  • Express
  • MongoDB

Keep client delivery in one place

Next Web Agency supports my freelance engagements, from prospective-client inquiries to project milestones and delivery documents. It is deployed for internal operations.

Building the delivery pipeline

I built frontend interfaces, API services and persistence for lead tracking, projects, tasks, collaborator assignments, documents and billing.

Extend the ERP foundation

The application adapts shared Next Web Works patterns for tenant scoping, authenticated routes, audit fields and React components. Agency-specific workflows sit on that foundation rather than becoming a disconnected application.

  1. Lead and scope
  2. Project and milestones
  3. Tasks and collaborators
  4. Documents and delivery
An internal delivery workflow rather than a claim of external SaaS adoption.
Systems Architecture · WebGL Topology

Interactive 3D Distributed Systems Graph

Live 3D topology visualizing service boundaries, isolation contracts, and asynchronous document rendering pipelines.

DRAG TO ORBIT · CLICK NODE TO INSPECT
Presentation Tier

Web Client

Next.js 16 · React 19
Protocol & TransportHTTPS / WSS · 120fps GSAP
Architecture Contract

App Router RSC with client-side interactive leaves and zero-latency audio synthesis.

Click any node in 3D space to focus its technical boundary.

Make handoffs explicit

Leads become scoped projects; projects contain milestones and tasks; documents preserve delivery context. Keeping these records connected makes the current state of a freelance engagement easier to follow.

Used internally

This is practical tooling for my own client delivery. I do not claim third-party agency adoption or public SaaS traction. Client briefs, contracts and operational records remain private.

Discuss this work

Discuss this workAll projects