How your project is set up

Your project is created for you as part of your arrangement with Kapitable — what arrives, who the first member is, and what to do when you take on another LBO.

Overview

You do not create your project. It is created for you.

A project is the workspace for one LBO (A1.3), and it corresponds to an arrangement you have with Kapitable. So the Kapitable team sets it up as part of onboarding you, and you arrive in a project that already exists.

That is worth stating plainly, because it is the first thing people look for and do not find.

What you'll learn

What arrives when your project is created, and what does not
Who the first member is, and what they do next
What to do when you take on another LBO
What you manage yourself from here on

What arrives

A project, named for the deal, and empty.

It has no companies, no shareholders and no history until you add them. That emptiness is the normal starting state rather than a sign something went wrong — and the order matters: companies first, then shareholders, then the events that produced today's ownership (A3.1).

The first member

Kapitable seeds one person as Project Admin.

From there you run yourselves. That person adds the rest of the deal team and sets each role (A2.3), and nothing about membership needs to come back to us.

It is worth choosing that first person deliberately, because a Project Admin can extend access to anyone else. It is the one grant made on your behalf rather than by you.

When you take on another LBO

One project is one LBO — not one company, and not one subscription round (A1.3). A ManCo, an add-on, a newco inserted into the structure: all of those are companies inside the project you already have.

A genuinely separate LBO is a separate project, and a separate arrangement. Contact the Kapitable team and it will be set up for you; there is no self-service path, deliberately, because a project carries a commercial agreement rather than being a folder you open.

Do not work around it by fitting two LBOs into one project. The structure, the cap tables and the reporting all assume one deal per project, and unpicking that later is considerably harder than asking.

What you manage yourselves

Everything inside the project:

Members and their roles (A2.3, A1.4)
Companies and the group structure (A3.1)
Shareholders across the LBO (A4.2)
Document templates for the project (A2.5)
Events, decisions and processes — the work itself

What you do not manage is the project's existence.

Common problems

There is no way to create a project. Correct, and deliberate. Projects are set up by Kapitable as part of your arrangement.

We have signed another deal. Contact Kapitable for a second project. Do not add the new LBO's companies to your existing one.

The project looks empty and nothing works. Expected on day one. Companies come first (A3.1), and most views have nothing to show until they exist.

Someone needs access and cannot be added. Only a Project Admin manages membership. Check who holds that role on this project (A2.6).

A1.3 — One project = one LBO · why the boundary sits where it does
A2.3 — Inviting your team · adding everyone else, which is yours to do
A1.4 — Roles and what each can see · what each role can reach
A3.1 — Three ways to create a company · the first real work in a new project