Customer Success — Onboarding, Retention, Expansion

Premise: the customer's first 90 days predict the next 10 years. We over-invest in onboarding because churn is fatal to SaaS unit economics in Indian hospitality (structural ~25% baseline). NRR ≥ 115% is the primary success metric.

1. Customer journey overview

                Sales close → CS handoff (Day 0)
                              │
                              ▼
                ┌─────────────────────────────┐
                │ ONBOARDING (Days 1-30)       │
                │  • Kickoff                   │
                │  • Configuration             │
                │  • Migration                 │
                │  • Training                  │
                │  • Go-live                   │
                └─────────────────────────────┘
                              │
                              ▼
                ┌─────────────────────────────┐
                │ STABILIZATION (Days 31-90)   │
                │  • Hyper-care                │
                │  • Adoption metrics          │
                │  • Issue burn-down           │
                │  • First QBR                 │
                └─────────────────────────────┘
                              │
                              ▼
                ┌─────────────────────────────┐
                │ EXPANSION (Days 91-365)      │
                │  • Module activation         │
                │  • Multi-property rollout    │
                │  • Cross-sell add-ons        │
                │  • Reference + case study    │
                └─────────────────────────────┘
                              │
                              ▼
                ┌─────────────────────────────┐
                │ RENEWAL + GROWTH (Year 2+)   │
                │  • Annual renewal            │
                │  • Pricing escalation        │
                │  • Multi-year locks          │
                │  • Advocacy                  │
                └─────────────────────────────┘

2. CS team structure

Role	EoFY26	EoFY27	Notes
VP Customer Success	1	1	hire by Q2 FY26
CSM — Enterprise (T4/T5)	2	6	1 CSM per 10 enterprise accounts
CSM — Mid-Market (T3)	2	8	1 CSM per 25 accounts
CSM — SMB (T2)	4	14	1 CSM per 50 accounts
CS Specialist — PLG (T1)	1	4	tech-touch + self-serve
Implementation Manager	4	12	drives first 90 days
Training Lead	1	2	builds + delivers training
Support Engineer (Tier 2)	2	8	escalations from L1
Support Engineer (L1)	4	14	24×7 (rotating shifts)
Total	21	69

Coverage model

Tier	Coverage
T1 PLG	Tech-touch (in-app + automated) + scheduled office hours
T2 SMB	1:50 ratio CSM; quarterly check-ins
T3 Mid	1:25 ratio CSM; monthly check-ins
T4 Enterprise	1:10 ratio CSM; bi-weekly check-ins
T5 Resort chains	1:10 ratio CSM + Implementation Manager attached

3. Onboarding playbook (Days 1-30)

Sales-to-CS handoff (Day 0)

Mandatory artifacts from Sales:

Signed contract + SOW
Decision criteria (the "why we won" doc)
Champion contact + relationship notes
Stakeholder map (DMU)
Pain points + success metrics agreed
Custom requirements / integrations needed
Implementation tier (Pro/Business/Enterprise)

Handoff meeting (60 min):

Sales walks CS through the customer story
CS confirms understanding
Joint customer kickoff date scheduled
VP Sales + VP CS both attend for T4/T5

Kickoff call (Day 1-3)

Attendees: customer DMU + KeyNova CSM + Implementation Manager + technical lead

Agenda (90 min):

Re-confirm scope, timeline, success metrics
Introduce KeyNova team + roles
Walk through implementation plan
Establish communication cadence (slack channel for enterprise, weekly call for mid+)
Define escalation path
Set first milestone (config complete)

Configuration phase (Days 1-14)

Customer responsibilities:

Provide property data (rooms, rates, OTAs, hardware list)
Provide branding (logo, colours)
Provide staff list + roles
Provide existing GST + bank details

KeyNova responsibilities:

Tenant + property setup
Module activation (per SOW)
OTA channel mapping
Hardware integration setup (with vendor)
Custom branding (receipts, booking engine)
User provisioning

Migration phase (Days 7-21, parallel)

Source vendors with prebuilt migration:

eZee Absolute
Hotelogix
IDS FortuneNEXT (Cloud only; on-prem needs manual extract)
Djubo / Mews
Cloudbeds
Tally + Excel (for properties without PMS)

Migration scope:

Active reservations (next 90 days)
Historical reservations (1-year mandatory, 3-year optional)
Guest profiles + history
Folios + payments
Rates + OTA mappings
Inventory + rate plans
POS menu + recipes (F&B)
Channel manager settings

Migration QA:

Day 14: parallel-run begins (both systems live for 30 days)
Day 21: reconciliation report (must match ±0.5% on key metrics)
Day 28: cutover decision (customer signs off)

