Steffen G.
Founder-Focused SaaS Architect | From First Idea to Paying Users
Most founders I work with are somewhere between a clear vision and a product that doesn't exist yet. Forty ideas, three that matter, and no obvious order to build them in. What usually happens first is that the idea gets smaller and sharper. Then it gets built. The part I enjoy most happens before the first line of code exists. Where the money comes from. What has to work for that to happen. What can wait until month six. πΌπ£π π©πππ£ π ππͺππ‘π ππ©. πππ’π π₯ππ§π¨π€π£, π¨π©ππ§π© π©π€ πππ£ππ¨π. I build and run my own SaaS products. I've shipped to the App Store, watched which features people actually opened, and cut things at midnight to get a release out a week earlier. That's the experience I bring into your project from day one. What you get out of working this way: - A working first version in front of real users within weeks - A short, agreed build list that everyone is confident about before anything starts - A data model that still holds when feature twelve arrives - Payment flows that stay correct when a webhook fires twice or a card fails mid-subscription - A clear picture of what version one is and what it costs - Someone who says early on when something can safely wait Where I create the most value: - Multi-tenant SaaS with clean role separation and strict data isolation - Stripe and Stripe Connect, subscriptions, webhooks, onboarding, payment state that holds under real traffic - Multi-role platforms where permissions and workflow logic carry the product - Operational software with compliance requirements, audit logging, and backend-heavy workflows - AI features routed through the backend, with cost control and rate limits handled from day one - Existing products ready to be restructured for their next stage of growth Selected work: Water Testing Laboratory Platform. Multi-tenant, five user roles, mobile field sampling, audit logging, strict separation between independent labs sharing one architecture. Compliance-driven and running in daily operations. Pro-Am Gauntlet. National tournament circuit. Registration across three divisions, Stripe with server-side webhook verification, thirty-minute reservation holds with automatic release, full admin operations. Live and serving real events. Far Out MedX. Credential tracking SaaS for certification-heavy careers. Alert engine with deduplication across four expiry thresholds, GPT-4o Vision document import, public shareable profiles. Delivered across six milestones. Gamified financial literacy simulator (NDA). Next.js and Supabase. Realtime state engine driving individual participant state from collective audience votes, LLM avatar integration, dual curriculum switching. In active development. Kolibi and Orivela. Two products I built and shipped myself. Expo and React Native on Supabase, client-side encryption, Claude Vision, Postgres with RLS throughout, App Store pipeline end to end. Stack: Next.js, TypeScript, Supabase (Postgres, Auth, RLS, Edge Functions, Realtime), Vercel, Stripe and Stripe Connect, Expo and React Native, Resend, Anthropic and OpenAI APIs. Bubble for workflow-heavy SaaS products. Send me what you're working on, even if it's still messy. The first conversation usually sharpens the picture either way. If it fits, we start with a milestone that produces something real and working, and scope the next one from there.