Skip to content
Back to the portfolio

Samurai: Motorcycle Shop Management

  • React
  • TypeScript
  • Supabase
  • PostgreSQL
  • Vite
  • TailwindCSS
  • Vercel

My role

A custom project for Samurai: I handled the product, the development and the operation on my own, with 206 commits from January to September 2026.

I built a mobile-first web system designed for a tablet at the workbench. A bike checks in with the customer, vehicle details and photos; the quote is built on the spot, with the photos, and turns into a job with one click. Each job has a status and progress photos, and the work order comes out as a PDF with check-in and check-out photos and a signature. There is also shipping calculated by ZIP code, reports with Excel export and user management with an activity log. The front end is React + TypeScript + Vite; the back end is Supabase (Postgres with RLS, Storage and Edge Functions), deployed on Vercel, with the code organized into domain, use cases and infrastructure.

Before

Quotes and job tracking without a dedicated system and with no record of the bike's condition at check-in, which left room for claims about missing or broken parts.

The problem

A motorcycle alignment shop needed to track check-ins, quotes and jobs in progress in one place, with proof of each bike's condition and reliable business numbers. With no record of how a bike arrived, there was no way to respond when a customer claimed a part was missing or broken.

The solution

I built a mobile-first web system designed for a tablet at the workbench. A bike checks in with the customer, vehicle details and photos; the quote is built on the spot, with the photos, and turns into a job with one click. Each job has a status and progress photos, and the work order comes out as a PDF with check-in and check-out photos and a signature. There is also shipping calculated by ZIP code, reports with Excel export and user management with an activity log. The front end is React + TypeScript + Vite; the back end is Supabase (Postgres with RLS, Storage and Edge Functions), deployed on Vercel, with the code organized into domain, use cases and infrastructure.

Decisions and trade-offs

Photos are compressed in the browser before upload and stored in two versions, thumbnail and original, with long caching, to fit the Supabase plan. Pagination and search run on the server instead of loading everything on screen. Row-level security (RLS) lives in the database itself. Use cases are covered by tests, with mutation testing.

The results

The system has been in production since early 2026, with 365 work orders and 255 customers on record. According to the owner, building the quote on the spot, on a tablet and with photos of the bike, helped close deals with more than one customer, and the check-in and check-out photos in the work order have almost ended the claims about missing or broken parts. In August I optimized how photos and queries travel, and Supabase egress dropped from 7 GB to 400 MB a month, which keeps the system within its plan.

Testimonial

The system changed the way Samurai works. At workshops with other shops, almost everyone still uses pen and paper; I open the system on my tablet and have everything at hand, wherever I am. I've closed deals with more than one customer because they watched the quote being put together on the spot, with photos of the bike. And since we now take photos at check-in and check-out, and they go on the service order, the arguments about missing parts or parts that arrived broken have almost stopped.

Heitor Asaeda, Owner of Samurai

Results by the numbers

  • 365service orders issued
  • 7 GB → 400 MBSupabase egress per month
  • 255customers on file
  • Entrada + saídaphotos on every service order
  • 38test files