what you get
- SaaS MVPs with auth, billing and an admin panel
- Dashboards and internal tools
- Calculators, document builders, checklists and flowcharts
- Integrations: APIs, Google Workspace, Telegram, payments
- Tests, monitoring and a runbook at handover
- A first working version in 2–3 weeks, then weekly iterations
work like this
- A document builder: data entered once, live A4 preview, PDF and DOCX export (NDA)
- Labor-law calculators, checklists and a typical-procedures guide for an HR platform (NDA)
- AI Campaign Orchestrator, a campaign mini-SaaS with review gates
- Nur, a local AI desktop app for Windows with a one-click installer
how it goes
- discover: One call, then a short written brief: who uses it, what done looks like, what can break.
- spec: A protocol before code: data, rules, acceptance criteria and test cases agreed up front.
- build: I direct AI coding agents and review every diff. Fast iterations, small PRs, nothing unreviewed.
- verify: Tests, evals and a reference to compare against. Results are reproducible.
- ship: Deploy on Vercel or Railway, add monitoring, hand over docs and a runbook.
questions
How do we agree on scope?
After a 20-minute call and a short written brief you get a fixed scope and a date, so the plan does not grow on its own.
How long does it take?
A bot or a site usually takes 1–2 weeks, an AI feature 2–4 weeks, a web app or MVP 4–8 weeks. You see a working version early and then every week.
Who owns the code?
You do. At handover you get the repository, documentation, a runbook and tests, deployed to your accounts.
Will you sign an NDA?
Yes. Most of my paid work is under NDA, which is why client names on this site are hidden.