Nest.IQ — Business Plan

Intelligent, mobility-led corporate residences for India. The art of arriving.

Audience: Prospective investors and joint-venture partners (lead partner: Embassy Group). Document: Master strategy and operating plan, synthesizing the full Nest.IQ strategy set. Date: May 2026.

Reading rules. Every figure in this plan is one of two things: (a) sourced to the intelligence reports in /00-intelligence/ and the Strategy Canon, carried with a confidence grade (HIGH / MED / LOW); or (b) explicitly flagged ⟨INPUT⟩ — a negotiated or to-be-confirmed value the venture's leadership must supply, which we never assume. Nothing is fabricated. Where arithmetic is shown, it is labelled ILLUSTRATIVE and built only from sourced ranges. No raise size, valuation, capital amount, or JV split is asserted anywhere. This document synthesizes the venture's full strategy set — vision, business model, financial framework, roadmap, go-to-market, and the three market-intelligence reports — into one consistent narrative.

1. Executive Summary

India receives the world's most valuable talent into a housing system that was never built to welcome it. The country's residential rental market is worth more than US$20B, yet only ~13–14% of it is organized or formal; 71% of renting households have no formal contract, and organized co-living is just ~5% penetrated [Market §"Market Structure", HIGH]. Fewer than fifteen homes in a hundred carry an accountable, enterprise-grade standard — and that sub-15% formal gap is not a footnote. It is the investment thesis.

The demand filling that gap is being manufactured, at scale and on a predictable cadence, by India's Global Capability Centre (GCC) boom: ~1,700 GCCs in 2024 employing ~1.9M people, projected to 2,400–2,550 centres and 3.0–4.5M+ employees by 2030 [Market §"GCC Engine", H trajectory / M 2030 headcount]. GCCs drove 29.2 msf of office leasing in 2024 (+29% YoY) — roughly 40% of all office leasing — and Bengaluru and Hyderabad alone account for >60% of it [Market, HIGH]. Each hiring ramp is a near-term block of 30-to-180-day housing demand, concentrated precisely where Nest.IQ will build.

Nest.IQ is the brand built to capture it: India's first intelligent, mobility-led corporate-residences company — owned-and-operated serviced homes for global enterprise talent on 30-to-180-day (to multi-year) assignments, built through joint ventures with developers and powered by IKAN, a ~30-year global mobility company with 1,000+ corporate clients, 50,000+ assignments, and a 200+ city footprint [Canon §1].

The market has split into two camps with one empty quadrant between them: hospitality-led operators that own inventory but fill it opportunistically, and mobility-led aggregators that own enterprise demand but no inventory. No one fuses owned/operated keys, captive mobility demand, and an intelligence layer into a single standard [Competitive §1–2]. That fusion is the business, and the wedge is one line: "Everyone can build the building. Only Nest.IQ arrives with the tenants — and the intelligence to keep them."

The structure protects the thesis. In the JV, the developer brings land, building, and construction capex; Nest.IQ brings brand, enterprise demand, operations, and technology. This converts a hotel's capex-and-payback risk into a fee-and-operating-margin business — the structural risk-transfer that let Ascott endure asset-light while Sonder's fixed-lease model collapsed into Chapter 7 in November 2025 [Competitive §8, "durable, proptech-grade economics"]. The plan that follows is deliberately a framework, not a forecast: it states what is sourced, flags what the founder must decide, and underwrites to a defensible base rather than a promised number.

2. Company & Vision

Nest.IQ exists to make arrival graceful. Moving countries or cities for work is one of the most disorienting things a person does — a hundred small uncertainties compressed into a single anxious week, usually at the exact moment an employer expects brilliance. The hotel is transient, the serviced apartment a compromise, the local rental a gamble made over WhatsApp with a stranger. None of it feels like home, and none of it was built to. Nest.IQ believes the moment a person lands to do meaningful work, the hardest part should already be handled — quietly, intelligently, completely. Arrival is the product.

The name carries the strategy: Nest is the warmth — belonging, shelter, the place you settle — and .IQ is the intelligence that makes this a platform rather than a portfolio of property. The essence is Arrival, perfected; the tagline, The art of arriving [Canon §2]. Five pillars define the brand: (1) demand, not just doors; (2) intelligence in every home; (3) one standard, every key; (4) the whole arrival — home plus immigration, relocation, and concierge; (5) built with India's best, for the world's best.

The IKAN backing is the heart of the model. For roughly thirty years, IKAN has moved the world's workforce — 1,000+ corporate clients, 50,000+ assignments, 200+ cities — woven into the relocation, immigration, and destination-services fabric of how global enterprises move their people, carrying live RMC and Fortune-500 relationships. That network is the demand engine. The relationship is simple:

