Back to proof Case study

A Brooklyn real estate developer's credible web presence

A site that looks like the real, working portfolio it represents — not a stock-photo template that could belong to anyone. This piece is about the method, not the client.

The challenge

A Brooklyn real estate developer needed a website that looked like the real, working portfolio it represents — not a stock-photo template that could belong to anyone. The hard part wasn't design taste. It was two practical problems every active developer has:

  • Some buildings are photographed; some aren't built yet. A portfolio with a few polished photos and a few blank spaces reads as unfinished.
  • The owner builds buildings, not websites. They wanted to make a few decisions and have a credible site appear — not learn a web tool.

The approach

The method is the product. Four moves did the work.

Real imagery, not stock

We sourced photographs of the developer's actual completed properties rather than generic city imagery — so a visitor sees the real work, the real materials, the real street. Each image is carefully sourced and verified before it goes on the page, and sourced photos are treated as placeholders until the client supplies or licenses finals.

Stage cards for what isn't photographed yet

For projects still in development, an empty slot would have undercut the whole portfolio. Instead, each unphotographed project gets an on-brand "in development" card — a clean blueprint-style placeholder with a simple phase tracker — so the pipeline reads as momentum, not as a gap. Every such card is clearly labeled as a rendering, never passed off as a finished photo.

A real sense of place

The site leads with imagery true to the developer's actual market, so the first impression matches the territory the business actually operates in — not a generic skyline borrowed from somewhere else.

Per-project depth

Beyond a single gallery, each project gets its own detail view, with a clean index tying them together — the structure a buyer, partner, or lender expects when they want to look closer.

It works where people actually look — on a phone

A subtle but important fix: interactive overlays that originally responded only to a mouse hover were rebuilt to respond to a tap, so the site behaves correctly on touch devices instead of hiding information on mobile. Most real estate gets browsed on a phone; the site is built for that first.

Built for a tap

Overlays reveal on tap — not hover — so nothing hides on a phone, where most of this audience actually browses.

The difference, shown

Generic template Stock skyline, blank slots
Real-imagery treatment Actual work, honest pipeline
Illustrative comparison — a generic stock template versus the real-imagery treatment. No real addresses or names shown. · Rendering
In development
A pipeline project
An anonymized example "in development" card — blueprint motif with a phase tracker, standing in for a project that isn't photographed yet. · Rendering

The done-with-you process

The developer made a handful of gut-level choices. We handled sourcing the imagery, building the pages, producing the stage cards, wiring the per-project structure, testing it on real devices, and walking it to a private preview link for review before anything went live.

The result

A credible, real-imagery portfolio site that shows the developer's actual completed work, presents the pipeline honestly with on-brand development cards instead of empty space, reads correctly on mobile, and is something the owner can stand behind with partners and lenders — without having become a web person to get it.

Want the same approach for your business?

Real work, not stock. Honest placeholders for what is not ready. Walked all the way to live. Fill in the form and we will come back with a quote scoped to what you actually need. Prefer email? Write to desk@zalmy.ai.

Your information is used only to respond to this request. We do not sell or share it.