Skip to content

Built for developers selling off-plan through direct teams and agency sales.

SwitchouseDeveloper Sales OS
Sign inRequest a demo

SOLUTION FOR PROJECT LAUNCH

Launch one project without rebuilding it for every sales channel.

A Developer Sales OS rollout for property developers launching a new off-plan project.

Import and map the inventory, configure commercial rules and permissions, publish managed buyer surfaces, equip direct and broker teams, and validate the path from selection to booking.

Request a demoSee the project-launch workflow

Current publishable state

Predmet. Cemagi

Units
113 scoped units
Available
46 41%
Floors
5 lines 1–15
Promotion
1 units
Unit board for Predmet. Cemagi, levels 5 to 3. Unit M1 5.78 is the record followed throughout this page.
Level 569.5 m² · OceanSoldM1 5.7558.3 m² · Ocean$219,000M1 5.7669.5 m² · Ocean$225,000M1 5.78−10%69.5 m² · OceanSoldM1 5.8058.3 m² · Ocean$225,000M1 5.8233 m² · Rice$123,000M1 5.87
Level 4199.7 m² · Ocean$430,000M1 4.57139.8 m² · R+O$400,000M1 4.568%69.5 m² · Ocean$197,000M1 4.5869.5 m² · OceanSoldM1 4.6058.3 m² · OceanSoldM1 4.6233 m² · Rice$113,000M1 4.68
Level 3165.7 m² · Ocean$380,000M1 3.36138.4 m² · R+O$350,000M1 3.358%69.5 m² · Ocean$172,000M1 3.377%69.5 m² · OceanSoldM1 3.3969.5 m² · OceanSoldM1 3.4133 m² · Rice$106,000M1 3.47

THE BUYING SITUATION

A project launch becomes fragile when every channel prepares its own version.

The project website needs units and layouts. Listing channels need mapped project data. The direct sales team needs current prices and payment plans. Agencies need assigned inventory, commissions and project materials. The deal team needs registration, attribution, hold and booking rules.

When each launch track starts from a different spreadsheet, file or chat, those versions can diverge before the first buyer moves forward.

Developer Sales OS starts with one Live Inventory and connects the managed publishing surfaces, sales-channel workspaces and controlled deal workflow around it.

THE CONNECTED PROJECT-LAUNCH WORKFLOW

Set up the project once, then prepare each sales surface and role from the same operating record.

  1. 01

    Import and map the project

    Upload the current project data, map source columns into Developer Sales OS and preview the result. Resolve import errors or discrepancies before teams use the inventory as their operating record.

  2. 02

    Configure the commercial state

    Set the units, availability, prices, payment plans, promotions, commissions, permissions, sales rules and supported project attributes required for launch.

  3. 03

    Publish managed buyer surfaces

    Use Websites & Distribution for the surfaces operated as part of the product: a managed project website on the developer's domain, a live catalogue embedded into an existing site and connected listing syndication.

  4. 04

    Equip direct and broker channels

    Configure Sales Workspace for internal sellers. Set up agency access, assigned projects, commercial terms and Agent Portal for approved partners.

  5. 05

    Validate selection and transaction progression

    Test how a buyer selection from a direct or broker channel opens in Reservations & Bookings, where registration and transaction progression begin. Confirm the configured path through offer, hold, deposit status and booking.

  6. 06

    Review the operating state

    Use Performance to inspect current inventory, supported channel activity and buyer progression for the project.

  1. Import and map
  2. Configure commercial rules
  3. Publish managed surfaces
  4. Set up sales channels
  5. Validate selection to booking
  6. Review the operating state

ONE LAUNCH, CONDITIONAL PRODUCT COMPOSITION

Start with the foundation. Add the channels and connections required by the launch.

  • Foundation — Live Inventory

    The current operating record behind the project's units, commercial terms, permissions and transaction state.

  • Managed publishing — Websites & Distribution

    Managed project websites, embedded catalogues and connected listing syndication powered by Live Inventory.

  • Sales channels — Sales Workspace and/or Agency Onboarding

    Configure Sales Workspace for internal teams, Agency Onboarding for agency onboarding and broker-led sales, or both according to the project's launch motion.

  • Transactions — Reservations & Bookings

    The shared record for registration, attribution, hold, deposit status and booking progression across direct and broker channels.

  • Visibility — Performance

    The Developer Sales OS view of inventory, supported channel activity and buyer progression after launch.

  • Connections — Platform & Integrations

    Use the supported API, MCP and webhook layer when retained systems or custom applications are in scope.

MANAGED PUBLISHING AND CUSTOM APPLICATIONS HAVE DIFFERENT OWNERS

Use Websites & Distribution when we operate the surface. Use the platform when the frontend is yours.

Websites & Distribution owns managed project websites, embedded catalogues and listing syndication.

If the developer's digital team or system integrator builds a custom website or application, it remains a platform-powered endpoint using supported Platform & Integrations access. It is not presented as a managed Websites & Distribution product.

KEEP THE CRM AND ROLL OUT ONE PROJECT FIRST

Connect the launch without moving every project or replacing the lead-management process.

The CRM can continue to own lead assignment, contact history and follow-up. Developer Sales OS keeps the property context and owns selections, registrations and transaction progression through booking.

Begin with one project, the teams selling it and the systems required for that launch. After the workflow is validated, apply the approved structure to additional projects and sales channels.

Bring one project before launch. Map the complete sales operation around it.

We'll map its inventory, managed publishing surfaces, direct sales team, broker network, retained systems and buyer journey in Developer Sales OS.

Request a demo