Siarhei Rudak — Senior Product Engineer
Solving business pain with outcome-driven solutions — end-to-end ownership
Find out if your app is ready for real users and real money.
I read your codebase and write the answer down: fixed price from $2,500, delivered in five working days — seven if your product takes payments.
Not sure it fits? Start with a free 30-minute call.
01 — Is this you?
- You built it fast — AI tools, an agency, a junior team. Real users and real money are about to go through it, and nobody can tell you whether it holds.
- You paid someone, the demo works, and you can't tell whether you got a product or a shell. The next invoice is due, and you need a second opinion first.
- You're already live, and it breaks in ways you can't predict — logins, payments, data. You need to know what to fix first, not a list of everything that's wrong.
What I review: web products and the APIs behind them. Not native mobile apps, not games, not machine-learning models.
02 — The offer
The Launch Verdict
A written answer to one question: can this product take real users and real money today, or not yet.
- A written go/no-go verdict on whether your product can take real users and real money.
- Every finding ranked by severity, with the evidence: where it is, how to see it yourself, and what it costs if it stays.
- A fix plan with named work items and the price of the sprint.
- A scope spec, written so another contractor can pick it up and price it — you keep it, whoever ends up doing the work.
- A recorded walkthrough of the findings, in my voice.
All of it arrives as one written document you can forward to anyone, plus the recorded video walkthrough.
- One round of written questions, within 14 days of delivery.
- 100% of the price credited into a Fix Sprint started within 30 days.
Fixed price from $2,500, delivered in five working days — seven if your product takes payments. Which of the two published prices applies depends on that same question, and it is agreed on the free call, before you pay.
Paid up front. If the work never starts, the whole amount comes back.
And if what I find is smaller than a sprint, there is no sprint to sell you: you keep the fix plan and the scope spec, and your own developer or any contractor can do the work.
The second price, what is not included, and every rule of the deal are on the offer page.
03 — How it runs
- Day 1 — Access and a walkthrough: what the product does, what "live" means for you, where the money and the user path run.
- Days 2–3 — The review itself. Findings collected with the evidence for each one.
- Day 4 — Severity ranking, then the fix plan with named items and a price.
- Day 5 — The written verdict and the recorded walkthrough, delivered.
- After — one round of written questions, within 14 days of delivery.
A product that takes payments runs the same sequence with up to two more days in the middle.
04 — Who I am
I'm Siarhei. For 15+ years I've shipped production B2B software as a full-stack engineer — React, Next.js, TypeScript, Node. I build with AI coding tools every day, which is exactly why I know where they leave holes.
One person does this work, and it's me. The review is not delegated: I read the code myself, I write the verdict myself, and my name is on it. If the answer is "not yet," you'll get it in plain words with the reasons — that is what you're paying for.
You can check me before you write: I publish my work on YouTube as @imrudax, and my history is on LinkedIn.
05 — Start here
Start with a free 30-minute call.
Thirty minutes to check whether your case fits. It's not a sales call: if it doesn't fit, I'll say so and tell you what would fit instead. And if your message already makes that clear, I'll say it by email and save us both the call.
06 — FAQ
What exactly do I get?
You get a written verdict on whether your product can take real users and real money, and the evidence behind it. Five things arrive: the verdict itself, every finding ranked by severity with where it is and how to see it yourself, a fix plan with named work items and a price, a scope spec written so another contractor can pick it up and price it, and a recorded video walkthrough. It comes as one document you can forward to anyone, plus the recording. Two things come with it: one round of written questions within 14 days of delivery, and 100% of the price credited into a Fix Sprint started within 30 days.
What does it cost?
A Launch Verdict is a fixed price from $2,500, paid up front. Which of the two published prices applies depends on whether the product takes payments — that is agreed on the free call, before you pay. Both prices are published on the offer page, and they are the prices.
What is not included?
No code is written or changed during the verdict — fixing is the next step, not this one. It is also not a penetration test, not a security certification, and not legal, design or marketing advice. I review web products and the APIs behind them, not native mobile apps or games. The full list of exclusions is on the offer page, in plain words.
What happens if the verdict says don't ship?
You get that answer in writing, with the reasons and what it would take to change it. That is a result, not a failed engagement — finding out before your users do is the entire point. You keep the fix plan and the scope spec either way, and what you do with them is your decision.
Who owns what you deliver?
You do. The verdict, the fix plan and the scope spec are yours to keep and to hand to anyone — including a contractor who isn't me.
What is the free call?
Thirty minutes to check whether your case fits what I do. It is not a sales call: if it doesn't fit, I say so and tell you what would fit instead. It is also where we agree which of the two prices applies, before any money moves. Nothing to prepare, nothing charged.
How is the Fix Sprint priced?
The exact price is named inside your verdict, from what the review actually found. I don't sell a sprint without a paid verdict first — pricing repair work before reading the code is guessing. The published range is on the offer page. And if what I find is smaller than a sprint, there is no sprint: you keep the fix plan and the scope spec, and your own developer or any contractor can do the work.
What access do you need?
Read-only access to the repository, plus a staging environment if you have one. I change nothing in your infrastructure and nothing in your accounts, and anything I exercise actively runs on staging or on a copy — never on your production data. The days start on the agreed start date, once that access is in place, so the clock never runs while you're waiting on your own team.
Will you sign an NDA?
Yes — a standard mutual NDA, signed before I get access to the repository. Send yours, or I'll send a short one. Either way it is in place before anything is shared.
What happens to my code?
It stays yours. I take read-only access, keep a working copy only while the review runs, and delete it when the verdict is delivered. AI coding tools are part of how I work, and every tool that would touch your code is named on the free call, before anything is sent anywhere — you decide with that in front of you.
What if my product is too early for this?
Then I'll tell you on the free call, and you won't buy a verdict you don't need. If nothing is running yet, there is nothing to review. The free MVP Brief Builder turns the idea into a structured project brief you can bring here or take anywhere.