In progress

Trustivo Car Rentals

Business workflows
Product design
Data consistency

A rental booking and fleet-management platform. I developed the concept and designed the layout, features, and workflows, using AI guidance and implementation assistance.

Visit live site

Skills used

Defining requirements
Workflow design
Interface design
Translating business rules

What I’m learning

How a Next.js application connects its interface, database, authentication, and external services. A key lesson: a working interface still needs consistent rules and end-to-end validation.

Developed with AI assistance. My role, implementation details, and evidence are described below.

Trustivo Car Rentals homepage with a blue-accented introduction and pickup and drop-off date search — Public homepage captured October 19, 2026. The screenshot shows the interface; booking, payment, and owner workflows were not exercised during this visit.

The idea behind Trustivo

Trustivo brings a renter-facing booking experience and owner-management tools into one application for a small rental fleet. The project also includes earlier, separate spreadsheet-analysis work. Its development story moves from organizing rental data to designing a web interface for finding vehicles, making reservations, and managing operations.

My role and tools

I originated the concept and designed the layout, features, and workflows. I used AI guidance and implementation assistance in Cursor to develop the application around those decisions.

The web application uses Next.js, React, TypeScript, and Tailwind CSS, with Prisma and PostgreSQL for data. The code integrates Stripe for checkout, UploadThing for uploads, and Resend for confirmation emails. The separate analysis scripts use Python, pandas, and NumPy.

September 16–18, 2026 · file records

Starting with rental data

The earliest retained files are spreadsheet exports covering inventory, rentals, expenses, and maintenance. Python scripts consolidate inconsistent vehicle identifiers and names into a master inventory and a per-vehicle financial summary.

This work highlights a practical data challenge: operational records do not always identify the same vehicle consistently. The analysis remains a separate snapshot and is not connected to the website. No private operational records or financial totals are reproduced here.

September 19–October 1, 2026

Establishing the booking application

The earliest surviving web files, dated September 19, include a Trustivo-branded layout, availability-search component, and fictional seed data. File dates do not establish exactly when each feature became functional.

The first Git commit on October 1 contains the broader application: public vehicle pages, a reservation flow, checkout integration, uploads, confirmation emails, and an owner dashboard. These are documented code paths, rather than end-to-end behavior verified in this portfolio review.

October 1–2, 2026 · Git history

Preparing for deployment

Deployment work targeted Vercel. The recorded fixes addressed bundler compatibility, Prisma client generation, and UploadThing type declarations. This stage shows how integrating services also introduces build and hosting requirements.

Those historical commits do not establish a successful deployment date. A later public visit on October 19 confirmed that the homepage was reachable at trustivorentals.com.

October 6, 2026 · Git history

Defining rental-day rules

Billing changed from a simpler date span to a 24-hour rental day with a 60-minute grace period. A day after drop-off is reserved for cleaning without being billed. The vehicle-page copy explains these rules to renters.

The change made operational rules an explicit part of both the application logic and the interface. The review documents the implementation; it does not confirm pricing behavior through a completed live checkout.

October 7, 2026 · Git history

Separating owner workflows

Owner sign-in and session checks were added after the initial booking application. The dashboard code includes reservation views, a calendar, fleet editing, vehicle-photo management, and pickup-location management. Customer accounts and a distinct administrator workflow remain incomplete.

October 19, 2026 · uncommitted work

Adding license review

The latest reviewed working-tree changes make a license image required before checkout and add owner approval and rejection controls. This work was uncommitted when the Cursor report was prepared, and its database-schema update and deployed status were not verified. It remains work in progress.

The public interface

The live homepage displays pickup and drop-off date controls, a vehicle listing, and links for finding reservations and accessing the owner dashboard. This confirms that the public page is available, without establishing that checkout, email, uploads, or owner sign-in work end to end.

Full Trustivo public homepage showing the date-search form, a vehicle listing, and reservation and owner-dashboard links — Public homepage, October 19, 2026. Listing details reflect this capture, not a verified fleet inventory or usage result. No customer information or owner-only screens were accessed.

Where the project stands

Trustivo remains in progress. The code review identifies unfinished deposit-hold handling, vehicle maintenance workflows, customer sign-in, and license verification. It also notes differences in availability rules between screens and APIs that need validation.

The development history comes from the supplied Cursor review of Git history and file timestamps. No application tests were rerun for that report. The public homepage was separately viewed on October 19, 2026; payment processing, owner workflows, and production usage results have not been verified for this case study.