Training phase (Days 15-25)

Role-based modules:

Role	Hours	Mode
Front-desk	6	classroom + practice
Housekeeping	3	mobile-app-led, on-floor
F&B / POS	4	hands-on at POS terminal
Reservations	4	classroom + practice
Accounts	4	classroom
Manager / supervisor	3	classroom
Owner / GM	2	self-paced + 1:1

Mode:

T1/T2 PLG: Videos + in-app guides + monthly office hours
T3/T4: On-site trainer for 2 days + virtual reinforcement for 3 weeks

Go-live (Days 22-30)

Pilot go-live (Day 22):

Single shift, one role function
KeyNova engineer on standby
Daily checkpoint at shift end

Full go-live (Day 28):

All roles + shifts live
24×7 hyper-care for 3 days
Founder hotline active for T4/T5

Decommission of old PMS (Day 30):

Customer signs cutover acceptance
Old vendor contracts paused/cancelled (customer-managed)
Data archive of old system retained

4. Hyper-care phase (Days 31-90)

Cadence:

Daily check-in calls (15 min) for first 14 days
Weekly check-in for next 6 weeks
Bi-weekly thereafter through Day 90

Health monitoring (daily):

Login activity (target: 80%+ of users active)
Module usage (target: 5+ modules engaged)
Error rates (target: < 0.1%)
Open tickets (target: < 3 P1/P2 open at any time)
Daily reconciliation matching (target: 100% match)

Triggered interventions:

Login drop > 30% week-over-week → CSM intervention call
3+ tickets in 24h → engineering deep-dive
Module abandonment (used week 1, not used week 4) → re-training

Day 30 review

Customer NPS captured (target: ≥ +40)
Open ticket review
Adoption metrics review
Adjust trajectory if needed

Day 60 review

Customer NPS again (target: ≥ +50)
First QBR scheduled
Identify expansion opportunities (modules not activated)
Reference-eligibility flag set

Day 90 review (graduation)

Customer NPS (target: ≥ +55)
Hyper-care handoff to standard CS cadence
Joint case-study commitment if customer agrees
Reference customer agreement (if applicable)

5. Adoption playbook

Adoption metrics that matter

Metric	Definition	Target
Daily Active Users (DAU)	Unique users / week / property	90%+ of provisioned users
Module activation	% of contracted modules used	90%+ within 90 days
Feature depth	Avg features used per module	70%+ of available
Mobile adoption	% of users on mobile app	60%+ for GM/owner
Reports generated	Per week	3+
OTA sync health	Last sync time per channel	< 5 min lag

Adoption nudges

In-app prompts when a feature isn't used
Weekly digest email with "things you haven't tried"
Customer-success-led monthly mini-trainings
"Power user" badges on dashboard (gamification, lightly)
Quarterly "feature of the quarter" campaign

Adoption rescue

When adoption drops below target:

CSM books a "review meeting" with champion
Identifies the blocker (training, technical, organizational)
Documents action plan with owner + date
Re-measures at 30-day re-check

6. Retention playbook

Renewal cadence (T2-T5)

Day -180 (6 months before renewal): business review + expansion discussion
Day -120: renewal forecast in CRM
Day -90: renewal proposal drafted with pricing
Day -60: champion + economic buyer review
Day -45: legal redlines exchanged
Day -30: signature
Day -7: renewal in hand

Renewal probability scoring

Each customer gets a "Health Score" updated weekly:

Factor	Weight	Source
Module usage	25%	product analytics
Login activity	15%	product analytics
Support tickets (volume + sentiment)	20%	support system
NPS score	15%	survey
CSM relationship quality	10%	CSM input
Champion stability (still in role)	10%	CSM input
Payment history (on-time)	5%	finance

Composite score → renewal forecast:

Healthy (≥ 75): renewal expected, expansion possible
At-risk (50-74): renewal likely but needs intervention
Critical (< 50): churn-risk, escalate to VP CS

Churn risk indicators

Champion leaves
Login activity drops 40%+ for 3 consecutive weeks
NPS score < 0 ever
3+ P1 tickets unresolved beyond SLA
Late payments (2+)
Multi-property customer pauses one property
Champion mentions evaluating alternatives

Any single indicator triggers automatic CSM intervention + manager review.

Save plays

Risk source	Save play
Pricing pressure	VP CS engages with custom retention offer (≤ 20% discount, capped 1 year)
Champion departure	Re-onboard new champion; founder intro for T4+
Product gap	Roadmap commitment letter with date; engineering attention
Service quality	Dedicated support pod; CEO apology call for T4+
M&A / restructure	Pause + bridge contract option
Genuine bad fit	Honest conversation; manage exit gracefully, refer competitor if needed

