Developments and units
A development has units, a unit has a status, and both change without anyone touching the design. That relationship belongs in the CMS, not in a duplicated page.
Webflow for property companies
Property websites where listings behave like data
Investments, units and listings have a structure. Most property websites ignore it and push everything into one page template, which is why adding a development becomes a development project of its own.
- Structured listings
- Fast media
- Routed enquiries
The content model
A portfolio is a set of relationships, not a set of pages.
Getting this right at the start is the difference between adding a development in an afternoon and rebuilding a template.
Locations and agents
Useful relationships remove repeated typing and power real navigation. Excessive ones create editor complexity nobody maintains. The line is worth drawing deliberately.
Status that means something
Available, reserved, sold. If status is a free-text field, it will be spelled three ways within a month and no filter will work.
Media weight
Property sites are image-heavy by nature. Sizes, formats and upload rules get decided during the build, or the site is slow the first time a full gallery is added.
Who this fits
Three different businesses, three different sites.
One or several investments
The site sells specific properties with a finite life. It needs to present a development well, hold the unit list, and route enquiries while the development is selling.
A changing catalogue
Volume and turnover are the problem, not presentation. Agents need to publish without help, and buyers need filters that actually narrow the list.
Credibility over inventory
The audience is investors or owners rather than buyers browsing. Track record, structure and clarity matter more than a gallery.
Enquiries
Where property sites lose the lead.
One form for everything
A general contact form sends a buyer asking about one unit into the same inbox as a supplier invoice. Enquiries that carry the property they came from, and reach the person responsible for it, are worth more than a higher form-fill rate on a form nobody routes.
Frequently asked questions
Questions connected to this decision.
Can the site connect to an external listings system?
Sometimes. It depends on whether that system offers an export or an API. If it does not, a manually managed CMS is often cheaper to run than a fragile integration, and I will say which applies to you.
Can agents add listings themselves?
Yes, that is the normal setup. The fields and rules are designed so a listing added by someone in a hurry still looks right.
How many listings can Webflow handle?
Enough for most agency and developer sites, but collection limits are real and depend on your plan. It is checked before the model is fixed.
Do you handle multilingual property sites?
Polish and English, yes. More languages need a translation process agreed first, because that is an editorial problem rather than a technical one.
Can you help with the photography?
I run a separate property photography business, so that conversation is possible. It is quoted separately and is never a condition of the website work.
Sources and basis
What supports this page.
CMS capabilities reference current Webflow documentation. Nothing here claims a sales or enquiry outcome, because that depends on the property, the price and the market rather than the website.
- Manage CMS Collections
Webflow University · Verified 2026-07-19
Reference for collections, fields, references and item limits, which govern what a content model can and cannot do.
- Web Content Accessibility Guidelines overview
W3C Web Accessibility Initiative · Verified 2026-07-19
The standard used when checking semantics, keyboard paths, contrast and responsive behaviour.
Related decisions
