Quick start
From zero to your first playbook running in 30 minutes — the 7 steps of the onboarding wizard.
This guide takes you from creating your account to having your first playbook running, in 7 steps. The goal: in 30 minutes you're working with real data, not a demo.
If you already have an account, you can skip to the step you're missing. The wizard saves automatically.
Before you start
Have on hand:
- Google Workspace or Microsoft 365 account (to connect email and calendar).
- Customer list — CSV or access to your current CRM. If you don't have one, LealUp includes demo data to test with.
- Logo and domain of your company (optional, for workspace branding).
- 5 minutes for each CSM you want to invite.
1. Create your account and workspace
Go to app.lealup.com and sign up with your corporate email. When signup completes:
- Your workspace is created (an isolated environment with its own subdomain
your-company.lealup.com). - Your user is automatically an Admin.
- 5 default playbooks are seeded (At-Risk, Renewal, Expansion, Onboarding, Win-Back).
One email can only belong to one workspace. If you're already invited to another, signup redirects you to that workspace.
2. Connect your email
Critical step — without email, the timeline stays empty.
- Gmail — OAuth with your Google account. LealUp syncs bidirectionally: emails sent from your email client show up in the timeline, and those you send from LealUp land in Gmail. No extension required.
- Outlook / Microsoft 365 — same, via Microsoft Graph (launching Q2 2026).
When you authorize, LealUp indexes the last 30 days of email. Ongoing sync is real-time via Pub/Sub.
3. Import your customers
Two options:
CSV (recommended to start) — download the template, fill in the minimum columns (name, domain, arr, status, owner_email), and upload it. The wizard matches columns to your fields.
Ingestion API — if your tech team already implemented it, customers arrive via POST /v1/ingest/events. See Event ingestion.
If you want to test without real data, turn on Load sample data (50 fictional customers with timelines).
4. Configure the health model
LealUp starts with the Balanced preset (usage 40%, engagement 30%, support 20%, sentiment 10%). You can:
- Leave it as-is and tune later when you have more data.
- Pick another preset — Usage Heavy, Engagement First, Support Critical.
- Customize dimensions, weights, and thresholds. See Health model.
If you're just starting, leave it on Balanced. It's better to iterate on real data than tune in a vacuum.
5. Review the seeded playbooks
The 5 default playbooks are already active. Open Playbooks in the menu and review:
| Playbook | Triggers when... | Generates tasks like... |
|---|---|---|
| At-Risk | health drops below 50 | "Schedule retention call", "Review open tickets" |
| Renewal | renewal within <60 days | "Prepare proposal", "Confirm champion" |
| Expansion | health ≥80 + growing usage | "Identify new stakeholder", "Propose upsell" |
| Onboarding | new customer (first 90 days) | "Kickoff call", "Technical setup" |
| Win-Back | churned customer | "Follow-up email at day 90" |
You can disable, edit, or clone any of them. See Playbooks and tasks.
6. Invite your team
Admin → Team → Invite. Enter the email and role:
- admin — full access.
- csm — their assigned portfolio, all playbooks.
- director — aggregate view, dashboards, no customer editing rights.
- viewer — read-only.
Each invite generates an email with a unique link to your workspace's subdomain. The user accepts and is active immediately.
7. Done!
We send you a summary by email. From here, next steps depending on your role:
- CSM → Daily workflow
- Admin → Configure your workspace (tune health, create fields, connect more integrations)
- Developer → API guide
Something failed?
- Invitation email didn't arrive → check spam; if it persists, see FAQ.
- CSV throws errors → make sure the first row is the header and the separator is a comma.
- Gmail doesn't sync → revoke permissions at Google Security and reconnect.
If none of the above works, email [email protected] with your workspace (subdomain) and the step where you got stuck.