By Idael Diaz, Director of Atlas Domus
Six weeks before a development starts pre-sales, the website looks dated, the project team has new imagery, and a campaign is about to send buyers to a page nobody has tested on a phone. A rebuild can seem like the obvious answer. The harder question is whether the launch actually needs a new foundation.
Make the decision against the tasks that have to work on day one. A prospect needs to verify the project, find what is available to review, and make a private inquiry. The sales team needs that inquiry to arrive with enough context to act.
Identify which problems belong to the existing site
Test one property journey on mobile before discussing a redesign. Open the project from a campaign or an existing search result, find a current property detail, and trace a test inquiry to its destination. Check what the editor must do to update availability, replace a floor plan, or change a disclosure.
A refresh can be enough when the underlying templates support those tasks and the changes are concentrated in the presentation or a few performance issues. A rebuild becomes easier to justify when project records cannot be maintained reliably, pages lack stable destinations, or sales and marketing have to manually reconstruct context from every inquiry.
Choose the smallest release that supports pre-sales
Compare the options against the actual deadline and available reviewers. For a refresh, scope the pages buyers use, the forms sales depends on, and the content approvals needed to get them live. For a rebuild, plan for redirects, a verified CMS model, and the conversion paths that must be carried across.
A pre-sales acceptance check should cover:
- The public project facts, design credits, and disclosure language the team has approved.
- Mobile readability and a usable inquiry path before video or heavy imagery finishes loading.
- Stable URLs or appropriate redirects for existing links from brokers, campaigns, and press.
- A test submission reaching the expected CRM record and owner.
- A documented rollback for changes to page templates, redirects, or forms.
Keep a short release list and a separate list for work that can follow. A new gallery or expanded portfolio can wait when the team still needs to verify the primary inquiry path.
Plan for a second decision after launch
Capture a baseline on the pages and tasks that matter before making the release. Check the same URLs after publishing. Keep lab performance tests, live inquiry routing, and sales outcomes separate in the review. A smaller video can reduce transfer size even when another script remains a drag on responsiveness.
When the launch is stable, review the issues that remain. If editing still requires engineering or the team cannot represent the project’s units consistently, use that evidence to scope a rebuild. If the update fixed the important tasks, the website can keep serving the launch while the team gathers better evidence for a later investment.
Review the site against the pre-sales deadline
Bring the launch date, current project site, and the path a buyer takes to request a viewing. Atlas Domus will help identify which changes fit a focused release and what a larger rebuild would need to preserve.
Book a Strategy & Website Consultation
