LaSata at 90 Broadway: A Squarespace Real Estate Website Case Study
A property development website needs to communicate more than an attractive lifestyle. Potential buyers also need clear information about the residences, location and next steps.
LaSata at 90 Broadway is part of my real estate portfolio for N1 USA. This article outlines the documented project brief and delivery, then explains practical website-planning lessons for property businesses.
The focus is the work and its design rationale. It is not a claim about increased sales or lead volume, because verified post-launch performance data is not included here.
The project brief
N1 USA needed four websites to market separate property developments. Each development required its own identity while maintaining a connection to the wider brand. The brief also called for clear presentation of residences, floor plans, amenities, location and availability.
I designed and developed four mobile-responsive websites with structured property information, clear navigation and enquiry pathways. The LaSata portfolio entry records Squarespace and Lovable among the project technologies.
You can view the published project summary and website preview in the LaSata at 90 Broadway portfolio entry.
That documented scope is the foundation of this case study. The following sections explain broader design considerations illustrated by the brief, rather than presenting undocumented research or performance findings.
Lesson 1: a development needs its own identity
When a company markets several developments, it is tempting to repeat one website with different photographs. That may create consistency, but it can also make distinct properties feel interchangeable.
A development’s identity should reflect its actual setting, architecture and intended market. Typography, imagery and tone can establish that character without making the information difficult to find.
At the same time, the parent brand needs enough consistency to feel credible. This can come from shared standards for navigation, contact information and content quality rather than identical page designs.
For a new project, I would begin by documenting what makes the development different and which brand elements should remain consistent across the portfolio.
Lesson 2: organize information around buyer questions
An attractive homepage creates interest, but buyers need practical answers. They may want to compare residence types, understand a floor plan or assess the surrounding area.
A useful property website separates these questions into understandable sections. It should not force visitors to search a long image gallery for essential specifications.
For a typical development, consider how the site explains:
The property and its location
Residence options
Floor plans and key dimensions
Amenities
Availability information
The enquiry or viewing process
The exact structure should follow the property’s real information. Do not create pages simply because another development uses them.
Lesson 3: make floor plans easier to understand
Floor plans often contain important detail that becomes difficult to read inside a small image. A useful presentation allows visitors to identify the plan, understand what it represents and access a clearer view where needed.
Use accurate labels and ensure downloadable files match the current version. If measurements, pricing or availability may change, the business should approve how that information is presented and maintained.
Supporting text can explain the difference between residence types without requiring the visitor to interpret every drawing immediately. That text should describe the actual property, not introduce unverified selling points.
This is a planning recommendation for property websites, not a statement that every possible feature was included in the LaSata build.
Lesson 4: connect interest to a specific enquiry
A generic contact page is useful, but the surrounding website should help visitors explain what they are interested in.
For a multi-development business, enquiries should clearly identify the relevant property. Where appropriate, the form can also ask about a residence type or viewing request.
Keep the initial form proportionate. The purpose is to begin a useful conversation, not require the visitor to complete a sales interview before making contact.
Button labels should explain the next step accurately. “Request information” and “Book a viewing” should not be used interchangeably if the second action does not actually confirm a viewing.
Lesson 5: give mobile visitors the same essential information
Property marketing often relies on large photographs, wide floor plans and detailed layouts. Those elements need deliberate mobile treatment.
Check whether visitors can read key information, enlarge relevant images and reach contact options comfortably on a phone. Important details should not disappear because they are difficult to fit into the mobile composition.
Test the page from the source where visitors may discover it, such as a social link or property campaign. The landing page should make sense even if the visitor never sees the homepage.
Lesson 6: establish an update process
A property website can become inaccurate after launch if availability and documents are not maintained. Assign responsibility for these updates before the site goes live.
Keep a record of where time-sensitive details appear. A price or availability statement repeated across multiple pages can be easy to miss during an update.
Where practical, reduce unnecessary repetition and use one authoritative page for changing information. The website should be manageable for the person responsible for keeping it current.
What the project demonstrates, and what it does not
The portfolio documents a delivered website project serving a clear marketing brief. It shows an approach to presenting separate developments within a wider business identity.
It does not provide verified before-and-after conversion rates, sales figures or search rankings. Those outcomes should be added only if reliable data becomes available and the client approves its use.
For a future performance review, useful measures could include qualified property enquiries, viewing requests and the pages visited before contact. The measurement plan should distinguish a button click from a completed enquiry.
Frequently asked questions
Can Squarespace be considered for a property development website?
Yes, for suitable marketing and enquiry requirements. Live property feeds, advanced search or specialist sales systems need separate technical assessment.
Should every development have a separate website?
Not necessarily. Separate sites may suit distinct identities, while a shared site may simplify management. The decision depends on the brand, audience and amount of unique content.
Do I need to publish sales results in a case study?
No. A case study can clearly explain the brief and delivered work. Performance claims should only be included when they are supported.
Discuss your property website
If your development needs a clear identity, structured property information and a practical enquiry route, I can help plan the website around those requirements.
Explore my Squarespace design service and book a discovery call to discuss your real estate project.
