Role
Full-stack product engineer
Case Study
Back to work
Saas Product
Freelance OS
A realtime operations dashboard for solo service businesses that combines lead tracking, tasks, bookings, billing boundaries, and plan-aware limits.
Next.jsConvexClerkStripeTailwind CSSTypeScript
Case study framing
This page is structured as a product and delivery narrative: what the system needed to do, what constraints shaped it, and how the implementation held up.
Role
Full-stack product engineer
Published
Jun 2026
Audience
Freelancers and solo operators
Outcome
Mapped a solo service business workflow into one product instead of scattered tools.
Reading mode
Read this case study through solution, architecture, process, outcomes, walkthrough.
Context
What the product needed to do
A realtime operations dashboard for solo service businesses that combines lead tracking, tasks, bookings, billing boundaries, and plan-aware limits.
Mapped a solo service business workflow into one product instead of scattered tools.
Project dossier
A compact read on scope, role, and who the system was designed for.
Work type
Saas Product
Role
Full-stack product engineer
Audience
Freelancers and solo operators
Published
Jun 2026
Outcome snapshot
Workflow scope
Leads to bookings
State model
Realtime operations
Business guardrails
Billing-aware limits
Problem
Solo operators often manage leads, bookings, tasks, and client notes across disconnected systems.
Solution
The product unifies intake, scheduling, client records, notes, and dashboard visibility into a single workflow-driven surface.
It also models plan boundaries explicitly so the business logic of a paid product is visible in the experience rather than bolted on afterward.
Architecture
Convex handled reactive state updates while auth and billing boundaries were modeled explicitly through Clerk and Stripe.
That architecture keeps the product responsive for operators while preserving clean ownership around identity, plan enforcement, and operational state.
Process
The main design decision was treating the app as an operating system for service work, not a set of independent features or disconnected admin pages.
That framing made it easier to prioritize sequence, state transitions, and dashboard clarity over a shallow checklist of features.
Outcomes
Realtime lead tracking and task visibility across the operating workflow
Timezone-aware scheduling that reflects how solo operators actually book work
Subscription-aware limits modeled as part of the product rather than an afterthought
A tighter product narrative around one workspace for service-business operations
Product walkthrough
Walkthrough
Inquiry Pipeline
Walkthrough
Dashboard Page
Related Work
See related case studies
Additional work with adjacent product, workflow, or technical characteristics.
Mentorly
A mentorship booking marketplace with profile discovery, session requests, notifications, and role-aware booking state.
Designed the core mentor-to-learner request and booking lifecycle as a product system.
Veloce Auto Spa
A premium mobile auto detailing booking platform pairing a polished marketing funnel with booking, payment, and operational admin tooling.
Designed a service platform where conversion, scheduling, payments, and operations reinforce each other
MedHub
A healthcare operations platform rebuilt around bookings, departments, services, and audit-safe workflow rules instead of generic admin CRUD.
Re-architected a generic stack into a clinic system with role-based access, safer bookings, and admin visibility.