Nest.IQ — Investor Strategy

India's intelligent, mobility-led corporate residences — owned and operated via developer JVs, powered by IKAN.

Audience: Capital partners (strategic developers, family offices, PE/real-estate funds, proptech/VC, hospitality investors) and the founding team. Status: Strategy artifact. Date: May 2026.

Reading rules (non-negotiable). Every figure here is one of two things: a sourced benchmark or comp (cited to /00-intelligence/, the Strategy Canon, and the Financial Framework, with confidence H/M/L), or an ⟨INPUT⟩ the founder must supply. No raise size, pre-/post-money valuation, ownership %, IRR, or return figure is asserted anywhere — each is marked ⟨INPUT⟩. The founder does not yet know investors or amounts; this document frames the case and the choices, not the terms. The valuation logic is a framework, not a promise.

1. The equity story — why this, why now, why us

One sentence. Nest.IQ owns the empty quadrant of India's premium long-stay market — owned/operated, enterprise-grade residences fused with captive enterprise demand and an intelligence layer — at the exact moment GCC-driven mobility demand is compounding and no incumbent has fused both halves.

Why this. India's residential rental market is ~US$20B, but only ~13–14% organized; 71% of renting households have no formal contract (Canon §3, TAM report §2.1; HIGH). The white space is structural, not cyclical: hospitality-led operators own inventory but rent it opportunistically through OTAs and brand distribution; mobility-led aggregators own captive enterprise demand but almost no real estate (Competitive-Analysis §2). No player in India fuses owned/operated keys + captive mobility demand + intelligence — that empty quadrant is the category Nest.IQ creates (Vision; Competitive-Analysis §8).

Why now. The demand engine is inflecting. GCCs: ~1,700 (2024) → 2,400–2,550 (2030); employees ~1.9M → 3.0–4.5M+; GCC office leasing hit 29.2 msf in 2024 (+29% YoY), ~40% of all office leasing, with Bengaluru + Hyderabad >60% (Canon §4; HIGH). Mobility is shifting into the exact 30–180-day band hotels serve poorly: +59% short-assignment growth YoY, 75% of firms relying on short-term placements, 76% of relocating employees wanting employer-provided temporary housing (TAM §5; HIGH directional). And the timing window is finite: Ascott is the one incumbent holding both halves of the thesis — scale operator (~6,100 India units → 12,000 by 2028) and co-owner of the largest mobility aggregator (SilverDoor/Synergy) (Competitive-Analysis §9). Defensibility is a function of speed and lock-in — secure developer JVs and enterprise contracts before Ascott deliberately fuses its halves.

Why us. The moat is captive demand, manufactured by IKAN — ~30 years, 1,000+ corporate clients, 50,000+ assignments, 200+ cities, RMC and Fortune-500 relationships (Canon §1). Demand precedes doors: Phase-1 strategy is to pre-secure enterprise occupancy contracts before launch (Canon §8). This is the one thing a developer cannot manufacture and the one thing an aggregator cannot monetize without owning keys. The wedge: "Everyone can build the building. Only Nest.IQ arrives with the tenants — and the intelligence to keep them."

The captive-demand moat, in underwriting terms. A hotel buys its occupancy every night; Nest.IQ contracts it in advance across a diversified 1,000+ client base. Extended-stay runs ~78% occupancy vs ~66% for transient hotels (Canon §3; M), avoids the 15–30% OTA/CAC drag of hospitality-led peers (Competitive-Analysis §2), and is counter-cyclical (extended-stay demand +2.2% in 2025 while overall hotel demand fell −0.8%; declined only once in 27 years). The diversification is also the hedge against the single-partner concentration that triggered Sonder's Chapter 7 collapse in 2025 (Competitive-Analysis §8.5).

2. The platform/proptech thesis & valuation FRAMING

This section is a framework for how to think about value, not a target. Nest.IQ has no actuals today; the multiples below are sourced, the conclusion is a range with logic mirrored from Canon §7 and the Financial Framework §4.

2.1 The two-engine value argument

Most real-estate businesses are valued as real estate: keys × yield. Nest.IQ argues for two engines:

1. The residences engine — owned/operated keys, earning a hospitality multiple on property-level EBITDA.
2. The .IQ engine — captive demand generates proprietary signal (who moves where, when, what a graceful arrival requires); signal trains matching/yield/ops intelligence and a cross-sell layer (immigration, relocation, destination, concierge). A genuine, recurring intelligence/services revenue line is what could earn a multiple above the hospitality base (Vision §.IQ; Business-Model §4).

