Operations platform

E‑Grúa

A multi-sided platform for crane and forklift operations, connecting customers, operators, and administration through responsive web experiences.

Scope
Product, shared contracts, and platform
Role
Principal end-to-end author
Stack
Next.js · React · NestJS · Prisma · PWA · Zod

The problem

A field service platform has different people, permissions, locations, documents, pricing rules, and moments of urgency. Each surface must stay clear while the system stays consistent.

Decisions

  • Separate customer, operator, and admin responsibilities without duplicating the domain model.
  • Use shared schemas to keep API, validation, and interfaces aligned.
  • Design for mobile-first work while keeping administration legible on larger screens.

Evidence

  • Customer and operator PWA surfaces plus an administration dashboard.
  • Shared TypeScript and Zod contracts across client and API boundaries.
  • Operational concepts including verification, documents, pricing, ratings, and reporting.

What I learned

  • Multi-sided products become understandable when each role sees only the next useful decision.
  • Shared contracts are a product tool: they keep promises consistent across surfaces.

Keep going?

Let’s talk about the real problem.

Start a conversationjacksonochoa135@outlook.com