Implementation
What actually happens between agreeing and going live.
Six steps, a clear split of who does what, and an honest answer about what sets the pace. You send what you already have. We build it with you.
The sequence
From your assets to a live experience.
Every project runs through the same six steps. What changes between projects is how much work each one takes, which is decided by the state of the material you start with rather than by the size of the development.
- 01
Project details and assets
You send what you already have: master plans, renders, floor plans, unit layouts, the unit schedule and your branding. We tell you what is usable as is and what needs work before anything is promised.
- 02
The experience is built
We prepare the imagery and build the views a buyer moves through, from the master plan to a building, a floor and a unit. This is done for you, not handed to you as a tool.
- 03
Inventory is imported and mapped
Your unit schedule is imported and each unit is tied to the shape a buyer clicks. Typologies, attributes and the rules for showing price are configured against how you actually sell.
- 04
Branding and sales channels
Your identity is applied, and we set up where the experience runs: your own site, your agencies' sites, standalone links and the gallery screen. Enquiry routing and attribution are configured here.
- 05
Validation
We walk the whole journey with your team on real devices, check every unit resolves, confirm enquiries arrive where they should, and fix what the walkthrough finds.
- 06
Publish and hand over
The experience goes live and your team is trained on the part they own day to day: availability, pricing visibility and enquiry settings. You leave knowing who changes what.
Responsibilities
Who does what, written down.
Most of the work is ours. Your side is mainly supplying material you already own and having someone who can make decisions.
You provide
- Master plans, site plans and building renders
- Floor plans and unit layouts
- The unit schedule: codes, typologies, areas and current status
- Project copy and branding assets
- Where the experience needs to run, and who handles enquiries
- A named person who can answer questions and approve the result
RegalScene handles
- Preparing and optimising every image for fast loading on a phone
- Building the master plan, building, floor and unit views
- Mapping each unit to its shape and importing your inventory
- Applying your branding and configuring enquiry routing
- Setting up embeds for your site and your agencies' sites
- Validation, publishing, training and support afterwards
Timing
What decides how long it takes?
Three things, and none of them is the size of the development. A forty-tower masterplan with clean artwork and a tidy unit schedule is a faster project than a single block whose floor plans are locked inside a PDF nobody can edit.
- The state of your assets. Usable artwork and a clean unit schedule are the whole game. Material that needs preparing adds the time it takes to prepare it.
- How many views the project needs. A single tower is not a township with phases, amenities and multiple building types.
- Whether anything has to connect to another system. Integration work is scoped separately, because it depends on what is on the other side.
We agree the plan when we scope the project, rather than quoting a date before seeing what we are working with.
After launch
What your team owns from day one.
The things that change weekly belong to you and need nobody's help: unit status as units sell, how prices appear, and where enquiries go. Releasing a new phase is a status change, not a project.
The things that change rarely stay with us. New towers, new developments or a new market are scoped as they come and publish into the experience you already have.
Questions
Questions about getting started
What do we need to have ready before we start?
Typically master plans, building images or renders, floor plans, unit layouts, your availability or inventory information, project copy, branding assets and your enquiry requirements. If something is missing or not in a usable state, preparing it becomes part of the scope rather than a surprise later.
How long does implementation take?
It depends on the state of your assets, how many views the project needs and whether any integration is involved. A single project whose visual assets and unit schedule are already in order moves quickly; one that needs artwork prepared or a schedule reconciled takes longer. We agree the plan when we scope the project rather than quoting a number before seeing it.
Do we build it ourselves?
No. We build your first experience with you during onboarding. It is not a tool you are left to figure out. Afterwards your team manages availability, pricing visibility and enquiry settings directly, and content changes are handled with you without needing developers.
What happens after launch?
Your team owns the day-to-day: unit status, how prices appear, and where enquiries go. New phases, towers or developments are scoped as they come and publish into the experience you already have, rather than starting again.
What if our assets are not ready?
That is a normal starting point and part of what we scope. RegalScene works from what developers already have, and where something needs preparation or optimisation that becomes part of the implementation scope. Telling you early is the point of the first step.
Send us what you have.
The fastest way to find out what your project needs is to show us the assets. We will tell you what is usable as it stands, what needs work, and what the first version would look like.