Cofounder Access Before Revenue

The popular advice is "figure out equity later, just ship." It fails when the first ten thousand dollars in monthly recurring revenue arrives and nobody can agree who holds the domain registrar login, who can change payout bank details, or who locked the other cofounder out of Git during an argument that started about vision.

Cofounders fight about pace, equity, and product direction. The fights that destroy companies fastest are often boring: who can delete the domain, who moved the payment processor, who changed DNS without telling the other person. Revenue arrives and small ambiguities become lawsuits in all but name.

Before the access map existed

Two cofounders started a logistics dashboard for regional freight brokers. One coded. One sold. The repository lived on the coder's personal GitHub because "we will move to a company org later." Deploy access felt like a reward. Registrar login sat in one person's password manager with no shared recovery.

They closed first revenue. Emotions ran hot. During a disagreement about pricing, the technical cofounder set the business cofounder's deploy access to read-only. Customers saw downtime. Enterprise pilots paused. Legal consult cost thousands. Friendship strain lasted months.

The fix was straightforward once calm returned: company org on Git, shared vault for registrar, processor admin documented, branch protection on main. The cost was trust they could not fully buy back.

Access before revenue means you write, in a shared doc or lightweight agreement, who holds admin on repository org, hosting, database, domain registrar, email DNS, payment processor, and analytics. You agree how to add and remove people and what happens if someone leaves.

The line we draw is this: this is not replacing counsel for entity formation and equity. This is operational clarity you can finish in one meeting. Access before revenue is not surveillance. It is mutual visibility so trust has structure.

Waiting until revenue means emotions run hot, lawyers cost more, and customers get caught in crossfire.

The turning point: one meeting, ninety minutes

Schedule ninety minutes before revenue, or immediately if revenue already started. Fill a table: system, admin holders, two-factor authentication yes or no, backup email, what happens if someone leaves.

Repository org. Production hosting. Database. Email provider. Domain registrar. Payment processor. Analytics. Social accounts if used for brand.

Sign with initials in the doc footer. Review quarterly. The business cofounder is not "non-technical" for access purposes. They need read access to billing dashboards and domain registrar, or explicit trust that the technical cofounder reports numbers monthly. Blind trust is not strategy.

Payment processor admin must be explicit. Who can change payout bank? Who sees full card data (hopefully nobody unnecessarily)? Agree refunds above a dollar threshold need both to acknowledge in Slack, or one founder owns support refunds with a weekly report.

Shared login in chat is a future disaster. Use org invites and two-factor authentication. Store recovery codes in a company vault, not one personal phone. If one cofounder's phone dies, the other can still access the registrar.

Domain and email are brand custody. Losing registrar access means losing the company front door. Founders forget registrar is not the same as hosting. Agree: no domain transfer without both notified. Agree: support@ is monitored by whom on weekends.

After the map: habits that prevent relapse

Teams with access maps decide faster on vendor changes because they know who clicks. Teams without maps debate power for weeks.

Before you need it, outline a cofounder leaving playbook: remove Git access within twenty-four hours, rotate API keys they knew, change shared passwords, confirm processor still accessible to staying founder, domain stays with company, customer email sent if deploy risk exists. Calm playbook beats midnight rage.

Enable branch protection on main. Pull request review for production. Stops accidental force push during stress. README states who to ping for deploy. On-call rotation even if only two people.

Quarterly access review on the same calendar invite. Remove ex-contractor seats. Confirm two-factor authentication. Update map. Fifteen minutes prevents years of pain.

Agree both founders are notified on payout bank changes. Classic fraud vector in founder disputes. If founders split, customers need honest email from a domain they trust. The access map includes who sends.

First ten thousand in monthly recurring revenue feels like proof. Founders who lacked an access map reinterpret old favors as theft. The map prevents narrative vacuum.

Contributions

• Schedule a ninety-minute access map meeting with your cofounder, or with future-you if solo with contractors.
• Move the repository to a company org if it still lives on a personal account.
• Enable two-factor authentication on registrar, Git hosting, and payment processor today.
• Ban shared passwords. Use invites and a shared password manager vault.
• Put quarterly access review on the calendar with initials on the updated map each time.

ARIA helps teams research, validate, plan, launch, ship, and run on infrastructure the company holds. Connect company accounts early, not cofounder personal accounts.

Solo founders with contractors follow the same discipline. Contractor invites, not owner role. Offboarding checklist. Access map lists contractor seats. Revenue makes contractors tempting to over-trust.

Equity splits belong in counsel documents. Access map belongs in operator doc. Link them only by noting entity name on both.

Angels sometimes ask who controls keys. A clean map answers without embarrassment. Agency partnerships: if an agency holds anything, contract says client owns and agency is invite-only.

Agree a mediator friend or coach before conflict if that helps your relationship. Access map reduces conflicts that need mediation.

Part-time cofounders still need visibility or explicit delegation document. "They handle tech" is not access policy. Advisors do not need admin by default. Read-only billing export monthly if helpful.

Do we need a lawyer for the map? Lawyer for equity. Map is operator hygiene.

What if we are friends? Friends need clarity most.

Can one cofounder own all keys? Yes if documented and recovery exists for the other.

What about IP? Entity IP is counsel. Repo custody is the map.

Revenue already started? Do the map this week.

What breaks when access stays vague?

Processor payout bank changes without both notified: classic fraud vector in disputes. Domain transfer during argument: customers see broken email. Force push to main during fight: production down during pilot week. Each is preventable with map plus branch protection.