Nest.IQ is the place. IKAN is the reason it's always full.

Where competitors must chase occupancy a guest at a time — paying the heavy customer-acquisition toll of hospitality — Nest.IQ arrives with the tenants already contracted. IKAN brings the demand and the thirty years of knowing what a graceful arrival requires; Nest.IQ turns it into homes, a standard, and ultimately a platform.

The arc is pilot to platform. It begins with a flagship in Bengaluru, occupancy pre-secured before a single guest arrives. The playbook then travels to the GCC capitals, the proof compounding city by city. As the footprint matures, Nest.IQ becomes more than residences — the connective tissue of how the world's talent lands in India: residences plus relocation plus immigration plus mobility technology plus concierge plus AI resident services, sitting at the intersection of real estate, mobility, hospitality, and proptech [Vision §"The arc"]. This long arc is held qualitatively, not as a promise of numbers — but the direction is unwavering.

3. Market Opportunity

3.1 The fragmentation thesis — the white space (HIGH confidence)

The reliable denominator is India's residential rental sector: >US$20B (2024), of which the organized/formal slice is only ~US$2.7–2.8B, roughly 13–14% of the total; 71% of renting households have no formal contract, and organized co-living sits at ~5% penetration (~0.3M beds, growing toward ~1.0M by 2030 at >17% CAGR) [TAM §2; Market §"Market Structure", HIGH]. The professionally managed, branded, enterprise-grade slice is smaller still. This is the most defensible structural fact in the entire thesis: the market is >85% informal and fragmented — and that is the white space an owned/operated, branded platform is built to capture.

3.2 The GCC demand engine (HIGH on trajectory and geography)

Office leasing is the hard, corroborated proxy that this demand is physical and on the ground: total India office leasing crossed 70 msf in 2025 — a third straight record year [TAM §3; Market §"GCC Engine"]. Critically, the geography is already solved: Bengaluru (~34–39% of GCC activity) plus Hyderabad (~20–23%) account for >60% of GCC leasing, South India holds ~64% of all GCCs, and the remaining target cities — Gurgaon/NCR, Pune, Mumbai, Chennai — are all named Tier-1 GCC hubs [Market, HIGH]. The six-city launch map maps directly onto where the demand physically is.

The shape of demand reinforces the fit. Corporate mobility is shifting decisively toward short assignments: 75% of companies expect to rely on short-term placements, a predicted +59% YoY jump in short assignments, and 76% of relocating employees want employer-provided temporary housing ("especially strong in India"), while 68% of programs are actively cutting costs [Market §"Mobility Shift", HIGH directional]. This 30-to-180-day dwell band is structurally mismatched to both hotels and long unfurnished leases — and is exactly what corporate housing serves. The demand story leans deliberately on GCC ramps, domestic relocation, and the short-assignment shift — not expat inflows, which are poorly measured [TAM §5, expat sizing LOW].

3.3 Two-tier TAM, SAM, and SOM — disciplined sizing

No clean, standalone India serviced-apartment USD figure exists in the published literature; we therefore triangulate from better-measured adjacent markets and present two TAM tiers rather than one inflated number [TAM §1–2]:

The "$12B today" framing is explicitly retired: US$12B is defensible only as a broad-basket 2030 figure, not a 2025 size [TAM §2.3; Canon §4]. SAM — enterprise-paid, medium-term furnished housing in the six cities — is modelled at ~US$0.6–1.5B (2025) (15–30% of TAM, growing to ~US$1.2–3.0B by 2030), and is labelled a modelled share, not a measured figure [TAM §3, LOW–MED]. SOM is built bottom-up from keys actually delivered — not a top-down percentage — driven by Nest.IQ's captive demand and owned JV inventory (see §11).

4. The Problem & The Solution

The problem is twofold — and felt on both sides of the transaction. For the global enterprise, housing inbound and relocating talent across multiple Indian cities means stitching together hotels billed by the night, fragmented local rentals with no accountability, and a serviced-apartment market with almost no scaled, enterprise-grade, branded supply. Premium business-hotel ADR runs ~INR 11k–14k and is climbing ~9%/yr — faster than inflation — so a 30-night stay at ~INR 12k ≈ ~INR 3.6L/month before per-night escalation compounds over 90–180 days [Market §"Hotel-Cost Wedge", HIGH]. For the 30-to-180-day dwell band, the hotel is economically irrational. For the resident, the experience is a transient room or a gamble — never a home, and never handled. The relocation-management companies that orchestrate these moves own no housing; they broker it and leak the margin to brokers and operators [Market §"RMC", E6].

