Kristian L.

⚙️ I automate your SaaS until the only notification left is Stripe saying you got paid. PROOF my most recent build. Tournament software for padel and tennis clubs: Next.js and Supabase, Stripe Connect for entry fees with split payments, refunds and club payouts, Postgres row level security, and over 1,800 automated tests. Schema, app, payments and tests, all mine. WHAT I DO Schema first, product second. Normalized designs, foreign keys, constraints and row level security, then Next.js and TypeScript on top of an optimized Supabase backend. Sized for the query plan, not for the demo. Payments. Stripe and Stripe Connect: checkout, subscriptions, split payments, refunds, payouts, webhooks, idempotency. On the money path a bug is not a bug, it is a refund email. Testing. Playwright for journeys, Vitest for units, running in CI. If you have a product and no tests, this is the fastest way to stop the bleeding. Data engineering. ETL pipelines, Python batch imports of large CSV and JSON with real error handling, dimensional models and reporting tables, zero downtime migrations with rollback, and query plan tuning when something gets slow. Plus cron jobs, so it keeps running while you sleep. Years of freelance backend and data migration work, including CMC Analytics. The SQL came first. The apps came later and are better for it. Send me your schema, your Stripe dashboard, or your untested repo. I will tell you how I would build it, and what I would not build.