Skip to main content

Onboarding

This page provides a high-level overview of the onboarding process for new projects on the Pluto platform. It covers the setup work required before launch and the training sessions that prepare your team to operate the system.


Project Setup Checklist

The following categories represent the key areas that must be configured before a project can go live. The order below reflects the typical setup sequence.

1. Division & Community Structure

Before configuring a project, the higher-level organizational structure must be in place. Pluto uses a four-level hierarchy:

Organization → Division → Community → Project

  • Division — A regional or business-unit grouping within your organization. Staff access, dashboard filtering, and template resolution are all scoped by division. Divisions are managed via the Admin section.
  • Community — Represents a development or master-planned community that contains one or more projects. Community-level settings include branding (logo), contact information, site maps, and parking locations. Communities are configured in the Workbench.

2. Construction Admin Setup

Establish the organizational structure within the platform:

Project Type Variations

The steps above apply to all project types, but the specifics will vary. Single-family projects, for instance, won't require parking and storage configuration, while a high-rise condominium may only have a single building entry but will need additional floor and unit-level data. The overall workflow remains the same — only the depth of detail changes based on the project type.

3. Sales Admin Setup

Configure the sales-side settings:

4. Template Setup

Configure the templates used throughout the sales and communication workflows:

  • PDF TemplatesContract documents, disclosure statements, and any project-specific forms.
  • Email Templates — Automated and manual email communications sent to purchasers, realtors, and staff, including device verifications. Templates support merge fields and modifiers.
  • SMS Templates — Text message templates for notifications and device verifications.
Starter Templates

Pluto provides a base set of templates to get you started. From there, an admin can customize any or all of these at the project, community, division, or organization (Corporate) level.

5. Customer Connect Setup

If Customer Connect is being used for the project:

6. Pre-Launch Validation

We recommend running at least three end-to-end test deals — with both purchaser and realtor participants — before going live. Each test should follow the full lifecycle:

  1. Reservation — Start from Customer Connect, if in use.
  2. Deal WritingIdentity verification, unit selection, options, and deposit configuration.
  3. Contract SigningDocument generation through the sales app, signing via the Signing Service.
  4. Client PortalPurchaser and realtor access, deal review, and outstanding signatures.

Vary the scenarios across tests (e.g., different unit types, option selections, or deposit methods) to ensure broad coverage.


Training Sessions

Training is structured into up to six sessions. Not all sessions are required for every project — the scope depends on team roles and which platform features are in use.

#SessionAudienceDescription
1Admin IntroductionAdminPlatform introduction, staff setup, role configuration, and system navigation.
2Project Setup & ConfigurationAdminWorkbench walkthrough — community/project configuration, unit management, and data entry.
3Templates & EmailsAdminPDF and email template creation at the project level. Covers merge fields and modifiers.
4Overview and Writing a New DealAll UsersDashboard, unit manager, reservations, identity verification, and the full new deal process.
5Deal Management, Client Portal, and SigningAll UsersDeal lifecycle, contacts, deposits, document management, client portal, signing service, and backfills.
6Customer ConnectAll Users OptionalReservation link management, the customer-facing reservation flow, and customer vs. realtor paths.