Lightswitch lets non-technical founders add subscriptions, paywalls and auth to AI-built apps without ever touching Stripe or Supabase. Over a six-week fractional sprint I designed the onboarding wizard, a design system, and the auth and checkout components the team built its soft launch on.
Lightswitch's pitch is that a non-technical founder can add payments, subscriptions and auth to an app built with tools like Lovable, Cursor or Replit, without ever touching Stripe or Supabase. All of that complexity had to disappear behind one product surface, the onboarding wizard, and it hadn't been designed yet.
Monica, the CEO, had spent a decade in consumer subscriptions but was stuck building a design system from scratch with no onboarding UX. She brought me in as a fractional designer to design the core setup flow, stand up a design system that could act as a forcing function for product decisions, and hand her technical co-founder auth and payment components ready to build from.
I designed the onboarding as a guided wizard: connect Supabase over OAuth instead of pasting keys, set the app basics, build a pricing plan on an interactive table that previews the customer-facing result in real time, connect Stripe through an embedded component that pulls the keys automatically, and configure Google Auth. One deliberate call: put pricing setup before the Stripe Connect step, so founders hit the rewarding part first and push through the tedious middle instead of dropping off.
Around it, a three-column dashboard, a collapsible dark sidebar, a content column, and a preview column showing the end app update at every step, and a standardized set of auth and checkout components: sign-in, sign-up, password reset, one- and two-plan pricing pages, and an embedded Stripe checkout. Customization was kept to a primary color and a logo, modeled on Shopify's checkout: trustworthy and consistent, not endlessly brandable. Opinionated defaults over configuration, plain language over developer-speak, and a preview at every step so nothing shipped blind.



The job wasn't to make it pretty. It was to settle a hundred product decisions by drawing them, so the team could stop debating and start building.
In six weeks the onboarding wizard, design system and component set went from nothing to prototypes the technical co-founder was shipping production code from, delivered in Replit and Figma, usually within a day of each sync. By the final sprint sync the monetization flow was nearly complete and the team was scoping a soft launch the following week, onboarding the first users by hand.
The engagement was scoped to continue past launch, with the next sprints already mapped: transactional emails, upgraded end-user pages, and eventually a visual workflow builder for freemium and premium journeys.