Every new Customer gets a ready workspace, setup done for them, and one rescue email if they stall. Most churn happens in the first week, before anyone sees the product work; doing the setup for them closes that gap.

Needs Customer

What you get

1workspace per new Customer, ready before their first sign-inTenant
1setup done for them: keys, imports and first callsAction
1rescue email to anyone whose start stallsMessage
1activation mark at first value, for the activation rateCustomer
1Issue for any setup step done by hand three timesIssue

Your agent does

Process.enable → Setting.update

You, to your agent

Welcome every new customer.

Do the onboarding setup for every new customer?

Who has not activated yet?

# 1. Process.enable
curl -X POST https://api.sb/leaseline.app/processes/process_onboarding/enable \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

# 2. Setting.update
curl -X PATCH https://api.sb/leaseline.app/settings/setting_1 \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"value":true,"key":"onboarding.doneForYou"}'

import { $ } from 'startup-builder'

await $.Process.enable({ process: 'process_onboarding' })
await $.Setting.update({ id: 'setting_1', value: true, key: 'onboarding.doneForYou' })

npx startup-builder do Process.enable --json '{"process":"process_onboarding"}'
npx startup-builder do Setting.update --json '{"id":"setting_1","value":true,"key":"onboarding.doneForYou"}'

{
  "name": "do",
  "arguments": {
    "code": "await $.Process.enable({ process: 'process_onboarding' })\nreturn await $.Setting.update({ id: 'setting_1', value: true, key: 'onboarding.doneForYou' })"
  }
}

Change it

Let customers set themselves up; just send the guide.
Call anyone who has not activated after three days.
Count the first import as activation.

Under the hood

Systems: Customer access, Success, Mailboxes
Nouns: Customer, Tenant, Message, Issue, Setting
Events: Customer.created, Customer.activated

The Onboarding Process starts on every Customer.created, with the Onboarding Specialist in the seat. A step done by hand three times becomes an Issue, so the product absorbs it. To test a shorter welcome email against the current one, see test two onboarding emails.

What you getCopy Anchor Link

Your agent doesCopy Anchor Link

Change itCopy Anchor Link

Under the hoodCopy Anchor Link

What you get

Your agent does

Change it

Under the hood