Annual price escalation

Default 8% YoY for SMB
Default 6% YoY for Mid-Market (Business tier)
CPI + 3% formula option for Enterprise (T4/T5)
Always discussed during 6-month renewal cycle, never sprung

7. Expansion playbook

Expansion paths

Type	Description	Avg uplift
Module activation	Customer turns on un-activated module (RM, banquet, etc.)	+15-30% ACV
Multi-property rollout	Customer adds properties to existing contract	+80-200% ACV
Tier upgrade	Pro → Business → Enterprise	+35-60% ACV
Add-ons	Premium support, dedicated CSM, custom integration	+5-20% ACV
Multi-year prepay	Convert to 2-3 year deal with bonus discount + locking	revenue stability

Expansion triggers

90-day successful go-live → "expand to property #2"
New property opening announcement → "open with KeyNova" program
Champion promotion → larger budget access
Industry peer success story → desire to match
New regulation (e.g., DPDPA enforcement) → compliance-driven expansion
Quarterly QBR identifies module fit

Cross-sell discipline

CSM owns the relationship; AE owns the deal
Cross-sell deals routed through original AE (or assigned successor)
CSM cannot quote price; routes to AE for proposals
50/50 comp split on expansion deals (CSM gets retention credit, AE gets new-revenue commission)

8. Support tiers

L1 Support (24×7)

Tickets via portal, email, WhatsApp (T1/T2)
SLA: First response ≤ 1 hour P0, ≤ 4 hours P1, ≤ 24 hours P2/P3
Resolution SLA: P0 ≤ 4h, P1 ≤ 24h, P2 ≤ 5d, P3 ≤ 30d
Hindi, Tamil, Telugu support staff (rotating)

L2 Support (engineering)

Escalation from L1 within ticket SLA
Bug fixes, deep technical
~20% of tickets escalate

L3 Support (specific engineers)

Architect-level escalation
< 2% of tickets reach L3
White-glove for T4/T5

Premium Support (paid add-on)

₹10k/mo/property
Dedicated support pod (named engineers)
SLA: First response ≤ 15 min P0/P1
Direct WhatsApp line to support lead
Quarterly health-check report

24×7 Founder Hotline (Day 1-30 for all customers)

WhatsApp number to founder + VP CS
Used for anything not resolved by standard support within SLA
Auto-disabled at Day 31

9. Customer feedback loops

NPS (quarterly)

Trigger: 30, 60, 90 days post-go-live, then quarterly
Tool: Delighted
Target: +50 by Day 90
Follow-up: every detractor (-10 to 0 score) gets a CSM call within 24h

Customer Advisory Board (CAB)

12 members across tiers (3 per tier × 4 tiers)
Quarterly meetings, 4-hour video + dinner
Annual offsite (2 days)
Outputs: roadmap influence, advocacy, peer connections
Honorarium: ₹50k KeyNova credit/year

Product feedback queue

Customers submit feature requests via in-app form
Product team triages weekly
Top-voted requests get public roadmap commit
Customer notified when their request ships

Customer health survey (annual)

30-question deep-dive
Categories: product, support, CSM, value, advocacy
Used for annual planning + retention forecasting

10. Customer advocacy program

Tiers of advocacy

Tier	Activity	Recognition
Reference customer	Willing to take 2-3 reference calls/year	₹25k credit/yr
Case study customer	Published case study	Premium credit + PR
Awards customer	Named in KeyNova Awards	Trophy + ₹2L credit
CAB member	Quarterly meetings	Credits + influence
Speaker	Speaks at KeyNova events	Travel + honorarium
Press references	Quoted in tier-1 press	Personal brand boost

Reference call mechanics

Customer commits to take 2-3 calls / year
CSM coordinates schedule + scope
KeyNova prep call before each
Customer credited with ₹25k/yr in advance

Logos and case studies

Logo permission: granted in initial contract (opt-out option)
Case study: separate agreement, mutual review of final
Press quotes: explicit per-quote permission
Customer Logo Wall on website + at all events

11. Onboarding playbook variants by tier

T1 (PLG) onboarding

Fully self-serve
14-day free trial
In-app guided tour
Lifecycle email + WhatsApp prompts
Day 3: "import your first reservation"
Day 7: "connect channel manager"
Day 12: "switch to paid"
Office hours (weekly Zoom open to all trial users)
Specialist available via chat if stuck

T6 (F&B) onboarding

