FounderAgreement.com
Free Founders' & Co-Founders' Agreement Builder — private, browser-based, no signup
What is FounderAgreement.com?
FounderAgreement.com is a free Founders' / Co-Founders' Agreement Builder for startup founders, co-founders, entrepreneurs, and early-stage teams. Create and download a Founders' / Co-Founders' Agreement in 5-10 minutes through a simple, guided experience.
The tool helps founders clarify important startup fundamentals before they become sources of conflict, including founder roles, responsibilities, equity ownership, vesting, decision-making, authority, and expectations.
Instead of starting with complicated legal templates or spending hours editing documents, founders answer guided questions and receive an instant downloadable Founders' / Co-Founders' Agreement PDF.
FounderAgreement.com is designed around simplicity and privacy. There is no signup required and no database storage. The browser-based experience works on both mobile and desktop devices.
Whether you are starting a new company, adding a co-founder, or formalizing an early-stage startup partnership, FounderAgreement.com helps you document key founder expectations quickly and clearly.
Ready to launch?
Submit your product and get discovered by builders and creators worldwide.
Launch Now
FounderPlaybooks.
What other founders did to grow.
2722 dispatches from hundreds of founders, pulled from the week's best podcasts.
Price sensitivity has three components: first is purchasing power, the other two are commitment — how committed are they, how passionate are they — and the last is how strong is your value proposition. It's really the relationship between those three things and you have to assess where the gaps are.
Price sensitivity has three components — purchasing power × commitment × value prop
'Are they cheap?' is the wrong question. Decompose willingness to pay into purchasing power, commitment to the activity, and strength of your value prop — then attack whichever is the binding constraint. Surfers seem cheap on the surface but coastal demographics are affluent and commitment is sky-high; the binding constraint is usually value-prop strength.
in my head the choice is sort of binary in that either this stays in a private git repo and no one ever sees it the end or make it open source and then like maybe somebody can do something with it I'm curious what other people will do with it curiosity more than anything
Open-sourcing a dead repo is a cheap validation test
After shutting Maybe down, Josh treated open-sourcing as the lowest-stakes possible 'launch' — pure curiosity, zero plan to revive. The repo hit a nerve, tens of thousands of people showed up, and the project came back to life with $1.1M+ in fresh funding within 10 days. Shipping something dead in public can be a cheaper validation test than building something new.
There's a play for whatever you're stuck on.
Read all 2722 playbooks