Two months before we planned to release our product, a co-founder vesting clause that nobody had actually signed came back to dismantle everything we had built. This is the story of how a single missing signature on a startup founders agreement erased eighteen months of work, and what every early-stage team should learn from our collapse.
The Promise of a Handshake and a Google Doc
We started the way many founders do. Two friends, a shared vision, and a long Google Doc full of ambitions. Product roadmap, target market, mockups, and revenue projections all lived in that document. What did not live there, at least not in any binding form, was a cofounder vesting agreement.
Early on, we had drafted a simple vesting schedule. Four years, with a one-year cliff, standard for most venture-backed startups. We even had a paragraph about what would happen if someone left early, failed to contribute, or simply lost interest. We felt prepared. We were not.
The mistake was elementary: we treated the draft like a finished contract. We emailed it back and forth, edited it in shared docs, and verbally agreed to its terms in countless late-night calls. We assumed that because we trusted each other, the document did not need formal signatures. In the messy first months of a startup, legal formalities feel optional, especially when everyone is busy building.
What the Vesting Clause Was Supposed to Do
The purpose of a founder vesting schedule is straightforward. It allocates equity over time, rewarding continued contribution rather than early presence. In our case, the clause said:
- Twenty-five percent of each founder’s shares would vest after the first twelve months.
- The remaining shares would vest monthly over the following three years.
- If a founder left before the cliff, they would forfeit unvested shares back to the company.
On paper, this protected everyone. The founders who stayed and built would keep their equity. The founder who left early would walk away with less. We even had a clause for involuntary departures and a section on what would happen to intellectual property if things fell apart.
None of it mattered, because no one had actually signed the document.
The Day the Dispute Began
The trouble started nine months into the journey, when one co-founder quietly began working on a competing idea. He had not left yet, not officially, but his contributions were slipping. Meetings were missed. Deadlines evaporated. Slack messages went unread for days.
We confronted him. The conversation was tense but not hostile. He claimed he was still committed. He pointed to the vesting clause we had drafted, suggesting that since he had not technically been removed, his shares were safe. He was right, in spirit. He was also wrong, legally, for reasons we did not yet understand.
When we tried to enforce the terms of that unsigned document, his response was immediate. He did not deny the conversation. He did not deny that we had agreed to the schedule. He simply said, “Show me where I signed.”
Why an Unsigned Vesting Clause Is Not a Contract
This was the harshest lesson of our entire startup journey. A vesting schedule that lives only in an unsigned Google Doc is not a binding contract in most jurisdictions. It is, at best, evidence of an informal understanding. Without signatures, dates, and sometimes notarization, the document carries no enforceable legal weight.
We learned that an unsigned founders agreement fails on three critical points:
- Lack of mutual assent. Courts require clear evidence that both parties intended to be bound. A shared draft with tracked changes suggests ongoing negotiation, not agreement.
- Absence of consideration. While equity can count as consideration, an unsigned promise to issue equity is often treated as a future promise rather than a current exchange of value.
- Statute of limitations and evidentiary problems. Even if the terms could be enforced, proving what was agreed becomes a he-said-she-said battle, which is expensive and rarely worth the legal fees for a pre-seed startup.
In short, our vesting clause was a wish list. When push came to shove, the departing founder could walk away with whatever shares had already been issued, regardless of our schedule, because the schedule had never been formally adopted.
The Dissolution: Two Months Before Launch
By the time our dispute reached its peak, our runway had thinned, our focus had shattered, and our team morale had bottomed out. We had been planning to launch a productivity tool for remote-first creative agencies, and our beta testers were already lined up. But with one founder effectively disengaged and a legal ambiguity hanging over our cap table, we could not move forward.
Investors we had been courting pulled back. They asked the obvious question: if you cannot agree on equity, why should we believe you can ship a product together? Without signed vesting in place, we had no way to cleanly buy out the departing co-founder or reclaim his shares. Bringing in new capital would have meant diluting existing equity, but our cap table was a mess of informal promises and no legal clarity.
Two months before our planned release, we made the painful decision to dissolve the company. We returned the small angel check we had raised. We refunded early customers who had pre-ordered. We shut down the servers and archived the codebase. The startup we had spent eighteen months building simply ceased to exist, not because the idea was bad, not because the market was wrong, but because we had failed to sign a piece of paper.
What Every Founder Should Do Differently
Our collapse was avoidable, and that is the most frustrating part. Looking back, there were several steps we could have taken, and that we now insist every founding team take before writing a single line of code.
1. Sign a Founders Agreement Before Incorporating
Even a simple one-page founders agreement signed by everyone at the outset can prevent the kind of dispute we faced. It should cover vesting, roles, IP assignment, and what happens when someone leaves. Many jurisdictions recognize electronic signatures on basic founder documents, so cost and complexity are not valid excuses.
2. Use a Proper Vesting Schedule From Day One
Adopt a four-year vesting schedule with a one-year cliff, and implement it through a formal Restricted Stock or Restricted Stock Unit agreement. These are standard documents, and templates are widely available. More importantly, they are enforceable.
3. Issue Shares Through a Cap Table Tool
Modern cap table platforms like Carta, Pulley, or AngelList will not let you issue shares without proper documentation. They guide you through vesting setup, founder agreements, and 83(b) elections. The friction these tools introduce is a feature, not a bug.
4. Get a Lawyer for the First Hour, Not the Last
Startup lawyers are expensive, but a one-hour consultation at the beginning can save a company later. Many offer founder-friendly packages or deferred payment plans. The hour we did not spend on legal review cost us the entire company.
The Quiet Lesson Behind a Loud Failure
Startups collapse for many reasons. Market failure, running out of cash, founder burnout. Those are visible, painful, but ultimately understandable. What we experienced was quieter, more avoidable, and in some ways more embarrassing. We had the right vesting terms. We had the right intentions. We simply failed to turn a draft into a contract.
If our story prevents even one founding team from making the same mistake, the wound of our dissolved startup will at least have served some purpose. Sign the document. Date it. Store it somewhere no one can edit without a paper trail. The best vesting clause in the world is worthless if no one has signed it.
