By Idael Diaz, Director of Atlas Domus
A developer sends a lookbook to a buyer’s representative ahead of a viewing. The file is polished, but the next day a floor plan changes. The sales team now needs to know which version is in circulation and which recipients should receive the update. The question is whether the presentation format supports the way the team sells.
PDFs still have a place in print, offline review, and controlled circulation. A web portfolio is useful when a project changes frequently, buyers need to compare options, or the brokerage needs a more reliable way to connect a request to the material that prompted it.
Compare the formats against the sales task
A PDF works well as a self-contained record. A recipient can keep it, mark it up, or take it into a meeting without connectivity. The same portability makes version control harder once a file has been forwarded. Use dates, version labels, and a clearly identified source for the current copy.
A web portfolio gives the team one current destination. It can connect a plan to a residence, let someone compare options on a phone, and direct a request to the appropriate team. Give the visitor useful navigation before adding motion or interactive effects. A buyer’s adviser should be able to open a specific residence quickly and return to the overall project without starting again.
Separate public material from controlled access
Decide which assets can be indexed, shared, downloaded, or seen only with approval. Apply those decisions to the website and the CRM process. A link that is merely hard to guess is a poor substitute for appropriate access controls when a seller needs private circulation.
Design a small first release around common tasks:
- Let visitors find a specific residence and identify the current version of its approved plan.
- Provide a straightforward way to request materials that require permission.
- Keep the reading experience usable on mobile and with slower connections.
- Give the sales team a dated source of truth and a path to flag outdated information.
Use engagement context with restraint
Where measurement is disclosed and appropriate, a viewing request can carry the project, residence, or portfolio section that prompted it. That context can help a broker answer a specific question. A page view may reflect casual browsing, a shared device, or a representative reviewing several properties. Treat it as context rather than purchase intent.
Capture what the visitor explicitly requests. Keep detailed analytics separate from the broker’s judgment about the relationship. Test which inquiry details reach the CRM before promising the sales team a richer handoff.
Keep the presentation maintainable after launch
Agree who updates the public portfolio, who releases private materials, and how version changes are communicated. Preserve a downloadable edition where advisers need offline access, with a visible publication date and a reference to the current source when appropriate.
Test a viewing request and a document revision before launch. If either requires several people to manually reconcile the version, refine the workflow before adding more interactivity.
Scope the right format for one portfolio
Bring one existing lookbook and the decisions you want it to support. Atlas Domus will assess where a web experience would improve comparison, version control, or inquiry routing and where the PDF remains the better format.
Request an Interactive Web Experience Scope
