L. E.
enes
Back to selected work

Case study · 01

MiTaller360

Workshop management SaaS

A complete operational product that centralizes customers, vehicles, work orders, scheduling, receipts and workshop administration.

View live productView repository
Role
Co-founder · Full Stack Developer
Scope
Frontend, API, data and production
Product
Operational SaaS for automotive workshops
Status
Production deployed · Early validation
  • Next.js
  • TypeScript
  • Tailwind CSS
  • NestJS
  • Prisma
  • PostgreSQL
  • Resend
  • Vercel
  • Render
MiTaller360 workshop operations dashboard
MiTaller360 workshop operations dashboard

01 · Context

From scattered operational information to one workspace.

MiTaller360 began with a concrete operational problem: workshop information was spread across messages and manual records, making day-to-day follow-up harder than it needed to be.

The product brings the essential workflow into one place so a workshop can understand what is pending, what is in progress and what needs attention without reconstructing the operation from separate conversations.

02 · Product scope

End-to-end responsibility across the product.

As co-founder and developer, I work across interface architecture, backend services, data modeling, integrations, deployment and functional QA.

  1. 01Authentication, protected areas and role-based permissions.
  2. 02Workshop, customer and vehicle management.
  3. 03Work orders with operational statuses and event history.
  4. 04Scheduling and workshop agenda.
  5. 05Non-fiscal receipts with PDF generation and email delivery.
  6. 06Platform administration, invitations and audit events.
  7. 07Supplier and spare-part workflows connected to workshop operations.

03 · Technical decisions

Clear boundaries between interface, services and data.

The product uses a monorepo with independent web and API applications. This keeps deployment boundaries explicit while allowing the contracts between both sides to evolve as one product.

  1. 01Next.js App Router and TypeScript for the product interface.
  2. 02NestJS REST API as the backend authority for business rules.
  3. 03Prisma and PostgreSQL for relational modeling and migrations.
  4. 04Object storage for workshop logos and Resend for transactional email.
  5. 05Reusable server-first UI with interactive behavior isolated to leaf components.

Product gallery

The workshop workflow, seen in context.

Selected product states show how the operational system works beyond its main dashboard.

A work order connects the reported issue, diagnosis, parts, labor and final cost in one operational record.

A work order connects the reported issue, diagnosis, parts, labor and final cost in one operational record.

MiTaller360 work order detail with diagnosis, parts and costs
The daily workshop summary remains usable on mobile without reducing the operational hierarchy.

The daily workshop summary remains usable on mobile without reducing the operational hierarchy.

Responsive MiTaller360 dashboard on a mobile viewport
Search, status filters and counters provide a direct entry point into active workshop work.

Search, status filters and counters provide a direct entry point into active workshop work.

MiTaller360 work order search, filters and operational counters
The monthly schedule connects appointments with workshop capacity and related work orders.

The monthly schedule connects appointments with workshop capacity and related work orders.

MiTaller360 monthly workshop schedule

04 · Production delivery

A deployed product, not a static prototype.

The frontend is deployed on Vercel and the API and database run on Render. The product also includes its own domain, transactional email configuration and production communication between services.

Delivery includes responsive QA, role-based workflow checks and iterative corrections using real product states rather than isolated interface mocks.