claude, inc.Open source ↗
An illustrated team of robots: the CEO and CTO above Developers, Designers, Marketing, Social Media, Finance, Small Business, Legal, and Sales.
MEET THE WHOLE COMPANYCEO + CTO · Eight departments · 54 specialist manuals

— THE COMPANY YOU BRING TO YOUR PROJECT

Bring the vision.
Meet your
company.

Eight business departments, led by a CEO and CTO in Claude Code. From the first idea to the next release, your whole company works from one project.

Your files. Your decisions. A company that remembers the work.

THE ORGANIZATIONEST. IN YOUR PROJECT
YOU · FOUNDER

The direction.

CLAUDE · CEO

Business direction.

Priorities & arbitration
CLAUDE · CTO

Technical direction.

Architecture, skills & security ↗

8 departments · 48 employee skills · 6 staff skills
54 operating manuals, one shared company

You set the direction.
The company carries the work.

One shared projectSpecialists with operating manualsTasks, dependencies & reviews

01 / MEET YOUR COMPANY

The right expertise.
Under one roof.

Browse every department and its six employees. Each skill has a job, a workflow, and a quality bar.

EXECUTIVE OFFICE / CTO

Technology that serves
the business.

Read the CTO charter ↗

CEO and CTO lead together. The CEO sets business priorities and arbitrates tradeoffs. The CTO owns architecture, agent infrastructure, security, skills, and code quality, bringing technical facts and options to the CEO for quick business decisions.

THE SIX EMPLOYEES OPEN A DELIVERABLE FORMAT TO SEE THE WORK

COMPANY STAFF

Continuity for the project. Accountability for the spend.

THE WHOLE COMPANY / 54 OPERATING MANUALS

Every specialty, connected.

Peer CEO and CTO executives, eight departments, and the manuals available to your project.

Open the full organization map ↗

Scroll across the map to explore all eight departments.

Organization map with the CEO and CTO as peers, eight departments with six manuals each, and six staff manuals. Every skill is named.

02 / HOW THE COMPANY WORKS

A project, with
a working organization.

Give the company context once. Return to the same project as the work develops.

  1. 01

    You bring the project.

    An existing codebase, a business, a new product, or a problem worth solving. Set the goal and constraints.

  2. 02

    The CEO scopes the work.

    Clarify what done means. Assign department owners, split tasks, and record dependencies in the project board.

  3. 03

    Departments deliver.

    The department heads use their employee manuals. Work produces files, decisions, and explicit handoffs.

  4. 04

    Review. Decide. Continue.

    Review the evidence. Record results and blockers locally, then pick up from the project’s saved state.

HARNESS & LOOPS / BUILT AROUND THE BUSINESS

Define the checks. Deliver. Review. Improve.

The CEO selects a project stage and effort, then combines each task’s acceptance contract with its department’s business checks. Each submission uses one iteration. Recorded reviews identify what passed, failed, or remains unknown; exhausted budgets require an explicit extension.

The CTO advises on technology and evidence across the company. A recorded PASS describes a review result; it is not a security certification.

↳ Execution happens in your local Claude Code session. This website prepares briefs and displays imported snapshots; it does not run employees.

03 / RETURN TO YOUR PROJECT

See where the
company stands.

Open the project state saved by the CLI to see actual recorded tasks, dependencies, and reviews.

Choose your local .claude/company/project.json file. It is read in this tab and never uploaded.

Read-only snapshot. Reopen the file to refresh it. Recorded statuses and reviewer names are supplied data; this page does not verify artifact files or execute reviews.

Or paste a project snapshot

In your project terminal, run company project status --format json and copy its output here. This is useful if your browser cannot read local files.

Read in this tab only. Cleared after a successful import or when you close the snapshot.

Your company’s work will appear here.
Start a local project below, then open its saved state.

04 / MAKE IT YOUR COMPANY

Bring something
you want to build.

Start with your own project, at any stage. The entire company is available; your brief gives it a direction.

  1. Install the company.

    Install the CLI and company files using the repository instructions. You’ll need Claude Code and Python 3.9+ locally.

    Open installation instructions ↗
  2. Download your project brief.

    Use the form here. Put company-brief.md in the project folder where you want the company to work.

  3. Initialize, then start.

    In a terminal inside that project folder:

    company project init --name 'My project' --brief-file company-brief.md
    company project start

    Replace the fixed sample name in your terminal if you want. Start opens a local Claude Code session with the company and saved project context.

COME BACK TO THE WORK

Run company project status to read your persistent board. Tasks, dependencies, and reviews are stored with the local project.

YOUR FOUNDER BRIEF

PREPARATION ONLY

What are we working on?

Use your own words. There is no recipe to fit.

Departments to prioritize Optional

Preferences for the CEO. All eight departments stay available, including those you leave unchecked.

Stays in this tab. No account, API key, or upload. Reloading clears your draft.0 / 8,000 B

The download contains your exact text and department preferences. The 8,000-byte limit includes the brief’s formatting.

Copy uses the command for your installation. The downloaded brief stays the same.