Siarhei Rudak: Product Engineer
I check, fix and build web products that have to hold real users and real money.
A written answer on what holds and what breaks. Fixed price, named before the work starts.
15 years of production B2B software. One person does the work. Reply within one business day.
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.
- You have a validated idea and a budget, and you'd rather have it built right once than rebuilt after the first paying customers.
What I take on: web products and the APIs behind them. Not native mobile apps, not games, not machine-learning models.
02: What I do
Check
I review the code with AI agents built for this, check the critical paths myself, run the product, and write down whether it can take real users and real money. Every finding comes with the evidence, ranked by what matters first. The plan is yours, whoever does the work.
Fix
The findings, fixed by the same person who found them. Done means the written scenarios we agreed pass, not that the calendar ran out.
Build
A product from idea to release, built to hold users and money from day one, not a demo that needs a second build.
Fixing starts with the check. I don't quote a fix on code that hasn't been reviewed.
Every step is a fixed price, named in writing before the work starts. What each step costs and covers is on the services page.
03: Who I am
I'm Siarhei. For 15 years I've built production B2B web products end to end: front end and back end, from the interface to the API and the data behind it. 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. None of it is handed off. I review the code with AI agents built for this, and check the critical paths myself. I write the verdict myself, and when there is fixing or building to do, I do that myself too. My name is on it. If the answer is "not yet," you'll get it in plain words with the reasons.
You can check me before you write: I publish my work on YouTube as @imrudax, and my history is on LinkedIn.
04: Start here
Start with a message.
Describe what you built and where it stands. You'll hear back from me within one business day, and nothing is paid until the first step and its price are agreed in writing. If your case isn't one I take on, I'll say so and tell you what would fit instead.
05: FAQ
Which of the three do I need?
You don't have to know. Describe where the product stands, and I name the step in my reply. If it is running, or about to be, it starts with a check; fixing comes after a check, never before it. If there is no product yet, the path is idea, then brief, then build: the free MVP Brief Builder turns the idea into a project brief, and that brief is the first step towards the spec a build is priced from.
What happens after I write?
You get a reply from me within one business day. If I need to know more, I ask by email. Then you get the first step and its price, in writing. Nothing is paid until you have both.
What don't you take on?
Native mobile apps, games and machine-learning models. I work on web products and the APIs behind them. The full list of what is not included is on the services page.
What if the answer is "don't ship"?
Then 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. The plan stays with you either way, and what you do with it is your decision.