2.2 Comparable multiples (sourced)

2.3 The defensible base / narrative ceiling logic

At ~1,750 keys (Canon's Phase-3 mid), illustrative room revenue ≈ US$46–51M (Financial Framework §3). At a 30–40% property EBITDA margin that is ~US$14–20M EBITDA (ILLUSTRATIVE — margin is ⟨INPUT⟩).

• Hospitality multiple (12–15×): US$14–20M × 12–15× → ~US$168–300M → the defensible base of US$150–300M.
• The US$500M ceiling requires either (a) a proptech/SaaS multiple (6–10× revenue, or 25–30× EBITDA OYO-style) applied to the genuine tech/cross-sell layer, or (b) real-estate equity participation in the JV assets. Narratively achievable (OYO, Stanza precedent) but not supported by Nest.IQ actuals today.

Verdict (Canon §7; Financial Framework §4.2; confidence Medium): defensible base US$150–300M (hospitality multiple); US$500M is a venture/strategic ceiling, not a promise — gated on the tech-premium thesis (⟨INPUT⟩: share of revenue that qualifies as SaaS) and/or captured real-estate equity (⟨INPUT⟩: land/asset treatment in the JV). Present it as a ceiling, never a forecast.

3. Capital strategy & uses-of-funds FRAMEWORK

No raise number is stated — it is ⟨INPUT⟩. What we can state honestly is what capital does and what drives the need. The JV structure is the headline: in a developer JV, land + building + construction capex sit with the developer — the single biggest reason Nest.IQ's capital base is light versus an asset-heavy operator (Financial Framework §5).

3.1 What capital actually does (drivers of the need)

3.2 The favourable working-capital traits (the model's edge)

1. Deposits as float. Commercial security deposits up to 6 months' rent (New Rent Law 2025) from corporate tenants — a source of float, not a use of cash (policy is ⟨INPUT⟩).
2. Contracted, recurring billing shortens DSO vs OTA-dependent hotels and avoids the 15–30% OTA/CAC drag.
3. Demand precedes doors — pre-secured enterprise occupancy compresses the ramp and de-risks the receivables build.

Net: corporate-housing working capital is structurally favourable vs transient hotels — large refundable deposits offset the enterprise-receivables drag. Sizing context only (owned hotels): India hotel ROI ~10–15%, payback 7–10 yrs; the JV's land-light structure is what can bend ROCE above the owned-hotel norm. The raise (⟨INPUT⟩) is sized from §3.1 minus the deposit float — set last, not first.

3.3 Use-of-funds allocation (illustrative shape)

The total raise is ⟨INPUT⟩ and asserted nowhere; what we can show is the shape of how capital is deployed, because the JV structure (capex sits with the developer) tilts the allocation decisively toward platform, people, and working capital rather than bricks. Each share below is an ⟨INPUT⟩ % that must sum to 100%; the ranges are qualitative priors, not commitments.

The shape is the message: in an asset-heavy operator, construction capex would dominate this table; here it is the developer's line, so Nest.IQ's capital concentrates in the platform and demand engine — the assets that earn the re-rate toward the US$150–300M base (and, if the .IQ layer becomes a genuine recurring line, toward the US$500M ceiling). The percentages stay ⟨INPUT⟩ until the founder sets the raise.

4. Structure options — where capital can sit

The actual structure is a management decision (and partly a negotiated outcome with the developer); each option below is presented with its trade-offs, not prescribed. They are not mutually exclusive — a likely path layers them over time.

The structural lesson (Competitive-Analysis §8.5). Sonder died on ~US$303M/yr fixed lease obligations against transient revenue. Survivors went asset-light/fee-led (Ascott) or paired tech with a structural demand source. Nest.IQ's JV-led (not asset-heavy-lease) structure + contracted enterprise demand is the combination that supports recurring, proptech-style economics rather than cyclical-hotelier ones.

5. Investor targeting — types, fit, and what each wants

Sequencing logic (founder's call, ⟨INPUT⟩): strategic-developer + family-office capital tends to fit the asset-backed JV layer earliest (lowest dilution, fastest to a tangible pilot); proptech/VC fits the platform/HoldCo layer once the .IQ engine and a multi-city footprint give the platform multiple something real to price.

5.1 Return framework per investor type

Different capital wants different returns, on different clocks, through different doors. The table frames return shape, time-to-liquidity, and exit path by archetype — so each conversation is anchored to how that investor actually gets paid. No IRR, MOIC, hold period, or return figure is asserted — every return value is ⟨INPUT⟩, set only once the raise, valuation, and split are fixed; the framework below gives the formulas, not the numbers.

IRR / MOIC framework (formulas, not promises). Returns are computed, never asserted — and only after the Financial Framework Input Register is populated. The skeleton, gated end-to-end on ⟨INPUT⟩:

Entry equity        =  raise × ownership taken          ⟨INPUT #12, valuation⟩
Exit equity value   =  exit EV × ownership at exit
                       where exit EV  =  exit-year EBITDA × exit multiple
                            EBITDA     =  §-driven, ⟨INPUT⟩    (Financial Framework §2–§3)
                            multiple   =  hospitality 12–15× base  →  SaaS/proptech 6–10× rev
                                          or 25–30× EBITDA at the ceiling  [S5][S7][S15]
                       (+ cumulative distributions / yield over the hold, if any)

MOIC  =  ( Exit equity value + distributions )  ÷  Entry equity
IRR   =  ( Exit equity value / Entry equity ) ^ (1 / hold years)  − 1     (simplified, no interim flows)
        →  use XIRR over the actual cash-flow dates once the ramp ⟨INPUT⟩ is set

Valuation frame:  defensible base  US$150–300M (hospitality multiple)
                  ceiling          US$500M (SaaS multiple on the .IQ layer OR captured RE equity)
                  — a narrative ceiling, never a number to underwrite today (§2.3; Canon §7)

The point of expressing returns as formulas is discipline: an investor can plug their own entry price, ownership, hold, and exit multiple into this skeleton and see the sensitivity for themselves — which is far more credible than a quoted IRR the venture has no actuals to support. Every variable is ⟨INPUT⟩; the venture asserts none.

6. Value-unlock milestones — what de-risks and re-rates the company

Each phase converts a narrative claim into a proven one, and each proof point is what lets the next round of capital price the company higher. Phases map to Canon §8.

The single highest-leverage de-risker is Milestone 0: contracts before doors. It is the proof that separates Nest.IQ from every operator chasing occupancy a night at a time.

6.1 Milestone → capital map

Capital is raised against milestones, not calendars. This map ties each phase's capital (the §3.3 use-of-funds shape) to the specific milestone it funds and the re-rate that milestone unlocks (§6 table). Phases carry only relative sequence and ⟨INPUT⟩ duration — no calendar dates are invented, and no phase amount is asserted (each is sized from the §3.1 drivers).

Read it as a staircase: each tranche funds the milestone that lets the next tranche price higher. Early capital (Foundation/Expansion) is the asset-backed JV layer that strategic-developer and family-office money fits; the Platform tranche is what gives proptech/VC something real to underwrite (§5.1). The whole map sits inside the same valuation frame — US$150–300M defensible base, US$500M ceiling — with each milestone moving the company along it. Amounts and timing remain ⟨INPUT⟩ until the raise is set (§3.3, last not first).

7. Comparable transactions & benchmarks (from research)

Caveat (Competitive §3.1, §3.2): Ascott India revenue is undisclosed — internal US$80–120M is unverified/likely high; defensible range US$40–90M (LOW). Marriott Executive Apartments India ≈ ₹40–80cr (NOT ₹1,500cr). Use these corrected figures.

8. Data-room checklist

Strategy & market — Strategy Canon; Vision; this Investor Strategy; TAM/SAM/SOM, Competitive-Analysis, and Market-Research reports (/00-intelligence/) with full source lists.

Commercial / demand — IKAN client roster, assignment volumes, RMC/Fortune-500 relationships; enterprise pipeline and any pre-let LOIs/contracts (the moat evidence); cross-sell attach data (flagged gap — ⟨INPUT⟩).

Financial — the driver-based Financial Framework + populated Input Register (the ~12 ⟨INPUT⟩ cells: FX, land treatment, capex/key, per-city ADR, occupancy, JV split, ramp, EBITDA + G&A, tech-premium %, receivables, deposits, raise); pilot P&L model; portfolio scale model; sensitivity analysis.

JV & legal — Embassy JV term sheet/agreement; JV economic split; corporate structure (HoldCo vs JV SPVs); IP/brand ownership (Nest.IQ marks, tokens.css, logo); IKAN relationship agreement.

Operations & tech — SOPs / operating standard; .IQ platform architecture, roadmap, and IP; resident-app spec; property pipeline by city.

Team & governance — founding team and IKAN leadership; org plan (Canon §8); cap table (⟨INPUT⟩); governance and board structure.

Risk — single-developer dependency mitigation (Prestige backup); occupancy/ramp sensitivities; competitive watch-item (Ascott) monitoring.

9. Objection-handling / investor FAQ

"Isn't this asset-heavy and capital-hungry?" No — that is the point of the JV. Land + building + construction capex sit with the developer. Nest.IQ contributes brand, demand, operations, and tech, and earns fees (and, where negotiated, an economic/equity share). Capital is for pre-opening, working capital, the .IQ platform, and central G&A — and the deposit float offsets the receivables drag (Financial Framework §5; Business-Model §1).

"What about occupancy risk?" The model is built to retire occupancy risk before it appears: pre-let enterprise contracts fill homes before they open across a diversified 1,000+ client base. Extended-stay structurally runs ~78% vs ~66% for transient hotels and is counter-cyclical. The pilot is deliberately in supply-heavy Bengaluru (~64.8% market occupancy) so the hardest case is proven first, with pre-let contracts as the mitigant (Canon §3, §6; Financial Framework §6).

"Ascott already has scale and owns an aggregator — won't they crush this?" Ascott is the one genuine watch-item — but it holds the two halves in separate hands and is hospitality-led by DNA. Fusing captive mobility demand into owned Indian inventory is a strategic pivot requiring (a) re-architecting around contracted demand, (b) a JV structure that captures asset upside (vs its REIT/management model), and (c) Indian owned-supply for SilverDoor/Synergy to point at — which must exist first. Defensibility = speed + lock-in. Nest.IQ's job is to secure JVs and enterprise contracts inside that window (Competitive-Analysis §9).

"Can the team actually execute?" The hard, scarce capability — captive enterprise demand — already exists in IKAN (30 years; 1,000+ clients; 50,000+ assignments). The build is operations + tech on top of proven demand, with a developer supplying assets. Milestone 0 (contracts before doors) is the early, objective execution proof (§6).

"Aren't you dependent on a single developer (Embassy)?" Embassy is the lead, Prestige is the named backup, and the model is developer-agnostic by design — the demand moat is portable to any JV partner. Crucially, the demand side is diversified across 1,000+ clients, which is exactly the concentration hedge Sonder lacked. The aggregators (SilverDoor/Synergy, AltoVita, Dwellworks, NCH) become channels once Nest.IQ owns keys, further diversifying distribution (Competitive-Analysis §5, §8.5).

"Why does this deserve more than a real-estate multiple?" It may not — and we don't promise it. The defensible base is US$150–300M on a hospitality multiple. The additional premium (toward the US$500M narrative ceiling) must be earned by a genuine, recurring .IQ revenue line and/or captured real-estate equity — both ⟨INPUT⟩-gated. We present the ceiling as a structural argument, never a number to underwrite today (Canon §7; §2 above).

"How much are you raising, at what valuation, for what stake?" ⟨INPUT⟩. The founder has not set a raise size, valuation, or ownership split, and this document asserts none. The raise is sized from the §3 drivers (net of deposit float) once the Financial Framework Input Register is populated, and the structure (§4) is a management/negotiation decision.

Prepared from the Strategy Canon, Financial Framework, Vision, and the TAM/SAM/SOM and Competitive-Analysis reports in /00-intelligence/. All market figures are sourced with stated confidence; all venture decisions not yet made are flagged ⟨INPUT⟩. No raise size, valuation, ownership %, IRR, or return is asserted. The valuation logic is a framework to be earned — not a forecast.

Source definitions (citations used here)

Every [Sn] ID appearing in this document resolves below. The financial-benchmark registry (Brief D) is maintained in the TAM/SAM/SOM report §8; that registry numbers S1, S3, S5, S7–S12, S15, S16 but does not separately list S2, S13, S14, so those three are defined here in full against real, dated, public sources to ensure no citation dangles.

Other inline references use prose pointers — "Canon §n" (Strategy Canon), "Financial Framework §n" (Financial Framework), "Competitive-Analysis §n" and "TAM §n" (in /00-intelligence/) — each resolving to a numbered section in the named document.