TheTripMan (Client • Booking + Payments Platform)
Booking + payments platform I built solo for an influencer-led transportation business (~1.2M audience). Live in production, taking real bookings on a revenue-share deal. Production code is private.
Confidentiality note
The production repository is private due to business confidentiality. Screenshots avoid any sensitive client data.
At a glance
Role
Solo
Type
Client work
Status
Live in production
Year
2025 – present
Stack
9 technologies
Links
Live · Case study
Media
Achievements
3 of 4 unlocked
Goes Live
Deployed for a paying client. The site is real and people are booking on it.
Content Pipeline
Wired the CMS so the client can edit copy without calling me at 11 PM.
Two-Nines Club
Site has been up reliably since launch.
Hidden achievement
Keep playing this project to find out.
Overview
Problem
A real business with a large social audience needed customers to browse services, book, and pay online — with no developer in the loop day-to-day — plus an admin to manage every booking.
My role
Solo full-stack developer: design, frontend, backend, Stripe payments, database, deployment, and ongoing maintenance. I own the whole thing.
Stack
Next.js 15 • TypeScript • Tailwind + shadcn/ui • Stripe (payments) • Postgres (Neon) + Prisma • Scheduling: Cal.com/Calendly + FullCalendar + Google Calendar • Resend email • GA4 analytics • Vercel
Highlights
- Designed, built, and deployed the entire booking + payments platform solo for a client with a ~1.2M-follower audience.
- Integrated Stripe for end-to-end payments, an authenticated admin dashboard, and automated email + calendar confirmations.
- Shipped to production with CI, accessibility tests, and analytics — the platform processes live customer bookings on a revenue-share agreement.
Case study
TheTripMan (Client)
Live site: https://www.trvoo.com (also reachable at thetripman.com)
Summary
A booking + payments platform I built solo for an influencer-led transportation business with a ~1.2M-follower audience. It's live in production and takes real customer bookings. I work on it on a revenue-share basis — I'm paid a commission on every booking the platform processes, so its success is directly tied to mine.
What I shipped
- A full booking flow: browse services → pick a time → enter details → pay → get a confirmation.
- Stripe payments wired end-to-end, with the booking only confirmed once payment succeeds.
- An authenticated admin dashboard so the client can see and manage every booking without touching code.
- Automated email confirmations (Resend) with calendar invites (.ics / Google Calendar) for both sides.
- Two scheduling modes (embed + custom calendar) so the booking experience matches how the business actually runs.
Tech snapshot
- Next.js 15 (App Router) + TypeScript
- Tailwind + shadcn/ui
- Stripe (payments)
- Postgres (Neon) + Prisma
- Scheduling: Cal.com/Calendly + FullCalendar + Google Calendar
- Resend email • GA4 analytics • Vercel
- Quality: Jest + jest-axe accessibility tests, Husky CI hooks
Why it matters
This is the project I'm proudest of. It's not coursework — it's a real product, with a real client, taking real money, that I own from the database to the deploy button. When I talk through architecture in an interview (how payments stay consistent with bookings, how the admin auth works, how I keep the client unblocked), this is the system I reach for.
Notes
The production repository is private out of respect for the client's business. Screenshots are chosen to avoid any sensitive data.