Zolvo's First Client Signed Before They Wrote a Single Line of Code. Why That's Not Luck — And How to Replicate It.
Isabela Rodriguez signed Zolvo's first client during the YC application process, before having a product. That's not luck or Silicon Valley magic. It's diagnosis. It's exactly what we do at ProjectApp before writing code.
Project App
Engineering Team
One of the data points from Isabela Rodriguez's story that caught my attention most: her first paying client signed during the Y Combinator application process, before Zolvo had a single line of code. YC accepted them partly because that was evidence the problem was real and Isabela understood it better than anyone. When I read that, I thought about something we've done at ProjectApp for a long time: the 5-day diagnosis that always happens before we write a line of code. The logic is exactly the same.
Why the Client Signed Before Seeing the Product
Isabela didn't sell a product. She sold the certainty that she understood the problem better than the client could articulate it themselves. She spoke with over 30 people in the sector before building. She knew exactly which part of the process was most expensive, where the most frequent errors were, and what that meant in terms of money lost every month.
"Our first paying client signed during the YC application process, before writing a single line of code. That's the highest indicator that the problem is real."
— Isabela Rodriguez, CEO of Zolvo
ProjectApp's Diagnosis: The Same Logic
At ProjectApp we don't start writing code until the diagnosis is done. It's 5 days where we map the client's real operation: how information flows today, where the bottlenecks are, which processes generate the most errors, which flow is most critical. That diagnosis lets us arrive at the proposal not with a list of features but with a description of the problem that the client recognizes as their own.
Days 1-2: Current Operation Mapping
How information flows today, who the actors are, what systems are used, where the friction points are.
Days 3-4: Priority Pain Identification
Which process generates the most cost, errors, or inefficiency. That's the system's entry point.
Day 5: Proposal Based on the Real Problem
Concrete scope, estimated timeline, and value proposition expressed in the client's business terms, not technology terms.
Key Takeaways
Key Takeaways
- 1Signing a client before having a product isn't YC magic — it's the result of understanding the problem better than anyone.
- 2The pre-code diagnosis isn't a formality — it's the most powerful sales tool in custom software.
- 3The proposal based on the client's problem converts more and generates more successful projects than the technology-based one.
- 4This principle applies equally for a YC startup solving commercial credit in the US and a custom software company in Medellín.
Isabela signed before writing code because she understood the problem better than the client themselves. At ProjectApp we do exactly the same — it's called diagnosis and it's the step that most impacts the final result of each project. The code is the consequence of having done it right.
If you have a software project in mind and want to understand exactly what needs to be built and why, ProjectApp's free diagnosis gives you that map in 5 days. Write to me.