Show the crane pick above the rendering, because that is the doubt
The first screen should prove you can get equipment to the water, not that you can photograph it afterward.
Every city pool buyer arrives with the same private worry: there is no driveway, the passage beside the house is narrow, and the yard is only reachable through the parlor floor or over the roof. Nothing on a standard pool website addresses it.
Put the answer at the top. A photograph of a crane pick over a row house, a conveyor running out a side alley, plywood and floor protection through a hallway, and one sentence that says you build where trucks cannot go. Buyers who have been told no by two other firms will read the rest of the page.
Renderings still belong on the site. They belong below the proof, because a rendering answers a question the visitor has not reached yet.
Name the work you do not do as well. A firm that says it does not take on rooftop installations, or only builds where a machine can reach, loses inquiries it was going to lose anyway and gains credibility with the ones it keeps.
The managing agent opens your site on a desktop with a board packet due
Two very different readers arrive on very different devices, and only one of them is standing in a yard.
The homeowner is on a phone, often outside, often at the end of the day, scrolling with one hand. Big tap targets, a phone number that dials, short paragraphs, and photographs that load before patience runs out.
The managing agent or board member is at a desk, comparing you against two other firms, and needs material they can forward. Insurance and licensing information, a description of how you work inside an occupied building, and a contact who answers during business hours. Anything they cannot copy into an email is friction.
Serve both without building two websites. One clear path from the homepage into building side work, another into residential, and no requirement that either reader wade through the other's content.
Keep a printable or easily shared version of your credentials and process material. Work that goes to a board travels as attachments, and a site that only exists as scrolling pages drops out of that conversation.
Six questions about the passage from the street to the back garden
The inquiry form is a qualifying tool, and in this city it has to ask about access before it asks about budget.
Ask for the property address, because in this metro the block answers half the questions a form cannot. Ask what type of building it is: single family, row house or townhouse, or a unit in a co-op or condo.
Ask how the rear garden is reached, with plain options: a driveway or drive through gate, a side passage, through the house, or unknown. Ask the approximate width of that passage if the owner knows it. Ask whether a board or managing agent is involved in approvals. Ask what the visitor is imagining: a full pool, a plunge pool, a spa, or a renovation of something that already exists.
Six fields answered honestly tell you whether the job is a truck roll or a phone call. Name, email and a budget dropdown tell you almost nothing and produce visits that end at a fence.
Explain why you are asking, in one line above the form. Buyers answer more questions when the reason is obvious, and a form that reads like a professional intake sets the tone before anyone speaks.
Publish the ugly middle of the job, not just the finished water
Portfolio photography that stops at the finished pool skips the part your buyer is most anxious about.
Show the sequence. The garden before, the protection going down, the excavation by hand or by machine, the material leaving, the steel, the equipment set, the restored garden and then the water. Buyers in this city have heard stories about neighbors' renovations and they want to see that you have a method.
Organize the gallery by access condition and building type rather than by year or by finish. A Staten Island backyard where a machine drove in, a townhouse garden reached through the house, a terrace installation, a building amenity pool rebuilt in phases. Visitors sort themselves.
Write a short caption on each project describing the constraint and how it was handled. Two sentences of real detail is worth more than twenty photographs without context.
Protect your clients. No addresses, no recognizable house numbers on private residential work, no building names without permission, and nothing that identifies a security arrangement inside a building.
Photographs of water are heavy, and half your visitors are underground
A pool site is an image site, and image weight is the most common reason a visitor never reaches the form.
Connections in this city are unreliable in ways suburban markets are not. People browse on a train platform, in a basement office, in a building with thick prewar walls, and a gallery built from full resolution photographs simply will not arrive.
Serve properly sized and compressed images, load below the fold work only as the visitor scrolls, and keep the top of the page light enough that something useful appears immediately. The hero image is worth optimizing more carefully than any other asset on the site.
Video of a crane pick or an excavation is persuasive and expensive to load. Host it so it does not block the rest of the page, never autoplay it with sound, and give it a still image the visitor can act on if the video never starts.
Test on an older phone over a weak connection rather than on the office network. The version of your site that matters is the slow one.
A price page that explains the city premium instead of apologizing for it
Buyers compare your number to a national average, and the site should explain the difference before the survey does.
A pool built behind a townhouse where every yard of material leaves by hand costs more than the same pool in a suburban yard. That is not a markup, it is a different job, and saying so plainly is more persuasive than trimming the number.
Write a page that describes what drives price here: access route, excavation method, spoil removal, street and parking conditions, building rules and scheduling, structure where water sits on a terrace or roof, and equipment and utility work. Explain the logic without quoting a figure you have not surveyed.
Anyone who reads that page and calls anyway has accepted the premise. The ones who do not call were never going to sign, and they cost you nothing except a page view.
Keep code, permitting and insurance statements general. Say the city runs its own regime, that timelines are longer than most people expect, and that specifics are worth confirming with the local building department, your insurer or your own counsel.
Questions we actually get
- What belongs in the first screen of a New York pool company's website?
- Evidence that you can reach the yard. A photograph of the hard part of a job, a sentence naming the access methods you use, the areas you serve, and a way to contact you. Renderings and finish galleries can wait until the visitor believes the project is possible on their property.
- How many fields should the inquiry form have?
- Enough to tell a truck roll from a phone call, which usually means around six. Address, building type, how the rear is reached, passage width if known, whether a board or managing agent is involved, and what kind of water they are picturing. Explain in one line why you are asking and most people will answer.
- Should we show pricing on the site?
- Publish the logic, not a number you have not surveyed. A page explaining what drives cost in this city, from access route to spoil removal to building rules, sets expectations and filters price shoppers. Quoting a figure without seeing the property invites arguments you cannot win.
- Do we need a separate section for co-op and condo building work?
- If you do that work, yes. The reader is different, the device is usually a desktop, and the material has to be forwardable into a board discussion. Describe your process and your insurance posture in general terms, and leave specific building requirements to the managing agent.
- Our gallery is slow. Is that really costing us inquiries?
- Very likely. Pool sites are image heavy by nature and a large share of visitors here browse on phones with poor connections. Compress and size images properly, load lower sections as the visitor scrolls, and test on an old phone over a weak signal rather than on office wifi.
