Gemini Pro
Analytics and research at massive scale.
I combine 23 years in IT and marketing with a network of AI agents — one person, a team's pace. Strategy, AI, web, and hardware. You pay for outcome and expertise — B2B billing down to the hour.
Analytics and research at massive scale.
Strategy, code, and linguistic nuance.
Oversight and cross-verification.
You pay for expertise and outcome. B2B billing down to the hour, minimum unit 60 minutes.
Ongoing team support and quick consultations.
In-depth work on documentation and systems audits.
Key business decisions with AI in the loop.
An ongoing partnership model for companies that need guaranteed availability. I act as an external CTO / strategic advisor, taking responsibility for technical continuity.
Deploying AI is an architecture that prevents errors. My proprietary approach cuts hallucinations by up to 80% through multi-stage, cross-model verification of the output. See the method in practice: the "One Question, 91 Minds" experiment (in Polish) — an open workflow, free to download.
Multi-stage verification and cross-model checking — up to −80% errors.
900M+ tokens monthly in production, API cost optimization.
Safety-First architecture, GDPR compliance.
"A hallucination isn't a bug in the model. It's a failure in the architecture that let it through."
14-day VAT invoice. Minimum unit: 60 min. Copyright transfers to the client.
Response within 24h on business days. Urgent mode (6h) +100%. Remote work, Polish as the working language (EN documentation).
Mutual NDA on request. Enterprise scale — projects generate 900M+ tokens/mo; API budget on the client's side.
I don't ask IF something will break, only WHAT happens then. Every layer of my ecosystem has a backup, an alert, and a recovery plan. Client projects get the same standard.
Every project lives in a private Git repository (GitHub). Full change history — any state can be restored, and I hand over client code together with its history.
Automated server snapshots (Hetzner) + daily copies to independent storage outside the main infrastructure + local copies. Three copies, two media types, one always offsite.
A standby server at a different provider, replicated live. A failure of the main one means data loss measured in seconds and a return online in minutes — not days.
External uptime monitoring plus internal health checks for services, certificates, and backups. I catch problems before a user reports them.
Every anomaly — from an expiring certificate to a failed backup — lands instantly as a push notification (Pushover). Even at night.
DNS, attack protection (WAF), and hiding origin servers behind an edge layer. Traffic passes through the filter before it touches the app.
The ones you're already asking yourself — so I'll answer them straight.
Documentation starts on day one, code and access credentials stay on your side, and the architecture has no vendor lock-in — any competent team can take over the project. In a retainer, an SLA with a defined response time is added on top.
Yours. Copyright transfers to the client (standard practice, see Billing), documentation in Polish, technical docs also in English.
No overhead: you don't pay for coordination, handoffs, and subcontractor margins. One person owns the decision and the outcome, and the network of AI agents gives you a team's pace. An agency makes sense when you need a long-term team for years — if that's you, I'll tell you straight.
We define the criteria before we start: process time, cost to serve, error rate. We measure in production, not in a demo. And if AI doesn't have a business case for you, you'll hear that before the first invoice.
Project status, expected hourly budget, and timeframe — I'll come back with a concrete proposal for the next step.
Contact form