Nest.IQ
Operating BlueprintOpen the platform →

Operating Blueprint · Powered by IKAN · Private & Confidential

How it all flows.

The whole business as one system — the value exchange, the surfaces, the journeys, and the multi-JV portfolio that "mission control" runs end to end. This is the map of what we operate and what we're building.

Built live todayPrototype designed, mock dataPlanned next build
01The value exchange

Four parties. One flywheel.

Nest.IQ sits in the middle of a value loop: developers supply the asset, IKAN supplies the demand, enterprises contract the homes, and residents live the arrival — each turn compounding the next.

Supply
Developers
Land, building & construction capital, via JV. Get recurring income + a financeable, branded asset.
⇄asset · JV
The operator
Nest.IQ
Brand, operations, the .IQ intelligence layer, and captive occupancy. Powered by IKAN.
⇄homes · service
Demand
Enterprises
GCCs & multinationals contract homes for assignees — pre-let before opening, via IKAN.
The wrap (IKAN)
Immigration · Relocation · Destination · Concierge
High-margin cross-sell around every stay — the LTV multiplier.
→serves
Experience
Residents
Global talent who arrive into a managed home + a whole-journey service. Renew & refer.

Full economics: Business Model · Strategy at a glance

02The system map

Every surface, and where it sits.

From the public story to the operations brain — four layers, each feeding the next.

① Acquisition — public
Marketing site Built
The public story
The narrative front door — thesis, model, the invitation in. → leads into the platform.
Platform — browse & enquire Built
Residences across GCC cities
Search, filter, open a home, enquire. The product surface enterprises & residents touch.
② Conversion — pipeline
Enquiry intake Prototype
Enquiry → record
Captures who, which home, dates, company → creates a pipeline record.
Sales pipeline / CRM Planned
Pipeline stages
Enquiry → qualified → LOI → contracted pre-let room-nights, with owners.
IKAN demand feed Planned
Assignment pipeline
Enterprise assignments routed to the right property & date — the moat, operationalised.
③ Operations — mission control
Mission Control (multi-JV admin) Prototype
Portfolio · occupancy · pipeline · alerts
One end-to-end view across every JV and property — status, occupancy, revenue signals, tasks.
Tenant / Resident Hub Prototype
The resident's home base
Stay details, services & the wrap, requests, documents, renewals.
④ Foundation — data & services
Data model Planned
JV · Property · Unit · Tenant
Backend / API Planned
Records, auth, roles
.IQ intelligence Planned
Yield · matching · ops
Integrations Planned
IKAN · payments · PMS
03The journeys

Three journeys carry the business.

A · Enterprise demand → contracted home

Enterprise
NeedAssignee inbound, 30–180 days
DiscoverVia IKAN / platform
EnquireSubmits on a residence
Nest.IQ
IntakePipeline record created
QualifyOwner, terms, LOI
ContractPre-let room-nights
AssignMatched to a property
Outcome
OccupancyHome filled before opening
Mission ControlStatus & revenue tracked

B · Resident arrival lifecycle (the wrap)

Before
VisaImmigration
MoveRelocation & logistics
Live
Move-inTenant Hub activated
ServicesDestination & concierge
RequestsIn-stay support
Stay → next
Renew / extendOr graceful checkout
ReferNPS & word-of-mouth

C · JV / developer onboarding (repeatable, multi-JV)

Pipeline
IdentifyDeveloper + micro-market
Term sheetJV economic split
SiteSelection & design
Fit-outBrand & SOPs
LaunchPre-let, then operate
Onboard to Mission ControlNew JV + properties

Journeys A & C detailed in GTM & Lead-gen and Roadmap.

04The multi-JV portfolio model

Not one JV — a portfolio of them.

Embassy is the first. The model is multi-vendor by design: many JVs, each with multiple properties and units, all rolled up into one operating view. The sample below is illustrative structure, not actual data.

Operating companyNest.IQ
↓

Embassy JV Lead

Bengaluru · ORR pilotSAMPLE
Bengaluru · ManyataPlanned

JV — Developer B Pipeline

HyderabadPlanned
PunePlanned

JV — Developer C Future

Gurgaon / NCRFuture
Mumbai · ChennaiFuture

Structure is illustrative of the multi-JV / multi-property hierarchy (JV → Property → Unit → Tenant). City sequencing follows the Roadmap; no occupancy or financials are asserted.

05Mission Control — the operations brain

One screen for every JV, property and key.

The admin center rolls the whole portfolio into one place: occupancy and revenue signals by property, the live enquiry pipeline, tenant roster, and alerts — across all JVs. It's how a multi-vendor operation stays one standard.

  • Portfolio KPIs — keys, occupancy, pre-let, RevPAR
  • Property grid — status & occupancy per site
  • Pipeline board — enquiries by stage
  • Tenants & the wrap — who's in-stay, what's attached
  • Alerts & tasks — what needs attention now

Wireframe — illustrative layout & sample figures, to be built on the platform foundation.

Nest.IQ · Mission Control — SAMPLE
3
Active JVs
7
Properties
—%
Portfolio occ.
⟨#⟩
Pre-let nights
Embassy · ORR pilotStabilizing
Embassy · ManyataFit-out
JV-B · HyderabadPlanning
PipelineEnquiry ⟨#⟩ · Qualified ⟨#⟩ · LOI ⟨#⟩ · Contracted ⟨#⟩
06The Tenant / Resident Hub

After the enquiry, a home base.

Welcome home — SAMPLE
Your stay
Residence · move-in → move-outConfirmed
Immigration
Visa & FRRO ✓
Relocation
Move scheduled
Services
Concierge · housekeeping
Documents
Agreement · invoices
Need something?New request +

The Hub is where an enquiry becomes a relationship. Existing clients and residents get a single place for their stay, the IKAN wrap, in-stay requests, documents, and renewals — turning a lease into lifetime value.

  • Stay overview — residence, dates, key info
  • The wrap — immigration, relocation, destination, concierge status
  • Requests & support — raise & track in-stay
  • Documents — agreement, invoices, receipts
  • Renewals & referrals — extend, re-book, refer

Wireframe — illustrative. Built on the same platform foundation as Mission Control.

07The data model

The entities everything hangs from.

Org
JV
Partner, economic split, status. Has many → Properties.
Asset
Property
City, micro-market, keys, stage. Has many → Units.
Inventory
Unit
Type, tier, rate, availability. Holds → a Stay.
People
Tenant
Resident + employer; linked to a Stay & the wrap.
Demand
Enquiry → Contract
Pipeline stage, company, dates → pre-let room-nights.
Experience
Stay + Services
Move-in/out, the wrap attach, requests, NPS.
Access
User & Role
Admin / operator / partner / resident — scoped to a JV.

A conceptual model — it lets the same surfaces serve one JV or many, with role-scoped access (multi-tenant by design).

08What's built, and what's next

An honest map of the build.

Built · live
Story & product surface
Marketing site, platform browse/enquire, decks, the full strategy library + this blueprint.
Prototype · designed
The operating surfaces
Enquiry intake, Mission Control (multi-JV), Tenant Hub — UI + mock data layer.
Planned · next
The real backend
API + data store, auth/roles, IKAN & payments integrations, the .IQ engine.

The discipline is the same as the strategy: nothing fabricated. Sample figures in the wireframes are labelled, and the real numbers fill in as the JV and the backend come online.

From blueprint to building.

This is the system we're operating and the product we're building out.

Open the platform → Strategy at a glance →

NEST.IQ · POWERED BY IKAN · PRIVATE & CONFIDENTIAL · 2026