services · 02
Web systems & SaaS that grow with the company.
Apps for one specific problem: auth, payments, admin, AI, integrations. The stack — React, Supabase, Stripe, Edge — picked for scaling, not for a CV.
What you get
Specifics, not promises.
Every project is a measurable business outcome. No "social media just because" or "sites that just look fine."
/01
Five-year architecture
I design the schema so it holds both the first and the hundred-thousandth user. Edge Functions instead of a monolith, RLS in Supabase, versioned migrations from day one.
/02
Stripe wired in from day one
Subscriptions, trials, coupons, VAT invoices, dunning for failed cards. Idempotent webhooks so nothing fires twice. No 'we'll integrate payments in phase two'.
/03
Admin panel as standard
Every SaaS gets an operator dashboard: users, MRR, churn, logs, errors. You don't have to commission a separate front later just to see what's happening in the product.
/04
AI ready to plug in
Architecture prepared for LLM logic: streaming, rate limiting, retries, queues. Claude or GPT can plug in without rebuilding the backend.
Process
From brief to launch.
- 01
Discovery sprint
A week of workshops: user stories, schema, feature map. Outcome: a 20-30 page architecture doc , something another developer could pick up and understand in an hour.
wk 1 - 02
MVP in four weeks
Auth, main flow, payments, admin panel. Vercel preview daily, live demo weekly. Decisions made together, not after the fact.
wk 2-5 - 03
Beta and market signals
First users, errors in PostHog, bottlenecks in Sentry. Iteration in two-week sprints , exactly where it hurts, not where it's comfortable.
wk 6-8 - 04
Going to market
Full tracking, documentation, incident runbook, knowledge transfer to your team. Or I stay on retainer — your call, not a contract requirement.
wk 9-12
Pricing
Clear ranges, no "it depends".
Final quote always after a 60-minute brief. Regardless of plan, I invoice in stages, never 100% upfront.
01
MVP
15-30k PLN
4-6 wks
- Auth + core flow
- Stripe basics
- Admin panel
- PostHog + Sentry
- Vercel deploy
02
Production
30-60k PLN
6-10 wks
- Everything in MVP
- Subscription + trial
- Public API
- LLM integration
- Edge Functions
- API documentation
- 60 days of care
03
Scale
60-150k PLN
10-16 wks
- Everything in Production
- Multi-tenant
- SOC2-ready audit
- Custom integrations
- Performance budgets
- On-call SLA optional
Related work
Here's what it looks like with clients.
FAQ
The questions I get most.
Do I own the code?
Always. Repo on your GitHub or GitLab from day one. Standard contract: full rights, all source code, all derivative work. Yours.
What about maintenance after launch?
You have three options. One: take it in-house , I hand over docs plus four hours of team onboarding. Two: retainer of 4-12 hours/month for bug fixes and small features. Three: bigger work I quote per project, not packed into a monthly fee.
Why Supabase, not a custom backend?
Because in 90% of SaaS MVPs Supabase saves 4-6 weeks of building auth, RLS, realtime and file handling from scratch. If requirements are unusual — we build a custom backend (Node, Go, Rails). It's an analysis call, not ideology.
Can I start with a smaller MVP and grow?
Yes, and that's the model I usually recommend. The first 4-6 weeks are an MVP for validation. Then you decide: push to Production, keep it in maintenance, or close it. No multi-year contracts.
How does invoicing work?
In stages: 30% upfront, 30% after the second sprint, 30% after beta, 10% after production launch. No 100% upfront. VAT invoice, B2B Poland or EU (reverse charge).
Can AI be part of the system from day one?
Yes — and often it should be. I have ready patterns for Claude/GPT streaming, RAG, function calling, agent loops. Usually adds 1-3 weeks of work, not more.
Next step
60 min brief. Free.
Hear the 5 questions I ask on the first call , a lot becomes obvious right there, before any project starts.