Skip to content

Create an organization

The first step of onboarding a new customer is creating their org. This is also where the billing relationship is established, so the details you enter here matter more than they look.

Console → top-left organization switcherCreate organization. You’re operating as your own user; the new org becomes a separate tenant immediately after creation.

FieldSourceNotes
Team nameCustomer’s ImpressumUse the legal entity name as it appears on the customer’s website Impressum. This becomes the invoice recipient downstream in Stripe.
PlanDiscussed during salesQuotas below. A customer with 2 Lead Pools falls into Professional.
Billing intervalMonthly or yearlyBoth are supported; yearly typically priced at a discount.
AddressCustomer’s ImpressumCopy from the Impressum so it stays consistent with VAT records. If the customer corrects it later, the source of truth is Stripe — that’s the only place the billing address actually lives.
Contact emailYour own onboarding inbox with +<customer> suffixSee below.

Quotas are per resource, not per “location” — an org can have multiple Calendars per physical location if it makes sense.

PlanLead PoolsCalendarsUser seats
Starter112
Professional (recommended)336
Business6612

Above the Business plan, contact sales for a custom quota. Quota enforcement happens at create-time — attempting to create a 4th Lead Pool on Professional surfaces an upgrade prompt.

When prompted for the org’s primary contact email, enter your own onboarding inbox with a Gmail-style +suffix, e.g. you+inspire-martial-arts@yourcompany.com. Mail still routes to you, and the suffix tags every system email so you can tell at a glance which org it came from. Stripe also surfaces the suffix in its customer list, which makes triage trivial.

Works with any Gmail-hosted inbox (so most operators).

The console switches you into the new org automatically.

Out of the box, a fresh org has:

  • A default set of lead-state categories (see Lead-state categories).
  • No Lead Pools, no Calendars, no Standorte. You create those next.
  • No email infrastructure wired up. See Email setup for the SendGrid + DNS dance.

The next step is to define the org’s Standorte — they’re the glue everything else hangs off.