Services
I don't sell hours. I ship systems that run.
Every engagement starts with Discovery: I take the problem apart, draw the architecture and price the running costs. Code comes after.
Four lines of work
01
Operational agents
An agent that knows your data and processes, does the work inside your systems and changes nothing without approval.
- Agent tools built on your services and rules, not shortcuts into the database
- Every write as a proposal with the amount and wording, approved with one click
- An MCP connector for Claude, voice, a cost budget, an action history
- Evals: a test set of conversations and the known cost of each task
The agent in your panel and/or in ClaudeAn eval and a cost reportDocumentation of tools and permissions
02
Edge and offline systems
Systems that must work where there is no internet: hardware, radio, a local server, with the cloud as a bonus.
- An edge server with a local network, HTTPS and a PWA that works offline
- Telemetry and location over LoRa / Meshtastic, geofencing, alarms
- Sync with the cloud when there is a link, without opening ports
- Device integration: label printers, scanners, sensors
A working hardware + software kitA range and capacity testAn install and recovery runbook
03
Vertical platforms
One system instead of five subscriptions: booking, payments, sales channels, invoices and e-signature, joined together.
- Booking, packages, vouchers, customer and company accounts
- Stripe, OTA (Bókun/Viator), Fakturownia, e-signature, calendars
- Sites prerendered for SEO, multilingual from day one
- Automation where there is no API, with a human on failure
A production system with a panelData migration from the old toolsTests and CI/CD
04
Architecture audit and oversight
A map of what really runs in production, what is exposed and what breaks first, followed by agents that keep watch.
- Architecture diagrams, trust boundaries, open ports, data flows
- A prioritised risk list with a fix plan
- Secrets, backups, a recovery procedure
- Oversight agents: a daily report, escalation, fixes as PRs
A report with diagramsA remediation planOptional: oversight deployed
How I work
Discovery → build → care
011–2 weeks, fixed price
Discovery
I take apart the process and current systems, draw the target architecture, price the running costs and split the work into stages that each ship something that works.
02staged, something in production every 1–3 weeks
Build
Code with tests, CI/CD and documented decisions. You see progress live, not at the end.
03monthly
Care
Updates, monitoring, backups, oversight agents and time for new work. No retainer for nothing: we set the scope every quarter.
No vibe coding
AI speeds up the typing, but I own the architecture, the tests and the decisions. Every decision is written down with its reason.
Your code, your accounts
The repository, cloud, keys and domains are yours from day one. No lock-in to me.
Zero open ports
Services behind a tunnel, secrets out of Git, admin access over VPN. Security is the default, not an add-on.
A human approves
The agent proposes, a human approves. Automation has gates wherever money or customers are involved.
Questions
How much does it cost?+
Discovery has a fixed price agreed after the intro call. The build is priced per stage, and every stage ends with something that works, so you always know what you're paying for. Care is a fixed monthly fee for an agreed scope.
Won't an AI agent do damage?+
The agent reads freely, but every change is a proposal with an exact description that a person approves. The server performs the write with the same rules as the manual panel. Nothing is deleted, and every action and its cost stays in the history.
Who owns the code and data?+
You do. The repository, cloud accounts, API keys and domains are in your name from the start. Decisions are documented in the repo, so another team can take over.
Do you work with companies outside Poland?+
Yes: systems run in London and in Greece. Calls in Polish or English.
Got a process that should run itself?
30 minutes, free. I'll tell you if it makes sense, how I'd build it and what it would cost to run.