Single source of truth: STRATEGY-CANON.html (esp. §6 model, §8 roadmap canon, §9 Embassy). All figures here are either sourced in /00-intelligence/ or flagged [USER INPUT]. No fabricated targets. KPIs are driver-based or qualitative. May 2026.
How to read this roadmap
Three phases, eight workstreams, one moat. The moat — captive enterprise demand pre-let into owned/operated keys — is not a phase; it is the thing every phase must protect and compound. The sequencing is deliberate: demand is contracted before doors open (Phase 1 proves it), the playbook is templated before it is multiplied (Phase 2), and the intelligence layer matures from feature to platform (Phase 3 monetizes it). The strategic clock is set externally by Ascott — the one incumbent holding both halves of the thesis (scale operator + co-owner of the SilverDoor/Synergy aggregator). Speed and lock-in are the defense (Canon §5, Competitive §9).
The single non-negotiable across all phases: capex sits with the developer. The developer brings land + building + construction capital; Nest.IQ brings brand, operations, technology, and demand. This converts hotel-style capex/payback risk (7–10 yr payback, ROI ~10–15%, Canon §6) into a fee/operating-margin business — the structural risk-transfer that protects the model.
Phase 1 — Foundation (0–12 months)
Bengaluru pilot · 50–80 keys · prove the moat in one city
| Workstream | What happens in Phase 1 |
|---|---|
| JV & legal | Finalize the Embassy JV (Prestige as backup, Canon §1). Structure — operating-agreement vs revenue-share-with-minimum-guarantee vs SPV — is a [management decision / USER INPUT]; propose familiar Embassy-style terms (≈20-yr operating agreement; base fee + GOP-weighted incentive; optional rev-share + minimum guarantee — Canon §9). Land treatment in the JV is [USER INPUT] (Canon §7). Execute brand-licensing and management agreements; stand up the JV entity and governance. |
| Real estate & fit-out | Site selection in Bengaluru's highest-demand GCC clusters: ORR / Embassy Tech Village / Whitefield (Canon §8). Capex borne by the developer. Nest.IQ owns product brief, design standard, fit-out spec, and FF&E to one brand standard. Sanity-anchor capex/key against ~₹1.3–1.4cr (escalated upscale proxy, Canon §6) — actual per-city/tier capex is [USER INPUT]. |
| Brand & marketing | Launch Nest.IQ publicly. Build the hand-crafted, anti-template site on /02-brand/tokens.css (light editorial luxury — warm porcelain + ink, with clay / teal / gold / indigo accents; Canon §2; never Gamma). PR is category creation — "intelligent, mobility-led corporate residences" — not a property opening. Lead with the wedge line: "Everyone can build the building. Only Nest.IQ arrives with the tenants." |
| Enterprise sales & occupancy | The moat in action: pre-let enterprise contracts BEFORE launch. Convert IKAN's 1,000+ corporate clients / 50,000+ assignments into signed/LOI'd occupancy for the Bengaluru keys (Canon §1, §3). Wire RMC / aggregator channels (SilverDoor/Synergy, AltoVita, Dwellworks, NCH) as future distribution (Competitive §5). Target a meaningful pre-let share of keys committed at handover [USER INPUT: % threshold]. |
| Operations & SOPs | Author the service standard and SOP library (housekeeping, F&B/ancillary, security, guest journey, the "whole arrival": home + immigration + relocation + concierge — Canon §2 pillar 4). Decide self-operate vs hospitality-management partner [USER INPUT]. Hire and train the pilot ops team to one consistent standard. |
| Technology / the .IQ layer | Ship the MVP intelligence stack: resident app (the in-home .IQ experience), demand-matching against the IKAN pipeline, and an ops/data spine. Instrument from day one so Phase-1 data trains Phase-2 matching. |
| People & org | Key hires: CEO/MD, Head of Operations, Head of Enterprise Sales (leverages IKAN relationships), Head of Brand/Marketing, founding Product/Tech lead. Lean leadership team; pilot ops staff. |
| Capital | Driver-based, no fabricated amount. Nest.IQ's capital need is operating/working-capital, brand, tech build, and team — NOT construction capex (developer-funded). Finance the working-capital drag of corporate receivables (45–90 days, Canon §6); use commercial security deposits (up to 6 months' rent) as a float source. Raise size and sources are [USER INPUT] (Canon §7). |
Phase-1 KPIs (driver-based): signed JV; keys under fit-out vs plan; pre-let coverage at handover; brand launch + PR reach (qualitative); SOPs published; .IQ MVP live; pilot occupancy ramp vs the 18–24 month stabilization curve (Bengaluru modelled below peers, ~65%, Canon §6).
Decision gates → Phase 2:
- JV executed and first keys delivered to standard.
- Pre-let proof: enterprise demand demonstrably fills keys ahead of/at opening (the moat validated, not asserted).
- Unit-economics signal: property-level performance tracking toward the JV's modelled fee/margin [USER INPUT targets] — no go-big until the single-city engine works.
- SOP +
.IQreplicability: playbook documented well enough to template.
Phase 2 — Expansion (12–36 months)
Hyderabad · Pune · Gurgaon · ~300–500 keys · multiply the playbook
| Workstream | What happens in Phase 2 |
|---|---|
| JV & legal | Extend the JV framework to new cities/sites. Decide single-developer-multi-city (deepen Embassy) vs multi-developer (add Prestige/others) — [USER INPUT]. Standardize JV term sheets so each new site is a repeatable contract, not a fresh negotiation. |
| Real estate & fit-out | Sites in the next GCC clusters: Hyderabad (HITEC City / Gachibowli), Pune (Hinjewadi / Kharadi), Gurgaon/NCR (Cyber City / Golf Course Ext). Hyderabad is the #2 GCC market (Bengaluru + Hyderabad >60% of GCC leasing, Canon §4). Capex developer-borne; Nest.IQ replicates the standardized product brief and fit-out kit for speed. |
| Brand & marketing | Shift from category creation to category leadership. Multi-city brand presence; case-study/PR engine off Phase-1 proof; deepen positioning as the premium enterprise/expat tier — complementary to Olive, not competitive (Canon §5, §9). |
| Enterprise sales & occupancy | Multi-city enterprise agreements — convert single-site clients into national/portfolio deals; pre-let each new city before opening (repeat the Phase-1 discipline). Activate aggregator channels as live distribution for owned keys, turning Nest.IQ from markup-reseller into preferred India supplier (Competitive §5, §8). |
| Operations & SOPs | Deploy the operating playbook city-by-city. Build the central ops function that enforces "one standard, every key" across geographies — the hardest scaling problem. QA/audit cadence; train-the-trainer to protect service consistency. |
| Technology / the .IQ layer | Scale demand-matching across cities; mature ops tooling; turn Phase-1 data into predictive occupancy/pricing signals. The .IQ layer becomes the cross-city control plane, not a per-property app. |
| People & org | Key hires: City/GM leads per city, Regional Ops Director, Revenue/Distribution lead, expanded Product/Data team, Finance/FP&A. Move from founder-led to function-led org. |
| Capital | Working capital scales with keys and receivables. If structures stay asset-light/fee-and-management (Canon §6), Nest.IQ's incremental capital is primarily team + tech + working-capital, not capex. Quantum and source are [USER INPUT]; the developer continues to carry construction capital per JV. |
Phase-2 KPIs (driver-based): new cities live vs plan; total keys vs ~300–500 band; per-city pre-let coverage; multi-city/portfolio enterprise contracts signed; cross-city service-consistency audit scores (qualitative/standard-based); aggregator channel volume on owned inventory; occupancy ramp per city vs stabilization curve.
Decision gates → Phase 3:
- Repeatability proven: ≥2 new cities performing to the templated playbook.
- Service consistency holds across geographies (the multi-city quality test).
- Channel flywheel live: aggregators reselling owned keys at improving margin.
.IQplatform-ready: data/tech demonstrably improving matching and occupancy — the basis for the Phase-3 proptech narrative.
Phase 3 — National Scale (36–60 months)
Mumbai · Chennai · NCR · Tier-2 GCC cities · 1,500+ keys · mature the platform
| Workstream | What happens in Phase 3 |
|---|---|
| JV & legal | Productize the JV model — a repeatable structure marketed to multiple developers nationally. Optional real-estate equity participation in JV assets is [USER INPUT] and matters for the valuation ceiling (Canon §7). |
| Real estate & fit-out | Complete the six-city footprint (add Mumbai, Chennai, full NCR) and enter Tier-2 GCC cities. Capex developer-borne. Mumbai/Chennai support higher ADR; model per-city (Canon §6). |
| Brand & marketing | National category-defining brand; international/RMC-facing positioning leveraging IKAN's 200+ cities. Brand becomes a demand magnet (lower CAC), reinforcing the captive-demand moat vs hospitality-led peers' 15–30% OTA/CAC drag (Canon §3). |
| Enterprise sales & occupancy | National master agreements; Nest.IQ as default India supplier across RMC + aggregator channels. Deepen the high-margin cross-sell wrap — relocation, immigration, destination services, concierge (IKAN ecosystem; attach-rate is a [USER INPUT / data gap], Canon §6). |
| Operations & SOPs | Operate at national scale with mature central ops, continuous QA, and a flagship service standard. SOPs are a competitive asset, not a document. |
| Technology / the .IQ layer | Platform/proptech layer matured (Canon §8): demand-matching, dynamic pricing, ops automation, resident experience, and a data product across the portfolio. This is the asset that could justify a proptech/SaaS valuation multiple beyond the hospitality base [USER INPUT thesis] (Canon §7, TAM §4.3). |
| People & org | Key hires: CxO bench (COO/CFO/CTO/CRO), national/regional leadership, platform/data-product org. Institutional, scalable org. |
| Capital | Capital supports national team, platform, and working capital. The asset-light/JV structure keeps Nest.IQ off the capex hook even at 1,500+ keys (Canon §6, Competitive §8). Any growth/strategic raise size and use are [USER INPUT]. |
Phase-3 KPIs (driver-based): total keys vs 1,500+; cities live incl. Tier-2; national enterprise/master agreements; cross-sell attach-rate (once measured — currently a flagged input); .IQ platform adoption and its measurable lift on occupancy/pricing; portfolio occupancy vs stabilized 78–82% upside band (Canon §6).
Valuation framing (narrative, not promise): defensible base US$150–300M on a hospitality multiple at 1,500–2,000 keys; US$500M only with a proptech/SaaS multiple or captured real-estate equity (Canon §7, TAM §4.3). Present as a ceiling, never a target.
Phase-gate criteria & dependencies
One matrix, the whole sequence: what must be true to enter a phase, what must be true to exit it (and earn the next), and the hard dependencies that gate the move. Hiring is tied to Business-Plan's org plan conceptually — each phase's exit assumes the next phase's leadership is in place before scale, not after. Every economic threshold is [USER INPUT]; no target is fabricated.
| Phase | Entry gate (to begin) | Exit gate (to advance) | Key dependencies |
|---|---|---|---|
| P1 — Foundation 0–12mo · BLR · 50–80 keys |
Embassy JV in active term-sheet; lead leadership (CEO/MD, Head of Ops, Head of Enterprise Sales) identified; IKAN demand book mapped to Bengaluru. | (1) JV executed + first keys to standard; (2) pre-let proof — enterprise demand fills keys at/ahead of opening [USER INPUT: % threshold]; (3) unit economics tracking to modelled fee/margin [USER INPUT]; (4) SOPs + .IQ MVP replicable. |
Signed Embassy JV (or Prestige backup); pre-let LOIs from IKAN's book; lead-team hires; authored SOP library; the .IQ MVP (resident app + demand-matching + ops spine); working-capital line for 45–90-day receivables. |
| P2 — Expansion 12–36mo · HYD/Pune/Gurgaon · ~300–500 keys |
All four P1 exit gates cleared; standardized JV term sheet drafted; per-city demand evidence before each fit-out completes. | (1) repeatability — ≥2 new cities to the templated playbook; (2) service consistency holds across geographies; (3) channel flywheel live — aggregators reselling owned keys at improving margin; (4) .IQ platform-ready (data demonstrably improving matching/occupancy). |
Repeatable JV template; per-city pre-let LOIs; function-led hires (City/GM leads, Regional Ops Director, Revenue/Distribution lead, Product/Data, Finance/FP&A); central ops QA/audit; aggregator onboarding complete; Phase-1 data corpus. |
| P3 — National scale 36–60mo · Mum/Chn/NCR/Tier-2 · 1,500+ keys |
All four P2 exit gates cleared; productized JV marketable to multiple developers; national demand pipeline across RMC + aggregator channels. | Scale & platform maturity: national footprint to plan; .IQ platform adoption with measurable occupancy/pricing lift; portfolio occupancy toward the 78–82% stabilized band; cross-sell attach-rate measured (currently a flagged input). |
Multi-developer JV demand; national/master enterprise agreements; CxO bench (COO/CFO/CTO/CRO) + platform/data-product org; matured .IQ platform; optional RE-equity decision [USER INPUT] for the valuation ceiling. |
Cross-phase dependencies
| Dependency | Why it gates the next move |
|---|---|
| IKAN demand pipeline → every phase | Pre-let occupancy is the moat. Each city's go-decision depends on demonstrable enterprise demand for that city before fit-out completes. |
| Embassy JV (Phase 1) → expansion template (Phase 2) | The first JV's structure and economics become the repeatable term sheet. A weak first deal poisons replication. |
SOPs + .IQ MVP (Phase 1) → multi-city rollout (Phase 2) |
You cannot template what isn't documented; you cannot scale matching on a model with no Phase-1 data to learn from. |
| Multi-city service consistency (Phase 2) → national scale (Phase 3) | "One standard, every key" must survive 4 cities before it survives 6+ and Tier-2. |
.IQ data accumulation (Phases 1–2) → platform/proptech layer (Phase 3) |
The valuation-upside tech thesis is earned only on accumulated portfolio data. |
| Working-capital financing (all phases) | Corporate receivables (45–90 days) scale with keys; deposit float partly offsets. Under-financing working capital stalls growth even with capex off-balance-sheet. |
| Speed vs Ascott (all phases) | Lock-in via JVs + enterprise contracts must outpace Ascott fusing its operator + aggregator halves (Competitive §9). |
Risk register
| # | Risk | Phase exposure | Mitigation |
|---|---|---|---|
| 1 | Occupancy ramp — stabilization slower than modelled (18–24mo base; 24–36mo downside; Bengaluru supply-heavy ~65%, Canon §6) | P1 acute; P2 per-city | Pre-let enterprise contracts before opening (the core mitigation); city-specific occupancy modelling [USER INPUT]; counter-cyclical extended-stay demand (+2.2% in 2025 vs −0.8% industry, Competitive §2). |
| 2 | Service consistency — quality drifts across cities/operators, eroding "one standard, every key" | P2/P3 acute | Codified SOPs + service standard from P1; central ops QA/audit cadence; train-the-trainer; self-operate-vs-partner decision [USER INPUT] made deliberately, not by default. |
| 3 | Capex / payback — hotel-style 7–10yr payback, ROI ~10–15% (Canon §6) | structural | JV risk-transfer: developer bears construction capex; Nest.IQ runs a fee/operating-margin model. This is the headline structural mitigation — it converts capex risk into the developer's column (Competitive §8). |
| 4 | City execution — site selection, fit-out timelines, local regulatory in new markets | P2/P3 | Standardized product brief + fit-out kit for speed; developer owns local regulatory (JV value exchange, Canon §6); campus-adjacent GCC-clustered site discipline (Market §3). |
| 5 | Ascott competitive timing — the one incumbent able to fuse owned keys + aggregator demand (co-owns SilverDoor/Synergy) (Competitive §9) | all phases | Speed and lock-in: move decisively on JVs and multi-year enterprise contracts before Ascott pivots. Ascott is hospitality-led by DNA, asset-light (no RE control), and its aggregator is a global agency, not India-owned supply — the gap is real but not indefinite. |
| 6 | JV dependency / single-partner concentration | P1 | Prestige as named backup (Canon §1); IKAN's diversified 1,000+ client base hedges the single-partner exposure that killed Sonder (Competitive §8). |
| 7 | Working-capital drag — receivables 45–90 days finance the gap | all phases | Deposit float (≤6 months' rent) as partial offset; receivables terms a deliberate [USER INPUT] policy, not an afterthought (Canon §6). |
| 8 | Cross-sell attach-rate unproven — relocation/immigration/concierge upside is a data gap | P2/P3 upside | Instrument from P1; model attach-rate as a flagged [USER INPUT], never as a baked-in revenue promise (Canon §6). |
One-page timeline summary
| Phase 1 — Foundation (0–12mo) | Phase 2 — Expansion (12–36mo) | Phase 3 — National (36–60mo) | |
|---|---|---|---|
| Geography | Bengaluru (ORR / ETV / Whitefield) | + Hyderabad, Pune, Gurgaon | + Mumbai, Chennai, NCR, Tier-2 |
| Keys | 50–80 | ~300–500 | 1,500+ |
| JV & legal | Execute Embassy JV (structure [USER INPUT]) | Standardize multi-city term sheets | Productize JV; optional RE equity [USER INPUT] |
| Real estate | First site, developer capex | Replicate fit-out kit, 3 cities | Complete 6 cities + Tier-2 |
| Brand | Launch Nest.IQ; category creation | Category leadership; case studies | National category-defining brand |
| Enterprise sales | Pre-let before launch | Multi-city enterprise deals | National master agreements + cross-sell |
| Operations | SOPs + service standard authored | Playbook deployed city-by-city | National ops at scale |
| Technology | .IQ MVP (app, matching, ops) |
Cross-city control plane | Platform/proptech layer matured |
| People | CEO, Ops, Sales, Brand, Tech leads | City GMs, Regional Ops, Data | CxO bench, platform org |
| Capital | Working capital + brand + tech (no capex) [USER INPUT] | Scales with keys (no capex) [USER INPUT] | National platform + WC (no capex) [USER INPUT] |
| Gate to next | JV live + pre-let proof + unit econ | Repeatability + consistency + channel | (scale / platform maturity) |
| Illustrative gross room revenue | ~US$1.3–2.1M (ILLUSTRATIVE, TAM §4) | ~US$7.9–14.6M (ILLUSTRATIVE) | ~US$39–58M (ILLUSTRATIVE) |
Revenue figures are ILLUSTRATIVE arithmetic (keys × 72% occ × ₹8,500 ADR × 365, INR 85/USD), before ancillary and cross-sell, with every input a Section-7 [USER INPUT] (TAM §4, Canon §7). Not forecasts.
Grounded in STRATEGY-CANON.html (§6, §8, §9) and /00-intelligence/ (Competitive-Analysis-Report §5/§8/§9; TAM-SAM-SOM-Report §4). No fabricated metric targets: all KPIs are driver-based or qualitative; all economic inputs are flagged [USER INPUT] or cited as sourced ranges. Capex is developer-borne throughout — the structural risk-transfer that defines the model.