SoleCo
Sign in

How SoleCo works

Three steps for a one-person company built with AI coding tools. Move your code and accounts out of your personal name and into your LLC or corporation. Write down how someone else would keep things running. Then check every three months that nothing slipped back.

Three stages

Where you are decides what matters now. At stage 1, the free scan is all you need.

  1. Stage 1

    Idea incubator

    Lots of solo-coded projects, none incorporated. Everything runs on your personal GitHub, Gmail, and cards.

    What matters now

    • Personal accounts are fine for now.
    • Keep each project in its own folder so one can move into a company cleanly later.
    • Know which project is likely to become the company.

    SoleCo: Free scan

  2. Stage 2

    C-corp or LLC, pre‑revenue

    One project is now a company on paper, but its code, email, and Stripe may still be in your personal name.

    What matters now

    • Move the product's code into a GitHub organization the company owns.
    • Set up company email, and open Stripe on the company's EIN (US company tax number).
    • Write a step-in guide so whoever steps in could keep it running, technical or not.

    SoleCo: Gate, $399 once

  3. Stage 3

    Revenue or raising

    Customers pay you or investors are looking. Other people now depend on the product.

    What matters now

    • Investors will check that the company, not you, owns the code and accounts.
    • Whoever steps in to keep the firm operating needs a way into your systems that stays sealed until it's needed. That access is split in two, and both parts are needed to use it. Give your backup person one half, and keep the other half somewhere they can reach with proof that something has happened to you. If you don't have a backup person you trust, you could get a lawyer.
    • Legal documents such as an IP assignment and power of attorney, prepared by your own lawyer.

    SoleCo: Monitor, $99/year. Legal documents come from your own lawyer.

Three steps

  1. Step 1

    Scan

    Free, a couple of minutes with your AI

    Copy SoleCo’s instructions into Claude Code, Codex, or Cursor. Your AI looks at your projects on your machine, asks which company each belongs to and a few other questions, and writes one file you import. You get a SoleCo Score, a red, yellow, or green verdict on each account, and the number of steps to raise-ready. Then it offers the quick fixes, like the right commit email per company and a CLAUDE.md in each repository.

    Read the instructions or answer the questions yourself in 10–15 minutes.

    SoleCo never stores passwords, API keys, recovery codes, or seed phrases. It records which accounts each company uses and whose login controls them, never the passwords themselves.

    It works wherever your companies are registered. The checklist, vaults, and step-in guide are the same everywhere; only the draft legal documents and the Delaware reminders are US-specific.

  2. Step 2

    Gate

    $399, once

    A checklist that saves as you go, with links to each vendor’s own instructions. Tasks marked for your AI, which is most of Today, it can do with your OK. Along the way, you print your step-in guide: plain instructions a trusted friend, relative, or developer could follow to keep the business running if you can’t. It says who to call first, what you’d want, and what not to touch. The names in it are typed in your browser and never reach SoleCo.

    1. 1Entity mapEvery legal entity, what it does, and which product lives where.
    2. 2Company emailVendor accounts should recover to the company's domain, not your personal inbox.
    3. 3GitHub organizationThe company's code lives in the company's organization, with two owners.
    4. 4Directory fenceOne folder, one set of remotes, one .env, and one commit identity per company.
    5. 5CLAUDE.md per companyEach repo tells agents (and humans) what it is, how to run it, and where production lives.
    6. 6Claude and AnthropicOne daily login. A company Team org only when a second human or diligence needs it.
    7. 7StripeThe account is on the company's EIN, and you're the only Super Administrator.
    8. 8Domains, DNS, and legacy contactsDomains renew on company cards, and each platform's own successor tools are set.
    9. 9Password managerTwo company vaults: Everyday, for what keeps things running, and Owner, for owner logins and recovery codes.
    10. 10Two-factor authenticationSecurity keys, such as YubiKeys, on every company owner account, with a spare kept with the Owner key.
    11. 11Owner keyEverything needed to open your Owner vault: its password, its two-factor recovery code, and a spare security key. It's kept in parts, so no single part opens anything, and it never travels by email.
    12. 12Step-in guideOne printed document for whoever steps in, technical or not: who to call, what you'd want, what to keep paid, and what not to touch. No passwords.
    13. 13Data-room indexThe list of documents diligence will ask for, and where each one is. Not the documents.
    14. 14Draft legal packStarting points for your lawyer, written to US practice. Every page says DRAFT. NOT LEGAL ADVICE. NOT EXECUTED.
    15. 15Working with your own lawyerSoleCo doesn't provide lawyers or send anything to anyone. You choose your own lawyer, pay them directly, and hand things over yourself.

  3. Step 3

    Monitor

    $99/year

    A check-in every three months, plus reminders when something needs attention: GitHub still has only one owner, Stripe is still on your personal login, a domain renews within 60 days, a Delaware deadline is coming, or you haven’t updated your account list in 90 days. If anyone uses your emergency logins, Monitor keeps a checklist open until every one of those passwords is changed.

One guide, two vaults, one Owner key

Nobody gets admin rights to your GitHub or Stripe “just in case.” Instead there are four pieces, and no single one is a way in. A lost guide has no passwords. A stolen part of the Owner key opens nothing. SoleCo holds none of them.

PieceWhat it holdsWhere it isWho can use it
Step-in guideWho to call, what you'd want, what to keep paid, what not to touch, and which accounts exist. No passwords.Printed. One copy with your lawyer, one with the person who steps in.Anyone who needs it
Everyday vaultLogins that keep things running: company email, the domain, hosting, accounting, a spare Claude seat.Your password managerThe person who steps in can request it. Access arrives after a waiting period you can cancel.
Owner vaultOwner logins for GitHub, Stripe, the registrar, and cloud, and every recovery code.Your password managerOnly with the Owner key
Owner keyEverything needed to open the Owner vault, kept in parts. No single part opens anything.Half in your lawyer's safe, in a numbered tamper-evident bag. The other half with the person who steps in, so they already have theirs.The two halves together, once your lawyer has checked identity and authority

After anyone uses emergency access, change every password they could reach. Monitor keeps a checklist open until you do.

SoleCo doesn't provide lawyers. “Your lawyer” means one you choose and pay yourself, if and when you want one.

Your Claude login stays the same

Keep your personal Claude login as the daily driver. Put each company’s source of truth in that company’s GitHub org. cd into the repo; do not /login every morning. Create a company Team org only when a second human needs a seat or diligence requires it. Do not share your personal Claude password with an assistant or successor.

Roles stay separate

  • The trustee or executor holds legal authority.
  • The person who steps in, or a developer they hire, keeps the product running.
  • Your lawyer, one you hire yourself, keeps half of the Owner key.
  • The accountant keeps the books.
  • An assistant, if you hire one, gets the shared company inbox and a few everyday logins. Never the Owner vault.
Run the free scanPricing