Configure the engagement. See the price before the call.

How working with me looks

1. A 30-minute call. You tell me the goal, the deadline and what already exists. I ask what would make it a success and what can wait. Free, and you leave with a recommendation either way.
2. A written scope within two days. What gets built, what does not, how we know it works, and the price: fixed per slice or hourly with a weekly cap. You can take it to anyone.
3. Weekly demos, code in your repo. Working software every week, in your accounts from the first commit. When something takes longer, we cut scope before we move the date.
4. A handover you can live with. Tests, CI, a short runbook and a recorded walkthrough. Anyone competent can pick it up after me, including your next hire.

Each kind of work up close

Review of one pull request

For a team that wants a second senior opinion before something risky merges, or a founder who wants to know what the code is really like. Not a full audit: one change, read properly.

One-week audit

For a CTO or founder before a raise, a rewrite, a new vendor, or adding AI features. You get a ranked list and a plan, not a 90-page PDF. I do not fix things during the audit week; that keeps the findings honest.

Ship one slice

For a team that needs one thing done end to end: a feature, an AI agent, an integration. Scope, build, measure, hand over. The best way to try working together before anything bigger.

MVP or product build

For a founder with a validated idea and a budget. Auth, billing, analytics and deploy from week one, a demo every week. Not a fit for an idea nobody has tested yet: validate it first.

Fractional tech or AI lead

For a company with developers but no senior technical voice. I join a few days a week, make the decisions written down and reviewable, and help you hire your permanent lead. I do not replace the team.

Maintenance and upgrades

For a product that works and should keep working: framework upgrades, dependency bumps, the legacy corner nobody dares to touch. Tests first, then changes.

A senior with AI agents or a classic agency?

I build with coding agents every day; they write most of the code and I design, decide and review every change. For the right project that makes one senior several times faster than before. The cost estimator lets you set that multiplier and shows what it depends on.

I am likely the better fit for a new product or a well-scoped slice, when one person can make decisions within a day, and when you want to see working software weekly without paying for coordination.

An agency is likely the better fit when you need many people in parallel from day one, 24/7 on-call, formal processes for a large organisation, or several disciplines at once (brand, content, native apps and backend together).

In regulated work (medical devices, finance, children’s data) validation, audits and sign-offs set the pace, not typing. AI still helps, but the speedup is smaller, and I will say so before we start. Low risk appetite is often the right call there.

When I am not the right choice

• You need a team of ten next week.
• You need someone on call nights and weekends.
• You want the cheapest hours, not the fewest.
• The idea has not met a single customer yet. Start with the free idea validator and ten conversations.

How I work

1. Confidential by default. NDA is standard. I never show your project, name or screenshots without written consent, which is why this site names no clients without permission.
2. Your code, your accounts. Code and data stay in your repository and accounts. AI tools run with training on your data turned off, and secrets never reach a model.
3. A handover you can use. Every project ends with the same checklist: a README that gets it running, one architecture diagram, written decisions, CI, a runbook and a recorded walkthrough. It is done when someone outside the project can run it from the docs.
4. Boring technology where it counts. I pick a stack you can hire for. Anything experimental needs your yes and an exit plan.
5. Approach matched to your risk appetite. Prototype, product or regulated: the level decides how much autonomy the agents get and how much review and validation each change needs.
6. Everything checkable. Every number on my pages links to its source. My tools are free, and the idea validator skill is open source (MIT).

Three risk levels, three ways of working

What a senior developer costs elsewhere

Median yearly pay of back-end and full-stack developers with 10+ years of experience, from the public Stack Overflow 2025 survey data (my calculation):

All seven countries, labor costs, freelance rates and hiring models →

How it is calculated

Hours are a range: weeks or days times hours per week, plus or minus 10 to 20 percent for the unknowns, depending on the kind of work. The audit and the PR review have a fixed size. Fractional months count 4.33 weeks. The price is hours times the rate; the full range uses my lowest and highest rate.

Questions

Is this a quote?

It is an honest starting point. After a 30-minute call I send a written scope with a fixed price or a capped number of hours. The final number usually lands inside the range shown here.

Fixed price or hourly?

Both work. Audits and reviews are fixed. Builds can be fixed per slice with a demo at the end, or hourly with a weekly cap. Fractional work is billed per day.

How do you invoice?

As a Polish business (B2B), monthly or per milestone, in PLN, EUR or USD. EU businesses get a reverse-charge invoice without VAT.

Why can you show prices when agencies do not?

Because it is just me and the rate does not depend on who is asking. Coding agents under rules make me faster; you pay for the hours a senior engineer spends, not for a team on the bench.

When can you start?

From 2 November 2026. The date on this page is updated when it changes.

Who owns the code?

You get all of it, written by hand or with agents: it lives in your repository and your accounts from the first commit, and the contract transfers to you whatever rights exist in it. To be honest about the law: under current guidance, parts generated by AI without enough human creative input may not be protected by copyright at all (US Copyright Office, 2025). So your protection rests on the contract, confidentiality and the fact that the code is yours to hold, not on copyright alone. I keep nothing that stops you from working with someone else.

Will you sign an NDA?

Yes. I also never name clients without their permission, which is why you will not find client names on this site.

Do you use AI on my code?

Yes, coding agents are how I work. They run on your accounts, or on my business accounts if you have none, always with training on your data turned off. Secrets never reach the model, and I review every change before it reaches you. I pick tools and models to match your appetite for risk: the privacy of your code and data matters more to me than speed. If your policy forbids AI tools, I follow it; the price then reflects my hours without agents.

Time zone and language?

Poland, Central European Time. English is my working language, Polish is native. I have worked across a nine-hour time difference with weekly calls and written status in between.

Can we stop early?

Yes. Work comes in slices, each finished and in your repo, so stopping after any slice leaves you with working software. The notice period goes into the contract.