Say which jurisdictions you build in before you show a single rendering
The fastest qualification you can offer a visitor here is a plain statement of where your crews actually work.
The District, suburban Maryland and Northern Virginia permit and license separately. A visitor in Silver Spring and one in Alexandria are shopping in different regulatory worlds, and both assume you might not cover them.
Put it above the fold in words, not on a map graphic that fails to load on a phone. Naming Montgomery County, Arlington, Alexandria and Fairfax County outright does more qualifying work than a service area map ever will.
Then give each jurisdiction its own page, describing generally how permitting and inspections run there and what you handle on the homeowner's behalf. Anything specific is worth confirming with the local building department, and saying so reads as experience rather than hedging.
Be honest about the edges of your coverage. Listing the whole metro when your crews stop at a certain drive time generates inquiries you decline, which wastes your staff's time and the visitor's.
The Arlington homeowner is reading this on a phone, in the yard, at dusk
Design for the real reading conditions of this trade rather than for a desktop mockup.
A large share of the traffic arrives on a phone, outdoors, in bad light, often while the person is physically standing in the space they are thinking about changing.
Type has to hold up in glare. Tap targets have to work with one thumb. The call button has to be reachable without scrolling back up, and the phone number needs to be a link rather than an image.
Assume attention measured in seconds. The first screen should carry a plain description of what you build, where you build it, and one action. Anything requiring a second thought belongs further down.
Test on an actual phone outside, not in a browser window resized to look like one. The difference is obvious the first time you try it.
Ask about alley access and gate width, because a Capitol Hill lot decides the price
The inquiry form for this trade has to capture the things that determine whether a job is even feasible.
Six or seven fields, chosen deliberately. Jurisdiction or the property's city and county. New build, renovation or repair. How equipment can reach the yard: driveway, side gate with a width, alley, or no access at all. Whether an HOA or a historic district may be involved.
Access is the field most sites omit and the one that changes the number most in this market. A walled rowhouse yard in Shaw reached only through an alley is a different job from a Reston subdivision with a driveway, in machine size, spoil removal and schedule.
Add a timing question that acknowledges the season. Someone hoping to swim next summer and someone hoping to swim in six weeks need different first conversations, and in a market with freeze risk the honest answer is sometimes about next year.
Offer a photo upload. Three pictures of the yard, the gate and the alley will tell your estimator more than any dropdown, and it makes the visitor feel the process has already started.
Feasibility content for a rowhouse yard that may not take a pool at all
Inside the District, the page that earns the call is the one that treats fit as a real question rather than an assumption.
Rowhouse and converted flat lots near Dupont Circle, in Petworth and around Capitol Hill are narrow, share walls, and are reached through an alley with permit parking on the street. Whether a pool works there is genuinely uncertain.
Build a page that walks through what generally determines it: available yard depth, setbacks, how a compact machine gets in, where spoil goes, how neighboring structures affect the approach. Historic districts may add review that is worth confirming with the relevant preservation office.
Show the work rather than a finished glamor shot. A conveyor running down an alley, a small machine threading a gate, a crew protecting a neighbor's wall. Photos of constraint prove more than photos of results.
Do not assess anyone's specific property in writing. Describe the general factors, then offer the site visit. The page is there to earn the visit, not to replace it.
A credentials and process page that survives procurement-style scrutiny
Many households in this metro read a contractor's website the way they read a vendor proposal.
A federal and contracting workforce is used to checking credentials, comparing written scopes and asking for references before signing anything. That habit follows people home into a backyard project.
Give them a page that answers it directly: licensing and registration by jurisdiction, insurance in general terms, how your contract and payment schedule are structured, who is on site day to day, what the warranty covers.
State pricing in ranges by project type if you can. A range with the drivers explained does more to earn a call than a hidden number, and it filters out people who were never going to proceed.
Do not fabricate proof to fill the page. If you have no published reviews or case studies yet, describe process and credentials plainly. Invented numbers are the fastest way to lose a reader who checks things for a living.
Speed budget: the excavation gallery cannot be the reason a visitor leaves
Construction photography is the most persuasive thing on the site and the heaviest, and both facts have to be managed at once.
Full resolution site photos, drone video headers and unoptimized gallery grids are the usual causes of a slow pool site. On a phone with a weak signal, the visitor leaves before the hero image resolves.
Serve modern image formats at sensible dimensions, load galleries only as the visitor scrolls to them, and give the first image priority so the top of the page paints quickly. Video headers are almost never worth their cost on mobile.
Keep third party scripts under control. Chat widgets, multiple analytics tags, review carousels and heat mapping tools accumulate quietly and each one adds weight.
Measure on a real connection rather than office wifi, and check again after every gallery update. Speed regressions almost always arrive with new photos.
Questions we actually get
- What has to be on the first screen of a pool company site here?
- Three things: what you build, which jurisdictions you build in, and one clear action. Naming the District, Montgomery County, Arlington, Alexandria and Fairfax County explicitly answers the question most visitors arrive with, and it does it faster than a map image. Renderings can wait until the second screen. Most visitors are on a phone, outdoors, deciding in a few seconds whether you are relevant to their property.
- What should the inquiry form ask that most pool forms do not?
- How equipment reaches the yard. Driveway, side gate with an approximate width, alley access, or none of those. In a market with rowhouse lots and walled yards, access changes the machine, the spoil removal method, the schedule and the price. Also ask for jurisdiction, project type, whether an HOA or historic district may be involved, and rough timing. A photo upload for the yard and gate is worth more than another dropdown.
- Do we need separate pages for each county and city?
- For the jurisdictions you actually serve, yes. Permitting and inspection run differently in the District, in suburban Maryland and in Northern Virginia, and a page that describes your process in that specific place is both better for search and more convincing to a reader. Keep the regulatory language general and point people to the local building department for current requirements rather than publishing specifics as fact.
- Is drone video worth having on the homepage?
- Rarely at the top. It is heavy, it delays the first paint on a phone, and it answers a question most visitors have not asked yet. Drone footage works better deep in a project page, where someone already interested wants to see the finished result. The top of the site should load fast and answer coverage and feasibility. Photographs of the build in progress usually persuade more than aerial footage anyway.
- We have no case studies or reviews yet. What do we put on the site instead?
- Process and credentials, described precisely. Licensing and registration by jurisdiction, how the contract and payment schedule work, who supervises the site, what the warranty covers, and photographs of your own work in progress even if the projects are unnamed. Do not invent testimonials or numbers. In a metro where a large share of buyers verify things professionally, fabricated proof is a bigger risk than an empty section.
