Your visitor has two other tabs open and three names in a notes app
Design for comparison, because that is the situation every visitor is actually in.
Assume you are being read side by side. The homeowner has two other remodelers open, a rough budget they are unsure about, and about ninety seconds of patience on a phone at nine at night.
Comparison rewards specificity. Two of the three sites will show a hero photo, a services list and a form. The one that says what it does, what it does not do, what it typically costs and how the first month works is the one that gets remembered when the partner asks who to call.
Design decisions follow from that. Fewer pages that say more. Real photographs of jobs you did, not stock. Copy written the way your best estimator talks, because the person reading it will meet that estimator soon.
Put a phone number and a form entry in reach on every screen, but do not confuse availability with persuasion. Nobody calls a remodeler because a button followed them down the page.
Give the review step its own page, because that is what stalls the decision
The question that freezes an Austin remodeling project is procedural, and almost nobody answers it on their site.
Interior work is one conversation. The moment a project changes the footprint or touches the outside of the house, local rules on impervious cover and tree protection enter the picture, and those rules are strict enough here to surprise people who remodeled somewhere else in Texas.
Homeowners sense there is a step and do not know what it involves. Left unexplained it becomes a reason to delay. Explained plainly it becomes a reason to hire the firm that clearly does this every week.
Write the page as a sequence, not a regulation. What generally triggers a longer look, who handles it, roughly where it sits in the project, and what they should confirm with the city before design work begins. Skip thresholds and numbers, and say plainly that requirements vary by lot.
Link to it from the form, the pricing page and any project write up where the footprint changed. It is the page that gets forwarded.
The form should ask about the driveway, the trees and whether the footprint changes
Three fields decide whether an inquiry is a phone call or an afternoon.
Standard remodeling forms collect a name, an email and a paragraph of hope. Yours should collect the facts that change your price and your calendar.
Ask what part of the metro the house is in, ask whether the project stays inside the existing walls, and ask about access: the driveway, the street, where a dumpster could sit, whether there are large trees near the work area. In Tarrytown or an older part of East Austin those answers matter as much as the square footage.
Put the easy questions first and the qualifying ones after the visitor is committed. A short first step with the address and the scope gets a higher completion rate, then a second screen can go deeper. If someone abandons the second screen you still have a lead worth calling.
Offer a photo upload. Two pictures of the driveway and one of the room save an entire round of questions, and homeowners are far more willing to send them than most contractors assume.
Renders and walkthrough video are the heaviest things you own, so load them on request
Speed on a remodeling site is a media problem long before it is a code problem.
The gallery is the reason people stay and the reason the site is slow. Sixty full resolution photos, a background video in the hero and a 3D walkthrough embedded on the home page will make a phone in a hill country driveway on a weak signal give up.
Fix it with restraint rather than plugins. Serve modern image formats at the size they actually display, load below the fold images only as someone scrolls, and make video and interactive walkthroughs click to play instead of automatic.
Audit the third party scripts too. Chat widgets, review carousels, heat mapping and three separate analytics tags routinely cost more than the photography does, and nobody ever removes one.
Test on a mid range Android phone on cellular data, not on the office fiber connection. The office test is the reason so many remodeling sites feel fast to their owners and slow to everyone else.
Publish the page about living in the house while the kitchen is gone
The unspoken objection is not price, it is six weeks of disruption, and no competitor is addressing it.
Somewhere in every kitchen decision is a person quietly wondering where the family will eat, what happens to the dog, how much dust gets into the rest of the house and whether the bathroom being out of service means moving out.
Answer all of it. What a temporary kitchen setup looks like, how you handle dust containment, what hours crews work, how many days the water is off, what you do about pets and deliveries.
The page costs you nothing to write and does more selling than another finished island photograph. It also filters. People who read it and proceed have accepted the disruption before they signed, which makes the job smoother for everyone.
Bath projects deserve their own short version, because a single bathroom house is a completely different conversation from a house with a spare.
Build the two pages your estimator can text from the truck
The site is a sales tool for your team, not only a marketing tool for strangers.
After a site visit, your estimator repeats the same two explanations. One is how a project is priced, including allowances and how change orders work. The other is what happens between a signed agreement and demolition day.
Put both on the site as clean, standalone pages, and make the URLs short enough to text. A homeowner who reads your process page an hour after meeting you is a homeowner talking to their partner in your words instead of a competitor's.
Keep them free of sales language. A page that reads like an internal document with the swearing removed builds more trust than one written for search engines.
Watch which pages get opened before a signature. Once you know, put the strongest ones one tap from the home page and stop burying them in a menu.
Questions we actually get
- How many photos should the portfolio hold?
- Fewer than you want, chosen better. A dozen projects shown properly, with a short account of what the house threw at you, outperforms eighty galleries nobody scrolls. Every extra image is a performance decision, and on a phone with a weak signal it is the one that costs you the inquiry.
- Do we need a separate page for every neighborhood we serve?
- Only where you can genuinely say something different. Pages for Round Rock and West Lake Hills are worth writing if the houses, the constraints and the questions differ, which they do. Ten copies of the same page with the name swapped help nobody and can hurt.
- Should we put prices on the site?
- Publish a posture, not a price list. A starting point for a full kitchen, a typical range for a hall bath, and a plain statement of what moves a number. Expect fewer inquiries and better ones. Owners who try it rarely go back.
- Is a chat widget worth adding?
- Sometimes, if a real person answers during working hours. An unattended bot that collects an email is a slower form with a performance cost attached. Measure it against the form for booked consultations, not for conversations started.
- WordPress or a hosted builder?
- Either can be made fast, and both are commonly made slow. What matters more is who maintains it, whether the image handling is disciplined, and whether you can edit a project page without calling anybody. Pick the one your team will actually keep current.
