Product number two shipped twice as fast: the cv-nhanh-web story

Why I wanted to do this

Once content-factory-web had its first real users, I realized something: the hardest part wasn't the "product idea" — it was the skeleton behind it: registration, verification, payment, notifications. The idea for a second product came naturally. Many people I know, especially friends job-hunting, kept struggling to present their CV in a clean, professional way. They weren't short on experience — they were short on a well-presented CV.

The question I asked myself at the time was: if the core infrastructure already exists from the first product, how fast could the second one really go?

The steps and the tools

Step 1 — Reuse the "backbone" almost as-is. The registration flow, OTP verification, wallet top-up, and the Telegram notification bot from content-factory-web carried over almost unchanged. That was the most effort-intensive part of the first product, and now I didn't have to rebuild it from scratch.

Step 2 — Spend 100% of the time on what's actually different: generating the CV. Instead of one generic keyword box, I designed a structured form — experience, skills, education, career goals — so the AI has enough context to write CV content that actually fits the real person, not something generic.

Step 3 — Build 3 different design templates (creative, modern, professional) instead of just one — because a job seeker in a creative field and one in finance clearly need two different presentation "vibes."

Step 4 — Get it in front of real users as early as possible. Because the infrastructure was already stable from the previous product, I could hand the first version to a few friends to try within days, not weeks.

The clearest lesson I learned: most of the time spent building a new product isn't spent on the "core feature" — it's spent on things that seem secondary: login, payment, notifications. Once you have a working foundation, the speed at which you can ship new products goes up dramatically, and you can pour all your energy into the part that actually creates distinct value.

Main tools used: Claude Code to write the new CV-generation logic and restructure the input form, FastAPI, and the entire registration/OTP/wallet/Telegram infrastructure already built.

If you want the details

If you already have a first product and are considering a second, a third — my biggest lesson is: separate your shared infrastructure from your product-specific logic from day one. If you want to know exactly how I organized the code for reuse, feel free to reach out by email or on LinkedIn.