Vibe-coded.
Now production-grade.

You built it with Lovable, Bolt or Cursor and it works. I’m a senior engineer who helps you find and fix the risks that matter before launch, then stays around for what comes next — without throwing away what you built.

review/launch-readiness · 4 files changedtypical fixes from a review
// src/lib/payments.ts — runs in the browserRemoved: const stripe = new Stripe("sk_live_••••••••");Added: // moved to the server: app/api/checkout/route.ts// firestore.rulesRemoved: allow read, write: if true;Added: allow read, update, delete: if request.auth.uid == resource.data.ownerId;// app/api/webhooks/stripe/route.tsRemoved: const event = JSON.parse(body);Added: const event = stripe.webhooks.constructEvent(body, sig, secret);
Not a code person? The report explains each fix in plain English.

Three steps from prototype to something you can sell.

  1. 01 / REVIEW

    Launch-readiness review

    Security, auth, payments, data, backups, deployment. A written report ranked by severity, plus a walkthrough call. Typically delivered within 3 business days after scope and access are confirmed.

    What the review covers

  2. 02 / FIX

    Fix sprint

    I fix what’s critical, in small reviewable pull requests. Fixed scope, typically 1–2 weeks. No unnecessary rewrites.

  3. 03 / KEEP

    Care plan

    Monitoring, updates, and a senior review of what the AI changes next. Priority help when something breaks.

01 / REVIEW · IN DETAIL

What the review covers.

An experienced engineer’s review of your code and setup, focused on the risks that matter most before launch. Typically delivered within 3 business days after scope and access are confirmed; larger apps get a scope and timeline agreed up front.

What I look at

  • Authentication and who can access which data
  • Payments, webhooks and other third-party integrations
  • Database rules, data model and backups
  • Secrets, API keys and configuration
  • Deployment, error monitoring and logs
  • Tests around the flows your business depends on

What you get

  • A plain-English summary you can act on without reading code
  • Findings ranked by severity and business impact
  • For each one: what the issue is and why it matters
  • Concrete recommendations and a suggested order to fix them
  • Scope, assumptions and limitations, stated up front
  • A walkthrough call to go through it together

What I need from you

  • Read access to the code repository
  • Access to hosting, database and auth or payment dashboards where relevant
  • A short note on what the app does and who uses it
  • Never your passwords: invite me as a collaborator and remove me afterwards

What it isn’t

  • Not a penetration test
  • Not a security certification or compliance audit
  • Not a guarantee that the app is free of bugs or vulnerabilities
  • If your stack is outside what I know well, I’ll say so on the intro call

After the report

You decide what happens next. Fix things yourself or with your team using the report, or I fix the critical items in a fixed-scope sprint. No obligation either way.

What I won’t do

The things founders tell me they’re afraid of.

  • Tell you to throw it away and start over
  • Lock you into me — you own every line and every account
  • Stop you from building with AI
  • Bill by the hour without a fixed scope

ALSO: LEGACY CODE

Older codebase that’s hard to change?

I also modernize older products step by step, while they keep shipping — no big-bang rewrite. That work is for software businesses and engineering teams, so it has its own page.

How I approach legacy modernization
Jakub Lenart

Jakub Lenart

Senior software engineer with 14+ years of building web applications, mostly in React and TypeScript. For the last four years I’ve worked remotely with an international SaaS startup.

Along the way I’ve migrated an application from a legacy framework to a modern one, implemented authentication and single sign-on with Auth0, and built and maintained AI-powered product features. On the backend I work with Python, ORMs and database migrations.

I care about small pull requests, human review, and code people actually understand. That’s what I bring to your app.

Launching soon? Get a second pair of eyes first.

Book a free 15-min call →