Full-Stack Development · 3 Years
Revedor SaaS Products
Three years shipping production SaaS — from frontend intern to the developer trusted with billing, backends and releases.
The problem
Early-stage SaaS products change direction fast. Revedor needed features shipped weekly across multiple client products without the codebase turning into a liability — and without a big team to absorb mistakes.
As the products grew, so did the stakes: real customers, real payments, real downtime costs. The gap between 'works on my machine' and 'production-grade' had to close.
My approach
Component systems over one-off screens
Pushed the frontends toward reusable Tailwind component libraries early, so new features assembled from tested parts instead of being rebuilt each sprint.
Own features end to end
Moved from frontend tickets to full vertical slices — schema, API, UI — which cut handoff losses and made me accountable for the whole outcome.
Boring, reliable payments
Integrated Stripe with a deliberately simple billing model: webhooks handled idempotently, subscription state stored locally, edge cases documented.
The solution
Shipped production features across multiple SaaS products for three years — dashboards, role-based access, billing flows, content pipelines — while the team stayed small.
Left behind documented components and APIs that new developers could pick up without archaeology.
The outcome
3 yrs
Production SaaS shipped
22+
Skills picked up on the job
2
Roles grown through
Next project
Freelance UX & Web →