Git branch protection on main with required review stops accidental damage during stress. README states who to ping for deploy. On-call rotation even for two people formalizes responsibility.

Shared password culture kills companies slowly. Ban shared passwords. Password manager shared vault yes. Slack DMs with root password no.

Recovery codes for two-factor authentication live in company vault, not one phone. Hardware failure should not become registrar hostage situation.

How do solo founders with contractors use the same map?

Contractor invites, not owner role. Access map lists contractor seats and end dates. Offboarding checklist before removing access: export state they maintained, rotate keys they touched, review recent deploys.

Revenue makes contractors tempting to over-trust. Map prevents "they handle tech" from meaning "we have no idea who admin is."

Agency partnerships: if agency holds anything, contract says client owns and agency is invite-only. Access before revenue applies to client entity, not only your consulting brand.

What do investors and angels actually ask?

Who controls keys. Who can shut down production. Whether domain and processor sit in company name. Clean map answers without embarrassment. Messy answers discount conviction even when product demo shines.

Dispute resolution without drama: agree mediator friend or coach before conflict if helpful. Access map reduces conflicts that need mediation. It does not replace hard conversations about equity and vision.

When one cofounder is part-time, part-time still needs visibility or explicit delegation document. Advisors do not need admin by default. Read-only billing export monthly if helpful.

Customer communication during cofounder change: honest email from domain customers trust. Map includes who sends if founders split. Calm playbook beats midnight rage posting.

Processor admin separate from equity doc but linked by entity name. Counsel handles IP assignment. Operators handle who clicks refund at 9pm Friday.

Quarterly review: same calendar invite, remove ex-contractor seats, confirm two-factor authentication, update map initials. Fifteen minutes prevents years of pain.

First ten thousand in monthly recurring revenue feels like proof. Founders without map reinterpret old favors as theft. Map prevents narrative vacuum where both sides invent history.

Cofounder access before revenue. Clarity is cheaper than court.

What should the ninety-minute meeting produce?

One shared document, not fifty-page contract. Table with systems down left column: Git org, hosting, database, email, registrar, processor, analytics, social if used. Columns for admin holders, two-factor yes or no, backup recovery location, offboarding steps.

Initials in footer with date. Photo or PDF stored in company vault. Review quarterly with calendar invite both accept before conflict.

Move repo to company org in same meeting if still personal. Enable two-factor before meeting ends. Ban shared passwords explicitly in writing even among friends.

Agree refund threshold requiring dual ack if that fits your relationship. Agree processor bank change notification rule. Agree domain transfer notification rule. Agree support@ weekend monitor.

Technical cofounder documents deploy ping in README. Business cofounder documents customer-facing sender domains. Both know where registrar login lives.

If solo with contractors, map lists contractor seats and end dates. Offboarding checklist attached. Revenue does not change rule: invites not owner.

Access map is operator hygiene lawyers do not replace. Equity doc is counsel domain map does not replace. Link by entity name only.

When revenue already started, shame is useless. Schedule map this week. Future you pays less than future you without map.

First ten thousand monthly recurring revenue magnifies slights. Map prevents vacuum where narrative invents theft. Clarity speeds vendor decisions because someone authorized clicks.

Customer email during founder change comes from domain buyers trust. Map names sender. Calm beats midnight social posting.

Investors ask who controls keys. Map answers. Angels notice sloppy custody even when demo glows.

Agency client: client owns client accounts. Contract says invite-only agency access. Access before revenue for client entity protects both sides.

Mediator friend named before conflict optional but cheap insurance. Map reduces need. Does not eliminate hard talks.

Part-time cofounder needs visibility or delegation doc. "Handles tech" is not policy. Advisors read-only unless exceptional case.

Branch protection on main. Review before production deploy. Prevents stress damage.

Quarterly fifteen minutes: remove ex seats, confirm two-factor, update initials. Cheaper than court.

Cofounder access before revenue. Schedule the meeting.

Revenue magnifies perceived slights when map absent. First meaningful monthly recurring revenue feels like proof of contribution. Without map both sides invent narrative from memory colored by stress.

Processor payout bank change with dual notification prevents classic fraud vector during founder dispute. Domain transfer with dual notification prevents front door theft during argument.

Recovery codes in company vault prevent registrar lockout when one phone dies or one cofounder travels. Operations continue. Drama shrinks.

Business cofounder read access billing registrar or explicit monthly report from technical cofounder. Blind trust not strategy. Visibility structured trust.

Shared password ban explicit in map footer even among friends especially among friends. Friends without clarity lose companies and friendship same quarter.

Git org move from personal account in meeting if needed. Cannot defer to after revenue. After revenue move feels like power move not hygiene.

Customer email during split from domain buyers trust. Map names sender before you need sender.

Investor angel key control question answered from map not embarrassed pause during coffee.

Agency client entity map invite-only agency seats contract language before deploy.

Access before revenue cheaper than access during divorce energy. Schedule ninety minutes. Finish map. Review quarterly fifteen minutes. Clarity compound interest.

If revenue already started, do not wait for perfect relationship moment. Schedule map this week. Awkward ninety minutes now beats awkward ninety days of production downtime later.

The map is living document. Initials on quarterly updates prove you reviewed, not only created once and filed. Investors notice difference between map and mythology.

Cofounder access before revenue. Clarity is cheaper than court.