The little lies founders tell without meaning to.

One of the first things I’ve learned as a lawyer is that I shouldn’t take my clients’ statements at face value.Not because they’re wrong, and not because they’re trying to mislead anyone. But because phrases like “we know who owns what” or “the company owns the IP” often carry more legal meaning than the person saying them intends.

That is where the gap appears: between the company as the founder understands it, and the company as the records can evidence it.

The corporate records problem

Founders often treat the cap table as the source of truth. But in diligence, the cap table is only a summary — and sometimes a deceptively clean one.

A cap table can show names, percentages, SAFEs, options, and share classes in a way that looks organized. However, the real diligence question is whether the company can prove the legal and economic story behind it.

The cap table tells you where the company says it landed. It does not always show how it got there. That “how” is where the risk lives.

Who actually authorized the shares? Were there enough authorized shares available? Does the charter support the classes and rights reflected in the cap table? Were the issuances approved by the board or shareholders where required? What exemption supported the issuance? Were advisor grants made under the right plan or legal theory? Were options granted before the equity plan existed, or outside the available pool? Do the SAFEs convert the way the model assumes? Are there side letters, MFN rights, pro rata rights, information rights, or investor promises sitting outside the spreadsheet? Does “fully diluted” mean the same thing to the founder, the investor, and the lawyer?

Those are not cosmetic questions, they affect economics, control, dilution, investor expectations, and sometimes whether the company can stand behind the ownership story it is presenting.

Sometimes the documents are there, but they do not speak to each other. The charter says one thing. The stock ledger says another. The cap table reflects a later understanding. The financing documents assume a conversion model no one has reconciled. An advisor was promised “1%,” but no one can say whether that meant pre-money, post-money, fully diluted, before the option pool, after the option pool, before the SAFEs, or after the SAFEs.

The most dangerous percentage in a startup is often the one no one defined.

A clean spreadsheet can hide a messy issuance history, and that history matters. Shares do not become valid because they appear in a spreadsheet. Options do not become properly granted because they are listed in a platform. SAFEs do not become economically simple because they are grouped under one label. Advisor equity does not become harmless because it is a small percentage. Informal promises do not disappear because they never made it into the cap table.

The cap table may show the current ownership picture, but the corporate records show whether that picture was properly built.

The IP ownership problem

Founders often say, “The company owns the IP.” Most of the time, they mean this in a practical sense. The company built the product, paid the contractors, controls the repository, uses the brand, and sells the technology. From the founder’s perspective, ownership feels obvious.

However, diligence asks a more precise question: can the company prove how the rights moved into the company?

For a startup, IP ownership is not just about who built the product. It is about whether the company can show a clean legal trail from every person or entity that created, contributed to, modified, or embedded something into what the company now treats as its own.

The IP question is not simply: “Who built it?” It is: “Who had the right to transfer it, what did they actually transfer, and what remained outside the transfer?”

That chain can break in ways that are much less obvious than a missing signature. A founder may have signed a confidentiality and invention assignment agreement with a prior employer. A developer may have reused retained code, internal tools, templates, or frameworks in the deliverable. A consultant may have signed a form designed for employees, not independent contractors. An agency may have subcontracted part of the work without clearly obtaining rights from the people who actually created it.

This is why an IP assignment is only as strong as the rights the contributor had to give. A person cannot transfer rights they do not own, and a company cannot assume that a signature solves every upstream issue.

It is also why “we paid for it” is not always enough. Payment may explain why the company expected to receive the work, but delivery is not the same as transfer. A contractor can deliver code, designs, content, documentation, or product assets without automatically transferring all ownership rights unless the agreement is structured to do that.

Then there is the embedded IP problem. The company may own the custom work created for it, but still depend on retained contractor IP, licensed tools, third-party code, open-source libraries, agency templates, datasets, model outputs, or materials created under someone else’s prior obligations. None of that is necessarily fatal. But it needs to be identified, documented, and licensed in a way that does not restrict the company’s ability to use, improve, commercialize, finance, or sell the product later.

Cross-border work adds another layer. A U.S. assignment form does not automatically solve a cross-border creation story. If founders, developers, agencies, or contractors worked from different jurisdictions, local law may affect employment status, moral rights, invention ownership, enforceability, or whether additional documentation is needed. The form may look familiar, but the creation story may be more international than the document assumes.

The statement “we own the IP” is often doing too much work. It compresses a much more detailed legal story into a sentence that may be true commercially, but incomplete legally.

That is why investment readiness is not just about having a data room. A data room is only where the company’s legal story becomes visible. If the story underneath is inconsistent, unsupported, or incomplete, the folder structure will not fix it.

The earlier founders identify those gaps, the more options they have. Some issues can be organized internally. Some may need legal cleanup. Some may need to be disclosed, explained, licensed, assigned, ratified, or documented. And some may be lower priority than founders fear, we can only know until we know.