Case Study · HELM
Plain-text passwords. No tests. A launch date that wasn't moving.
HELM had a live hospitality platform with real bookings — built on Replit and never designed for production. We rebuilt auth, payments, and three conflicting dashboards into one role-based platform in 12 weeks.
Status: In delivery, pre-public launch. Numbers describe the build, not live usage.
Last updated:
Problem
The challenge
HELM had a live hospitality platform with real bookings — built on Replit and never designed for production. Auth was broken, payments weren't integrated, and three separate dashboards showed conflicting data that no one trusted.
Outcome
What we built
We rebuilt auth with proper session management, integrated payments end-to-end, and consolidated three dashboards into a single role-based interface — providers, admins, and staff all working from the same live data. The entire data layer was re-architected for the provider scale HELM was pitching to investors.
- →Rebuilt auth with session management & recovery
- →End-to-end payment integration
- →3 dashboards → 1 unified role-based platform
- →Full data layer re-architected for scale
Tech stack
Full stack used on this build
Canonical stack: Next.js, NestJS, PostgreSQL, GCP Cloud Run. Timeline: 12 weeks (~90 days).
Screenshots
Product in context
“They proved that previous development failures don't have to be fatal — the right team can salvage the vision.”
— Ben Karpinski, Product Manager, HELM Inc.
Talk to an engineer
30 minutes. You'll leave with a rough scope and a real timeline — whether or not you work with us.
