CRM & Sales - Setup Guide
How to set up Vitally
Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.
What you're signing up for
Medium to high. Integrating data sources (Segment, warehouse, Salesforce, product analytics tools) is a real integration project; typically 4-8 weeks with Vitally's onboarding team. Configuring health
Read these before you start
- Vitally requires clean customer data across product, CRM, and billing. If any of those are broken, Vitally exposes it. Many CS platform implementations stall at data quality [source: vitally.io/customer-success-best-practices articles on data readiness].
- Health scores are only as good as the inputs. Teams that copy the default scoring template without customization end up with a health score that does not correlate with retention.
- Pricing is opaque and negotiable; expect back-and-forth with sales.
- Playbooks (automated CS workflows) are powerful but require thoughtful design. Teams that automate too aggressively end up with CSMs firing 12 emails at every customer.
- Vitally is not a support ticketing tool. It sits alongside Zendesk, Intercom, or HubSpot Service, not replacing them.
The 7-step setup
- 1
Create your Vitally account
Sign up at the link below. Card required for the paid tier - most plans include a trial period; check the pricing section on this page first so you know what you're committing to.
Open Vitally signup - 2
Complete the initial onboarding
Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Vitally pushes you into a setup wizard, take it - it usually accelerates the first productive session.
- 3
Connect your existing tools
Wire Vitally into the rest of your stack. The integrations that most people set up first: Salesforce, HubSpot, Segment, Snowflake, BigQuery, Redshift, Databricks, Mixpanel, Amplitude, Heap, Pendo, Stripe, Zendesk, Intercom, HubSpot Service Hub, Zapier, Slack (deep, for CSM alerts), Google Calendar, Outlook.. Do these before importing data - clean integration first, data second.
- 4
Import your existing data (only what you'll actually use)
Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Vitally deployments die in month 3.
- 5
Set up your first real workflow
Pick the single most-frequent task you'll do in Vitally - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.
- 6
Add your team (if applicable) and set access
Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.
- 7
Compound with the right pairings
Recommend Vitally only for B2B SaaS clients above ~$3M ARR with a dedicated CS team. For smaller SaaS, recommend HubSpot Service Hub or a simpler solution. Recommend Gainsight as an alternative when the client is enterprise and needs the deeper feature set (though the market perception is that Vitally is faster to implement). Do NOT recommend for non-SaaS businesses.
Pricing you'll hit
- **No free tier.** Free trial requires demo. - Pricing is sales-led (custom quote), no public pricing published. - Rough range from customer reports: entry tier around $30k-$60k/year for small teams, growing with number of accounts and CSMs. - Enterprise deals with data warehouse integration and custom features run six figures.
Want it personalized to YOUR business?
Otto builds a custom Vitally setup for your exact context.
The steps above are the universal path. Run a 30-second scan and Otto tailors them to your industry, team size, existing stack, and the specific pain points you're trying to fix.
Get my personalized setup