The solution is the missing middle, made deliberate. Nest.IQ owns and operates serviced homes to one enterprise standard, fills them with captive enterprise demand contracted before the doors open, wraps the whole arrival — home, immigration, relocation, concierge — into a single accountable experience, and runs every key with intelligence. It is not a hotel (built for the transient) and not consumer co-living (built for the individual choosing a lifestyle). It is intelligent, mobility-led corporate residences — a category the market has not had a name for, defined not by the building but by the arrival [Vision §"The category"].

5. Business & Operating Model

5.1 The JV value exchange

Nest.IQ does not buy land or fund buildings. It manufactures the one thing real estate cannot manufacture on its own — guaranteed enterprise occupancy — wrapped in a premium operating standard and an intelligence layer that compounds with scale. The structure is a joint venture with a developer:

The risk/return logic is better than either incumbent structure: Ascott deliberately offloads real estate to a REIT, and Ahuja leases on thin margins, but Nest.IQ's JV captures operating margin plus asset-upside participation without funding capex — consistent with the management-agreement and branded-residence terms developers like Embassy already sign [Business-Model §1; Competitive §8, "superior asset economics through the JV"].

5.2 The demand moat — captive enterprise occupancy

The moat is not the building; it is who fills it, and how cheaply. Extended-stay assets run ~78% occupancy vs ~66% for hotels — a +10–12pt structural premium — and extended-stay demand rose +2.2% in 2025 while overall hotel demand fell −0.8%, having declined only once in 27 years [Business-Model §3, MED]. A captive channel eliminates most of the 15–20% CAC and 15–30% OTA-commission drag (plus ~50% OTA cancellation rates) that burden hospitality-led peers. In underwriting terms: a hotel buys its occupancy every night; Nest.IQ contracts it in advance across a diversified 1,000+ client base — the diversification that the single-partner concentration killing Sonder did not have.

5.3 Revenue streams

Stream 1 is the underwrite. Stream 2 lifts property economics modestly. Stream 3 is the LTV story and the clearest differentiator from any hospitality operator — but its attach-rate has no public benchmark and must be supplied, not assumed [Business-Model §5; Canon §6]. Where a JV includes for-sale branded units, a licensing path exists: branded-residence royalty 2–5% of sales, with a branded premium of ~33% globally (up to ~75% in Pune).

5.4 Deal structures (norms sourced; the split is ⟨INPUT⟩)

The actual split is a negotiated ⟨INPUT⟩ per deal — no public India benchmark exists [Business-Model §6; Financial-Framework §1]. That fee streams are real in India is validated by IHCL's management-fee income growing ₹470cr → ₹562cr (+20%), with >95% of new signings capital-light. The recommended posture mirrors familiar terms: a ≈20-year operating agreement; base fee on revenue + incentive on GOP weighted to profit; optional revenue-share + minimum guarantee to give the developer a downside floor.

5.5 How Nest.IQ relates to IKAN's aggregator and the global aggregators

Nest.IQ is an independent, owned/JV brand — this plan does not pitch the aggregation business. IKAN's existing B2B aggregator (mobility demand routed to third-party supply) sits at the opposite end of the value chain; Nest.IQ owns and operates the keys. Two relationships matter: (1) IKAN's enterprise and RMC pipeline feeds occupancy as captive demand; and (2) the global aggregators — SilverDoor/Synergy, AltoVita, Dwellworks, National Corporate Housing — become channels once Nest.IQ owns inventory, reselling vetted owned keys and converting Nest.IQ from a markup reseller into their preferred India supplier [Business-Model §2; Competitive §5].

6. The .IQ Intelligence & Technology

The ".IQ" is not decoration. It is the system that turns a portfolio of serviced homes into a learning network, and it is the basis for any valuation premium above a pure hospitality multiple [Business-Model §4]:

1. Demand-matching. IKAN's assignment data — assignee profile, family size, stay length, employer, location need — is matched to the right unit, sub-market, and price. Nest.IQ owns both the demand signal and the supply; the aggregators route this signal blind.
2. Occupancy & yield optimization. Dynamic allocation and pricing across owned inventory and pre-let contracts, lifting occupancy toward the 78–82% stabilized upside and protecting ADR by city.
3. Smart operations & resident app. One operating standard ("one standard, every key") instrumented through software — check-in, service requests, the arrival experience, and the concierge/relocation wrap delivered in-app.
4. Data network effects. Every assignment, stay, and renewal improves matching, pricing, and forecasting. More keys and more assignments make the next match better — a compounding advantage neither a pure operator nor a pure aggregator can replicate.
5. Cross-sell engine. The app surfaces IKAN ecosystem services at the moment of need, expanding LTV per assignee.

