Przemysław Zalewski

Rescue for AI-built apps

Built it with AI. Stuck before launch?

The app almost works. The agent keeps fixing one thing and breaking another, the deploy fails, or login only works on your laptop. I take it from there: a short call, access to the repo, and a few focused hours until it builds, deploys and does what it should.

See price and start date →

Przemysław Zalewski
  • “someone you can always count on”public LinkedIn recommendation
  • “a true bias for action”client CTO, on LinkedIn
  • 15+ yearsshipping software
  • Free call, no pitch deck30 minutes, then you decide

What is usually wrong

The build fails after an update

A dependency moved, the agent upgraded half of the project, and now nothing compiles.

The deploy ships the wrong thing

The hosting serves source files instead of the build, or the environment variables never made it to production.

Login only works locally

Redirect URLs, cookies or the auth provider settings still point at localhost.

The agent made it worse

Each prompt fixes one bug and adds two. The history is a pile of “fix fix fix” commits.

Data goes to the wrong place

Forms save nothing, or save twice, or the table the app reads is not the one it writes.

It has “almost worked” for a week

One feature is 90% done and the last 10% keeps sliding.

How it works

  1. 30-minute call

    You show me the app and what should happen. I tell you honestly if it is a few hours or a bigger job.

  2. Access to the repo

    GitHub (export from Lovable or Bolt first), the hosting and a test account. Nothing on your personal logins.

  3. 2 to 8 hours of work

    Fixed price for the hours you pick in the configurator.

  4. A pull request and a recording

    The fix with a plain description of what was wrong, a list of what is likely to break next, and a 10-minute video on how to keep it working.

What I do not do here

  • Rewrite the app from scratch.
  • Work inside your Lovable or Bolt account without a GitHub export.
  • Promise a date before the call.
  • Security reviews or audits. This is about getting the app unstuck.

Why me

I build with coding agents every day, under rules I wrote for them, and I have shipped 25+ apps since 2009. I know the ways agents get stuck because I spend my days getting them unstuck.

An AI coding agent as a team member, under enforced rules

The problem
Coding agents produce ten times the output and ten times the mess. A team of four wanted the speed without a slop swamp on main.
What I did
I authored the rule set shared by Claude Code and Codex: mechanical checks over written rules, lint and test gates for security, API surface and CSP, agents working on main with hooks, every PR reviewed by a human, AI-assisted content disclosed as such.
Result
In 2026 the agent opened about 30% of merged pull requests across two products and I reviewed about 85% of them. My own output went from under 1,000 to 5,000+ commits a year.

~30% PRs by agent ~85% reviewed 5,000+ commits/yr

Restarting delivery after three years of maintenance mode

The problem
A mature product had drifted into maintenance. The backlog was old and the team small.
What I did
Agent-assisted development under an enforced rule set, help docs migrated from WordPress into the repo as markdown with 301 redirects and i18n, help added to the Definition of Done.
Result
Commit volume up about 40× year over year in 2026, one less server to break during holidays, docs that match the product.

~40× commits YoY docs-as-code

Help center moved from WordPress into the repo as docs-as-code

The problem
An unmaintained WordPress help site: red in audits, no sitemap, expiring certificates, plugins nobody understood.
What I did
Markdown in the repo, versioned with the product, all languages generated automatically, interlinking, 301 redirects for every old address, help added to the Definition of Done.
Result
One machine less to break during holidays, docs that match the product, better SEO and GEO, context agents can read.

docs-as-code 301s i18n

See also: Cloudflare · Next.js

Want it unstuck this week?

Pick the hours in the configurator, then book a 30-minute call. You get a pull request, not a report.

See price and start date → Check if it is ready for the stores

FAQ

Questions

My Lovable app is not working. Can you fix it?
Usually yes. Export it to GitHub first, so I can work on the code directly. Most fixes take a few hours.
Claude Code broke my project. What now?
Do not keep prompting. Commit what you have, then book a call. With git history I can usually find where it went wrong and get back to a working state.
How much does it cost?
You pick 2 to 8 hours in the configurator and see the fixed price before you book. The rate is the same as for my other work.
Will you finish my app?
If what is left fits in a few hours, yes. If it is bigger, I will say so on the call and suggest a first slice instead.
Can you put it in the App Store and Google Play?
Yes, that is a separate offer. The free store-readiness check shows what is missing first.

Let’s find out in 30 minutes

A free 30-minute call. You bring the problem, I bring questions. No prices on this page because scope comes first.

If I am the wrong person I will say so on the call and point you to someone better.

or write to ciunkos@gmail.com

After you book: a calendar invite, then the call. Nothing else to fill in.

Available from November 2026 · B2B contract or employment · Wrocław, Poland (CET), remote