24hr
idea to live product
SaaS Onboarding Platform Built and Shipped in 24 Hours
Series A HR-Tech Startup (Confidential)
24hr
Idea to live product
36hr
Until board demo
3
Additional features in 2 weeks
Context
The business context
A Series A HR-tech startup was three weeks away from having a working product - and 36 hours away from a board demo that could either extend their runway or end it. Their founding team had strong domain expertise and a clear product vision in Figma. What they didn't have was a deployable version. Their existing development team was building methodically and correctly, but 'correctly' meant three more weeks of infrastructure setup, auth flows, and role management before a demo-worthy state. They needed a completely different approach for the next 36 hours.
The problem
5 specific problems that needed solving
Board demo in 36 hours with no live product - only static Figma prototypes that couldn't demonstrate real user flows
In-house dev team three weeks from a deployable version - no feasible path to accelerate within the existing sprint
Series A runway decision riding on the demo outcome - a failed or unconvincing demo meant renegotiating terms under pressure
Product needed real authentication, working user flows, and an admin dashboard - not a clickable prototype - to be credible to board members
No tolerance for a slow, exploratory build: every hour mattered and the scope had to be fixed before a line of code was written
Our approach
Ruthless scope, maximum speed.
We started with a 90-minute scoping call - not to explore features, but to eliminate everything that wasn't essential for the demo to land. By the end of that call, we had a fixed scope: user registration and login, a three-step onboarding flow matching the Figma designs, a role-based dashboard with seeded demo data, and a working admin panel. Nothing else. We've learned that 24-hour builds succeed or fail based on scope discipline. Adding a feature at hour 16 that wasn't scoped at hour 0 kills the entire project. We held the line.
Fixed scope agreed in the first 90 minutes - nothing added after scoping, no exceptions
AI-assisted scaffolding with pre-built auth and dashboard templates cut setup time from 6 hours to under 90 minutes
Continuous deployment from hour 2 - every commit went live immediately so the client could review progress in real time
Seeded demo data designed specifically for the board demo narrative - not placeholder text, but realistic HR workflow data matching the startup's use case
What we built
A fully functional onboarding platform in one working day
A Next.js application with Supabase for authentication and database, deployed on Vercel with a custom domain by hour 20. The product included a complete user registration and email verification flow, a three-step onboarding sequence capturing employee profiles and role assignments, a role-based dashboard (employee view and manager view) with real data interactions, and an admin panel for user management and role configuration. All Figma designs were implemented faithfully - the demo used the same visual language the founders had already socialised with the board.
Authentication system
Supabase Auth with email/password registration, email verification, and session management. Role-based access (employee, manager, admin) enforced at the database level with Row Level Security - not just in the UI.
Onboarding flow
Three-step onboarding sequence (profile setup → department assignment → role configuration) matching the Figma designs exactly, with progress persistence so partially completed onboarding resumes correctly on next login.
Role-based dashboards
Separate dashboard views for employees (personal profile, team overview, tasks) and managers (team management, onboarding progress tracking, approval workflows). Seeded with realistic demo data tailored to the startup's target HR use case.
Admin panel
Full CRUD interface for user management, role assignments, department configuration, and onboarding template management. Designed for the founder to demo live edits during the board presentation.
Production deployment
Custom domain configured, SSL provisioned, environment variables secured. Deployed to Vercel's edge network with a global CDN - no loading delays during a demo. Database migrations version-controlled from day one so the in-house dev team could take ownership cleanly.
Impact
What changed in production
The demo ran flawlessly. The board saw a working product, not a prototype - and extended the Series A on the terms the founders needed.
Demo went live on schedule. Board extended the Series A runway. The startup shipped three additional features using the Thinkscoop codebase in the following two weeks. The product is still running on the original architecture.
24hr
Idea to live product
36hr
Until board demo
3
Additional features in 2 weeks
Learnings
What we took away from this project
Scope agreement is the most valuable hour of a 24-hour build
Every minute spent eliminating scope ambiguity before the build starts saves 3 minutes of rework during it. The 90-minute scoping call felt like overhead when we were racing against a 36-hour deadline. It was the reason we finished. Any feature request that came in after that call - however reasonable - was parked for the post-demo backlog.
Demo data is a product decision
We spent 90 minutes specifically designing the seeded demo data to tell the narrative the founders wanted the board to see. Employee names, department structures, onboarding progress percentages - all crafted to illustrate the product's value in the most compelling way for a board audience evaluating a Series A investment. Generic 'Lorem Ipsum' data would have undermined the demo's credibility. The data was as important as the feature set.
Clean handoff is as important as the build itself
A 24-hour build that the client's in-house team can't maintain or extend is a short-term win with long-term cost. We documented every architectural decision, kept the schema simple and well-commented, and ran a 30-minute handoff call with the in-house dev team at hour 22 - before the demo, not after. They shipped three new features on the codebase within two weeks. That's the measure of a clean handoff.
24hr
idea to live product
At a glance
Tech stack
Capabilities
Build something similar?
We've solved this category of problem before. Let's scope yours.
Start a conversation View related serviceMore work