The intelligence loop is the moat's engine: captive demand fills the homes; filled homes generate proprietary signal; that signal trains the intelligence that matches, fills, and runs the next home better than the last — which deepens the enterprise relationship and secures more demand [Vision §".IQ"]. With discipline, this is what could justify a multiple above the hospitality base — but the tech-premium thesis is itself an ⟨INPUT⟩ (the share of revenue that qualifies as recurring/SaaS), and the valuation framing in §11 treats it as a ceiling, not a promise.

7. Competitive Advantage & Moat

The two-camp split is the whole opportunity. On one side, hospitality-led operators (Ascott/CapitaLand, Marriott Executive Apartments, Frasers, Hilton, Lemon Tree/Keys) own inventory but fill it opportunistically through OTAs and corporate rate programs — mobility demand is a byproduct, never the underwrite. On the other, mobility-led aggregators own the relocation demand through deep RMC relationships but own almost no real estate, reselling third-party supply for a markup [Competitive §1–2]. No player in India fuses owned/operated keys with a captive mobility pipeline and intelligence. Nest.IQ occupies that empty quadrant.

Ascott is the scale leader and the single most important watch-item. It runs ~6,100 India units across 22 properties (85% Tier-1), targeting 12,000 by 2028, asset-light via the CapitaLand Ascott Trust REIT (CLAS FY24 revenue S$809.5M, 61% management contracts) [Competitive §3.1]. Crucially, Ascott co-owns the SilverDoor/Synergy aggregator — it is the one incumbent that already holds both halves of the thesis in separate hands. Three factors separate it from fusing them: it is hospitality-led by DNA, asset-light (so it controls little underlying real-estate economics), and its aggregator is a global agency, not India-owned supply. The window is real but not indefinite; defensibility is a function of speed and lock-in [Competitive §9].