POS-led implementation (1 outlet first)
Hardware verification + setup
Menu + recipe + KOT/KDS configuration
Staff training (1 day per outlet)
Pilot service shift (with KeyNova engineer)
Aggregator integration (Zomato/Swiggy)
Compress timeline: 7-14 days per outlet

PG / Coliving onboarding

Bed-level inventory setup
Recurring billing config (UPI mandate)
KYC workflow (Aadhaar masking)
Tenant agreement template config
Maintenance + asset workflow
Compress timeline: 7-10 days per property

12. CS KPIs

Customer-facing KPIs

KPI	Year 1 target	Year 2 target
Customer NPS (30-day post-go-live)	+45	+55
Customer NPS (annual)	+40	+55
First-month adoption (DAU%)	85%	90%
Time to value (first reservation imported)	< 24h (PLG), < 72h (others)	same
CSAT on support	≥ 4.4/5	≥ 4.6/5
Average ticket resolution time	< 24h (P2-P3)	same

Business KPIs (the ones the CFO watches)

KPI	Year 1 target	Year 2 target
Gross Revenue Retention (GRR)	≥ 92%	≥ 94%
Net Revenue Retention (NRR)	≥ 108%	≥ 115%
Logo churn rate	≤ 12%	≤ 8%
Revenue churn rate	≤ 8%	≤ 6%
Expansion ARR as % of ARR	10%	20%
Reference-able customers	≥ 20% of base	≥ 30% of base
Time to first expansion	< 12 months	< 9 months

13. Operating cadence

Cadence	Meeting	Owner
Daily	At-risk review (10 min)	VP CS
Weekly	CSM pod stand-up	Director of CS
Weekly	Top 10 customer review with VP CS + CRO	VP CS
Bi-weekly	Hyper-care progress	Implementation lead
Monthly	Health-score dashboard	VP CS
Monthly	Customer marketing review	Customer Marketing
Quarterly	CAB	VP CS
Quarterly	Renewal forecast	VP CS + CRO + CFO
Annual	Customer health survey	VP CS

14. Tech stack

CRM: Salesforce Service Cloud + Sales Cloud
Support: Zendesk / Freshworks (TBD by VP CS)
Product analytics: Mixpanel / Amplitude
In-app guidance: Pendo
NPS: Delighted
Knowledge base: Notion (public) + internal docs
Status page: Statuspage.io at status.keynova.ai
Communication: WhatsApp Business API + email + Slack Connect (Enterprise)
Health scoring: custom dashboard built on Salesforce data

15. Anti-patterns we avoid

CSM as glorified account manager — they own outcomes, not just relationships
Pure proactive cadence — every meeting should produce a customer outcome
Hiding bad news — escalate fast; founders prefer hearing it from CS than from the customer
Selling during CS calls — cross-sell is structured separately; CS calls are about success
Renewal as a surprise event — renewal motion starts 180 days out, never panic-mode
Letting champions leave silently — flag champion departures immediately
Heroic individual customer rescues — they don't scale; build patterns

Last reviewed: 2026-05-16 — needs VP CS hire + product analytics tooling

1. Customer journey overview​

2. CS team structure​

Coverage model​

3. Onboarding playbook (Days 1-30)​

Sales-to-CS handoff (Day 0)​

Kickoff call (Day 1-3)​

Configuration phase (Days 1-14)​

Migration phase (Days 7-21, parallel)​

Training phase (Days 15-25)​

Go-live (Days 22-30)​

4. Hyper-care phase (Days 31-90)​

Day 30 review​

Day 60 review​

Day 90 review (graduation)​

5. Adoption playbook​

Adoption metrics that matter​

Adoption nudges​

Adoption rescue​

6. Retention playbook​

Renewal cadence (T2-T5)​

Renewal probability scoring​

Churn risk indicators​

Save plays​

Annual price escalation​

7. Expansion playbook​

Expansion paths​

Expansion triggers​

Cross-sell discipline​

8. Support tiers​

L1 Support (24×7)​

L2 Support (engineering)​

L3 Support (specific engineers)​

Premium Support (paid add-on)​

24×7 Founder Hotline (Day 1-30 for all customers)​

9. Customer feedback loops​

NPS (quarterly)​

Customer Advisory Board (CAB)​

Product feedback queue​

Customer health survey (annual)​

10. Customer advocacy program​

Tiers of advocacy​

Reference call mechanics​

Logos and case studies​

11. Onboarding playbook variants by tier​

T1 (PLG) onboarding​

T6 (F&B) onboarding​

PG / Coliving onboarding​

12. CS KPIs​

Customer-facing KPIs​

Business KPIs (the ones the CFO watches)​

13. Operating cadence​

14. Tech stack​

15. Anti-patterns we avoid​