Gonzalo Maldonado believes that moving from the role of Staff Engineer or technical leader to startup founder does not require abandoning an engineering mindset, but rather expanding it to include the market, customers, and financing. During his presentation at QCon San Francisco, he introduced a framework he called VC Abstraction Layer Knowledge (VALK), meaning a layer of knowledge that helps engineers translate technical evaluation and platform management practices into startup-related decisions.
The basic idea is not that every internal platform can be turned into a commercial product. Metrics tools, log distribution, or framework operations may become companies such as Datadog, Honeycomb, and Temporal, but this requires proving that a real problem exists and that there is a market willing to pay—not merely that colleagues like the tool inside the organization.
A Platform the Team Loves Does Not Mean It Is a Sellable Product
Maldonado distinguishes between an internal platform user and an external customer. Within an organization, use of the tool may be mandated by a manager or supported by the team, whereas external customers owe the founder neither loyalty nor time. Therefore, it is not enough to ask whether they would use the product; it is better to verify whether the problem has actually happened to them, how painful it is, and whether they are willing to take a concrete step such as signing a letter of intent, starting a trial, or paying.
The speaker suggests viewing the product as a remedy for a painful problem, not as a nice-to-have feature that can be postponed. He also links platform evaluation to determining market size: the total addressable market (TAM), the serviceable available market that can actually be reached (SAM), and then the serviceable obtainable market that can be monetized in the near term (SOM). The founder should begin with what they can reach and prove, not with the largest theoretical market.
Validation Before Building the Product
Maldonado warns against the “build it and they will come” rule, considering it one of the most misleading pieces of advice for technical founders. Instead of jumping directly into building an MVP, he presents a 12-week experimental path: begin by interviewing around 50 people to understand actual problems, then build an initial version, run trials with potential customers, and attempt to reach revenue or a clear payment commitment between weeks nine and twelve. If sufficient evidence does not emerge, the team should return to the problem-understanding stage rather than continue developing an unvalidated product.
These stages are not a guarantee of success, but they reduce uncertainty. The speaker emphasizes that startups need to track customer retention, revenue, growth, customer acquisition cost, and unit economics. If the company spends $5 to produce one dollar in revenue, that is an unsustainable model regardless of the quality of the technology.
How Does an Engineer Translate Their Experience into Investors’ Language?
Maldonado believes that a technical decision document resembles in structure what investors look for: the target customer persona corresponds to the ideal customer profile, success metrics correspond to unit economics, and the deployment plan corresponds to the go-to-market strategy. Therefore, funding pitches should focus on the problem, customers, revenue, retention, and growth—not solely on technical architecture details.
He says that the post-zero interest rate policy (ZIRP) environment has made venture capital more selective; investors compare startup bets with alternative returns that can reach 5% in bonds, according to his presentation. For this reason, he advises starting with as little external funding as possible and proving demand or “traction” before seeking larger rounds. He also warns against raising money simply for the sake of raising it, because a high valuation and expansion before the fundamentals are proven may make it more difficult to save the company later.
Scaling, Founding Partners, and Nontechnical Debt
The founder cannot remain the bottleneck for every decision. Maldonado suggests that the leader gradually relinquish responsibilities every three to six months, moving to the next more important “tower” while keeping previous operations stable.
He also places legal matters close to technical debt in importance. Contracts, intellectual property ownership, founder agreements, and financing instruments such as SAFE are all matters that should be organized early with the help of a lawyer. He stresses that disagreements among founders can kill companies, and that choosing a partner with complementary skills and the ability to make decisions under pressure is more important than mere friendship or technical similarity.
certi.news reading: The practical value of the presentation is that it reframes founding a startup as a cycle of validation and measurement, not as an automatic extension of successfully building a platform within an organization. However, the framework remains a personal experience and a speaker’s perspective, not a guaranteed formula; moreover, failure figures, funding expectations, and the proposed timeline should be treated as general guidance rather than fixed rules for every market or industry.