ICP and Segmentation
Discipline: every rep must know which tier they are talking to within the first 30 seconds of a call. Mis-tiering leads to wrong demo, wrong price, wrong close-plan.
1. The 6-segment grid
DEAL SIZE →
LOW (<₹3L) MID (₹3-15L) HIGH (>₹15L)
┌──────────────┬──────────────────┬─────────────────────┐
COMPLEX │ │ │ │
ORG │ │ T3: 4★/Boutique│ T4: 4★/5★ Chains │
(branded, │ │ 30-100 keys │ 200+ keys, multi │
multi-prop) │ │ │ property │
├──────────────┼──────────────────┼─────────────────────┤
SIMPLE │ T1: PLG │ T2: 3★/Mid │ │
ORG │ Homestay, │ 50-150 keys │ T5: Resort Chains │
(owner-op, │ PG, 1-2 │ single-prop or │ (40-150 keys │
single-prop) │ outlet F&B │ 2-3 properties │ each, multi-prop) │
│ │ │ │
├──────────────┼──────────────────┼─────────────────────┤
F&B FOCUS │ │ T6: Resto │ │
│ │ chains (2-10 │ │
│ │ outlets, QSR/ │ │
│ │ casual dining) │ │
└──────────────┴──────────────────┴─────────────────────┘
| Tier | Description | Size | Motion | Avg ACV |
|---|---|---|---|---|
| T1 — PLG | Homestay, AirBnB, small PG, 1-outlet F&B | <25 keys/beds | Self-serve, free trial | ₹30-50k |
| T2 — SMB hotel | 3★ / boutique, 50-150 keys, 1-3 properties | 50-150 keys | Inside sales | ₹6-12 lakh |
| T3 — Mid-market hotel | 4★ / branded boutique, 30-100 keys | 30-100 keys | Inside + AE | ₹10-18 lakh |
| T4 — Enterprise chain | 4-5★, 200+ keys total, multi-property | 200+ keys | Direct AE | ₹35-90 lakh |
| T5 — Resort chain | Multi-property resort group, banquet/spa/F&B heavy | 40-150 keys each | Direct AE | ₹40-120 lakh |
| T6 — Restaurant chain | 2-10 outlets, QSR / casual / fine-dining | 2-10 outlets | Inside + AE | ₹8-25 lakh |
2. T1 — Homestay / PG / Small F&B (PLG tier)
Firmographics
- Size: 1-25 keys (homestays), 1-30 beds (PGs), 1 outlet (F&B)
- Revenue: ₹20 lakh - ₹2 Cr / yr
- Locations: anywhere; heavy in Goa, Kerala, Himachal, Uttarakhand, hill stations, Tier-2 cities
- Owner profile: solo entrepreneur, frequently 30-45 yrs old, tech-comfortable, runs everything from phone
Pain points
- Manages bookings across MakeMyTrip + Airbnb + Booking.com + direct WhatsApp
- Double bookings on OTAs are a real problem
- Accounts/GST is "do it monthly with my CA"
- No view of profitability per channel
Why they buy KeyNova
- ₹2,499/mo all-inclusive — no procurement, just sign up
- Mobile-first — runs the business from phone
- Channel manager pays for itself in 1 prevented double booking
- WhatsApp guest messaging built in
Decision criteria (in order)
- Price
- Ease of setup (must be under 30 min)
- Channel manager (MakeMyTrip, Booking.com)
- Reviews from peers (Facebook host groups)
- Payment processing (UPI/Razorpay)
Where to find them
- Facebook host groups (e.g., "AirBnB Hosts India", "Goa Homestay Owners")
- WhatsApp groups via referrals
- YouTube tutorial discovery (we make tutorials, we appear)
- Instagram (small-business owner content)
- Listings on MakeMyTrip / Booking.com (paid leads from those platforms' partner programs)
Disqualify if
- Looking for property-management as a service (we're software, not management)
- Want commission model (we are flat-fee SaaS)
- Need offline mode as primary use-case (we are cloud-first)
3. T2 — SMB Hotel (3★ / boutique, 50-150 keys)
Firmographics
- Size: 50-150 keys, often 1 property, sometimes 2-3 under same owner
- Revenue: ₹3 Cr - ₹25 Cr / yr
- Locations: Tier-1 + Tier-2 cities; tourism circuits; pilgrimage towns
- Owner profile: family-owned, second-generation, often MBA-educated
Pain points
- Running 3-5 separate vendors (PMS + POS + channel + payment gateway + accounting)
- Reconciliation eats 15-25 hours/wk of accounts team
- Owner has no real-time visibility — gets reports next morning
- Staff turnover means re-training on 4 different systems
- GST e-invoice not happening because legacy PMS doesn't support IRN
Why they buy KeyNova
- "One throat to choke" — single vendor
- Hindi UI for housekeeping/F&B staff
- e-invoice + GSTIN validation built in
- Razorpay/UPI native — lower MDR than legacy gateway
Decision criteria
- Total cost of ownership (vs current 4-5 vendors)
- Compliance (GST, DPDPA) — increasingly important
- Implementation timeline (must go live within 4 weeks)
- References from similar properties
- Local support availability
Decision-making unit (DMU)
- Owner / MD — economic buyer, final say
- GM — daily user, must champion
- Accounts head — kills deals over reconciliation
- IT head / IT vendor — integration objections
Where to find them
- FHRAI events (every state chapter has 200-500 members)
- Hotelivate / HVS webinars
- LinkedIn (owner + GM both active)
- Trade publications: Hotelier India, Express Hospitality
- Hardware vendor referrals (Star Micronics, Posiflex etc.)
- Consultant referrals (Hotelivate, Noesis)
Disqualify if
- Less than 30 keys (push to T1)
- Already on Opera / Protel (Y2 target — too sticky)
- Looking for free trial (this tier closes via demo + POC)
4. T3 — Mid-market hotel (4★ / branded boutique, 30-100 keys)
Firmographics
- Size: 30-100 keys, branded 4★, often part of mini-chains (2-5 properties)
- Revenue: ₹10 Cr - ₹50 Cr / yr
- Locations: Tier-1 metros + leisure destinations (Goa, Udaipur, Jaipur, Coorg)
- Owner/Operator: professional management; may have separate ownership + operator
Pain points
- Strict brand SOPs vs. PMS limitations (e.g., loyalty program tracking)
- Revenue management is manual / spreadsheet-based
- Need for chain-level reporting; current PMS is property-only
- High-net-worth guest CRM with stay history is poor
- F&B + banquet contributing 30-50% revenue, needs integration
Why they buy KeyNova
- Modern UX matches their brand standards
- Multi-property tenant model — chain-level analytics
- Revenue Strategy module (Phase 1)
- Banquet + F&B in same folio
- Branded receipt templates customisable
Decision criteria
- Brand alignment (UI, receipts, guest-facing screens)
- Multi-property reporting
- Revenue management capability
- Integration with hardware (door locks, IPTV, key cards)
- API openness for custom integrations
DMU
- MD / Owner — strategic
- VP Operations — typical economic buyer
- GM of pilot property — champion
- Director of Revenue — heavy demand on RM module
- IT — integration sign-off
Where to find them
- HSMAI / HEDNA events
- Hotelivate Investor Conferences
- Direct enterprise outreach via LinkedIn Sales Nav
- Tier-1 conferences: HICSA, FHRAI Convention
- Strategic consultant relationships
Disqualify if
- On Opera/Protel and < 12 months from contract renewal (re-engage at 9 months pre-renewal)
- Looking for white-label
5. T4 — Enterprise hotel chain (4-5★, 200+ keys, multi-property)
Firmographics
- Size: 5+ properties, 1,000+ total keys
- Revenue: ₹100 Cr+ / yr
- Examples: Lemon Tree, Sarovar, Royal Orchid, Pride, Cygnett, Justa, FabHotels, Treebo
- Locations: Pan-India
Pain points
- Stuck on Opera/Protel for 5★ flagships, mixed-stack on rest
- Brand SOP rollout takes 6+ months across properties
- Revenue management is fragmented across properties
- M&A integration of acquired properties takes 12-18 months on legacy
- DPDPA compliance is a fire-drill on legacy stack
Why they buy KeyNova
- Cloud = same-day rollout of policy changes across all properties
- Open API = integrates with their existing data lake
- DPDPA-native saves them an ₹X Cr compliance program
- ₹/key/month TCO is 30-40% lower than legacy
Decision criteria
- Reference customers in same tier
- SLA + 24×7 support
- Multi-region availability + DR plan
- Open API + integration ecosystem
- Migration path from legacy
- Roadmap commitments (AI, analytics)
- Total cost of ownership over 5 years
DMU (large — 7-12 stakeholders)
- CEO / MD — strategic sponsor
- COO — operations VP
- CFO — financial
- CIO / CTO — technical
- VP Operations — daily user
- Director of Revenue — RM module
- Brand / Marketing VP — guest-facing surfaces
- Procurement / Legal — contract
- Property GMs (sample 2-3) — pilot champions
Sales motion
- Named account program, 1 AE owns ≤25 accounts
- Engagement starts with executive briefing (CEO ↔ CEO if needed)
- Discovery 4-6 weeks, including site visits
- Pilot at one flagship property, 8-12 weeks
- Rollout 6-18 months across chain
Disqualify if
- Public-sector (government hotels) — different procurement reality
- Currently in middle of M&A — defer 6 months
6. T5 — Resort chains (40-150 keys each, multi-property)
Firmographics
- Examples: Sterling Holidays, Club Mahindra, Niraamaya, Evolve Back, Postcard, Della
- Revenue: ₹50 Cr - ₹500 Cr / yr
- Locations: Hill stations, beaches, wildlife circuits, wellness destinations
What's different from T4
- Banquet + spa + F&B is 40-60% of revenue (vs 25-35% in city hotels)
- Group bookings + corporate retreats
- Loyalty / membership model often present (Club Mahindra-style)
- Activities + experiences ancillary revenue
- Seasonal inventory/rate management
Why they buy KeyNova
- Banquet + spa + F&B unified with rooms
- Group booking + event PNR module
- Multi-property loyalty
- AI revenue strategist for seasonal demand
- Mobile app for guest in-stay (room service, activity booking)
Special considerations
- Connectivity in remote properties — needs offline reconciliation
- Hardware bundle (door locks, key cards) often part of deal
- Procurement is owner-led (founder still active in most cases)
7. T6 — Restaurant chain (POS, 2-10 outlets)
Firmographics
- Size: 2-10 outlets, QSR / casual dining / fine dining / cloud kitchen
- Revenue: ₹2 Cr - ₹50 Cr / yr
- Examples: Local 2-5 outlet players in every metro
- Owner profile: chef-owner OR business-owner
Pain points
- Disconnected POS at each outlet — no central inventory
- Zomato/Swiggy orders come in separately; staff retypes into POS
- No real-time view of food cost / wastage
- GST e-invoice in restaurants is just emerging
- Loyalty / repeat-customer data is poor
Why they buy KeyNova POS
- KDS app on tablet/TV
- Zomato + Swiggy aggregator orders into same KDS
- Recipe-costing + ingredient-level inventory (Phase 2 module, in roadmap)
- GST e-invoice + IRN
- Multi-outlet inventory consolidation
Decision criteria
- POS speed at peak hours (< 3 sec per transaction)
- Aggregator integration
- Offline mode (internet drops kill restaurants)
- Hardware compatibility (existing printers, KDS)
- Loyalty / CRM
- Price (most price-sensitive of the tiers)
DMU
- Owner — economic buyer, usually decision in 2-3 meetings
- Operations head — daily user
- Chef (for KDS workflows)
- Accountant (GST, reconciliation)
Where to find them
- NRAI events + Food Forum
- Sourcing Hardware Expo (every metro hosts one annually)
- Zomato Restaurant Partner events
- Cloud Kitchen Festival (Bangalore, Mumbai)
- Direct LinkedIn outreach to owners
8. Account scoring — the rep's checklist
Every prospect gets a score before a rep agrees to demo. The score determines which tier they go in and what motion runs.
Tier match — 30 pts
T1 — 5 pts (PLG self-serve)
T2 — 25 pts (sweet spot)
T3 — 30 pts (sweet spot)
T4 — 20 pts (longer cycle)
T5 — 25 pts
T6 — 20 pts
Budget signal — 20 pts
Discussed budget — 20
Mentioned existing spend on PMS/POS — 15
No signal — 5
Timing — 20 pts
Renewal in 0-3 months — 20
Renewal in 3-6 months — 15
Greenfield property opening — 18
No event — 5
Compliance pressure — 15 pts
Mentioned e-invoice / DPDPA — 15
Cert-In incident in past — 12
Audit failure — 10
No signal — 0
Champion identified — 15 pts
GM/owner directly engaged — 15
Mid-mgmt engaged — 8
Only IT engaged — 4
| Score | Action |
|---|---|
| 80+ | Priority demo within 48h, AE assigned |
| 60-79 | Demo within 1 week, ISR/AE |
| 40-59 | Send nurture content, re-qualify in 30d |
| <40 | Drop to marketing nurture / disqualify |
9. Out-of-scope (do not pursue, for now)
| Segment | Why excluded | Re-visit |
|---|---|---|
| Hostels (backpacker) | Too price-sensitive, low ARPU | Year 3 |
| Cruise / houseboat | Niche, hardware-heavy | Year 3 |
| Service apartments (long-stay corporate) | Different DMU, niche | Year 2 |
| Hospitals / clinics (hospitality stays) | Wrong vertical | Never |
| Govt-owned hotels (ITDC, state tourism) | Procurement nightmare | Year 3+ |
| Catering-only (no outlet) | Wrong product fit | Never |
Last reviewed: 2026-05-16