Tomasz Fiedoruk Tomasz Fiedoruk · B2B Offer/ availability: a limited number of projects

New-era advisory.
Me + a network of AI agents.

I combine 23 years in IT and marketing with a network of AI agents, so you get one person working at the pace of a team. Brand, communication, strategy, AI, web, hardware. You pay for expertise and results, by the hour, on a B2B invoice.

Job schedule SCHEMAT
start end CALL 30 min, not billed SCOPE ranges in writing WORK billed by the hour HANDOVER documents and access are yours
rate 200–450invoice B2Bmin. item 1 hQuality Loop

Orchestrator

AI-01RESEARCH

Independent research

Analytics and research at massive scale, in parallel and from many sources.

AI-02SYNTHESIS

Synthesis & architecture

Strategy, solution architecture, code and linguistic nuance.

AI-03VERIFICATION

Red-team & verification

Independent oversight and cross-verification of outputs.

Engine: swappable frontier models (currently Claude Opus/Fable, OpenAI GPT Sol, Kimi K), chosen per task.

A1
900M+
tokens / day in production
A2
80%
hallucination reduction
A3
23 yrs
professionally — since 2003
A4
8
production systems
01 / Pricing

A transparent billing model

B2B invoice, billed in whole hours, with one hour as the smallest line item.

TIER-01 · OPERATIONAL

Operational Support

Ongoing team support and quick consultations.

200 PLN / h
≈ €50 / h
  • Ad-hoc questions
  • Quick material review
  • Process consultations
  • Team support
Book a 30-min call
TIER-02 · DEVELOPMENT

Analysis & Development

In-depth work on documentation and systems audits.

300 PLN / h
≈ €70 / h
  • Analyses and roadmaps
  • AI systems audits
  • Technical solution reviews
  • Workshop preparation
Book a 30-min call
02 / Configurator

Build your scope

Tick what you actually need. You'll see the hours and the cost before anyone sends you a quote.

Start from a ready set
Or assemble your own
Strategy & Decisions450 PLN / h
Analysis & Development300 PLN / h
Operational Support200 PLN / h
Your scope

Tick at least one item and I'll do the maths.

Indicative ranges, meant for a conversation. They're not a commercial offer or a fixed price list. A call usually narrows them, and sometimes it turns out half the items are unnecessary.

03 / Partner track

Retainer: Strategic Partner

An ongoing partnership for companies that want one accountable person on the other side. I cover both layers, the brand and the technology. I shape what you say to the market, and I stand behind the system that has to deliver on it. Nothing gets bounced back and forth between two vendors.

Custom · reserved hours every month
Ask about the partner offer
  • + Brand oversight — message reviews and first response in a crisis.
  • + Reserved time — 40 h a month held for you.
  • + Priority delivery — your work goes ahead of project queues.
  • + Response SLA — a fixed window for critical issues.
04 / Method

AI Quality Loop™

Deploying AI well is an architecture problem, and good architecture stops errors before they get out. My own 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.

M-01QUALITY

Hallucination reduction

Multi-stage verification and cross-model checking, up to −80% errors.

M-02SCALE

Enterprise Scale

900M+ tokens daily in production, API cost optimization.

M-03SECURITY

Data security

Safety-First architecture, GDPR compliance.

NOTE-02 · Principle

"A hallucination isn't a bug in the model. It's a failure in the architecture that let it through."

05 / Collaboration standards
B2B-01BILLING

Billing

14-day VAT invoice. Minimum unit: 60 min. Copyright transfers to the client.

B2B-02SLA

SLA

Response within 24h on business days. Urgent mode (6h) +100%. Remote work, Polish as the working language (EN documentation).

B2B-03CONFIDENTIALITY

Confidentiality

Mutual NDA on request. Enterprise scale: projects generate 900M+ tokens/day, with the API budget on the client's side.

06 / Continuity and security

I assume failure — and design so it doesn't hurt

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.

SEC-01CODE

Versioning everything

Every project lives in a private Git repository (GitHub). Full change history, so any state can be restored, and the history goes to the client along with the code.

SEC-02BACKUPS

Backup 3-2-1

Automated server snapshots (Hetzner) + daily copies to independent storage outside the main infrastructure + local copies. Three copies, two media types, one always offsite.

SEC-03DISASTER RECOVERY

Failover mirror

A standby server at a different provider, replicated live. If the main one fails, you lose seconds of data and you are back online in a few minutes.

SEC-04MONITORING

24/7 monitoring

External uptime monitoring plus internal health checks for services, certificates, and backups. I catch problems before a user reports them. Monitoring and alerts run automatically 24/7; human response follows the agreed hours and SLA.

SEC-05ALERTS

Push to phone

Every anomaly — from an expiring certificate to a failed backup — lands instantly as a push notification (Pushover). Even at night.

SEC-06EDGE

Cloudflare shield

When a project needs it, I put it behind a Cloudflare proxy: DNS, attack protection (WAF), and origin hiding. Traffic is filtered at the edge before it touches the app.

07 / Honest questions

Questions worth asking me

The ones you're already asking yourself, so here are the answers.

Documentation starts on day one, source files and access credentials stay with you, and the architecture has no vendor lock-in, so any competent team can take over the project. A retainer adds an SLA with a defined response time.

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, or 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 there's no business case for AI at your company, you'll hear that before the first invoice.

08 / Contact

Have a project? Describe it in three sentences.

Tell me the project status, the expected hourly budget and the timeframe. I'll come back with a concrete proposal for the next step.

Contact form