Procedure · Stage 0 · Software track, Every founder
Code and account ownership
Awaiting CA/CS check — do not rely on it yet. The legal, tax or patent lines on this page have not been checked by a CA, CS or patent agent.
The mistake

The mistake
“A non-coding founder had interns build the site on their own accounts, then fought over the code.”
What it cost: Lost control of the code.
01Why it repeats
The problem appears only when someone leaves.
Pause
Write it down before you read the procedure. Your answer stays in this browser.
02Where it sits
- Stage
- 0
- Exit test
- Company owns the GitHub organisation, host, database, domain and email (track gate at stage 0)
- Proof file
- Certificate of incorporation; signed founders' agreement; DPIIT certificate if applied
03The procedure
Answer the pause question above, then choose Show the procedure.
- 1The company owns every account from day one: GitHub organisation, host, database, domain, email. People are added as members and removed on exit.
- 2Everyone who builds signs an IP-assignment and confidentiality agreement before starting. Interns and freelancers may not count as employees.
- 3An offboarding checklist: remove access, rotate keys, collect files.
You cannot prove someone deleted a copy; the agreement and the access controls are the protection.
04The template
Internship form and IP-assignment agreement
Signed by every intern or freelancer before they build anything.
Coming soonDetails
05India specifics
Not yet written.
06Last verified
Last verified: Awaiting check
07The why
No psychology in this one: it is a procedure problem, not a judgement problem.
Guidance, not advice
Guidance, not advice
This is guidance, not advice. Confirm your own case with a CA, CS or patent agent.
08Track additions for this stage
Showing all tracks. Answer three questions to see only yours.
| Stage | Physical product | Software | Services |
|---|---|---|---|
| 0 | Trademark filed for the name | Company owns the GitHub organisation, host, database, domain and email | Standard contract template chosen |
Ledger line
Write one Mistake Ledger line for this gate, pass or fail: what you expected and what happened.
Open the Mistake Ledger