The rest of the field is sub-scale: Marriott Executive Apartments India is ~₹40–80cr / 2 properties / ~150 units (the old "₹1,500cr" figure is a rejected conflation with Marriott's system-wide India revenue); Ahuja is ~₹59–71cr across ~10 cities, leased and reportedly absent from Bengaluru (not the "₹100–150cr / 2 cities" of the old deck) [Competitive §3.2, §4.1]. Frasers and Hilton extended-stay are negligible or nascent in India.

Aggregators are future channels, not rivals — once Nest.IQ owns keys, the demand-rich, inventory-poor routers resell its vetted supply [Competitive §5; §8, "aggregators become channels"]. Embassy is a complementary partner, not a competitor. Embassy already brings land, capital, REIT financing, a hospitality portfolio, the Olive by Embassy co-living platform (stated ambition ~100k+ owned/operated beds in five years), its "Spark by Hilton" strategic licensing agreement, and an "Open Hotels" AI-native operator [Competitive §6.2, sourced [C:13][C:14]]. Per Embassy's own public disclosures it also operates branded hotels and a GCC-enablement platform; specifics such as flagged hotel-key counts and the GCC-platform branding sit in Embassy's own materials and are carried here as attributed, not independently verified. What none of it can do is manufacture guaranteed enterprise/expat occupancy from Fortune-500 mobility programs. Nest.IQ sits above Olive's volume co-living tier as the premium expat/managed-corporate layer, completing Embassy's office-park ecosystem rather than duplicating any part of it [Competitive §6.2].

The structure is the durable advantage. Sonder's Chapter 7 liquidation was killed by ~US$303M/yr fixed lease obligations against transient revenue; the survivors went asset-light/fee-led or paired tech with a structural demand source. Nest.IQ's JV-led (not asset-heavy-lease) structure plus contracted demand across a diversified 1,000+ client base is the combination that supports recurring, proptech-style economics rather than cyclical-hotelier ones [Competitive §8, "durable, proptech-grade economics"].

8. Go-To-Market

The demand engine inverts the usual lodging playbook. Most lodging businesses are born empty and spend years — and 15–30% OTA/CAC drag — buying occupancy. Nest.IQ arrives with the tenants already contracted, converting at near-zero marginal acquisition cost [GTM §1]. The pre-let strategy makes this real:

1. Underwrite occupancy at the LOI stage. Before the JV is finalized, IKAN's enterprise team secures anchor demand commitments — LOIs and framework agreements from GCCs and RMCs for a block of room-nights once inventory delivers — de-risking the developer's pro-forma.
2. Convert the existing assignment pipeline into a forward order book. A measurable share of IKAN's 50,000+ placements routes into the first city — the mechanism is owned, not bought (the redirectable share is an ⟨INPUT⟩).
3. Open to a waitlist, not a vacancy. The Bengaluru pilot launches with named corporate accounts already contracted, compressing the 18–24-month stabilization ramp.

The ICP is the company that pays and the person who lives there. Primary B2B buyers: GCC Heads of Mobility / Workplace / Admin (the sharpest ICP); RMCs (a ~US$34.2B market that owns no housing and leaks the margin); and Fortune-500 global-mobility leads (~63% of India domestic-relocation programs are now run by global-mobility teams) [GTM §2]. The resident — the relocating GCC engineer or manager — drives renewal and word-of-mouth, so the product voice stays quiet luxury.

Four sequenced channels: (1) direct enterprise sales via IKAN — the moat channel, where near-zero CAC lives; (2) aggregators as B2B2C channels after Nest.IQ owns inventory (with the caution that SilverDoor/Synergy is Ascott-backed — list there, but never depend on it); (3) developer co-marketing to Embassy office-park tenants ("your new hires, housed inside the park"); and (4) inbound (a hand-built, anti-template site capturing category-defining queries) [GTM §3].

The sales narrative runs three competitive cuts: vs hotels, win on TCO ("stop paying nightly rates for a quarterly stay"); vs aggregators, win on owned quality and accountability ("they forward your booking; we own the home"); vs local operators, win on brand and trust ("global-standard residences, underwritten by 50,000 assignments of operating history") [GTM §4]. Pricing is value-based against hotel TCO, priced city-specific, with length-of-stay tiers and framework rates — but specific rate cards are ⟨INPUT⟩; no invented price points. A signal-driven lead-generation engine (built on the founder's lead scraper) monitors GCC announcements, office-lease signings, funding rounds, hiring surges, and leadership relocations, enriches each record, and routes it into IKAN's CRM with signal metadata — detecting demand the moment it forms rather than buying lists [GTM §6].

8.1 The pre-let funnel — signals to contracted room-nights

The GTM motion is a single pipeline that turns a demand signal into a contracted block of room-nights before a key is built. The framework is fixed; the conversion rate at every stage is an ⟨INPUT⟩ the founder must set against live pipeline data — this plan invents no volumes and no rates.

The funnel inverts the usual lodging sequence: instead of opening empty and buying occupancy through OTAs at 15–30% drag, Nest.IQ underwrites occupancy at the LOI stage and opens to a waitlist. The redirectable share of IKAN's 50,000+ assignment pipeline is itself an ⟨INPUT⟩ — owned, not assumed [GTM §1–2]. Funnel velocity and stage conversion become the leading indicators tracked in the KPI dashboard (§12); the pre-let room-night count is the single number that proves the moat before any capital is at risk.

9. Execution Roadmap

The moat — captive enterprise demand pre-let into owned/operated keys — is not a phase; it is the thing every phase protects and compounds. The single non-negotiable across all phases: capex sits with the developer. The strategic clock is set externally by Ascott; speed and lock-in are the defense [Roadmap §"How to read"].

Phase 1 proves the moat in one city: finalize the JV, select sites in Bengaluru's highest-demand GCC clusters, author the SOP library and the "whole arrival" service standard, ship the .IQ MVP, and — the decisive move — pre-secure enterprise occupancy contracts before launch. The gates to Phase 2 are a signed JV with keys delivered to standard, pre-let proof (demand demonstrably fills keys ahead of opening), a unit-economics signal tracking toward the JV's modelled targets, and a documented, replicable playbook [Roadmap §"Phase 1"].

Phase 2 multiplies the playbook into Hyderabad (HITEC City / Gachibowli), Pune (Hinjewadi / Kharadi), and Gurgaon (Cyber City / Golf Course Ext), standardizing JV term sheets, building the central ops function that enforces "one standard, every key," and activating aggregator channels as live distribution. Phase 3 completes the six-city footprint, enters Tier-2 GCC cities, matures the .IQ platform into a data product, and deepens the high-margin cross-sell wrap. Capex remains developer-borne throughout, even at 1,500+ keys — the structural risk-transfer that defines the model.

10. Organization & People

People are where this model is won or lost: the moat is captive demand, but the standard — "one standard, every key" — is delivered by an organization, not a spreadsheet. Nest.IQ is built to scale from a lean, founder-led core to a function-led organization to an institutional leadership bench, hiring ahead of each phase rather than behind it. (All roles below are defined by mandate; no individuals beyond the founder are named, and every headcount, name, and compensation figure is a flagged ⟨INPUT⟩.)

10.1 Why this team — the IKAN pedigree

The credibility of a new venture is usually its weakest line. Here it is the strongest. Nest.IQ is not a first-time entrant guessing at enterprise mobility — it is incubated inside IKAN, a ~30-year global talent-mobility company with 1,000+ corporate clients, 50,000+ assignments, a 200+ city footprint, and live RMC and Fortune-500 relationships [Canon §1]. That institutional base supplies three things money cannot buy at launch: (1) a standing enterprise sales relationship set the venture inherits rather than builds; (2) three decades of operating knowledge about what a graceful arrival actually requires — immigration, relocation, destination, concierge; and (3) a recruiting magnet, since mobility, hospitality, and proptech operators join a category leader with a real demand book far more readily than a cold start. The venture is led day-to-day by its founder/operator, Eashan (from IKAN), with the broader leadership bench defined by role and filled as each phase opens (⟨INPUT: names, hire dates⟩).

10.2 Organization structure by phase

The shape evolves deliberately: a founder-led pod that proves the pilot, a function-led structure that enforces one standard across cities, and an institutional org with a full leadership bench and a platform/data-product group.

10.3 Phase-tied hiring plan

Each role is mapped to the phase in which it is first hired. The principle is to staff the standard and the demand engine first, then layer in multi-city operations, then institutional depth. Counts per role are ⟨INPUT⟩.

The self-operate-versus-hospitality-management-partner decision is a deliberate ⟨INPUT⟩, not a default — it materially changes the operations headcount in P2–P3 and is made against the pilot's service-quality and unit-economics evidence [Roadmap §"Risk register"].

10.4 Advisory board

A focused advisory board de-risks the categories where a young venture is thinnest, mapped to seats (no names asserted — each is an ⟨INPUT⟩):

• Real estate & developer JVs — structuring, REIT/asset-recycle dynamics, and developer-side credibility (a natural seat for the lead JV partner's nominee, ⟨INPUT⟩).
• Hospitality operations — branded serviced-living standards, openings, and quality systems at scale.
• Global mobility / RMC — enterprise procurement, duty-of-care, and the buyer's decision frame (complements IKAN's own relationships).
• Proptech / data — the .IQ intelligence roadmap and the recurring-revenue thesis that underwrites any multiple above the hospitality base.
• Legal / regulatory — FDI, GST, DPDP, and foreign-national tenancy (see §14).

The board is advisory, convened on a defined cadence (⟨INPUT⟩); fiduciary governance follows the JV and any institutional capital, whose board composition is itself an ⟨INPUT⟩.

10.5 Compensation & equity philosophy

Stated as principle, not numbers — every figure, band, and pool size is a flagged ⟨INPUT⟩ the venture's leadership and its capital partners must set:

• Pay for the standard and the outcome. Cash benchmarked to market for mobility/hospitality/proptech talent in the target cities, with a meaningful variable component tied to the operating KPIs in §12 — stabilized occupancy, pre-let room-nights, NPS, and EBITDA discipline — not vanity growth.
• Equity aligns the long arc. A founder-and-team equity pool (size ⟨INPUT⟩) vesting over multi-year horizons so the people protecting "one standard, every key" share in the platform value they create.
• Operators are owners. City GMs and senior operators carry performance-linked incentives tied to their property/region's KPIs, reinforcing the standard locally.
• Consistency over heroics. Incentives reward sustained quality and retention (resident NPS, renewal, service consistency), because the model compounds on reliability, not one-off wins.
• Governed by the cap table. Any equity instruments, option pool, and JV-level participation are set with the developer and investors; this plan asserts no pool size, strike, or split.

The hardest scaling problem is human, not financial: protecting "one standard, every key" across geographies. The mitigations are codified SOPs from Phase 1, a central QA/audit cadence, and train-the-trainer discipline — anchored by the institutional operating culture Nest.IQ inherits from IKAN [Roadmap §"Risk register"].

11. Financial Framework

This is a framework, not a forecast. The model is a driver-based skeleton: every cell is either a sourced benchmark range or an ⟨INPUT⟩ the founder must supply. Until the inputs are set, all output is illustrative [Financial-Framework §0].

The driver chain is transparent: Keys × Occupancy % × ADR × 365 = Room revenue, then + ancillary + cross-sell − opex = property GOP/EBITDA, applied across a stabilization ramp, with the JV split deducted to reach Nest.IQ's share. The sourced anchors:

Illustrative gross room revenue by phase (arithmetic: keys × 72% occ × ₹8,500 ADR × 365, at ₹85/USD; before ancillary and cross-sell; every input an ⟨INPUT⟩ cell):

These figures are reused verbatim across the canon, the financial framework, and the TAM/SAM/SOM report so every Nest.IQ deliverable agrees. They are illustrative scale checks, not forecasts — they assume one blended ADR, flat occupancy, no stabilization ramp, no per-city mix, no ancillary/cross-sell uplift, and no JV-split deduction [Financial-Framework §3; TAM §4].

Two margin layers stay separate: property-level EBITDA of 28–40% (reference points: India listed hotels ~36%, IHCL ~35%, Lemon Tree owned ~46.8%, Ascott SR gross ~45.8%, OYO asset-light ~17.5%), from which corporate G&A must be deducted separately as an ⟨INPUT⟩. The "mobility-integrated 35–45%" claim is aspirational and unbenchmarked — flagged, not asserted [Financial-Framework §1, §"Sensitivity"].

Working capital is structurally favourable versus transient hotels: commercial security deposits up to 6 months' rent are a float source, and contracted monthly billing shortens DSO — offset by enterprise net-45/90 receivables (the drag Nest.IQ finances). Both the receivables terms and deposit policy are ⟨INPUT⟩ [Financial-Framework §5].

Valuation framing — a range with logic, not a target. At Phase-3 mid (~1,750 keys), illustrative room revenue ≈ US$46–51M; at a 30–40% property EBITDA margin, ~US$14–20M EBITDA; at a hospitality multiple of 12–15×, ~US$168–300M — the defensible base of US$150–300M. US$500M is a narrative ceiling, reachable only with a proptech/SaaS multiple applied to the tech/cross-sell layer or real-estate equity participation in the JV assets — presented as a ceiling, never a promise, and gated on the tech-premium thesis (⟨INPUT⟩) [Financial-Framework §4; TAM §4.3, MED].

The framework runs on ~12 founder inputs — none assumed anywhere: (1) USD/INR rate; (2) land treatment in the JV; (3) capex/key per city & tier; (4) per-city ADR; (5) per-city stabilized occupancy; (6) JV economic split; (7) stabilization ramp; (8) target EBITDA by model + corporate G&A; (9) tech-premium thesis; (10) receivables terms; (11) security-deposit policy; (12) raise size / capital sources. No raise size, valuation, capital amount, or JV split is asserted — filling these twelve cells is what converts this framework into a forecast [Financial-Framework §1].

12. KPI Dashboard

One dashboard, two kinds of metric. North-star KPIs measure whether the moat is working — captive demand pre-let into owned keys at a premium. Guardrail KPIs ensure the growth is healthy, not bought. Targets are stated as direction or sourced anchor where one exists; every numeric target is a flagged ⟨INPUT⟩ the founder sets per city and deal. The discipline: a number on this dashboard is never invented to look good.

The dashboard ties directly to the rest of the plan: the GTM funnel (§8.1) feeds pre-let room-nights and enterprise contracts; the financial drivers (§11) feed occupancy, ADR realization, RevPAR, and EBITDA margin; the IKAN ecosystem feeds cross-sell attach; and the operating standard (§10) shows up as NPS. North-star KPIs are reported to the JV and investors; guardrails govern whether the venture scales the next city or pauses to fix the standard.

13. Exit & Returns

Different capital wants different things from the same business — and Nest.IQ is deliberately structured to satisfy several at once: a developer/JV partner wants asset value and recycle optionality; a strategic wants category control; financial capital wants a multiple and a path to liquidity. This section frames what each wants, time-to-liquidity, and exit path qualitatively. It asserts no IRRs and no dates, and stays consistent with the §11 valuation framing: a defensible base of US$150–300M on a hospitality multiple, with US$500M as a narrative ceiling gated on the proptech/SaaS premium or real-estate equity participation — a ceiling, never a promise.

Three things make these paths credible rather than aspirational. First, the structure already mirrors a known exit machine: Ascott runs asset-light and recycles real estate through the CapitaLand Ascott Trust REIT — the same recycle logic a developer JV partner underwrites here [Competitive §3.1]. Second, fee streams are real and monetizable in India: IHCL's management-fee income grew ₹470cr → ₹562cr (+20%) with >95% of new signings capital-light, evidence that operating-fee businesses command value locally [Financial-Framework §1]. Third, the valuation is underwritten to the base, not the ceiling — every figure here traces to §11, and the proptech multiple is treated as upside contingent on an ⟨INPUT⟩ thesis, never as a promised return. No exit is asserted as guaranteed; liquidity timing, the JV split, and any return profile remain founder/partner ⟨INPUT⟩s set against the live model [Financial-Framework §4; TAM §4.3, MED].

14. Regulatory, Risk & ESG

This section consolidates three things a partner underwrites: the execution and market risks the model carries, the regulatory regime it operates inside, and the ESG / responsible-operations posture the brand commits to. Specific legal and tax claims are stated as the prevailing framework and flagged for transaction-specific counsel — nothing here is a substitute for deal-stage legal, tax, and regulatory advice, and any rate, threshold, or treatment is qualified accordingly.

14.1 Execution & market risks

Sources: Business-Model §10; Roadmap §"Risk register"; Competitive §8, §9.

14.2 Regulatory landscape

The serviced-residences model sits at the intersection of real estate, hospitality, and data — a regime that is navigable and, in places, advantageous, but one Nest.IQ treats as a deliberate design input rather than an afterthought. The structure (developer holds land, building, and local approvals; Nest.IQ operates) already places much of the heaviest regulatory burden with the partner best equipped to carry it.

Regulatory specifics above describe the prevailing framework as commonly understood and are deliberately qualified; rates, routes, thresholds, and treatments are confirmed at transaction stage with Indian legal and tax counsel and carried as ⟨INPUT⟩, not asserted.

14.3 ESG & responsible operations

ESG is not a bolt-on for a residences brand whose promise is care at the moment people are most vulnerable — it is an extension of "the art of arriving," and increasingly a procurement requirement for the Fortune-500 and GCC buyers Nest.IQ sells to (supplier ESG and duty-of-care diligence is now standard in enterprise mobility).

• Environmental. Operating-standard targets for energy and water efficiency, waste reduction, and sustainable fit-out/procurement; because assets are developer-built, Nest.IQ can specify green-building and efficiency criteria into JV fit-out kits. Specific targets/certifications ⟨INPUT⟩.
• Social. Resident safety, well-being, and accessibility; fair-labour and living-wage standards for operating and housekeeping staff; the duty-of-care obligations enterprise clients carry for relocating employees — directly served by the immigration/relocation wrap.
• Governance & data ethics. DPDP-aligned data protection (§14.2), transparent enterprise contracting, anti-bribery/anti-corruption, and the advisory-board oversight described in §10.4.

Reporting cadence and any ESG framework alignment are an ⟨INPUT⟩; the principle is that responsible operations are part of the product and the enterprise sale, not a separate compliance track.

15. The Path & Next Steps

The thesis is structurally sound: a >85% fragmented rental market [HIGH], a physical, concentrated, recurring GCC demand engine [HIGH on trajectory and geography], a captive demand book no competitor owns, and a JV structure that sits on the right side of the line Sonder crossed. The category is real, the white space is empty, and the clock is set by a single watch-item — Ascott — that has not yet fused its halves.

Immediate priorities:

1. Finalize the Embassy JV (Prestige as named backup) on familiar terms — a ≈20-year operating agreement, base fee on revenue plus GOP-weighted incentive, and an optional revenue-share with minimum guarantee to give the developer a downside floor. Position Nest.IQ as complementary to Olive [Canon §9].
2. Pre-let the Bengaluru pilot — convert IKAN's existing client book into signed/LOI'd anchor occupancy before the 50–80-key flagship opens. The 90-day north-star is not revenue but committed pre-let room-nights and named anchor accounts [GTM §8].
3. Stand up the demand engine — wire the signal-driven lead-generation pipeline (GCC announcements, lease signings, hiring surges) into IKAN's CRM for Bengaluru and Hyderabad.
4. Build the foundations — launch the hand-crafted brand and site, author the SOP and service-standard library, and ship the .IQ MVP, instrumented from day one so Phase-1 data trains Phase-2 matching.
5. Set the financial inputs — populate the twelve-cell Input Register so the framework becomes a live model.

Capital need is framed, not asserted. Nest.IQ's capital base is operating set-up, working capital, brand, technology, and team — not construction capex (developer-funded in the JV). The drivers of the need are pre-opening costs (~5–9% of development cost), the working-capital receivables drag (partly offset by deposit float), and central G&A funded ahead of property cash flow. The raise size and capital sources are an ⟨INPUT⟩ the founder must set against those drivers — not a number this plan invents [Financial-Framework §5; Roadmap §"Capital"].

Nest.IQ is the place the world's talent lands in India — and IKAN is the reason it is always full. We will know we have won when "where will they stay?" stops being a question, because the answer, across every GCC capital in India, has quietly become the same.

The art of arriving.

Synthesized from the Nest.IQ strategy set: ../01-strategy/STRATEGY-CANON.html (single source of truth), ../01-strategy/Business-Model.html, ../01-strategy/Financial-Framework.html, ../01-strategy/Vision.html, ../01-strategy/Roadmap.html, ../01-strategy/GTM-Leadgen.html, and the intelligence reports ../00-intelligence/Market-Research-Report.html, ../00-intelligence/Competitive-Analysis-Report.html, ../00-intelligence/TAM-SAM-SOM-Report.html (all sourced [1]–[32], [S1]–[S16], [E1]–[E26], [a1]–[d4], [C:6]–[C:34]). Every figure is sourced with a confidence grade or flagged ⟨INPUT⟩. All forward figures are ILLUSTRATIVE framework outputs from sourced ranges; no forecast, raise size, valuation, capital amount, or JV split is asserted.