Select mobile stack components and set weekly time commitments over the MVP build window.
Technical Co-Founder Commitment
Business / Non-Technical Co-Founder
Protects both non-technical and technical founders by releasing equity tranches upon verified technical delivery and business traction.
| Phase / Milestone | Verification Criteria | Est. Timeline | Tech Tranche | Biz Tranche |
|---|---|---|---|---|
| Phase 1: Architecture & DB Setup | Auth schemas, PostgreSQL/Supabase initialized, cloud repo & CI/CD deployed | Weeks 1 - 3 | 15% of Grant | 15% of Grant |
| Phase 2: Mobile MVP on TestFlight | iOS & Android builds executing core user flow, push notifications live | Weeks 4 - 10 | 35% of Grant | 35% of Grant |
| Phase 3: Beta Launch & Traction | 100 active beta users onboarded, initial feedback loops instrumented | Weeks 11 - 14 | 25% of Grant | 25% of Grant |
| Phase 4: Store Release & Monetization | App Store / Google Play public approval, Stripe/IAP billing active | Weeks 15 - 16 | 25% of Grant | 25% of Grant |
Audit legal, tax, and intellectual property alignment prior to signing partnership agreements.
-
Mutual Intellectual Property (IP) AssignmentAll code, trademarks, user data, and designs belong to corporate entity, not individuals.
-
Timely Section 83(b) Tax Election FilingMust be filed with IRS within 30 days of equity grant to prevent taxes on future vesting value.
-
Standard 4-Year Vesting with 1-Year CliffPrevents a founder walking away after 2 months with a permanent unearned 30-50% stake.
-
Jurisdiction & Geographic Nexus Clarity (e.g. Florida / US)Governing law and dispute resolution state defined (crucial for remote co-founders).
-
Stealth Idea Scope & Non-Compete CarveoutsClear boundaries on pre-existing code repositories vs newly created venture IP.
Generate structured Markdown and JSON agreements ready for founder vetting and legal counsel review.
Generating agreement...
Saved contribution valuation arithmetic
Read the explanation
Saved technical thirty-five weekly hours times sixteen weeks gives five hundred sixty; business thirty times sixteen gives four hundred eighty. Bars share zero at one pixel per modeled labor hour. Estimated labor and duration are inputs rather than verified project execution. Five hundred sixty technical hours times assumed one hundred ten gives sixty-one thousand six hundred assigned value. Four hundred eighty business hours times seventy-five gives thirty-six thousand. Bars share zero at point zero zero eight pixels per assigned dollar. Rates are scenario assumptions, not actual market valuations or legal equity rights. Five thousand business cash augments thirty-six thousand labor value to forty-one thousand; technical cash zero leaves sixty-one thousand six hundred. Combined one hundred two thousand six hundred divides each slice to equity percentages. Bars share zero at point zero zero eight pixels per assigned dollar. This is an authored allocation model, not an executed agreement. Complete raw term-sheet JSON and actual preset/resize preserved.